Version 8 (modified by Vic Thomas, 7 years ago) (diff)


Understanding the AM API using Content Centric Networking

Image Map

1. Design the Experiment

  1. In today's experiment you will use resources at the aggregate assigned to you by the tutorial leader

2. Establish the Environment

2.1 Set up ssh keys and configure Omni

If your account is from the GENI Portal follow the instructions in the Section 2 of this exercise.

If your account is from the iMinds member authority ( follow the instructions at

3. Obtain Resources

3.2. Load the experiment topology

For this exercise, we will edit an existing RSpec file. Start by loading this predefined topology into jFed.

  1. Launch jFed.
  2. Click on the Open URL menu (see figure)
  3. If you have been assigned iMinds aggregate {{{wall1}}}, enter the url If you have {{wall2}}}, enter
Import an RSpec into jFed
Figure 3-1 Import an RSpec into jFed.
  1. You should see a 4-node linear topology. Double-click on each node to make sure you are using the aggregate assigned to you ( iMinds Virtual Wall 1 or iMinds Virtual Wall 2 . If needed, change the aggregate from the drop-down list and click Save. Do this for all nodes
Import an RSpec into jFed
Figure 3-2 Make sure resource is being requested from the correct aggregate.

3.3. Modify the RSpec to automatically install and execute CCNX software

For this experiment, we need to install the following software on the nodes:

  • The CCNX software (ccnx-0.6.1-F15-x64.tar.gz)
  • Scripts that set up the CCNX software (ccnx-setup.tar.gz)
  • Scripts used to pull atmospheric precipitation data using the CCNX protocol (ccnx-atmos-F15-x64.tar.gz)

When the nodes start up, we need the following scripts to be executed:

  • Script that sets up the node (node-setup)
  • Script that sets up the ccnx protocol (ccnx-setup)
  • Script that setup up ccnx protocol routes (add-precip-routes)

We automate the installation and running of the software using install and execute scripts in the RSpec. Let's view the RSpec we uploaded.

  1. Click on the RSpec Editor tab on the jFed tools.
  2. Study this RSpec looking for node specifications. Pay special attention to how the scripts to install and execute the CCN software.
View and edit an RSpec in jFed
Figure 3-3 View and edit an RSpec in jFed.

3.5. Save the request RSpec in a Local File

For this tutorial we will use the Omni tool to create a slice and add resources to the slice.

  1. Save the RSpec to a file by clicking on the Save button.
  2. Remember the name of the RSpec file and its location.
View and edit an RSpec in jFed
Figure 3-4 View and edit an RSpec in jFed.

Open up a terminal window.

Create a slice. To avoid name collisions with others in the class, pick a name that is lab1 followed by the initials of your name. For example:

omni createslice lab1vtt

3.6. Instantiate the new experiment using Omni

For this step, we'll change the approach a bit and switch to a new client tool, the command line Omni client.

From a terminal, please enter the command:


where AM_NICKNAME is the nickname for your assigned aggregate manager and SLICENAME is the name of the slice you created earlier (both of these are given on your worksheet). RSPEC_FILE should be replaced with the filename of the RSpec you saved in step 4.

If all is well, Omni should give you a number of informational messages, such as:

INFO:omni:Loading config file /home/geni/.gcf/omni_config

It should quickly proceed to the point where it makes the request to the remote manager:

INFO:omni:Creating sliver(s) from rspec file /home/geni/Downloads/experiments.rspec for slice ...

This step can sometimes be time-consuming, so please be patient. If it succeeds, within a couple of minutes Omni should report:

INFO:omni: Completed createsliver:

and your resource reservation is complete!


Next: Execute

Attachments (4)

Download all attachments as: .zip