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

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

--

EG-EXP-2: ExoGENI Single Site Acceptance Test

This page captures status for the test case EG-EXP-2, which verifies basic operations of VMs and data flows within one rack. 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)?
Step 2 Color(#63B8FF,In Progress)? only one supported image available, no image playpen
Step 3 Feature not available
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10 only one node at BBN, no image playpen
Step 11
Step 12
Step 13
Step 14
Step 15
Step 16
Step 17
Step 18


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.


Prerequisites

Status for test prerequisites:

Prereq: Two GPO Ubuntu images have been tested in the ExoGENI image playpen environment and have been uploaded to the RENCI VM image repository using available ExoGENI documentation. One Ubuntu image is for the VM and one Ubuntu image is for the bare metal node in this test.

Status: Image Playpen should be available when x3650M4 nodes become available the week of 05/28.

Prereq: Traffic generation tools may be part of image or may be installed at experiment runtime.

Status: Done: Only using ping with mixed sizes and rates for now.

Prereq: Administrative accounts have been created for GPO staff on the BBN ExoGENI rack.

Status: Done

Prereq: GENI Experimenter1 and Experimenter2 accounts exist.

Status: Done. Two account already exist, lnevers@bbn.com and lnevers1@bbn.com, these will be used in all acceptance tests.

Prereq: Baseline Monitoring is in place for the entire BBN site, to ensure that any problems are quickly identified.

Status: Testing with current version of monitoring, to be re-tested when monitoring is finalized.

Test Plan Steps

Notes:

  1. Bare Metal nodes are available via EXoSM only.
  2. Bare Metal node only support one version at this time.
  3. 1 Bare metal at BBN and 1 at RENCI.

Step 1. As Experimenter1, request ListResources from BBN ExoGENI

User account lnevers is used for this tests, and the listresources is requested as follows from the BBN ExoGENI rack Head Node:

$ ./src/omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc listresources --available -o

Step 2. Review advertisement RSpec for a list of OS images which can be loaded, and identify available resources

Feature not available in ExoGENI listresources. Available image information is collected out-of-band as far as the AM API. Custom Images will be tested that not in the list resources, verification will be based on custom image successful installation and usage in the ExoGENI rack.

Step 3. Verify that the GPO Ubuntu image is available

Same as step 2.

Step 4. Define a request RSpec for two VMs, each with a GPO Ubuntu image

Create the Rspec and place copy here. Add link for location to store RSpec.

Step 5. Create the first slice

$ ./src/omni.py createslice experiment1

Step 6. Create a sliver in the first slice, using the RSpec defined in step 4.

$ ./src/omni.py  -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc createsliver experiment1 exorspec/exo-2vm-1lan.rspec 

Verify that the sliver creation was completed, by looking for "'geni_status': 'ready'" in the output of the sliverstatus command:

$ ./src/omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc sliverstatus experiment1        

Once sliver is ready, determine which hosts were assigned:

$ ./src/omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc listresources experiment1 

Step 7. Log in to each of the systems, and send traffic to the other system sharing a VLAN

$ ssh root@192.1.242.11
root@debian:~# ifconfig
root@debian:~# ping 172.16.1.1 -c 4

Step 8. Using root privileges on one of the VMs load a Kernel module.

Once logged in, show current modules loaded:

root@debian:~# lsmod|

Install module XXX

which module??

Check the list modules to verify that the module is installed:

root@debian:~# lsmod|egrep XXX

Step 9. As Experimenter2, request ListResources from BBN ExoGENI.

User account lnevers1 will be used for this tests, and the listresources is requested as follows from the BBN ExoGENI rack Head Node:

$ ./src/omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc listresources --available -o

Step 10. Define a request RSpec for two bare metal nodes, both using the uploaded GPO Ubuntu images.

Create the Rspec and place copy here. Add link for location to store RSpec.

Step 11. Create the second slice.

$ ./src/omni.py createslice experiment2

Step 12. Create a sliver in the second slice, using the RSpec defined in step 10.

$ ./src/omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc createsliver experiment2 exo-2vm-1lan.rspec 

Step 13. Log in to each of the systems, and send traffic to the other system.

Step 14. Verify that experimenters 1 and 2 cannot use the control plane to access each other's resources

(e.g. via unauthenticated SSH, shared writable filesystem mount)

Step 15. Review system statistics and VM isolation and network isolation on data plane.

Step 16. Verify that each VM has a distinct MAC address for that interface.

Step 17. Verify that VMs' MAC addresses are learned on the data plane switch.

Step 18. Stop traffic and delete slivers.