wiki:GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

Version 24 (modified by nriga@bbn.com, 7 years ago) (diff)

--

Experimenter Workflow and Example Topologies


Prework

  1. Download and install VirtualBox on your machine, we have tested versions 4.1.8
    • If your computer runs Ubuntu 10.04 which comes with VirtualBox 3.1.6_OSE, please download the latest version of VirtualBox.
  2. Download the VM image
  3. Run VirtualBox and Import Appliance (File->Import Appliance), accept the default settings for the VM.
    • If you are using a FAT32 filesystem you will NOT be able to load the image.
  4. Start the VM and log in
  5. Change the default password, on the task bar on the top, click on the right on the user 'geni', and choose the Change Password button.
  6. Verify that the VM has connectivity. Start Firefox (shortcut on the top bar) and try to load Google. If you can't reach any website, restore VM's Network connection.
    • On the far right on the top bar, there is the network icon (two opposite facing arrows).
    • Click that icon and choose 'Auto eth0'.
    • Try loading the webpage again.

Useful Tips

  • You can copy-paste between the host and the guest VM.
  • In the terminal within the VM, use Ctrl-Shift-C to copy and Ctrl-Shift-V to paste.
  • vim and emacs editors are installed on the VM, so feel free to use them for editing your files.
  • To replace a pattern within the file:
    • If you are using vim, while in command mode, type:
      %s/pattern/replace_text/gc
      
      And press 'y' for the instances of the pattern you want replaced, 'n' otherwise.
    • If you are using emacs, press Alt-x and then type:
      query-replace
      
      and press ENTER. Enter the pattern to be replaced, press ENTER, enter the text you want to replace it with and press ENTER. Press 'y' for the instances of the pattern you want replaced, 'n' otherwise.
  • If you want to have a shared folder between your machine and the VM so that it's easier to transfer files during the tutorial, you have to do this before starting the VM. Follow these instructions
  • If you get an error running Omni, look at the troubleshoot page for help.

Overview of Alice's Experiment

Alice and Bob, two GENI experimenters, have volunteered to help us write these instructions. They are going to reserve separate hosts but they will be sharing the network infrastructure.

No image "alice-bob-setup.png" attached to GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

Alice's information for the tutorial is :

MyPLC AM
<USERNAME> alice The user name for the tutorial's GPO ProtoGENI account
ProtoGENI host pg46.emulab.net (@clemson) Node controlled by Utah's ProtoGENI AM
<PCNAME> pg46 For PG rspec
MyPLC host of-planet1.stanford.edu Node controlled by Stanford's
Backup MyPLC host navis.gpolab.bbn.com Node controlled by GPO's

MyPLC AM, if you run into problems with the first MyPLC host, you can try again

with this host rspec
<SUBNET> 10.42.122.0/24 The subnet to use for Layer3 ping
<SUBNET-OCT> 122 For the OF rspec
<ETH-TYPE> 10122 The ethernet type for Layer2 ping, for the OF
<PORT> 10122 The port that the OpenFlow controller is listening on

And after Alice and Bob completed the tutorial, Alice's scratchpad is :

MyPLC host on the pre-configured subnet to the MyPLC hosts your neighbor's MyPLC host on the pre-configured subnet address of your MyPLC host on your subnet IP address of your neighbor's MyPLC host on the your subnet
SCRATCHPAD Complete this info
My MyPLC host IP(144) 10.42.144. 90 IP address of your
MyPLC login name pgenigpolabbbncom_aliceslice Your login name
Neighbor's MyPLC host IP(144) 10.42.144. 52 IP address of
My MyPLC host IP(your subnet) 10.42 . 122 . 90 The IP
Neighbor's MyPLC host IP(your subnet) 10.42 . 122 . 52

I. Getting Started

1. Update the VM files

Before you start make sure you update the tutorial files.

  • Open a terminal window (there is a shortcut on the top bar).
  • Change the directory to go under the bin directory of the tutorial
       cd Tutorials/ExptWorkflow/bin
    
  • Download the latest version of the update script
       wget http://192.1.249.166:8383/downloadRSpecs.sh
    
  • Make it an executable
       chmod +x downloadRSpecs.sh
    
  • Leave the bin directory and execute the update script
      cd ..; downloadRSpecs.sh
    

2. Firewalls

Some of the compute resources are behind a firewall. To avoid any firewall problems, please first login to "ops.pgeni.gpolab.bbn.com", since we might need to tunnel some traffic through this connection.

To do that :

  • Open a terminal window (there is a shortcut on the top bar).
  • Change to the directory of your team. Substitute ## with the number of your team.
    cd Tutorials/ExptWorkflow/gpousr##
    
  • Connect to ops.pgeni.gpolab.bbn.com
    xterm -e ssh -i ssh/geni_key -F ssh/config gpousr##@ops &
    

3. Flack vs OMNI

1. Configure Omni

The purpose of this first exercise is to setup Omni to use your credentials and keys.

1a. Setup omni

Omni uses as input a configuration file, where you can specify information such as which clearinghouse to use, where your certificate and keys are located, etc. Under the Tutorials/Omni/<username> directory (where <username> is your username on the piece of paper you were given upon entering the room), there is a configuration file, omni_config.

  • Open a terminal (there is a shortcut on the top bar).
  • First lets update the files that are on the VM:
    cd Tutorials/Omni/
    downloadRSpecs.sh 
    

  • The rest of the tutorial assumes that you are under the

Tutorials/Omni/<username> directory :

cd <username>
  • Remove the passphrase from your certificate. For security best

practices you should keep a passphrase on your certificate. To avoid typing the passphrase throughout the tutorial, we will temporarily remove the passphrase. Run

clear_cert.sh <username>

It will prompt you for the passphrase which should be included on the slip

that was given to you.

  • Verify that you have the necessary credential and key files
    ls ssh |grep <username>
    
    For gpousr21 the output looks like :
    geni@geni-vm:~/omni_tutorial$ ls ssh | grep gpousr21
    gpousr21_cert_ct.pem
    gpousr21_cert.pem
    gpousr21_key
    gpousr21_key.pub
    
gpousr21_cert_ct.pem Cleartext certificate for gpousr21, i.e. does not
require any passphrase
gpousr21_cert.pem Encrypted certificate for gpousr21
gpousr21_key The private key that gpousr21 would use to login to the
nodes
gpousr21_key.pub The corresponding public key that gpousr21 will ask to
be loaded to the nodes
  • Look at the omni_config. Open omni_config. For the tutorial you

should use the cleartext certificate, but when running your own experiments, for security best practices always use your encrypted certificate.

For gpousr21 using a cleartext certificate the omni_config file looks

like :

# This file is the omni_config for GEC 12 tutorial 
# Experimental topologies on the GENI Mesoscale network with Omni

# General section of omni config
[omni]
default_cf = pgeni
users = gpousr21

# ---------- Users ----------
[gpousr21]
# Make sure the urn matches the URN of the credential
urn = urn:publicid:IDN+pgeni.gpolab.bbn.com+user+gpousr21

# Public key to be installed in compute resources. For multiple 
# keys use a comma separated file
keys = ~/Tutorials/Omni/gpousr20/ssh/gpousr21_key.pub

# If -a option is not specified the omni command will by run against all 
# the following AMs
aggregates =  http://emulab.net/protogeni/xmlrpc/am,
https://pgeni.gpolab.bbn.com/protogeni/xmlrpc/am,
http://myplc.gpolab.bbn.com:12346/, http://myplc.clemson.edu:12346/,
https://myplc.stanford.edu:12346/,
https://wings-openflow-1.wail.wisc.edu:12346/,
https://of.cs.washington.edu:12346/, https://plc.orbit-lab.org:12346/,
https://myplc.grnoc.iu.edu:12346/, https://myplc.cip.gatech.edu:12346/,
https://foam-tutorial.gpolab.bbn.com:3626/foam/gapi/1

# ---------- Frameworks ----------
[pgeni]
type = pg
ch = https://www.emulab.net:443/protogeni/xmlrpc/ch
sa = https://www.pgeni.gpolab.bbn.com:443/protogeni/xmlrpc/sa

# Use the following two lines if you are using
# a certificate with a passphrase
#cert = ~/Tutorials/Omni/gpousr21/ssh/gpousr21_cert.pem
#key = ~/Tutorials/Omni/gpousr21/ssh/gpousr21_cert.pem

# Use the following two lines if you are using 
# a cleartext cert.
cert = ~/Tutorials/Omni/gpousr21/ssh/gpousr21_cert_ct.pem
key = ~/Tutorials/Omni/gpousr21/ssh/gpousr21_cert_ct.pem

#------AM nicknames----------------
# Instead of typing the whole url of an AM in the -a option you can 
# specify a nickname in this section and use the nickname instead

# Format :
# Nickname=URN, URL
# URN is optional
[aggregate_nicknames]
# ProtoGENI AMs and PlanetLab central
pg-gpo=urn:publicid:IDN+pgeni.gpolab.bbn.com+authority+am,https://pgeni.gpolab.bbn.com/protogeni/xmlrpc/am
pg-utah=,https://www.emulab.net/protogeni/xmlrpc/am
pg-ky=urn:publicid:IDN+uky.emulab.net+authority+am,https://www.uky.emulab.net/protogeni/xmlrpc/am
plc=,https://www.planet-lab.org:12346

# Private myplc installations
pl-gpo=,http://myplc.gpolab.bbn.com:12346/
pl-clemson=,http://myplc.clemson.edu:12346/
pl-stanford=,https://myplc.stanford.edu:12346/
pl-wisconsin=,https://wings-openflow-1.wail.wisc.edu:12346/
pl-washington=,https://of.cs.washington.edu:12346/
pl-rutgers=,https://plc.orbit-lab.org:12346/
pl-indiana=,https://localhost:1234/
pl-gatech=,https://localhost:2346/


# Tutorial OpenFlow AM
of-tut=,https://foam-tutorial.gpolab.bbn.com:3626/foam/gapi/1

# Other OpenFlow AMs
of-gpo=,https://foam.gpolab.bbn.com:3626/foam/gapi/1

Note, the pgeni framework definition includes the Utah Emulab clearinghouse,

which is the only clearinghouse for ProtoGENI aggregates. For additional configuration details please see the [http://trac.gpolab.bbn.com/gcf/wiki/Omni Omni] page for more details. The omni_configuration parameters shown define the following:

Parameter Use
default_cf Default Clearinghouse and credentials used if not specified
on the command line.
users users setting used when reserving slices.
urn The username URN
keys A comma separated list of public ssh key files to be uploaded to
the Clearinghouse and to your resources
type Clearinghouse/credentials type "pg" indicates ProtoGENI, see the
Omni page.
ch ProtoGENI Clearinghouse URL.
sa Slice Authority URL.
cert Location of your SSL encrypted certificate (contains both a
certificate and a key).
key Location of your SSL encrypted key (contains both a certificate and
a key).
<AM nickname> Optional URN, required URL of an Aggregate Manager.
  • Verify that the user URN is correct. Get the URN from your omni config
    grep urn omni_config
    
    Verify that it matches the urn in your cert (disregard the leading URI:)
         openssl x509 -noout -text -in ./ssh/<username>_cert_ct.pem | grep
    'urn:publicid' 
    
    For gpousr21 the output looks like
    geni@geni-vm:~/omni_tutorial$ grep urn omni_config
    urn = urn:publicid:IDN+pgeni.gpolab.bbn.com+user+gpousr21
    geni@geni-vm:~/omni_tutorial$ openssl x509 -noout -text -in
    ./ssh/gpousr21_cert_ct.pem | grep 'urn:publicid' 
                    URI:urn:publicid:IDN+pgeni.gpolab.bbn.com+user+gpousr21,
    email:gpousr21@pgeni.gpolab.bbn.com
    

1b. Test configuration

In order to test that our configuration is correct, you can issue a getversion command. For this step we have used PlanetLab's AM, but you can use any Aggregate Manager(AM).

omni.py getversion -a http://www.planet-lab.org:12346

Or equivalently using the PlanetLab nickname:

omni.py getversion -a plc

gpousr21 decided to use PlanetLab central :

geni@geni-tutorial:~/Tutorials/Omni/gpousr21$ omni.py getversion -a plc
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
INFO:omni:Substituting AM nickname plc with URL
https://www.planet-lab.org:12346, URN unspecified_AM_URN
INFO:omni:AM URN: unspecified_AM_URN (url: https://www.planet-lab.org:12346) has
version:
INFO:omni:{   'ad_rspec_versions': [   {   'extensions': [
'http://www.protogeni.net/resources/rspec/ext/gre-tunnel/1',
                                                   'http://www.protogeni.net/resources/rspec/ext/other-ext/3'],
                                 'namespace':
'http://www.protogeni.net/resources/rspec/2',
                                 'schema':
'http://www.protogeni.net/resources/rspec/2/ad.xsd',
                                 'type': 'ProtoGENI',
                                 'version': '2'},
                             {   'extensions': [],
                                 'namespace': None,
                                 'schema': None,
                                 'type': 'SFA',
                                 'version': '1'}],
    'code_tag': '1.0-35',
    'code_url': 'git://git.onelab.eu/sfa.git@sfa-1.0-35',
    'default_ad_rspec': {   'extensions': [],
                            'namespace': None,
                            'schema': None,
                            'type': 'SFA',
                            'version': '1'},
    'geni_api': 1,
    'hostname': 'www.planet-lab.org',
    'hrn': 'plc',
    'interface': 'aggregate',
    'request_rspec_versions': [   {   'extensions': [
'http://www.protogeni.net/resources/rspec/ext/gre-tunnel/1',
                                                        'http://www.protogeni.net/resources/rspec/ext/other-ext/3'],
                                      'namespace':
'http://www.protogeni.net/resources/rspec/2',
                                      'schema':
'http://www.protogeni.net/resources/rspec/2/request.xsd',
                                      'type': 'ProtoGENI',
                                      'version': '2'},
                                  {   'extensions': [],
                                      'namespace': None,
                                      'schema': None,
                                      'type': 'SFA',
                                      'version': '1'}],
    'sfa': 1,
    'testbed': 'myplc'}
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed getversion:

  Options as run:
    aggregate: plc
    framework: pgeni
    native: True

  Args: getversion

  Result Summary: 
Got version for 1 out of 1 aggregates
 
INFO:omni: ============================================================

2. Make a slice

Before we continue with the rest of the tutorial, we need to create a slice that will contain all our slivers with the different AMs. Since the omni_config specifies using GPO's ProtoGENI as the Slice Authority (SA), your slice will be created in the pgeni.gpolab.bbn.com namespace.

2a. Createslice

For this tutorial we will create a slice named gposlice## (where ## matches your username); you should always choose a slice name that is meaningful to you. To avoid confusion, avoid creating a slice with the same name as your username (i.e. if your username is alice, don't name your slice alice too).

omni.py createslice gposlice##

2b. Renew Slice

Note in the above output that our new slice expires soon. Your slivers can not last longer then your slice, and your resources will go away when the reservation expires. For your experiments be sure to renew your slice for the duration of your experiment. For the tutorial you don't need to extend the lifetime, but if you wanted to, this is what it would look like:

omni.py renewslice gposlice## 20111105T00:00:00

For Alice the output would like:

geni@geni-tutorial:~/Tutorials/Omni/gpousr21$ omni.py renewslice gposlice21
20111105T00:00:00
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
INFO:omni.protogeni:Requesting new slice expiration '2011-11-05T00:00:00'
INFO:omni:Slice gposlice21 now expires at 2011-11-05 00:00:00 UTC
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+gposlice21 expires
on 2011-11-05 00:00:00 UTC
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed renewslice:

  Options as run:
    framework: pgeni
    native: True

  Args: renewslice gposlice21 20111105T00:00:00

  Result Summary: Slice gposlice21 now expires at 2011-11-05 00:00:00 UTC
Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+gposlice21 expires on
2011-11-05 00:00:00 UTC 
INFO:omni: ============================================================

Note: You can not renew the slice expiration time to an earlier time that its current expiration time. Also there is no deleteslice operation. However, you can delete all the slivers in your slice and let the slice expire.

2c. List your Slices

If you want to find out what slices you currently have, you can use an Omni command to listmyslices.

omni.py listmyslices <username>

We've pre-reserved resources in a second slice (ctrl##) in advance of the tutorial for each user.

So for gpousr21 the output would look like :

geni@geni-tutorial:~/Tutorials/Omni/gpousr21$ omni.py listmyslices gpousr21
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
INFO:omni:User 'gpousr21' has slices: 
  urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+gposlice21
  urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+ctrl21
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed listmyslices:

  Options as run:
    framework: pgeni
    native: True

  Args: listmyslices gpousr21

  Result Summary: Found 2 slices for user 'gpousr21'.
 
INFO:omni: ============================================================

3. Make a ProtoGENI sliver

The first resource we are going to add to our slice is a ProtoGENI host.

3a. Createsliver

Under the Tutorials/Omni/<username> directory, there is a directory called rspecs that has all the necessary RSpecs for the tutorial. For this tutorial we are going to use ProtoGENI hosts from GPO's ProtoGENI, as well as Wide Area ProtoGENI hosts from Utah's ProtoGENI cluster.

  • If your ProtoGENI host is in the emulab.net(e.g. pg30.emulab.net),

namespace then it belongs to Utah's cluster and you should use Utah's AM (nickname: pg-utah), and use rspecs/final/protogeni_utah_<username>.rspec

  • If your ProtoGENI host is in the pgeni.gpolab.bbn.com(e.g.

pc1.pgeni.gpolab.bbn.com), namespace then it belongs to GPO's cluster and you should use GPO's AM (nickname: pg-gpo), and use rspecs/final/protogeni_gpo_<username>_v02.rspec

  • Advanced Option: If you are interested in creating your own RSpecs

follow the instructions under [#ReservingProtoGENInodeswithFlack Reserving ProtoGENI nodes with Flack]. Then skip to the Next Step.

gpousr21 was assigned host pc1.pgeni.gpolab.bbn.com so she should use

pg_gpo.rspec:

<!--
This rspec will reserve one wide-area ProtoGENI host

AM: http://www.emulab.net/protogeni/xmlrpc/am
-->
<!--  This file is an rspec for GEC 12 tutorial 
-->

<rspec type="request" 
       xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/request.xsd" 
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
       xmlns="http://www.protogeni.net/resources/rspec/2">

  <node client_id="pc1" 
        component_manager_id="urn:publicid:IDN+pgeni.gpolab.bbn.com+authority+cm" 
        component_id="urn:publicid:IDN+pgeni.gpolab.bbn.com+node+pc1" 
        component_name="pc1" exclusive="true">
    <sliver_type name="raw-pc">
      <disk_image
name="urn:publicid:IDN+pgeni.gpolab.bbn.com+image+emulab-ops//UBUNTU1004-STD"/>
    </sliver_type>
    <services>
      <execute command="cd /home/gpousr21/config_dir;./install.sh" shell="sh "
/>
      <install install_path="/home/gpousr21"
url="http://192.1.249.166:8383/gec12tutorial_ubuntu.tar.gz" file_type="tar.gz"/>
    </services>
  </node>

</rspec>


  • Now you are ready to reserve your host on the appropriate AM. For

easy access and to be able to copy and paste AM URLs that are used in this tutorial, we made a table. If your node is pg46.emulab.net, you are sharing your node with Alice. Alice has already created the sliver for you, so you can run the 'createsliver' command, and its ok if it fails.

omni.py createsliver -a <AM_NICKNAME> gposlice## rspecs/final/<rspec_file>

The output should look like :

geni@geni-vm:~/omni_tutorial$ omni.py createsliver -a
http://www.emulab.net/protogeni/xmlrpc/am aliceslice rspecs/pg_utah.rspec 

FILL IN HERE

3b. Sliverstatus

We asked for an exclusive ProtoGENI host, which means that the node needs to be loaded with the right OS and booted, before our sliver is ready to use. This will take a while. We can check the status of our sliver, using the sliverstatus call.

omni.py sliverstatus -a <AM_NICKNAME> gposlice##

The status will probably be 'not ready', you can continue with the next steps of the tutorial, and we will come back to this node later.

II. Using Physical Topology to Influence Your Experiment

In this exercise we are going to test and see how the underlying network topology can affect the topology of your experiment. For this exercise we have already setup the networking portion of the exercise, so you just need to reserve your compute resources.

1. Make a MyPLC sliver

For this exercise you would need to reserve two MyPlc hosts, each in a different AM. Under the rspecs directory (Tutorials/ExptWorkflow/gpousr##/rspecs/) there are the two MyPLC rspecs that you should use.

  • The name of the rspec is of the form myplc-<site>-<node>.rspec. You should take a look in this table to find out what is the

nickname for the AM, and try to reserve the sliver. Also open your omni_config file and check how the nicknames are defined.

For example gpousr21 was assigned host bain.gpolab.bbn.com and this is what the rspec looks like:

<?xml version="1.0" ?>
<!-- Resources at AM:
  URN: http://myplc.gpolab.bbn.com:12346/
 -->

<rspec type="request" 
       xmlns="http://www.protogeni.net/resources/rspec/2" 
       xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
       xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
       xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/request.xsd">
    <node
component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+bain.gpolab.bbn.com" 
    component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" 
    component_name="bain.gpolab.bbn.com" 
    exclusive="false"
    client_id="ganel">
        <sliver_type name="plab-vnode"/>
    </node>
</rspec>
  • Now you are ready to reserve your host on the appropriate AM. For easy access and to be able to copy and paste AM URLs and nicknames that are used in this tutorial, we made a table.
    omni.py createsliver -a <AM_NICKNAME> gposlice## rspecs/<rspec_file>
    

The output should look like :

geni@geni-tutorial:~/Tutorials/ExptWorkflow/gpousr10$ omni.py createsliver sliceomni10
rspecs/final/myplc-gpolab-ganel.rspec -a pl-gpo
INFO:omni:Loading config file omni_config
INFO:omni:Using control framework pgeni
INFO:omni:Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni10 expires
within 1 day on 2011-11-04 06:57:31 UTC
INFO:omni:Substituting AM nickname pl-gpo with URL
http://myplc.gpolab.bbn.com:12346/, URN unspecified_AM_URN
INFO:omni:Substituting AM nickname pl-gpo with URL
http://myplc.gpolab.bbn.com:12346/, URN unspecified_AM_URN
INFO:omni:Creating sliver(s) from rspec file
rspecs/final/myplc-gpolab-ganel.rspec for slice
urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni10
INFO:omni:Asked http://myplc.gpolab.bbn.com:12346/ to reserve resources. Result:
INFO:omni:<?xml version="1.0" ?>
INFO:omni:<!-- Reserved resources for:
  Slice: sliceomni10
  At AM:
  URL: http://myplc.gpolab.bbn.com:12346/
 -->
INFO:omni:<rspec expires="2011-11-04T01:58:07Z" generated="2011-11-04T00:58:07Z"
type="manifest" xmlns="http://www.protogeni.net/resources/rspec/2"
xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1"
xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/manifest.xsd">  
    <node client_id="ganel.gpolab.bbn.com"
component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+ganel.gpolab.bbn.com"
component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am"
component_name="ganel.gpolab.bbn.com" exclusive="false"
sliver_id="urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni10:291:4:0">    
        <hardware_type name="plab-pc"/>    
        <hardware_type name="pc"/>    
        <location country="us" latitude="42.3897" longitude="-71.1475"/>    
        <sliver_type name="plab-vnode"/>    
    </node>  
</rspec>
INFO:omni: ------------------------------------------------------------
INFO:omni: Completed createsliver:

  Options as run:
    aggregate: pl-gpo
    framework: pgeni
    native: True

  Args: createsliver sliceomni10 rspecs/final/myplc-gpolab-ganel.rspec

  Result Summary: Slice urn:publicid:IDN+pgeni.gpolab.bbn.com+slice+sliceomni10
expires within 1 day(s) on 2011-11-04 06:57:31 UTC
Reserved resources on http://myplc.gpolab.bbn.com:12346/.  
INFO:omni: ============================================================

Follow the same procedure to reserve your second myPLC host.

2. Login to the nodes --- Omni Scripting

After reserving the nodes, you are ready to login. When reserving PlanetLab resources, using a ProtoGENI clearinghouse, the login name that should be used to access the nodes is 'not' the username. The login is listed as part of the sliverstatus call. For common functionality like this that is expected to be used often, omni gives you the capability of writing scripts and including omni as a library. Under the /home/geni/gcf directory there is a folder 'examples' that includes example python scripts that use Omni. One script that is available is the readyToLogin.py script that will return the exact command for logging-in to your nodes.

readyToLogin -a <AM_NICKNAME> sliceomni##

The script will return the actual command that you would need to use for logging in.

For gpousr21 the script would return :

================================================================================
Aggregate [https://myplc.stanford.edu:12346] has a PlanetLab sliver.
of-planet1.stanford.edu's pl_boot_state is: 
  boot
Login using:
  xterm -e ssh -i ./ssh/geni_key pgenigpolabbbncom_gposlice21@bain.gpolab.bbn.com &

================================================================================

Note: If your hosts are in Georgia Tech you would need to use the connection through ops. To do that run

xterm -e ssh -i ssh/geni_key -F ssh/config pgenigpolabbbncom_gposlice##@<hostname> &

For gpousr21 that would be :

xterm -e ssh -i ssh/geni_key -F ssh/config pgenigpolabbbncom_gposlice21@bain &

3. Test Different Topologies

The Mesoscale deployment can offer different topologies for communicating between hosts. We have provisioned two different subnets in the Mesoscale infrastructure, each using a different VLAN (one using 3715 and the other 3716).

The two subnets that have been provisioned are 10.42.144.0/24 on 3715 and 10.42.149.0/24 on 3716.

First of all let's see how we can figure out the IP of the hosts we reserved :

  • List all the interfaces on your host. You will see that there are many interfaces of the form eth1.XXXX
    /sbin/ifconfig
    
    Part of the output would look like :
    eth1.1750:42147 Link encap:Ethernet  HWaddr 00:B0:D0:E1:6F:78  
           inet addr:10.42.147.90  Bcast:10.42.147.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    
    eth1.1750:42148 Link encap:Ethernet  HWaddr 00:B0:D0:E1:6F:78  
           inet addr:10.42.148.90  Bcast:10.42.148.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
    
  • Figure out the last octet of the IP address of your hosts. The way these MyPLC hosts are setup, is that they have multiple subinterfaces, each configured to be part of a different IP subnet. Almost all subnets in the hosts are in the form of 10.42.Y.0/24. You will notice that for all these subnets, your host has the same last octet. In the example above all the subinterfaces of eth1, will have an IP address that will end in 90 (10.42.147.90, 10.42.148.90)
  • Ping over 3715. After logging in to your hosts, ping from host1 to host2. Assuming that host2 has a last octet of YYY you should:
    ping 10.42.144.YYY
    
    Notice the RTT on the packets.
  • Ping over 3716. After logging in to your hosts, ping from one host2 to host1. Assuming that host1 has XXX as it's last octet you should ping
    ping 10.42.149.XXX
    
  • Notice the RTT on the packets and compare it with the above ping.

III. Run a Layer 2 Experiment

The mesoscale GENI resources are connected on Layer 2, which enables Layer 2, i.e. non-IP, experiments. In this exercise we are going to run a layer 2 ping program, where we are going to send raw Ethernet frames of a custom Ethernet type to a server and receive a reply. Currently MyPLC only supports IP experiments, so we will use our ProtoGENI host which we have reserved in the beginning.

  • Check that your sliver is ready
    omni.py sliverstatus -a <AM_NICKNAME> <SLICE_NAME>
    
    If you haven't reserved your own node, then try logging in with your credentials anyway. If you fail please let us know.
  • If your sliver is ready, login to the node (if your host is pg33, pg32 please read the notes):
    ssh -i ./ssh/geni_key <username>@<host>
    

For Alice, that has reserved node pg46.emulab.net:

ssh -i ./ssh/geni_key alice@pg46.emulab.net

NOTE 1: If your node is pg32.emulab.net or pg33.emulab.net, you will need to do some extra work to login to the node. The control interface of these nodes is behind a firewall so you will login to your node through 'ops.pgeni.gpolab.bbn.com'. Run

xterm -e ssh -i ./ssh/geni_key gpousr##@<hostname> &

  • Check to see that the software has been downloaded :
    [alice@protogeni1 ~]$ pingPlus
    
  • Test that the node has been configured correctly. The data interfaces in the ProtoGENI nodes are not configured. The install script that was run when you reserved the node should have configured it for you.
     [alice@protogeni1 ~]$ /sbin/ifconfig
    
    This should list at least three interfaces, the loopback and the control interface and an interface with a name similar to eth#.#### Verify that the data interface is up :
    [alice@protogeni1 ~]$ /sbin/ifconfig
    
    and note the name of the data interface, the data interface is the one that has an IP address in the 10.42.149.0/24 subnet:
    eth1.1750 Link encap:Ethernet  HWaddr 00:1F:29:32:92:4D  
           inet addr:10.42.149.146  Bcast:10.42.149.255  Mask:255.255.255.0
           inet6 addr: fe80::21f:29ff:fe32:924d/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:118 errors:0 dropped:0 overruns:0 frame:0
           TX packets:115 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0 
           RX bytes:5428 (5.3 KiB)  TX bytes:3482 (3.4 KiB)
    
    
    In this case the name is 'eth1.1750'.
  • Run the Layer 2 Ping. We have pre-configured the network to forward along Layer2 packets of Ethernet type listed in your account sheet, so let's try pinging with that. The software that is going to send Layer 2 pings, is called pingPlus.

There is a server running at a host with mac address 00:0c:29:7b:c5:b3. Run the client :

sudo /usr/local/bin/pingPlus 00:0c:29:7b:c5:b3 <interface_name> <EthType> 

For Alice the output would be :

[alice@protogeni1 ~/pingPlus]$ sudo /usr/local/bin/pingPlus 00:0c:29:7b:c5:b3 eth1.1750 10136
RQ:'5019+6242' to 00:0c:29:7b:c5:b3.
RL:5019+6242=11261 from 00:0c:29:7b:c5:b3.

Send a stream of packets, by specifying the number of packets as the last parameter :

sudo ./pingPlus 00:0c:29:7b:c5:b3 <interface_name> <EthType> 10

Note:If the program is stuck waiting for a reply for more than 1 minute, press Ctrl-C to exit and try again.

Congratulations you ran a Layer two experiment across the country!

IV Using OpenFlow in mesoscale

Another way to control the path that your packets are taking is with OpenFlow controllers. In this exercise we are going to use an OpenFlow controller that will deflect packets from one server to another one. We will start first by reserving an OpenFlow sliver.

1. Make an OpenFlow sliver

In the previous step, we have used a pre-configured setup to run our test. We have reserved OpenFlow slivers and we are running some default controllers to route the packets for the above subnets and ethernet types. In this experiment you will reserve an OpenFlow sliver and point it to a controller to route your traffic. For the tutorial purposes we are already running the controller for you. The only thing you will have to do is point your OpenFlow sliver to the running controller.

1a. OpenFlow controller

In a typical OpenFlow experiment, the first step is to figure out where you are going to run your controller. The OpenFlow controller should be able to accept connections from switches. To make this tutorial simpler we have already setup the controllers that are running on a myPlc host at GPO.

In the previous example we have pointed the slivers for subnets 10.42.144.0/24 and 10.42.149.0/24 to an OpenFlow controller that acts like a layer 2 switch. This is why you were able to ping between your hosts.

1b. OpenFlow sliver

Until you have reserved an OpenFlow sliver, traffic will not be forwarded between your hosts on your assigned subnet.

Try pinging between the myPlc hosts from Exercise II but using the subnet that has been assigned to you. For example for Alice that was assigned subnet 133 she would try :

ping 10.42.133.YYY

Since there is no OpenFlow sliver configured yet to forward packets in your subnet, ping should fail.

Ask us to give you a slip of paper with the information about your OpenFlow sliver.

  • Personalize your rspec. There is a sample OpenFlow rspec, under the rspecs folder (rspecs/openflow-tutorial-template.rspec), that you would need to modify in order to reserve the flowspace that has been assigned to you. In the beginning of the file there is a list of tags you would need to replace. More specifically
    • <USERNAME> : Your username
    • <CTRL-PORT> : The port that your controller will be listening on on

navis.gpolab.bbn.com

  • <VLAN> : Which core VLAN you are using for your experiment.
  • <IP_SUBNET_OCT> : The last octet of the subnet that has been assigned

to you

  • <ETH_TYPE> : The ethtype that have been assigned to

you for use in this exercise

  • Create the OpenFlow sliver. The flowspace for the tutorial is managed by a central AM running at GPO :
    omni.py createsliver gposliceXX ./rspecs/openflow-tutorial-template.rspec -a of-tut
    
  • Try pinging again
       ping 10.42.<IP_SUBNET_OCT>.YYY
    

Notice how the first ping packets have higher delay than the subsequent packets. This is because when the first packet goes through, the switches will ask your controller about how to handle the packet. Your controller will install a flow on the switch to handle this and all subsequent packets of the flow. The large delay reflects the roundtrip time between the switch and your controller. Subsequent packets will be forwarded directly by the switch based on the flow that your controller installed and thus their switching will be faster.

1d. Try the Layer 2 ping using your controller

Try running the Layer 2 ping that you did before but using the <ETH_TYPE> that was assigned to you, in your OpenFlow slip.

sudo /usr/local/bin/pingPlus 00:0c:29:7b:c5:b3 <interface_name> <ETH_TYPE>

V. Cleanup resources

Although all your reservations, have expiration times, its always good practice to release the resources, after your experiment is over to make them available to other experimenters.

1. Deletesliver

For each createsliver that you have run, you will need to run deletesliver to release the resources

omni.py deletesliver -a <AM URL> sliceomni## 
omni.py deletesliver -a <AM URL> sliceflack##

For Alice this would look like

# Delete ProtoGENI sliver
omni.py deletesliver -a pg-utan aliceslice

# Delete MyPLC slivers
omni.py deletesliver -a pl-stanford aliceslice
omni.py deletesliver -a pl-gpo aliceslice

#Delete OpenFlow slivers
 omni.py deletesliver -a of-tut aliceslice

You can not delete your slice. Although this will be cleaned up when it expires, it should be an empty container and thus does not hold up any resources.

Congratulations, you have finished the tutorial! Now you are ready to design and run your own experiments. Don't hesitate to email us with any questions you might have.

VI. Fill out the tutorial survey

We love to hear what you think so that we can improve the tutorials in the future. Please complete the online survey and get a GENI tatoo!

VI. Get Your Own Account

The accounts, that you used in the above steps, will be deactivated after the tutorial. If you do not already have an account at GPO's ProtoGENI cluster, you should get your own account so that you can further experiment with GENI.

1a. Get a temporary account

To get a temporary account that will be deactivated on March 31st 2012, apply for an account at this page https://www.pgeni.gpolab.bbn.com/joinproject.php3. For Project name use : GpoTutorial.

1b. Get a permanent account

If you would like to run your own experiments in this infrastructure, please contact us at help@geni.net to get a permanent account.

2. Getting to Know Omni

Now that you have your own account, you should configure Omni to use your own personal info, instead of the pre-made accounts.

2a. Generate and Download your ProtoGENI certificate

  1. Start Firefox within the VM and

https://www.pgeni.gpolab.bbn.com/login.php3 log in to your account.

  1. Select Generate SSL Cert and follow instructions.
  2. Select Download your SSL Cert (it's on the left of the page), and

click on the 'Download it in PEM format' link.

  1. Copy the contents of the page (Ctrl-A, Ctrl-C)
  2. Open a terminal (there is a shortcut on the top bar) under the

omni_tutorial directory there should be an ssh directory

cd omni_tutorial/ssh
  1. Open a file called <username>_cert.pem, paste your cert(Ctrl-Shift-V)

and save.

pico <username>_cert.pem>
Ctrl-Shift-V
Ctrl-X
  1. Remove the passphrase from your certificate. For security best

practices you should keep a passphrase on your certificate. If you want to avoid typing your passphrase throughout the tutorial, you might want to temporarily remove your passphrase

openssl rsa -in ./<username>_cert.pem -out ./<username>_cert_ct.pem 
openssl x509 -in ./<username>_cert.pem >> ./<username>_cert_ct.pem 
chmod 400 ./<username>_cert_ct.pem

If you want a way to type your passphrase only once per session, look

[http://trac.gpolab.bbn.com/gcf/wiki/OmniTroubleShoot#Q.WhydoesOmnipromptformyPEMpassphrasesomanytimesCantOmnipromptonlyonce here].

2b. Generate a pair of private/public keys.

In order to be able to login to the resources you will reserve will need a pair of keys. You can use any set of existing keys you might have, or you can generate a new pair. For security best practices you should have a passphrase on your keys.

ssh-keygen -f <username>_key

Now you can go back to [wiki:GEC11NetworkingExperiments/Tutorial#I.ConfigureOmni (I)] and follow the steps using your own certificate and key.

Creating PlanetLab Request RSpecs from Advertisement RSpecs

  1. Use Omni to download and save the advertised RSpec from the aggregate you

care about.

  1. In general the command is:
    $ omni.py -a <url or nickname of aggregate> -t ProtoGENI 2 -o listresources
    
    For example, to get the request RSpec from the MyPLC at the GPO Lab:
    $ omni.py -a pl-gpo -t ProtoGENI 2 -o listresources
    
    (Version 2 of the AM API renames the ProtoGENI v2 RSpecs as GENI v3 RSpecs

so in the near future the command will become: {{{$ omni.py <url or nickname of aggregate> -t GENI 3 -o listresources}}})

  1. The output of this command is:
    geni@geni-tutorial:~/Tutorials/Omni/gpousr20$ omni.py -a pl-gpo -t ProtoGENI 2
    -o listresources
    INFO:omni:Loading config file omni_config
    INFO:omni:Using control framework pgeni
    INFO:omni:Saving output to a file.
    INFO:omni:Substituting AM nickname pl-gpo with URL
    http://myplc.gpolab.bbn.com:12346/, URN unspecified_AM_URN
    INFO:omni:Listed resources on 1 out of 1 possible aggregates.
    INFO:omni:Writing to 'rspec-myplc-gpolab-bbn-com-12346-.xml'
    INFO:omni: ------------------------------------------------------------
    INFO:omni: Completed listresources:
    
      Options as run:
        aggregate: pl-gpo
        framework: pgeni
        native: True
        output: True
        rspectype: ('ProtoGENI', '2')
    
      Args: listresources
    
      Result Summary: Retrieved resources from 1 aggregates.
    Wrote rspecs from 1 aggregates to 1 files
    Saved listResources RSpec at unspecified_AM_URN to file
    rspec-myplc-gpolab-bbn-com-12346-.xml. 
    . 
    INFO:omni: ============================================================
    
  1. Copy and edit the RSpec file.
    1. Copy the advertisement RSpec file. The new file will become the

request RSpec. In general this would be:

cp <advertisement RSpec filename> <manifest RSpec filename>

The value of <advertisement RSpec filename> appears in the Omni

summary.

In this case we will generate a request for the node "navis":

cp rspec-myplc-gpolab-bbn-com-12346-.xml pl-gpo-navis.rspec
  1. Edit the request Rspec file:
    emacs pl-gpo-navis.rspec &
    
    or
    vi pl-gpo-navis.rspec
    
  2. Edit the <rspec> tag.
    1. In the <rspec> tag, remove the expires and

generated attributes.

  1. In the <rspec> tag, change the type="advertisement"

attribute to type="request".

  1. In the <rspec> tag, change 'ad' to 'request' in the schema

location. That is, change this:

xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/ad.xsd"

To this:

xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/request.xsd"
  1. The <rspec> tag should now look like this (note that the

whitespace has been adjusted for ease of reading):

<rspec type="request" 
       xmlns="http://www.protogeni.net/resources/rspec/2" 
       xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
       xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
       xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/request.xsd"> 
  1. Remove the node tags you do not want to request.
    1. For example to only reserve the node navis.gpolab.bbn.com

remove the following text:

    <node
component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+bain.gpolab.bbn.com" 
          component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" 
          component_name="bain.gpolab.bbn.com" 
          exclusive="false">    
    .... 
   </node>  
    <node
component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+sardis.gpolab.bbn.com" 
          component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" 
          component_name="sardis.gpolab.bbn.com" 
          exclusive="false">
    ....     
   </node>  
    <node
component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+ganel.gpolab.bbn.com" 
          component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" 
          component_name="ganel.gpolab.bbn.com" exclusive="false">
    ....     
   </node>  
    <node
component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+gardil.gpolab.bbn.com" 
          component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am" 
          component_name="gardil.gpolab.bbn.com" exclusive="false">    
    .... 
    </node> 
  1. At this point the entire file should look like this:
    <?xml version="1.0" ?>
    <!-- Resources at AM:
      URN: unspecified_AM_URN
      URL: http://myplc.gpolab.bbn.com:12346/
     -->
    <rspec type="request" 
           xmlns="http://www.protogeni.net/resources/rspec/2" 
           xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
           xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
           xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
    http://www.protogeni.net/resources/rspec/2/request.xsd">  
        <node
    component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+navis.gpolab.bbn.com"
    component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am"
    component_name="navis.gpolab.bbn.com" exclusive="false">    
            <hardware_type name="plab-pc"/>    
            <hardware_type name="pc"/>    
            <available now="true"/>    
            <sliver_type name="plab-vnode">      
                <planetlab:initscript name="gpolab_sirius"/>      
            </sliver_type>    
            <location country="us" latitude="42.3897" longitude="-71.1475"/>    
        </node>  
    </rspec>
    
  1. Edit the <node> tag you are trying to reserve.
    1. Remove all <hardware_type>, <available>,

<location>, and <planetlab:initscript"/> tags which exist from the <node> tag you are trying to reserve.

  1. Add the attribute client_id to the <node> tag you are

trying to reserve. The value is your choice, so here we will use client_id="navis".

  1. The final request RSpec file should look like this:
    <?xml version="1.0" ?>
    <!-- Resources at AM:
      URN: unspecified_AM_URN
      URL: http://myplc.gpolab.bbn.com:12346/
     -->
    <rspec type="request" 
           xmlns="http://www.protogeni.net/resources/rspec/2" 
           xmlns:flack="http://www.protogeni.net/resources/rspec/ext/flack/1" 
           xmlns:planetlab="http://www.planet-lab.org/resources/sfa/ext/planetlab/1" 
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
           xsi:schemaLocation="http://www.protogeni.net/resources/rspec/2
    http://www.protogeni.net/resources/rspec/2/request.xsd">  
        <node
    component_id="urn:publicid:IDN+plc:gpolab:gpolab+node+navis.gpolab.bbn.com"
    component_manager_id="urn:publicid:IDN+plc:gpolab+authority+am"
    component_name="navis.gpolab.bbn.com" exclusive="false" client_id="navis">    
            <sliver_type name="plab-vnode">         
            </sliver_type>    
        </node>  
    </rspec>
    
  1. Save the file.
  1. Run rspeclint to verify that the file is correct. If it works, you should

see no errors returned by the call.

In general, this is:

rspeclint http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/request.xsd <request RSpec filename>

For this example do:

rspeclint http://www.protogeni.net/resources/rspec/2
http://www.protogeni.net/resources/rspec/2/request.xsd pl-gpo-navis.rspec

Reserving ProtoGENI nodes with Flack

These instructions assume you have already created a slice using omni.

  1. Login to GPO's ProtoGENI instance with your tutorial credentials
    1. Click on: https://www.pgeni.gpolab.bbn.com/login.php3
    2. Use your GPO tutorial username and password as listed on the sheet of

paper you were handed on the way into the tutorial.

  1. Login to Flack.
    1. Open a separate browser window or tab.
    2. Click on: http://www.protogeni.net
    3. Scroll down to the large map in the middle of the page.
    4. Click "Login"
    5. In the pull down menu in the upper right hand corner select:

pgeni.gpolab.bbn.com

  1. Click "Download"
  2. Enter the password from the sheet of paper in the box near the bottom.
  3. Click "OK" in the lower left hand corner.
  4. You are now logged in.
  1. Reserve the ProtoGENI node listed on your sheet of paper.
    1. For a ProtoGENI Utah node, do the following:
      1. In the Resources window on the right, select the button for your

slice. A window will open.

  1. Click on "utahemulab.cm".
  2. Find the node listed on the sheet of paper in the list of nodes on

the left.

  1. Drag your node onto the blank canvas on the right.
  2. Click on the blue "i" (Information) icon on the node.
  3. Click "Add Install Service"
  4. In the two boxes, enter the following filling in your username:

"/home/<username>" in "http://192.1.249.166:8383/gec12tutorial_fedora.tar.gz"

  1. Click "Add Execute Service"
  2. In the box, enter the following filling in your username: "cd

/home/<username>/config_dir;./install.sh"

  1. Confirm Rspec version is set to "2" in the pull-down menu in the

upper right hand corner.

  1. Click "Apply" Note : After hitting apply, click on the blue "i" button again,

if you can't see the information you entered, then :

  1. Close this window.
  2. On your VM open the rspec with your favorite editor, and copy the

whole rspec

  1. On your slice canvas on the top, there is an import button. From

the list, choose the "Import from clipboard" option.

  1. The node should appear on your canvas, press the blue "i" button

to verify that it is loaded correctly.

  1. Click "Submit"
  1. For a ProtoGENI GPO node, do the following:
    1. In the Resources window on the right, select the button for your

slice. A window will open.

  1. Click on "bbn-pgeni.cm" (not "bbn-pgeni1.cm", "bbn-pgeni2.cm", or

"bbn-pgeni3.cm").

  1. Find the node listed on the sheet of paper in the list of nodes on

the left.

  1. Drag your node onto the blank canvas on the right.
  2. Click on the blue "i" (Information) icon on the node.
  3. Click "Add Install Service"
  4. In the two boxes, enter the following filling in your username:

"/home/<username>" in "http://192.1.249.166:8383/gec12tutorial_ubuntu.tar.gz"

  1. Click "Add Execute Service"
  2. In the box, enter the following filling in your username: "cd

/users/<username> ;sudo /bin/sh ./config_dir/install.sh"

  1. For the test image, enter:

"urn:publicid:IDN+pgeni.gpolab.bbn.com+image+emulab-ops//UBUNTU1004-STD"

  1. Choose Rspec version "0.2" from the pull-down menu in the upper

right hand corner.

  1. Click "Apply"
  2. Click "Submit"
  1. Confirm the reserved node is visible via omni.
    1. If you reserved a ProtoGENI Utah host, run:
      omni.py -a pg-utah -t ProtoGENI 2 listresources <slicename>
      
    2. If you reserved a ProtoGENI GPO host, run:
      omni.py -a pg-gpo -t ProtoGENI 0.2 listresources <slicename>
      
  2. Note that you can also download the request RSpec from Flack for later use

in a AM API client tool like Omni.

  1. In Flack, click on the magnifying glass in the upper right hand

corner.

  1. The request RSpec will appear in the window.
  2. You can then choose to download the RSpec in a file or copy it to

the clipboard.

AM URL Table

AM Nickname URL
TUTORIAL AM
Clemson's MyPLC pl-clemson http://myplc.clemson.edu:12346
GPO's ProtoGENI pg-gpo http://www.pgeni.gpolab.bbn.com/protogeni/xmlrpc/am
GPO's MyPLC pl-gpo http://myplc.gpolab.bbn.com:12346
GPO's Tutorial OF of-tut https://foam-tutorial.gpolab.bbn.com:3626/foam/gapi/1
Rutgers MyPLC pl-rutgers https://plc.orbit-lab.org:12346/
Stanford's MyPLC pl-stanford https://myplc.stanford.edu:12346
Utah's ProtoGENI pg-utah http://www.emulab.net/protogeni/xmlrpc/am
Washington's MyPLC pl-washington https://of.cs.washington.edu:12346/
Wisconsin's MyPLC pl-wisconsin https://wings-openflow-1.wail.wisc.edu:12346/
OTHER
PlanetLab plchttp://www.planet-lab.org:12346
Kentucky's ProtoGENI pg-ky https://www.uky.emulab.net/protogeni/xmlrpc/am

Attachments (7)

Download all attachments as: .zip