Changes between Version 9 and Version 10 of GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute
- Timestamp:
- 06/16/16 09:32:53 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute
v9 v10 69 69 Keep the quotes format unchanged, otherwise the script may not run. 70 70 71 Run '''copy-scripts.sh''', this will automatically transfer the necessary files to the nodes in our topology. 71 Run {{{copy-scripts.sh}}}, this will automatically transfer the necessary files to the nodes in our topology. 72 {{{ 73 $ ./copy-scripts.sh 74 }}} 72 75 73 76 Login into the node '''Custodian''' and start the NDN Forwarding Daemon (NFD), … … 80 83 === 5.1 Run the NDN application on the same node === 81 84 85 You are now ready to start the producer application by registering a namespace. 86 {{{ 87 $ python producer.py -n /nytimes 88 }}} 89 You should see a message 90 {{{ 91 $ Registering prefix /nytimes 92 }}} 93 Open another terminal on the custodian node and run 94 {{{ 95 $ python consumer.py -u /nytimes/science 96 }}} 97 This will start the consumer application that will send Interest request packets to the producer. Take a moment to look at the entries in the NFD. 98 You are all set. Stop the producer application by {{{Ctrl + C}}} and stop the NFD 99 {{{ 100 $ nfd-stop 101 }}} 82 102 103 === 5.2 Run the NDN application on the entire topology === 104 For this section, we are going to start the NFD in all nodes and register the namespace. We automated these tasks for some nodes. You will do it in one node. 105 On your computer, run 106 {{{ 107 $ ./setup-app-remote.sh 108 }}} 109 You should see NFD being started on the nodes. 110 111 SSH to the {{{Custodian}}} node and start the {{{producer}}} application 83 112 {{{ 84 113 $ python producer.py -n /nytimes 85 114 }}} 86 115 87 On another terminal, run116 SSH to the {{{Experimenter}}} node and start the {{{consumer}}} application 88 117 {{{ 89 118 $ python consumer.py -u /nytimes/science 90 119 }}} 120 This time the {{{Interest}}} request travelled the entire topology, leaving breadcrumbs. The {{{Data}}} packet follows the breadcrumbs back to the {{{consumer}}}, leaving cached versions of the content. This is call in-network caching and it is one of the most important features in {{{Information Centric Networking}}} 121 You can check this phenomenon by running the same consumer application in the {{{PI}}} node. 122 SSH to the {{{PI}}} node and start the {{{consumer}}} application 123 {{{ 124 $ python consumer.py -u /nytimes/science 125 }}} 126 This time your {{{PI}}} node gets the content back, but nothing happens on the {{{Custodian}}} because the requested content is cached in the {{{University}}} node. 127 You can repeat the experiment with different namespaces 128 {{{ 129 $ python consumer.py -u /nytimes/math 130 }}} 91 131 92 93 === 5.2 Run the NDN application on the entire topology ===94 95 96 97 132 === 5.3 (Optional) Visualize experiment data flows === 98 133 To use the GENI Desktop to visualize the data flows in your network, continue with the instructions [wiki:GENIExperimenter/Tutorials/GettingStarted_PartII_ccn/Procedure/Execute/GEMINI here].