| 1 | |
| 2 | = IG-EXP-6: InstaGENI and Meso-scale Multi-site OpenFlow Acceptance Test = |
| 3 | |
| 4 | 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 [wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus InstaGENI Acceptance Test Status] page. |
| 5 | |
| 6 | |
| 7 | = Test Status = |
| 8 | This section captures the status for each step in the acceptance test plan. |
| 9 | |
| 10 | || '''Step''' || '''State''' || '''Date completed''' ||''' Ticket ''' || '''Comments''' || |
| 11 | || Step 1 || || || || || |
| 12 | || Step 2 || || || || || |
| 13 | || Step 3 || || || || || |
| 14 | || Step 4 || || || || || |
| 15 | || Step 5 || || || || || |
| 16 | || Step 6 || || || || || |
| 17 | || Step 7 || || || || || |
| 18 | || Step 8 || || || || || |
| 19 | || Step 9 || || || || || |
| 20 | || Step 10 || || || || || |
| 21 | || Step 11 || || || || || |
| 22 | || Step 12 || || || || || |
| 23 | || Step 13 || || || || || |
| 24 | || Step 14 || || || || || |
| 25 | || Step 15 || || || || || |
| 26 | || Step 16 || || || || || |
| 27 | || Step 17 || || || || || |
| 28 | || Step 18 || || || || || |
| 29 | || Step 19 || || || || || |
| 30 | || Step 20 || || || || || |
| 31 | || Step 21 || || || || || |
| 32 | || Step 22 || || || || || |
| 33 | || Step 23 || || || || || |
| 34 | || Step 24 || || || || || |
| 35 | || Step 25 || || || || || |
| 36 | || Step 26 || || || || || |
| 37 | || Step 27 || || || || || |
| 38 | || Step 28 || || || || || |
| 39 | || Step 29 || || || || || |
| 40 | || Step 30 || || || || || |
| 41 | || Step 31 || || || || || |
| 42 | || Step 32 || || || || || |
| 43 | || Step 33 || || || || || |
| 44 | || Step 34 || || || || || |
| 45 | || Step 35 || || || || || |
| 46 | || Step 36 || || || || || |
| 47 | || Step 37 || || || || || |
| 48 | || Step 38 || || || || || |
| 49 | || Step 39 || || || || || |
| 50 | || Step 40 || || || || || |
| 51 | || Step 41 || || || || || |
| 52 | |
| 53 | |
| 54 | || ''State Legend'' || ''Description '' || |
| 55 | || || |
| 56 | || [[Color(green,Pass)]] || Test completed and met all criteria || |
| 57 | || [[Color( #98FB98, #100000 , Pass)]] || Test completed and met most criteria. Exceptions documented|| |
| 58 | || [[Color( #F0FFF0, #100000 , Complete)]] || Test completed but requiring re-execution due to expected changes || |
| 59 | || [[Color( #B0E0E6, #100000 , Complete)]] || Test completed with workaround for ticketed issue(s)|| |
| 60 | || [[Color(#CAE1FF,Workaround)]] || Test in progress with workaround for ticketed issue(s). || |
| 61 | || [[Color(#63B8FF,In Progress)]] || Currently under test. || |
| 62 | || [[Color(red,Fail)]] || Test completed and failed to meet criteria. || |
| 63 | || [[Color(orange,Blocked)]] || Blocked by ticketed issue(s). || |
| 64 | |
| 65 | |
| 66 | |
| 67 | = Test Plan Steps = |
| 68 | 1. As Experimenter1, request !ListResources from BBN InstaGENI, Utah InstaGENI, and from FOAM at I2 and NLR Site. |
| 69 | 2. Review !ListResources output from all AMs. |
| 70 | 3. Define a request RSpec for a VM at the BBN InstaGENI. |
| 71 | 4. Define a request RSpec for a VM at the Utah InstaGENI. |
| 72 | 5. Define request RSpecs for !OpenFlow resources from BBN FOAM to access GENI !OpenFlow core resources. |
| 73 | 6. Define request RSpecs for !OpenFlow core resources at I2 FOAM |
| 74 | 7. Define request RSpecs for !OpenFlow core resources at NLR FOAM. |
| 75 | 8. Create the first slice. |
| 76 | 9. Create a sliver in the first slice at each AM, using the RSpecs defined above. |
| 77 | 10. Log in to each of the systems, verify IP address assignment. Send traffic to the other system, leave traffic running. |
| 78 | 11. As Experimenter2, define a request RSpec for one VM and one physical node at BBN InstaGENI. |
| 79 | 12. Define a request RSpec for two VMs on the same experiment node at Utah InstaGENI. |
| 80 | 11. Define request RSpecs for !OpenFlow resources from BBN FOAM to access GENI !OpenFlow core resources. |
| 81 | 14. Define request RSpecs for !OpenFlow core resources at I2 FOAM. |
| 82 | 15. Define request RSpecs for !OpenFlow core resources at NLR FOAM. |
| 83 | 16. Create a second slice. |
| 84 | 17. Create a sliver in the second slice at each AM, using the RSpecs defined above. |
| 85 | 18. Log in to each of the systems in the slice, and send traffic to each other systems; leave traffic running |
| 86 | 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). |
| 87 | 20. Review !ListResources output from all AMs. |
| 88 | 21. Define a request RSpec for a VM at the BBN InstaGENI. |
| 89 | 22. Define a request RSpec for a compute resource at the BBN meso-scale site. |
| 90 | 23. Define a request RSpec for a compute resource at a meso-scale site. |
| 91 | 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). |
| 92 | 25. If PG access to !OpenFlow is available, define a request RSpec for the PG !OpenFlow resource. |
| 93 | 26. Create a third slice. |
| 94 | 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. |
| 95 | 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. |
| 96 | 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. |
| 97 | 30. Review baseline monitoring statistics and checks. |
| 98 | 31. As site administrator, identify all controllers that the BBN InstaGENI !OpenFlow switch is connected to |
| 99 | 32. As Experimenter3, verify that traffic only flows on the network resources assigned to slivers as specified by the controller. |
| 100 | 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. |
| 101 | 34. Set the hard and soft timeout of flowtable entries |
| 102 | 35. Get switch statistics and flowtable entries for slivers from the !OpenFlow switch. |
| 103 | 36. Get layer 2 topology information about slivers in each slice. |
| 104 | 37. Install flows that match only on layer 2 fields, and confirm whether the matching is done in hardware. |
| 105 | 38. If supported, install flows that match only on layer 3 fields, and confirm whether the matching is done in hardware. |
| 106 | 39. Run test for at least 4 hours. |
| 107 | 40. Review monitoring statistics and checks as above. |
| 108 | 41. Delete slivers. |