Changes between Version 30 and Version 31 of GENIRacksHome/ExogeniRacks/SiteConfirmationTests

Timestamp:

10/31/12 14:58:34 (11 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/ExogeniRacks/SiteConfirmationTests

@@ -8 +8 @@
 == EG-CT-1 - Access to New Site VM resources ==
 
-The ExoGENI Confirmation Test EG-CT-1 creates a sliver at the New Site ExoGENI aggregate that includes 4 VMs all in the same rack.  The VMs are used to exchange traffic. Resources are released upon completion of the test.  Following is the sequence of operations for this test at the new ExoGENI Rack:
+The ExoGENI Confirmation Test EG-CT-1 creates a sliver at the New Site ExoGENI aggregate that includes 4 VMs all in the same rack.  The VMs are used to exchange traffic. Resources are released upon completion of the test. The test topology used:
+
+[[Image(IG-CT-1.jpg)]]
+
+Following is the sequence of operations for this test at the new ExoGENI Rack:
 
  1. Get AM API version, verify that orca_version is same or newer than existing racks.
@@ -19 +23 @@
 == EG-CT-2 - Access to New Site bare metal and VM resources ==
 
-This confirmation test creates a sliver at the ExoSM requesting one bare metal node and one VM at the new ExoGENI site. The VM and bare metal resources are used to exchange traffic. Slivers are deleted upon completions.  Following is the sequence of AM operations for this test at the new ExoGENI Rack:
+This confirmation test creates a sliver at the ExoSM requesting one bare metal node and one VM at the new ExoGENI site. The VM and bare metal resources are used to exchange traffic. Slivers are deleted upon completions.  The test topology used:
+
+[[Image(IG-CT-2.jpg)]]
+
+Following is the sequence of AM operations for this test at the new ExoGENI Rack:
 
  1. List resources at the ExoSM to determine VM and bare metal available at the New Site. Write RSpec.
@@ -28 +36 @@
 == EG-CT-3 - Multiple sites experiment  ==
 
-This confirmation test creates a sliver at the New ExoGENI Site and one sliver at the GPO ExoGENI requesting one VM at each site.  All VMs exchange traffic and slivers are deleted upon completion.  Following is the sequence of AM operations for this test at each ExoGENI Rack:
+This confirmation test creates a sliver at the New ExoGENI Site and one sliver at the GPO ExoGENI requesting one VM at each site.  All VMs exchange traffic and slivers are deleted upon completion.  The test topology used:
+
+[[Image(IG-CT-3.jpg)]]
+
+Following is the sequence of AM operations for this test at each ExoGENI Rack:
 
  1. List resources at the ExoSM to determine available resources for experiment at GPO ExoGENI and at New ExoGENI Site. Write RSpecs.
@@ -37 +49 @@
 == EG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
 
-This confirmation creates a sliver at the New ExoGENI Site requesting one VM on shared VLAN 1750. The New Site sliver inter-operates with !OpenFlow slivers that include: a Meso-scale site, an InstaGENI site, and an Emulab !OpenFlow node.  Each of the VMs exchange traffic, and slivers are deleted upon completions.  Following is the sequence of AM operations for this test at each ExoGENI Rack:
+This confirmation creates a sliver at the New ExoGENI Site requesting one VM on shared VLAN 1750. The New Site sliver inter-operates with !OpenFlow slivers that include: a Meso-scale site, an InstaGENI site, and an Emulab !OpenFlow node.  Each of the VMs exchange traffic, and slivers are deleted upon completions.  The test topology used:
+
+[[Image(IG-CT-4.jpg)]]
+
+Following is the sequence of AM operations for this test at each ExoGENI Rack:
 
  1. List resources at the ExoSM to determine available resources at GPO ExoGENI and New Site ExoGENI racks. Do the same for the AMs at the Meso-scale site, InstaGENI site, and at the PG Utah site. Write compute resources RSpecs requesting nodes on VLAN 1750 for each aggregate.