Changes between Version 6 and Version 7 of GENIRacksHome/InstageniRacks/SiteConfirmationTests

Timestamp:

10/30/12 14:16:54 (11 years ago)

Author:

lnevers@bbn.com

Comment:

--

GENIRacksHome/InstageniRacks/SiteConfirmationTests

@@ -40 +40 @@
 This confirmation test will create a sliver at the New InstaGENI Site with 1 VM on shared VLAN 1750. This New Site sliver will inter-operate with !OpenFlow slivers that include: a Meso-scale site, an ExoGENI site, and an Emulab !OpenFlow node.  All nodes will exchange traffic and slivers will be deleted upon completions.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
 
- 1. List resources at the Aggregate Manager to determine available compute resources at GPO InstaGENI, New Site InstaGENI, Meso-scale site, and at the Emulab site. Write compute resources RSpecs requesting shared nodes at InstaGENI and Emulab aggregates. Write compute resource RSPec to request nodes at Meso-scale site.
+ 1. List resources at the Aggregate Manager to determine available compute resources at GPO InstaGENI, New Site InstaGENI, Meso-scale site, ExoGENI Site, and at the Emulab site. Write compute resources RSpecs requesting shared nodes at InstaGENI and Emulab aggregates. Write compute resource RSPec to request nodes at Meso-scale site.
  2. List resources at the intermediate FOAM aggregates and at Meso-scale aggregate to determine available resources.  Write remaining RSpecs.
- 2. Create slice, and create slivers at core and Meso-scale FOAM aggregates.
+ 2. Create slice, and create slivers at core, ExoGENI and Meso-scale FOAM aggregates.
  3. Create slivers at the GPO, Emulab, and New Site InstaGENI aggregate requesting 1 shared VLAN VM at each site.
  4. Create compute resource sliver at Meso-scale site.
- 5. Login to compute resources at New Site InstaGENI, GPO InstaGENI, Emulab, and Meso-scale sites and exchange traffic with each of the other remotes.
+ 5. Login to compute resources at New Site InstaGENI, GPO InstaGENI, Emulab, ExoGENI, and Meso-scale sites and exchange traffic with each of the other remotes.
  6. Delete slivers, and verify that resources are released by checking listresources available details.