Changes between Version 45 and Version 46 of GENIRacksHome/ExogeniRacks/AggregateSurvey

Timestamp:

04/25/12 16:53:34 (12 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/ExogeniRacks/AggregateSurvey

@@ -13 +13 @@
 == AM API Acceptance Tests ==
 
-Using the RSpec from the previous survey was not able to run the test with the same options as on 04/25/2012.  The AM API acceptance test defaults to RSpec V3 while the RSpec are V2, this was not reported as a problem last time, but now seems to cause all 13 tests to fail. If interested in this mismatched scenario, see the [http://groups.geni.net/geni/attachment/wiki/GENIRacksHome/ExogeniRacks/AggregateSurvey/failed-v3-support.txt command output] and the [http://groups.geni.net/geni/attachment/wiki/GENIRacksHome/ExogeniRacks/AggregateSurvey/exogeni-log-20120425.txt log] for details.
+Using the RSpec from the previous survey was not able to run the test with the same options as on 04/25/2012.  The AM API acceptance test defaults to RSpec V3 while the RSpec I had been using were V2. This mismatch was not reported as a problem last time, but now seems to cause all 13 tests to fail. If interested in this mismatched RSpec versions scenario, see the [http://groups.geni.net/geni/attachment/wiki/GENIRacksHome/ExogeniRacks/AggregateSurvey/failed-v3-support.txt command output] and the [http://groups.geni.net/geni/attachment/wiki/GENIRacksHome/ExogeniRacks/AggregateSurvey/exogeni-log-20120425.txt log] for details.
 
 Re-run acceptance test with the new argument "--ProtoGENIv2" for the V2 RSpecs:
@@ -94 +94 @@
 == Experiments with Omni Commands ==
 
-Ran several experiments using various combinations of aggregates and hosts, only one very minor issue was found relating to requesting resources at the wrong component manager, see ticket [http://groups.geni.net/exogeni/ticket/2 ticket 2] for details.  Following are the Experiements that were tested:
+Ran several experiments using various combinations of aggregates and hosts, only one very minor issue was found relating to requesting resources at the wrong component manager, see ticket [http://groups.geni.net/exogeni/ticket/2 ticket 2] for details.  Following are the Experiments that were tested:
 
 1. Set up a 2 nodes (1@BBN, 1@RENCI) experiment using the ExoSM (!https://geni.renci.org:11443/orca/xmlrpc) only. Same RSpec as previous survey (04/11/2012).  This experiment worked as expected. Two nodes were allocated and the requested addresses were configured on the hosts with the requested link.  Verified connectivity between the two hosts by running ping concurrently on each host in each direction for 10 minutes.
@@ -106 +106 @@
 5. Created a 2 node (2@RENCI) experiment using RENCI SM (!https://bbn-hn.exogeni.gpolab.bbn.com:11443/orca/xmlrpc). See RSpec [here].  This experiment worked as expected. Two nodes were allocated and the requested addresses were configured on the hosts with the requested link. Verified connectivity.
 
-
-
+=== List Resources ===
+Ran list resources at each of the 3 aggregates:
+{{{
+ $ ./src/omni.py -a https://bbn-hn.exogeni.net:11443/orca/xmlrpc listresources -o   # BBN rack SM
+ $ ./src/omni.py -a https://rci-hn.exogeni.net:11443/orca/xmlrpc listresources -o  # RENCI rack SM
+ $ ./src/omni.py -a  https://geni.renci.org:11443/orca/xmlrpc listresources -o     # ExoGENI SM
+}}}
+List resources output file attached as [ rspec-bbn-hn-exogeni-net-11443-orca.xml], rspec-rci-hn-exogeni-net-11443-orca.xml and  [rspec-geni-renci-org-11443-orca.xml
 
 = Status 04/11/2012 =