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

Version 6 (modified by lnevers@bbn.com, 8 years ago) (diff)

--

EG-EXP-6: ExoGENI and Meso-scale Multi-site OpenFlow Acceptance Test

This page captures status for the test case EG-EXP-6, which verifies ExoGENI rack interoperability with other meso-scale GENI sites. 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
Step 19
Step 20
Step 21
Step 22
Step 23
Step 24
Step 25
Step 26
Step 27
Step 28
Step 29
Step 30
Step 31
Step 32
Step 33
Step 34
Step 35
Step 36
Step 37

State Legend Description
Color(green,Pass)? Test completed and met all criteria
Color( #98FB98, #100000 , Pass)? Test completed and met most criteria. Exceptions documented
Color( #F0FFF0, #100000 , Complete)? Test completed but requiring re-execution due to expected changes
Color( #B0E0E6, #100000 , Complete)? Test completed with workaround for ticketed issue(s)
Color(#CAE1FF,Workaround)? Test in progress with workaround for ticketed issue(s).
Color(#63B8FF,In Progress)? Currently under test.
Color(red,Fail)? Test completed and failed to meet criteria.
Color(orange,Blocked)? Blocked by ticketed issue(s).

Test Plan Steps

  1. As Experimenter1, request ListResources from BBN ExoGENI, RENCI ExoGENI, and FOAM at NLR Site. (The NLR "site" is actually the FOAM for the NLR core meso-scale OpenFlow network, not an actual physical site.)
  2. Review ListResources output from all AMs.
  3. Define a request RSpec for a VM at the BBN ExoGENI.
  4. Define a request RSpec for a VM at the RENCI ExoGENI.
  5. Define request RSpecs for OpenFlow resources from BBN FOAM to access GENI OpenFlow core resources.
  6. Define request RSpecs for OpenFlow core resources at NLR FOAM.
  7. Create the first slice.
  8. Create a sliver in the first slice at each AM, using the RSpecs defined above.
  9. Log in to each of the systems, verify IP address assignment. Send traffic to the other system, leave traffic running.
  10. As Experimenter2, define a request RSpec for one VM and one bare metal node at BBN ExoGENI.
  11. Define a request RSpec for two VMs on the same worker node at RENCI ExoGENI.
  12. Define request RSpecs for OpenFlow resources from GPO FOAM to access GENI OpenFlow core resources.
  13. Define request RSpecs for OpenFlow core resources at NLR FOAM.
  14. Create a second slice.
  15. Create a sliver in the second slice at each AM, using the RSpecs defined above.
  16. Log in to each of the systems in the slice, and send traffic to each other systems; leave traffic running
  17. As Experimenter3, request ListResources from BBN ExoGENI, GPO FOAM, and FOAM at Meso-scale Site (NLR Site GPO and Internet2 site TBD).
  18. Review ListResources output from all AMs.
  19. Define a request RSpec for a VM at the BBN ExoGENI.
  20. Define a request RSpec for a compute resource at the GPO Meso-scale site.
  21. Define a request RSpec for a compute resource at a Meso-scale site.
  22. Define request RSpecs for OpenFlow resources to allow connection from OF BBN ExoGENI to Meso-scale OF sites(GPO and second site TBD) (NLR and I2).
  23. Create a third slice.
  24. Create a sliver that connects the Internet2 Meso-scale OpenFlow site to the BBN ExoGENI Site, and the GPO Meso-scale site.
  25. Log in to each of the compute resources in the slice, configure data plane network interfaces on any non-ExoGENI resources as necessary, and send traffic to each other systems; leave traffic running.
  26. Verify that all three experiments continue to run without impacting each other's traffic, and that data is exchanged over the path along which data is supposed to flow.
  27. Review baseline, GMOC, and monitoring statistics.
  28. As site administrator, identify all controllers that the BBN ExoGENI OpenFlow switch is connected to
  29. As Experimenter3, verify that traffic only flows on the network resources assigned to slivers as specified by the controller.
  30. Verify that no default controller, switch fail-open behavior, or other resource other than experimenters' controllers, can control how traffic flows on network resources assigned to experimenters' slivers.
  31. Set the hard and soft timeout of flowtable entries
  32. Get switch statistics and flowtable entries for slivers from the OpenFlow switch.
  33. Get layer 2 topology information about slivers in each slice.
  34. Install flows that match on layer 2 fields and/or layer 3 fields.
  35. Run test for at least 4 hours.
  36. Review monitoring statistics and checks as above.
  37. Stop traffic and delete slivers.