EG-EXP-1: Bare Metal Support Acceptance Test

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

Test Status

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

Step	State	Ticket	Comments
Step 1	Color(yellow,Complete)?		1 Bare Metal is available at BBN and 1 at RENCI
Step 2	Color(yellow,Complete)?		default image only is supported
Step 3	Color(orange,Blocked)?		Replace Bare metal with VM for Windows
Step 4	Color(orange,Blocked)?		Replace Bare metal with VM for Windows
Step 5	Color(yellow,Complete)?
Step 6	Color(yellow,Complete)?
Step 7	Color(yellow,Complete)?
Step 8	Color(orange,Blocked)?		Not possible at this time to redefine bare metal allocation

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

Notes:

1. Bare Metal nodes are available via EXoSM only.
   
2. Bare Metal node only support one OS version at this time, CentOS release 6.3.
   
3. 1 Bare metal at BBN and 1 at RENCI.
   

Step 1. Determine which nodes can be used as bare metal, aka exclusive node

The omni_configuration used for this scenario includes a nick_name for the ExoSM which is used through out the steps:

exosm=,https://geni.renci.org:11443/orca/xmlrpc

Determine available bare metal resources from the ExoSM.

$ omni.py listresources -a exosm -o

The listresources output file rspec-geni-renci-org-11443-orca.xml has the bare metal resources at the two ExoGENI sites BBN and RENCI:

$ egrep "xcat-cloud|available now" rspec-geni-renci-org-11443-orca.xml 
      <node component_id="urn:publicid:IDN+exogeni.net:bbnvmsite+node+orca-xcat-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:bbnvmsite+authority+am" component_name="orca-xcat-cloud" exclusive="false">    
            <hardware_type name="orca-xcat-cloud">      
            <available now="true"/>    

      <node component_id="urn:publicid:IDN+exogeni.net:rcivmsite+node+orca-xcat-cloud" component_manager_id="urn:publicid:IDN+exogeni.net:rcivmsite+authority+am" component_name="orca-xcat-cloud" exclusive="false">    
            <hardware_type name="orca-xcat-cloud">      
            <available now="true"/>    

Verify that each is available (available now="true") before requesting the bare metal nodes.

Step 2. Obtain a list of OS images which can be loaded on bare metal nodes from the ExoGENI team.

The list should be based on successful bare metal loads by ExoGENI team or others in GENI community and should be available on a public web page.

At the time of feature delivery, bare metal nodes only supported one image. The reserved bare metal nodes ran these two OS:

[root@bbn-w4 ~]# cat /etc/issue
CentOS release 6.2 (Final)
Kernel \r on an \m
[root@bbn-w4 ~]# uname -a
Linux bbn-w4 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@bbn-w4 ~]# 

and

[root@rci-w4 ~]# cat /etc/issue
CentOS release 6.3 (Final)
Kernel \r on an \m
[root@rci-w4 ~]# uname -a
Linux rci-w4 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

The plan is for all bare metal to run the CentOS release 6.3 OS, at some point.

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

There is no plan to support MS Windows on a bare metal node, this test will replace bare metal Windows with a Windows VM in future test runs.

Step 4. Reserve and boot 2 bare metal node using the Microsoft image.

There is no plan to support MS Windows on a bare metal node, this test will replace bare metal Windows with a Windows VM in future test runs.

Step 5. Obtain a recent Linux OS image for bare metal nodes from the ExoGENI team's successful test list

The bare metal nodes only support one image at this time. The default image is the one used to develop the support for this feature.

Step 6. Reserve and boot a bare metal node using this Linux OS image.

$ omni.py createslice 2bare
$ omni.py -a exosm createsliver 2bare EG-EXP-1-2baremetal
$ omni.py -a exosm sliverstatus 2bare

Once the sliver is ready determine the addresses associated with the sliver:

$ omni.py -a exosm listresources 2bare -o 
$ egrep hostname 2bare-rspec-geni-renci-org-11443-orca.xml
<login authentication="ssh-keys" hostname="192.1.242.110" port="22" username="root"/>      
<login authentication="ssh-keys" hostname="152.54.14.200" port="22" username="root"/

Step 7. Release bare metal resource.

Once traffic is exchanged successfully between the two bare metal nodes, delete the sliver.

First, login on the BBN Rack bare metal node and send traffic:

$ ssh 192.1.242.110 -l root
[root@bbn-w4 ~]# cat /etc/issue
CentOS release 6.2 (Final)
Kernel \r on an \m
[root@bbn-w4 ~]# uname -a
Linux bbn-w4 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux
[root@bbn-w4 ~]#ping 172.16.1.2 

Second, login on the BBN Rack bare metal node and send traffic:

$ ssh 192.152.54.14.200 -l root
[root@rci-w4 ~]# cat /etc/issue
CentOS release 6.3 (Final)
Kernel \r on an \m
[root@rci-w4 ~]# uname -a
Linux rci-w4 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@rci-w4 ~]#ping 172.16.1.1

Delete the sliver while the traffic is being exchanged:

$ omni.py -a exosm deletesliver 2bare

Step 8. Modify Aggregate resource allocation for the rack to add 1 additional bare metal node (2 total) for use in experimenter test cases.

Not possible at this time.