Version 19 (modified by, 10 years ago) (diff)


Click Example

Hello GENI index Hello GENI index Hello GENI index

1. Obtain Resources

In this step, we are going to setup the experiment. In this tutorial we assume that you are sufficiently comfortable with omni to know when your slice is ready using readyToLogin.

Note These instructions assume you are using at least omni version 2.6, but it is possible to do the exercise using the tool of your choice.
  1. Create a slice, where <slicename> is click<initials>:
    omni createslice <slicename>
  2. Create a sliver :
    omni createsliver -a AGG_NICKNAME <slicename> <rspec_url>
  1. Check the status of your sliver
    readyToLogin <slicename> --useSliceAggregates

Install scripts

While you wait for your sliver to become ready, we will see how we can automate the installation of our experiment with install scripts. In this experiment we are going to use software routers in order to write our own forwarding scheme. This means that in any experiment we are going to run we want the basic installation of the software router to always be present. The configuration might change from run to run, but the software should always be installed. The software to be installed, and the scripts to be executed at boot time, are defined in the rspecs. Follow these steps to locate your install script and identify the different parts.

  1. Download the RSpec from On a UNIX-like system you can do:
       cd /tmp
       wget <rspec_url>
  2. Open your rspec and look for the install tag and copy the value of the URL attribute.
  3. Look for the execute tag and write down the name of the script to be executed.
  4. Download and untar the software. On a UNIX-like system you can do:
    cd /tmp
    mkdir click
    cd click
    wget <software_url>
    tar xvfz <software_name>
  5. Look in your rspec and locate the execute tag. Note what script is being executed at boot time.
  6. Locate the script and open it. Can you identify the different parts?

Next: Execute