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

Version 9 (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
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
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.


Test Plan Steps

  1. As Experimenter1, request ListResources from BBN ExoGENI.
  2. Review advertisement RSpec for a list of OS images which can be loaded, and identify available resources.
  3. Verify that the GPO Ubuntu image is available.
  4. Define a request RSpec for two VMs, each with a GPO Ubuntu image.
  5. Create the first slice.
  6. Create a sliver in the first slice, using the RSpec defined in step 4.
  7. Log in to each of the systems, and send traffic to the other system sharing a VLAN.
  8. Using root privileges on one of the VMs load a Kernel module.
  9. As Experimenter2, request ListResources from BBN ExoGENI.
  10. Define a request RSpec for two bare metal nodes, both using the uploaded GPO Ubuntu images.
  11. Create the second slice.
  12. Create a sliver in the second slice, using the RSpec defined in step 10.
  13. Log in to each of the systems, and send traffic to the other system.
  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)
  15. Review system statistics and VM isolation and network isolation on data plane.
  16. Verify that each VM has a distinct MAC address for that interface.
  17. Verify that VMs' MAC addresses are learned on the data plane switch.
  18. Stop traffic and delete slivers.