| | 1 | |
| | 2 | = EG-EXP-2: InstaGENI Single Site Acceptance Test = |
| | 3 | |
| | 4 | 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 [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 | |
| | 32 | || ''State Legend'' || ''Description '' || |
| | 33 | || || |
| | 34 | || [[Color(green,Pass)]] || Test completed and met all criteria || |
| | 35 | || [[Color( #98FB98, #100000 , Pass)]] || Test completed and met most criteria. Exceptions documented|| |
| | 36 | || [[Color( #F0FFF0, #100000 , Complete)]] || Test completed but requiring re-execution due to expected changes || |
| | 37 | || [[Color( #B0E0E6, #100000 , Complete)]] || Test completed with workaround for ticketed issue(s)|| |
| | 38 | || [[Color(#CAE1FF,Workaround)]] || Test in progress with workaround for ticketed issue(s). || |
| | 39 | || [[Color(#63B8FF,In Progress)]] || Currently under test. || |
| | 40 | || [[Color(red,Fail)]] || Test completed and failed to meet criteria. || |
| | 41 | || [[Color(orange,Blocked)]] || Blocked by ticketed issue(s). || |
| | 42 | |
| | 43 | |
| | 44 | |
| | 45 | = Test Plan Steps = |
| | 46 | |
| | 47 | 1. As Experimenter1, request !ListResources from Utah InstaGENI. |
| | 48 | 2. Review advertisement RSpec for a list of OS images which can be loaded, and identify available resources. |
| | 49 | 3. Verify that the GPO Ubuntu customized image is available in the advertisement RSpec. |
| | 50 | 4. Define a request RSpec for two VMs, each with a GPO Ubuntu image. Request a publically routable IP address and public TCP/UDP port mapping for the control interface on each node. |
| | 51 | 5. Create the first slice. |
| | 52 | 6. Create a sliver in the first slice, using the RSpec defined in step 4. |
| | 53 | 7. Log in to each of the systems, and send traffic to the other system sharing a VLAN. |
| | 54 | 8. Using root privileges on one of the VMs load a Kernel module. It is expected this will not work on shared OpenVZ nodes, testing will proceed past this step. |
| | 55 | 9. Run a netcat listener and bind to port XYZ on each of the VMs in the Utah rack. |
| | 56 | 10. Send traffic to port XYZ on each of the VMs in the Utah rack over the control network from any commodity Internet host. |
| | 57 | 11. As Experimenter2, request !ListResources from Utah InstaGENI. |
| | 58 | 12. Define a request RSpec for two physical nodes, both using the uploaded GPO Ubuntu images. |
| | 59 | 13. Create the second slice. |
| | 60 | 14. Create a sliver in the second slice, using the RSpec defined in step 12. |
| | 61 | 15. Log in to each of the systems, and send traffic to the other system. |
| | 62 | 16. 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) |
| | 63 | 17. Review system statistics and VM isolation and network isolation on data plane. |
| | 64 | 18. Verify that each VM has a distinct MAC address for that interface. |
| | 65 | 19. Verify that VMs' MAC addresses are learned on the data plane switch. |
| | 66 | 20. Stop traffic and delete slivers. |
