Changes between Version 1 and Version 2 of GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial


Ignore:
Timestamp:
03/12/12 19:28:26 (7 years ago)
Author:
nriga@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC13Agenda/ExperimenterWorkflowTutorial/Tutorial

    v1 v2  
    569569are the two MyPLC rspecs that you should use.
    570570
    571    * The name of the rspec is of the form myplc-<site>-<node>.rspec. You should
    572 take a look in this [#AMURLTable table] to find out what is the
    573 nickname for the AM, and try to reserve the sliver. Also open your omni_config file
    574 and check how the nicknames are defined.
     571   * The name of the rspec is of the form myplc-<site>-<node>.rspec. You should take a look in this [#AMURLTable table] to find out what is the
     572nickname for the AM, and try to reserve the sliver. Also open your omni_config file and check how the nicknames are defined.
    575573
    576574   * '''Advanced Option''': If you are interested in creating your own RSpecs
    577 follow the instructions under
    578 [##CreatingPlanetLabRequestRSpecsfromAdvertisementRSpecs Creating PL Request
    579 RSpecs from Ad. RSpecs]. Then skip to the [#a2.Logintothenodes---OmniScripting
     575follow the instructions under [#CreatingPlanetLabRequestRSpecsfromAdvertisementRSpecs Creating PL Request RSpecs from Ad. RSpecs]. Then skip to the [#a2.Logintothenodes---OmniScripting
    580576Next Step].
    581577
     
    606602   }}}
    607603
    608    * Now you are ready to reserve your host on the '''appropriate''' AM. For
    609 easy access and to be able to copy and paste AM URLs and nicknames that are used
    610 in this tutorial, we made a [#AMURLTable table].
     604   * 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 [#AMURLTable table].
    611605  {{{
    612606omni.py createsliver -a <AM_NICKNAME> gposlice## rspecs/<rspec_file>
     
    675669== 2. Login to the nodes --- Omni Scripting ==
    676670
    677 After reserving the nodes, we are ready to login. When reserving !PlanetLab
     671After reserving the nodes, you are ready to login. When reserving !PlanetLab
    678672resources, using a different clearinghouse, the login name that should be used
    679673to access the nodes is ''''not'''' the username. The username is listed as part
     
    686680your nodes.
    687681{{{
    688 readyToLogin -a <AM_NICKNAME> gposlice##
     682readyToLogin -a <AM_NICKNAME> sliceomni##
    689683}}}
    690684
     
    700694  boot
    701695Login using:
    702   xterm -e ssh -i ssh/gpousr21_key
     696  xterm -e ssh -i ./ssh/geni_key
    703697pgenigpolabbbncom_gposlice21@bain.gpolab.bbn.com &
    704698
     
    708702For user gpousr21 this would be :
    709703{{{
    710 xterm -e ssh -i ssh/gpousr##_key -F ssh/config gpousr##@ops &
     704xterm -e ssh -i ./ssh/geni_key -F ssh/config gpousr##@ops &
    711705}}}
    712706
    713707'''Note''': If your hosts are in Georgia Tech you would need to use the
    714 connection through ops.
     708connection through ops.
     709 
    715710To do that run
    716711{{{
    717 xterm -e ssh -i ssh/gpousr##_key -F ssh/config <hostname> &
     712xterm -e ssh -i ssh/geni_key -F ssh/config <hostname> &
    718713}}}
    719714
    720715For gpousr21 that would be :
    721716{{{
    722 xterm -e ssh -i ssh/gpousr21_key -F ssh/config bain &
     717xterm -e ssh -i ssh/geni_key -F ssh/config bain &
    723718}}}
    724719
     
    734729First of all let's see how we can figure out the IP of the hosts we reserved :
    735730
    736    * List all the interfaces in your host. You will see that there many
     731   * List all the interfaces in your host. You will see that there are many
    737732interfaces of the form eth1.XXXX
    738733   {{{
     
    762757
    763758   {{{
    764 ping 10.42.131.YYY
     759ping 10.42.144.YYY
    765760   }}}
    766761   Notice the RTT on the packets.
     
    770765
    771766   {{{
    772 ping 10.42.132.XXX
     767ping 10.42.149.XXX
    773768   }}}
    774769   Notice the RTT on the packets and compare it with the above ping.