Version 8 (modified by, 8 years ago) (diff)

Revert to GEC22 version

Understanding the AM API using Content Centric Networking

Image Map

4 Wait for resources to be ready

You can tell whether your nodes are ready by using a script built on omni called readyToLogin.

  1. Please use the command:
    readyToLogin -a AM_NICKNAME SLICENAME 
    where (as before) AM_NICKNAME and SLICENAME are your aggregate 
    manager nickname and your slice name (both found on your worksheet). 
  2. If it reports that the sliver is not yet ready (for example, it might say that the status is "changing"), then wait a minute or two and try again. Once everything is complete, readyToLogin will give output that should look something like this:
    rschr's geni_status is: ready (am_status:ready)  
    User example logs in to rschr using: 
            ssh  -p 32768 -i /Users/example/.ssh/geni_key_portal 
    User example logs in to collar using: 
            ssh -p 32769 -i /Users/example/.ssh/geni_key_portal 

5 Trying out the CCN protocol

The install and execute services requested in our RSpec have already started, and nodes in our experiment should be running the CCN (Content Centric Networking) protocol. Our experiment consists of:

  • A data source (node dsrc1 that holds precipitation data from the US National Oceanic and Atmospheric Administration (NOAA).
  • A researcher node rsrchr that gets data from the data source
  • A collaborator node collab that gets data from the researcher

Key features of the CCN protocol include:

  • Data is accessed by name. In our case we use a program called client to get precipitation data by date range (e.g. precipitation between 1902/01/01 and 1902/01/02).
  • All nodes cache data for a certain period of time. When a node receives a request for data, it checks its local cache. If the data is in it's cache, it returns that data. Otherwise, it forwards it on to its neighbor.

We verify this caching behavior by:

  • Logging into the researcher node and using the client program to get precipitation data for a certain date range. The client displays how long it took to get the data.
  • Retrieving the same data again and noting how we get it much faster since it comes out of a cache.
  • Requesting data for different date ranges and seeing how long it took to retrieve the data.
  • Requesting the data again and note it is retrieved much faster.

If you have time, you can repeat the above steps on the collaborator node. Note: There is an optional part to this exercise that uses the GENI Desktop to visualize traffic on the links in our network. There you can visualize which data requests went all the way to the data source (node dsrc1) and which data requests were fulfilled from a node's cache.

5.1 Run the CCN application

  1. Log into the node rsrchr using the ssh command returned by readyToLogin.
  2. Once you are logged in, ask for precipitation data from 1 Jan 1902 to 2 Jan 1902:
    $ /opt/ccnx-atmos/  
    Start Date in YYYY/MM/DD? 1902/01/01 
    End Date in YYYY/MM/DD? 1902/01/02 
  3. You should see output that looks like:
    Asking for /ndn/, Saving to 
    Time for 1.09802699089=  
    Asking for /ndn/, Saving to 
    Time for 4.65998315811=  
    Joining files.. 
    Concat + write time 0.0735998153687 
    Wrote to 

Note that it took about 1.1 and 4.7 seconds respectively to retrieve data for Jan 1 and Jan 2

  1. Run the client again and request the same data. This time your output should look like:
    Asking for /ndn/, Saving to 
    Time for 0.0423700809479=  
    Asking for /ndn/, Saving to 
    Time for 0.0388598442078=  
    Joining files.. 
    Concat + write time 0.0237510204315 
    Wrote to 

Notice how much faster the data was retrieved this time.

  1. If time permits, log into the collaborator node collab and run queries from there. (Pick dates in January of 1902.) Notice different data retrieval times depending on whether the data came from the datasource, the cache at rsrchr, or the local cache.

5.2 (Optional) Visualize experiment data flows

To use the GENI Desktop to visualize the data flows in your network, continue with the instructions here.


Next: Finish