Changes between Version 1 and Version 2 of GEC15Agenda/AdvancedGENITopoOmni/Instructions/L3DeflectExperiment

Timestamp:

10/21/12 14:16:56 (11 years ago)

Author:

nriga@bbn.com

Comment:

--

GEC15Agenda/AdvancedGENITopoOmni/Instructions/L3DeflectExperiment

@@ -1 +1 @@
 [[PageOutline]]
 
-= Example Experiment -Layer 3 Deflect =
+= Example Experiment - Layer 3 Deflect =
 
 In this example experiment, you will configure and run an OpenFlow experiment. In this experiment we are going to deflect service requests from one server to another. We are going to use:
@@ -26 +26 @@
 omni.py createslice <slicename>
 }}}
-  i. '''Create a sliver''' using the rspec from the URL given in your paper slip:
-  {{{
-omni.py createsliver -a pg-utah <slicename> <rspec_url>
+  i. '''Create all the slivers''' using the rspecs from the URL given in your paper slip:
+  {{{
+omni.py createsliver -a <AM_nickname> <slicename> <rspec_url>
 }}}
   i. '''Check the status of your sliver'''
   {{{
-omni.py sliverstatus -a pg-utah <slicename>
+omni.py sliverstatus -a <AM_nickname> <slicename>
 }}}
 
@@ -38 +38 @@
 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. 
-  i. Download your rspec
+  i. Download your rspec you used in the `pg-utah` AM.
   {{{
    cd /tmp
@@ -53 +53 @@
   i. Locate the script and open it. Can you identify the different parts? 
 
-== 3. Configure your routers ==
-Once our sliver is ready we will go ahead and configure our click routers. In this example we have 4 routers, so instead of logging into each one of them and configuring it, we are going to use remote execution and configure them from our VM. 
+== 3. Configure your hosts ==
+Once our slivers iare ready we will go ahead and configure our myPlc hosts. Instead of logging into each host to install the necessary softwarem we are going to use remote execution and install it from our VM.
 
 === 3a. Login and remote execution ===
@@ -60 +60 @@
 
 {{{
-readyToLogin.py -a pg-utah <slicename> > login.out 2>&1
+readyToLogin.py -a <AM_nickname> <slicename> > login.out 2>&1
 }}}
 
@@ -71 +71 @@
 ================================================================================
  
-Host left
-  Port 30778
-  HostName pc403.emulab.net
+Host ganel.gpolab.bbn.com
+  Port 22
+  HostName ganel.gpolab.bbn.com
+  User pgenigpolabbbncom_testdeflect 
+  IdentityFile /home/nriga/.ssh/geni_key 
+
+Host sardis.gpolab.bbn.com
+  Port 22
+  HostName sardis.gpolab.bbn.com
+  User pgenigpolabbbncom_testdeflect 
+  IdentityFile /home/nriga/.ssh/geni_key 
+
+
+...<more output>...
+}}}
+
+Copy all the above information and paste it into your `.ssh/config` file, and do the same for all the AMs,  then you can very easily login into your nodes, just by using the name that is after the `Host` attribute.
+
+Your `~/.ssh/config` file should look like
+{{{
+IdentityFile /home/geni/.ssh/geni_key
+
+Host ganel.gpolab.bbn.com
+  Port 22
+  HostName ganel.gpolab.bbn.com
+  User pgenigpolabbbncom_testdeflect 
+  IdentityFile /home/nriga/.ssh/geni_key 
+ 
+Host sardis.gpolab.bbn.com
+  Port 22
+  HostName sardis.gpolab.bbn.com
+  User pgenigpolabbbncom_testdeflect 
+  IdentityFile /home/nriga/.ssh/geni_key 
+
+Host planetlab5.clemson.edu
+  Port 22
+  HostName planetlab5.clemson.edu
+  User pgenigpolabbbncom_testdeflect 
+  IdentityFile /home/nriga/.ssh/geni_key 
+
+Host ofctrl
+  Port 22
+  HostName pc104.emulab.net
   User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-Host hostB
-  Port 30779
-  HostName pc490.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-Host hostA
-  Port 30778
-  HostName pc545.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-Host bottom
-  Port 30778
-  HostName pc490.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
- 
-Host right
-  Port 30778
-  HostName pc411.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
- 
-Host top
-  Port 30779
-  HostName pc545.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-...<more output>...
-}}}
-
-Copy all the above information and paste it into your `.ssh/config` file, then you can very easily login into your nodes, just by using the nickname (client_id) of the nodes. 
-
-Your `~/.ssh/config` file should look like
-{{{
-IdentityFile /home/geni/.ssh/geni_key
-Host left
-  Port 30778
-  HostName pc403.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
- 
-Host hostB
-  Port 30779
-  HostName pc490.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-Host hostA
-  Port 30778
-  HostName pc545.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-Host bottom
-  Port 30778
-  HostName pc490.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-Host right
-  Port 30778
-  HostName pc411.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
-
-Host top
-  Port 30779
-  HostName pc545.emulab.net
-  User inki 
-  IdentityFile /home/geni/.ssh/geni_key 
+  IdentityFile /home/nriga/.ssh/geni_key
 
 }}}