Changes between Version 36 and Version 37 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-4


Ignore:
Timestamp:
10/17/12 11:21:59 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-4

    v36 v37  
    44This page captures status for the test case EG-EXP-4, which verifies the ability to support basic operations of VMs and data flows between two racks. For overall status see the [wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus ExoGENI Acceptance Test Status] page.
    55
    6 ''Last update: 07/27/12''
     6''Last update: 10/17/12''
    77
    88
     
    4343= Test Plan Steps =
    4444
    45 This test case is modified to use ExoSM to request resources across sites. The nickname:
    46 {{{
    47 exosm=,https://geni.renci.org:11443/orca/xmlrpc
    48 }}}
    49 is used in place of individual site's SM for each experiment in this test case:
    50 {{{
    51 exo-bbn=,https://bbn-hn.exogeni.net:11443/orca/xmlrpc
    52 exo-rci=,https://rci-hn.exogeni.net:11443/orca/xmlrpc
    53 }}}
    54 
    55 Also, for initial test run only VMs used.
     45This test case is modified to use ExoSM to request resources across sites. The omni commands shown in this test use nicknames nick_names for aggregates, which are:
     46{{{
     47eg-sm=,https://geni.renci.org:11443/orca/xmlrpc
     48}}}
     49is used in place of individual site's aggregates:
     50{{{
     51eg-gpo=,https://bbn-hn.exogeni.net:11443/orca/xmlrpc
     52eg-renci=,https://rci-hn.exogeni.net:11443/orca/xmlrpc
     53}}}
     54
    5655
    5756== Step 1. As Experimenter1, Request !ListResources RENCI ExoGENI ==
    5857
    59 Using the credentials lnevers1@bbn.com, request listresources from ExoSM, to determine which resources can be requested for the first experiment:
    60 
    61 {{{
    62 $ omni.py -a exosm listresources -o
     58Using the credentials lnevers@bbn.com, request listresources from ExoSM, to determine which resources can be requested for the first experiment:
     59
     60{{{
     61$ omni.py -a eg-sm listresources -o
    6362}}}
    6463The above command generates a file named ''rspec-geni-renci-org-11443-orca.xml''.
     
    8079
    8180== Step 5. Create a sliver ==
     81
    8282Using the ExoSM and the RSpecs defined above create a sliver with one VM at BBN and one VM at RENCI:
    8383{{{
    84 $ omni.py createsliver -a exosm EG-EXP-4-exp1 EG-EXP-4-exp1.rspec
     84$ omni.py createsliver -a eg-sm EG-EXP-4-exp1 EG-EXP-4-exp1.rspec
    8585}}}
    8686
    8787Verify that sliver status is ready:
    8888{{{
    89 $ omni.py sliverstatus -a exosm EG-EXP-4-exp1 
     89$ omni.py sliverstatus -a eg-sm EG-EXP-4-exp1 
    9090}}}
    9191When sliverstatus reports ''geni_status'' as  ''ready'', you can collect a listresource for the sliver to determined which VMs are allocated to the sliver:
    9292{{{
    93 $  omni.py listresources -a exosm EG-EXP-4-exp1  -o
     93$  omni.py listresources -a eg-sm EG-EXP-4-exp1  -o
    9494$  egrep hostname EG-EXP-4-exp1-rspec-geni-renci-org-11443-orca.xml
    9595   <login authentication="ssh-keys" hostname="152.54.14.34" port="22" username="root"/>     
    9696   <login authentication="ssh-keys" hostname="192.1.242.12" port="22" username="root"/>
    9797}}}
     98
     99Also can determine login information as follows:
     100{{{
     101$ examples/readyToLogin.py -a eg-sm EG-EXP-4-exp1   
     102.....
     103
     104XXXXX
    98105
    99106== Step 6. Log in to each of the systems, and send traffic to the other system, leave traffic running ==
     
    125132== Step 7. As Experimenter2, Request !ListResources from RENCI ExoGENI ==
    126133
    127 Using the credentials lnevers@bbn.com, request listresources from ExoSM, to determine which resources can be requested:
    128 {{{
    129 $ omni.py -a exosm listresources -o
     134Using the credentials lnevers2@bbn.com, request listresources from ExoSM, to determine which resources can be requested:
     135{{{
     136$ omni.py -a eg-sm listresources -o
    130137}}}
    131138
     
    153160Using the ExoSM and the RSpecs defined in step 8 create a sliver:
    154161{{{
    155 $ omni.py createsliver -a exosm EG-EXP-4-exp2 EG-EXP-4-exp2.rspec
     162$ omni.py createsliver -a eg-sm EG-EXP-4-exp2 EG-EXP-4-exp2.rspec
    156163}}}
    157164
    158165Verify that sliver status is ready:
    159166{{{
    160 $ omni.py sliverstatus -a exosm EG-EXP-4-exp2
     167$ omni.py sliverstatus -a eg-sm EG-EXP-4-exp2
    161168}}}
    162169Determined which nodes (VMs and bare metal) are allocated to this sliver:
    163170{{{
    164 $ omni.py listresources -a exosm EG-EXP-4-exp2 -o
     171$ omni.py listresources -a eg-sm EG-EXP-4-exp2 -o
    165172$ egrep hostname EG-EXP-4-exp2-rspec-geni-renci-org-11443-orca.xml
    166173<login authentication="ssh-keys" hostname="192.1.242.13" port="22" username="root"/>     
     
    169176<login authentication="ssh-keys" hostname="152.54.14.37" port="22" username="root"/>   
    170177}}}
     178
     179Also can determine login information as follows:
     180{{{
     181$ examples/readyToLogin.py -a eg-sm EG-EXP-4-exp2   
     182.....
     183
     184XXXX
    171185
    172186== Step 11. Log in to each of the end-point systems, and send traffic to the other end-point system which shares the same VLAN  ==
     
    309323}}}
    310324
    311 == Step 13. Construct and send a non-IP ethernet packet over the data plane interface. ==
    312 
    313 Working on program to send non-IP traffic, to be executed later.
    314 
     325== Step 13. Construct and send a non-IP Ethernet packet over the data plane interface. ==
     326
     327On two ExoGENI hosts in the BBN rack, installed and compiled the the GPO package PingPlus, which is available at the [http://software.geni.net/local-sw/ GPO Software Repository] to generate a non-IP Ethernet packet.
     328
     329Determined interface information on each host.  Host1:
     330{{{
     331root@debian:~/pingPlus-0.2# ifconfig eth1
     332eth1      Link encap:Ethernet  HWaddr 52:54:00:9c:3f:8a 
     333          inet addr:172.16.1.1  Bcast:172.16.255.255  Mask:255.255.0.0
     334          inet6 addr: fe80::5054:ff:fe9c:3f8a/64 Scope:Link
     335          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     336          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
     337          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
     338          collisions:0 txqueuelen:1000
     339          RX bytes:1128 (1.1 KiB)  TX bytes:398 (398.0 B)
     340}}}
     341Host2:
     342{{{
     343eth1      Link encap:Ethernet  HWaddr 52:54:00:0e:e5:a1 
     344          inet addr:172.16.1.2  Bcast:172.16.255.255  Mask:255.255.0.0
     345          inet6 addr: fe80::5054:ff:fe0e:e5a1/64 Scope:Link
     346          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
     347          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
     348          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
     349          collisions:0 txqueuelen:1000
     350          RX bytes:916 (916.0 B)  TX bytes:398 (398.0 B)
     351}}}
     352
     353Started the pingPlusListener on host1:
     354{{{
     355$ sudo ./pingPlusListener 10111
     356}}}
     357
     358Started tcpdump on host1:
     359{{{{
     360$ sudo tcpdump ether host 52:54:00:0e:e5:a1
     361}}}}
     362
     363On host 2 sent 10 packets with !pingPlus to host1:
     364{{{
     365$ sudo ./pingPlus 52:54:00:9c:3f:8a eth0 10111 12
     366}}}
     367
     368Packets were received on host1:
     369{{{
     370
     371}}}
     372
     373TCPdump captured the content of the Ethernet packet:
     374{{{
     375
     376}}}
    315377== Step 14. Review baseline monitoring statistics ==
    316378