Version 4 (modified by, 10 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
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
Status Legend Description
Color(green,Pass)? Completed and met criteria
Color( #5adefa, #100000 , pass)? Completed and met most criteria. Exceptions documented
Color(red,Fail)? Completed and failed to meet criteria
Color(orange,Blocked)? Blocked by ticketed issue
In progress Currently under test

Test Plan Steps

  1. As Experimenter1, Request ListResources RENCI ExoGENI.
  2. Review ListResources output.
  3. 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.
  4. Create the first slice.
  5. Create a sliver at the RENCI ExoGENI aggregate using the RSpecs defined above.
  6. Log in to each of the systems, and send traffic to the other system, leave traffic running.
  7. As Experimenter2, Request ListResources from RENCI ExoGENI.
  8. 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.
  9. Create a second slice.
  10. In the second slice, create a sliver at the RENCI ExoGENI aggregate using the RSpecs defined above.
  11. Log in to each of the end-point systems, and send traffic to the other end-point system which shares the same VLAN.
  12. Verify traffic handling per experiment, VM isolation, and MAC address assignment.
  13. Construct and send a non-IP ethernet packet over the data plane interface.
  14. Review baseline monitoring statistics.
  15. Run test for at least 4 hours.
  16. Review baseline monitoring statistics.
  17. Stop traffic and delete slivers.