Changes between Version 9 and Version 10 of GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute


Ignore:
Timestamp:
06/16/16 09:32:53 (8 years ago)
Author:
tteixeir@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIExperimenter/Tutorials/jacks/GettingStarted_PartII_ndn/Procedure/Execute

    v9 v10  
    6969Keep the quotes format unchanged, otherwise the script may not run.
    7070
    71 Run '''copy-scripts.sh''', this will automatically transfer the necessary files to the nodes in our topology.
     71Run {{{copy-scripts.sh}}}, this will automatically transfer the necessary files to the nodes in our topology.
     72     {{{
     73     $ ./copy-scripts.sh
     74     }}}
    7275
    7376Login into the node '''Custodian''' and start the NDN Forwarding Daemon (NFD),
    … …  
    8083=== 5.1 Run the NDN application on the same node ===
    8184
     85You are now ready to start the producer application by registering a namespace.
     86     {{{
     87     $ python producer.py -n /nytimes
     88     }}}
     89You should see a message
     90     {{{
     91     $ Registering prefix /nytimes
     92     }}}
     93Open another terminal on the custodian node and run
     94     {{{
     95     $ python consumer.py -u /nytimes/science
     96     }}}
     97This 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.
     98You are all set. Stop the producer application by {{{Ctrl + C}}} and stop the NFD
     99     {{{
     100     $ nfd-stop
     101     }}}
    82102
     103=== 5.2 Run the NDN application on the entire topology ===
     104For 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.
     105On your computer, run
     106     {{{
     107     $ ./setup-app-remote.sh
     108     }}}
     109You should see NFD being started on the nodes.
     110
     111SSH to the {{{Custodian}}} node and start the {{{producer}}} application
    83112     {{{
    84113     $ python producer.py -n /nytimes
    85114     }}}
    86115
    87 On another terminal, run
     116SSH to the {{{Experimenter}}} node and start the {{{consumer}}} application
    88117     {{{
    89118     $ python consumer.py -u /nytimes/science
    90119     }}}
     120This 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}}}
     121You can check this phenomenon by running the same consumer application in the {{{PI}}} node.
     122SSH to the {{{PI}}} node and start the {{{consumer}}} application
     123     {{{
     124     $ python consumer.py -u /nytimes/science
     125     }}}
     126This time your {{{PI}}} node gets the content back, but nothing happens on the {{{Custodian}}} because the requested content is cached in the {{{University}}} node.
     127You can repeat the experiment with different namespaces
     128     {{{
     129     $ python consumer.py -u /nytimes/math
     130     }}}
    91131
    92 
    93 === 5.2 Run the NDN application on the entire topology ===
    94 
    95 
    96          
    97132=== 5.3 (Optional) Visualize experiment data flows ===
    98133   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].