= EG-EXP-2: InstaGENI Single Site Acceptance Test = 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. = Test Status = This section captures the status for each step in the acceptance test plan. || '''Step''' || '''State''' || '''Date completed''' ||''' Ticket ''' || '''Comments''' || || Step 1 ||[[Color( #F0FFF0, #100000 , Complete)]]|| || instaticket:14|| || || Step 2 ||[[Color(#63B8FF,In Progress)]] || || ||Email to geni-dev-utah to figure out how to get image listed. || || 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 || || || || || || ''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). || = Prerequisites = Status for test prerequisites: __Prereq:__ InstaGENI makes available at least two Linux distributions and a FreeBSD image as stated in design document __Status:__ Done __Prereq:__ Two GPO customized Ubuntu image snapshots are available and have been manually uploaded by the rack administrator using available InstaGENI documentation. One Ubuntu image is for the VM and one Ubuntu image is for the physical node in this test. __Status:__ Need to talk to Peter about creating images. __Prereq:__ Traffic generation tools may be part of image or may be installed at experiment runtime. __Status:__ Only using ping with mixed sizes and rates for now. __Prereq:__ Administrative accounts have been created for GPO staff on the Utah InstaGENI rack. __Status:__ Done __Prereq:__ GENI Experimenter1 and Experimenter2 accounts exist. __Status:__ Two account already exist, lnevers@bbn.com and lnevers1@bbn.com, these will be used in all acceptance tests. __Prereq:__ Baseline Monitoring is in place for the entire Utah site, to ensure that any problems are quickly identified. __Status:__ Blocked on prerequisite tests completion. = Test Plan Steps = == Step 1. As Experimenter1, request !ListResources from Utah InstaGENI == As experimenter lnevers@bbn.com requested the list of available resources as follows: {{{ $ ./src/omni.py -a insta-utah listresources --available --api-version 2 -t GENI 3 --available -o }}} == Step 2. Review advertisement RSpec for a list of OS images which can be loaded, and identify available resources == Used the output file from previous step to determine list of OS images available and available compute resources: {{{ $ egrep "node component|disk_image|available" rspec-boss-utah-geniracks-net-protogeni-xmlrpc-am-2-0.xml }}} The following disk images were listed: {{{ }}} Note 1: instaticket:14 written for duplicate default image in the Advertisement RSpec. [[BR]] Note 2: Need to send email to geni-dev-utah to figure out procedure. [[BR]] Note 3: Need to talk to Peter about Ubuntu images to build. [[BR]] == Step 3. Verify that the GPO Ubuntu customized image is available in the advertisement RSpec == == Step 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 == == Step 5. Create the first slice == == Step 6. Create a sliver in the first slice, using the RSpec defined in step 4 == == Step 7. Log in to each of the systems, and send traffic to the other system sharing a VLAN == == Step 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 == == Step 9. Run a netcat listener and bind to port XYZ on each of the VMs in the Utah rack == == Step 10. Send traffic to port XYZ on each of the VMs in the Utah rack over the control network from any commodity Internet host == == Step 11. As Experimenter2, request !ListResources from Utah InstaGENI == == Step 12. Define a request RSpec for two physical nodes, both using the uploaded GPO Ubuntu images == == Step 13. Create the second slice == == Step 14. Create a sliver in the second slice, using the RSpec defined in step 12 == == Step 15. Log in to each of the systems, and send traffic to the other system == == Step 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) == == Step 17. Review system statistics and VM isolation and network isolation on data plane == == Step 18. Verify that each VM has a distinct MAC address for that interface == == Step 19. Verify that VMs' MAC addresses are learned on the data plane switch == == Step 20. Stop traffic and delete slivers ==