wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-EXP-6

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

--

IG-EXP-6: InstaGENI and Meso-scale Multi-site OpenFlow Acceptance Test

This page captures status for the test case IG-EXP-6, which verifies InstaGENI rack interoperability with other meso-scale GENI sites. For overall status see the InstaGENI 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(orange,Blocked)? BBN rack is not available yet
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
Step 38
Step 39
Step 40
Step 41


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 InstaGENI, Utah InstaGENI, and from FOAM at I2 and NLR Site.
  2. Review ListResources output from all AMs.
  3. Define a request RSpec for a VM at the BBN InstaGENI.
  4. Define a request RSpec for a VM at the Utah InstaGENI.
  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 I2 FOAM
  7. Define request RSpecs for OpenFlow core resources at NLR FOAM.
  8. Create the first slice.
  9. Create a sliver in the first slice at each AM, using the RSpecs defined above.
  10. Log in to each of the systems, verify IP address assignment. Send traffic to the other system, leave traffic running.
  11. As Experimenter2, define a request RSpec for one VM and one physical node at BBN InstaGENI.
  12. Define a request RSpec for two VMs on the same experiment node at Utah InstaGENI.
  13. Define request RSpecs for OpenFlow resources from BBN FOAM to access GENI OpenFlow core resources.
  14. Define request RSpecs for OpenFlow core resources at I2 FOAM.
  15. Define request RSpecs for OpenFlow core resources at NLR FOAM.
  16. Create a second slice.
  17. Create a sliver in the second slice at each AM, using the RSpecs defined above.
  18. Log in to each of the systems in the slice, and send traffic to each other systems; leave traffic running
  19. As Experimenter3, request ListResources from BBN InstaGENI, BBN meso-scale FOAM, and FOAM at Meso-scale Site (Internet2 Site BBN and NLR site is TBD).
  20. Review ListResources output from all AMs.
  21. Define a request RSpec for a VM at the BBN InstaGENI.
  22. Define a request RSpec for a compute resource at the BBN meso-scale site.
  23. Define a request RSpec for a compute resource at a meso-scale site.
  24. Define request RSpecs for OpenFlow resources to allow connection from OpenFlow BBN InstaGENI to Meso-scale OpenFlow sites(BBN and second site TBD) (I2 and NLR).
  25. If PG access to OpenFlow is available, define a request RSpec for the PG OpenFlow resource.
  26. Create a third slice.
  27. Create slivers that connects the TBD Internet2 Meso-scale OpenFlow site to the BBN InstaGENI Site, and the BBN Meso-scale site; and if available, to PG node.
  28. Log in to each of the compute resources in the slice, configure data plane network interfaces on any non-InstaGENI resources as necessary, and send traffic to each other systems; leave traffic running.
  29. Verify that all three experiment continue to run without impacting each other's traffic, and that data is exchanged over the path along which data is supposed to flow.
  30. Review baseline monitoring statistics and checks.
  31. As site administrator, identify all controllers that the BBN InstaGENI OpenFlow switch is connected to
  32. As Experimenter3, verify that traffic only flows on the network resources assigned to slivers as specified by the controller.
  33. 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.
  34. Set the hard and soft timeout of flowtable entries
  35. Get switch statistics and flowtable entries for slivers from the OpenFlow switch.
  36. Get layer 2 topology information about slivers in each slice.
  37. Install flows that match only on layer 2 fields, and confirm whether the matching is done in hardware.
  38. If supported, install flows that match only on layer 3 fields, and confirm whether the matching is done in hardware.
  39. Run test for at least 4 hours.
  40. Review monitoring statistics and checks as above.
  41. Delete slivers.

Attachments (11)