Version 20 (modified by, 9 years ago) (diff)


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 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)? instaticket:14 Blocked on prerequisite tests completion
Step 2 Color(orange,Blocked)? instaticket:20 Have customized image, waiting on reply for how to make it available.
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,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.


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. Sent email request to (instaticket:20)

Prereq: Traffic generation tools may be part of image or may be installed at experiment runtime.

Status: Done: 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: Done. Two account already exist, and, 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 requested the list of available resources as follows:

 $ ./src/ -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:

<disk_image description="FreeBSD 8.2 32-bit version" name="" os="FreeBSD" version="8.2"/>      
<disk_image default="true" description="Standard 32-bit Fedora 15 image" name="" os="Fedora" version="15"/>      
<disk_image description="Standard 64-bit Ubuntu 11 image" name="" os="Linux" version="11.04"/>      
<disk_image default="true" description="Standard 32-bit Fedora 15 image" name="" os="Fedora" version="15"/>      

Note 1: instaticket:14 written for duplicate default image in the Advertisement RSpec.
Note 2: Sent email to geni-dev-utah to figure out procedure.
Note 3: Need to talk to Peter about Ubuntu images to build.

Step 3. Verify that the GPO Ubuntu customized image is available in the advertisement RSpec

Defined customized OS image as defined in the Custom OS InstaGENI notes page. Still working on making this image available to users.

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