Changes between Version 15 and Version 16 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-1

Timestamp:

07/05/12 07:16:40 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-EXP-1

@@ -31 +31 @@
 = Test Plan Steps =
 
-Notes:
-1. Bare Metal nodes are available via EXoSM only.
-2. Bare Metal node only support one version at this time.
-3. 1 Bare metal at BBN and 1 at RENCI.
+'''Notes:''' [[BR]]
+1. Bare Metal nodes are available via EXoSM only. [[BR]]
+2. Bare Metal node only support one version at this time. [[BR]]
+3. 1 Bare metal at BBN and 1 at RENCI. [[BR]]
 
 == Step 1. Determine which nodes can be used as bare metal, aka exclusive node ==
+Note that the omni_configuration includes a nick_name for the ExoSM:
+{{{
+exosm=,https://geni.renci.org:11443/orca/xmlrpc
+}}}
 
+Determine available bare metal resources from the ExoSM. 
+{{{
+$ cd ..;./src/omni.py listresources -a exosm -o
+}}}  
 
+The listresource output file rspec-geni-renci-org-11443-orca.xml lists the bare metal
+resources at the two sites BBN and RENCI:
+{{{
+$ egrep baremetal 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="bbnvmsite.rdf#bbnvmsite/Domain/baremetalce" exclusive="false">    
+      <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="rcivmsite.rdf#rcivmsite/Domain/baremetalce" exclusive="false">    
+}}}
+Verify that each is available before requesting the node.
 
 == 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, need to request list of images that are available for Linux Bare Metal nodes as well verifying the external advertisement of the images.
+
+At the time of feature delivery, only supports one image.
 
 == 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.
+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.
+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
+}}}
 
 == Step 7. Release bare metal resource. ==
-
+Once traffic is exchanged successfully between the two bare metal nodes, delete the sliver:
+{{{
+$ 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. ==