wiki:GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-4

Version 22 (modified by lnevers@bbn.com, 7 years ago) (diff)

--

EG-EXP-4: ExoGENI Multi-site Acceptance Test

This 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 ExoGENI Acceptance Test Status page.

Test Status

This section captures the status for each step in the acceptance test plan.

Step State Date completed Ticket Comments
Step 1 Color(yellow,Complete)? exoticket:46 Run with ExoSM
Step 2 Color(yellow,Complete)?
Step 3 Color(yellow,Complete)?
Step 4 Color(yellow,Complete)?
Step 5 Color(yellow,Complete)?
Step 6 Color(yellow,Complete)?
Step 7 Color(yellow,Complete)? Run with ExoSM
Step 8 Color(yellow,Complete)?
Step 9 Color(yellow,Complete)?
Step 10 Color(orange,Blocked)? exoticket:47
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17


State Legend Description
Color(green,Pass)? Test completed and met all criteria
Color(#98FB98,Pass: most criteria)? Test completed and met most criteria. Exceptions documented
Color(red,Fail)? Test completed and failed to meet criteria.
Color(yellow,Complete)? Test completed but will require re-execution due to expected changes
Color(orange,Blocked)? Blocked by ticketed issue(s).
Color(#63B8FF,In Progress)? Currently under test.


Test Plan Steps

This test case is modified to use ExoSM to request resources across sites. The nickname:

exosm=,https://geni.renci.org:11443/orca/xmlrpc

is used in place of individual site's SM for each experiment in this test case:

exo-bbn=,https://bbn-hn.exogeni.net:11443/orca/xmlrpc
exo-rci=,https://rci-hn.exogeni.net:11443/orca/xmlrpc

Also, for initial test run only VMs used.

Step 1. As Experimenter1, Request ListResources RENCI ExoGENI

Using the credentials lnevers@bbn.com, request listresources from ExoSM, to determine which resources can be requested. As experimenter lnevers1@bbn.com executed the steps for the first experiment:

$ ./src/omni.py -a exosm listresources -o

Step 2. Review ListResources output

Reviewed content of output file named rspec-geni-renci-org-11443-orca.xml and determined site information for VM request.

Step 3. Define a request RSpec

Define a request RSpec for a VM at BBN ExoGENI, a VM at RENCI ExoGENI and an unbound exclusive non-OpenFlow VLAN to connect the 2 endpoints. RSpec created is [EG-EXP-4-exp1.rspec inster_link_here]

Step 4. Create the first slice.

Using the following command create a slice for the first experiment:

 $ ./src/omni.py createslice EG-EXP-4-exp1

Step 5. Create a sliver

Using the ExoSM and the RSpecs defined above create a sliver:

$ ./src/omni.py createsliver -a exosm EG-EXP-4-exp1 EG-EXP-4-exp1.rspec

Verify that sliver status is ready:

$ ./src/omni.py sliverstatus -a exosm EG-EXP-4-exp1  

Determined which VMs are allocated to this sliver:

$ $ ./src/omni.py listresources -a exosm EG-EXP-4-exp1  -o
$ $ egrep hostname EG-EXP-4-exp1-rspec-geni-renci-org-11443-orca.xml 
                  <login authentication="ssh-keys" hostname="192.1.242.13" port="22" username="root"/>      
                  <login authentication="ssh-keys" hostname="152.54.14.20" port="22" username="root"/> 

Step 6. Log in to each of the systems, and send traffic to the other system, leave traffic running

Connect to the RENCI VM and send traffic to the BBN VM:

$ ssh root@152.54.14.20

Last login: Tue Jul 26 13:12:00 2011 from 10.0.2.1
root@debian:~# ifconfig|egrep 172.16
          inet addr:172.16.7.2  Bcast:172.16.7.255  Mask:255.255.255.0
root@debian:~# ping 172.16.7.1

Connect to the BBN VM and send traffic to the RENCI VM:

Last login: Tue Jul 26 13:12:00 2011 from 10.0.2.1
root@debian:~# ifconfig |egrep 172.16
          inet addr:172.16.7.1  Bcast:172.16.7.255  Mask:255.255.255.0
root@debian:~# ping 172.16.7.2

Step 7. As Experimenter2, Request ListResources from RENCI ExoGENI

Using the credentials lnevers@bbn.com, request listresources from ExoSM, to determine which resources can be requested:

$ ./src/omni.py -a exosm listresources -o

Step 8. Define a request RSpec

Full step description: "Define a request RSpec for one VM and one bare metal node each with two interfaces in the BBN ExoGENI rack, two VMs at RENCI, and two VLANs to connect the BBN ExoGENI to the RENCI ExoGENI."

RSpec created is [EG-EXP-4-exp2.rspec inster_link_here]

Step 9. Create a second slice

Using the following command create a slice for the second experiment:

$ ./src/omni.py createslice EG-EXP-4-exp2

Step 10. In the second slice, create a sliver at the RENCI ExoGENI aggregate using the RSpecs defined above

Using the ExoSM and the RSpecs defined above create a sliver:

$ ./src/omni.py createsliver -a exosm EG-EXP-4-exp2 ./exorspec/EG-EXP-4-exp2.rspec

Verify that sliver status is ready:

$ ./src/omni.py sliverstatus -a exosm EG-EXP-4-exp2 -0  

Determined which VMs are allocated to this sliver:

$ ./src/omni.py listresources -a exosm EG-EXP-4-exp2 -o
$ egrep ssh EG-EXP-4-exp2-rspec-geni-renci-org-11443-orca.xml 
                  <login authentication="ssh-keys" hostname="192.1.242.110" port="22" username="root"/>      
                  <login authentication="ssh-keys" hostname="192.1.242.12" port="22" username="root"/>      
                  <login authentication="ssh-keys" hostname="152.54.14.18" port="22" username="root"/>      
                  <login authentication="ssh-keys" hostname="152.54.14.19" port="22" username="root"/>      
 
     

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

The following were assigned:

<login authentication="ssh-keys" hostname="192.1.242.12" port="22" username="root"/>      
<login authentication="ssh-keys" hostname="192.1.242.11" port="22" username="root"/>      
<login authentication="ssh-keys" hostname="192.1.242.13" port="22" username="root"/>      
<login authentication="ssh-keys" hostname="192.1.242.7" port="22" username="root"/>      

Step 12. Verify traffic handling per experiment, VM isolation, and MAC address assignment

Logged into each host and ping remotes:

Step 13. Construct and send a non-IP ethernet packet over the data plane interface.

Step 14. Review baseline monitoring statistics

Step 15. Run test for at least 4 hours

Step 16. Review baseline monitoring statistics

Step 17. Stop traffic and delete slivers