IG-EXP-1: Bare Metal Support Acceptance Test

This page captures status for the test case IG-EXP-1, which verified support for bare metal nodes. For overall status see the ExoGENI Acceptance Test Status page.

Last update: 08/20/12

Test Status

This section captures the status for each step in the acceptance test plan.

Step	State	Date completed	Ticket	Comments
Step 1	Color(green,Pass)?
Step 2	Color(red,Fail)?		​instaticket:13	Windows XP instructions exist, not worth taking up resources for weeks.
Step 3	Color(red,Fail)?			Windows XP instructions exist, not worth taking up resources for weeks.
Step 4	Color(green,Pass)?
Step 5	Color(green,Pass)?
Step 6	Color(green,Pass)?
Step 7

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

This experiment was conducted on May 24, 2012. For this test a nick_name alias is used for the Utah InstaGENI aggregate manager:

insta-utah=,http://utah.geniracks.net/protogeni/xmlrpc/am

Step 1. Determine which nodes can be used as exclusive nodes

Able to determine which node are exclusive and if they are available via Omni listresources. No issues found. ListResources obtained with the following Omni command:

 $ omni.py -a insta-utah listresources --available --api-version 2 -t GENI 3 -o

Step 2. Obtain 2 licensed recent Microsoft OS images for physical nodes from the site (BBN)

Need to get InstaGENI folks to document the non-support of MS Windows and cleanup of windows references (​ticket 13).

Step 3. Reserve and boot 2 physical nodes using Microsoft image

MS Windows is not verified (​ticket 13) According to email from Leigh, this is very time intensive and would require weeks. Also Windows XP instructions exist.

Step 4. Obtain a recent Linux OS image for physical nodes from the InstaGENI list

Have requested the list of currently supported OS by InstaGENI. Initially only Standard 32-bit Fedora 15 image was available, two images have been added to the list of available OS in the Utah InstaGENI rack (​ticket 13). Tested each images made available to experimenters, by setting up a 2 raw pc with 1 lan experiment for each image and attached Rspec:

• FreeBSD 8.2 32-bit version
• Standard 64-bit Ubuntu 11 image
• Standard 32-bit Fedora 15 image (default)

Command used to determine images:

 $ omni.py -a insta-utah listresources --available --api-version 2 -t GENI 3 --available -o
 $ egrep "node component|disk_image|available" rspec-boss-utah-geniracks-net-protogeni-xmlrpc-am-2-0.xml 

Step 5. Reserve and boot physical node using each loading a different Linux OS image

Using the RSpec [ ​http://groups.geni.net/geni/browser/trunk/GENIRacks/InstaGENI/Spiral4/RSpecs/AcceptanceTests/IG-EXP-1/IG-EXP-1.rspec that includes 1 FreeBSD, and 1 Ubuntu node, create a slice and sliver:

$ omni.py createslice IG-EXP-1
$ omni.py -a insta-utah createsliver IG-EXP-1 IG-EXP-1.rspec --api-version 2 -t GENI 3 

Verify that the sliver is ready with a Omni sliverstatus command and verify that 'pg_status' is 'ready':

 $ omni.py -a insta-utah sliverstatus IG-EXP-1 --api-version 2 -t GENI 3

Once sliver is ready, check the host allocation for the sliver EG-EXP-1:

 $ omni.py -a insta-utah listresources IG-EXP-1 --api-version 2 -t GENI 3 -o
 $ egrep "login" IG-EXP-1-rspec-utah-geniracks-net-protogeni.xml 
      <login authentication="ssh-keys" hostname="pc4.utah.geniracks.net" port="22" username="lnevers"/>    
      <login authentication="ssh-keys" hostname="pc2.utah.geniracks.net" port="22" username="lnevers"/>   

VerifY dataplane connectivity for each endpoints in each experiment:

Step 6. Release physical node resource

Release compute resources:

 $ omni.py -a insta-utah deletesliver IG-EXP-1

Step 7. Modify Aggregate resource allocation for the rack to add 1 additional physical node