Changes between Version 3 and Version 4 of GENIRacksHome/InstageniRacks/SiteConfirmationTests


Ignore:
Timestamp:
10/30/12 14:05:06 (11 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIRacksHome/InstageniRacks/SiteConfirmationTests

    v3 v4  
    44
    55As new InstaGENI sites are deployed, the GPO will complete a series of InstaGENI (IG) Site Confirmation Tests (CT) to validate Meso-scale specific features. These confirmation tests verify experimenter access to network and compute resources at the newly installed InstaGENI site, the ability to monitor the site, and potentially some initial administrative task.  The experiments defined for the Confirmation Tests make two assumptions: GPO personnel have been white-listed on the site rack, and Omni tools are used for all AM API operations.
     6Also this tests may replace the GPO InstaGENI rack with the Utah InstaGENI rack if needed.
    67
    78
    … …  
    2829== IG-CT-3 - Multiple sites experiment  ==
    2930
    30 This confirmation test will create a sliver at the New InstaGENI Site and one sliver at the GPO requesting 1 VM at each aggregate. The VMs will be used to exchange traffic and slivers will be deleted upon completions.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
     31This confirmation test will create a sliver at the New InstaGENI Site and one sliver at the GPO requesting 1 VM at each aggregate. The VMs will exchange traffic and slivers will be deleted upon completions.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
    3132
    3233 1. List resources at the Aggregate Manager to determine available resources for experiment at GPO InstaGENI and at New InstaGENISite. Write RSpecs.
    … …  
    3536 4. Delete sliver, and verify that resources are released by checking listresources available details.
    3637
    37 == IG-CT-4 - Multiple sites !OpenFlow experiment ==
     38== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
    3839
    39 This confirmation test will create a sliver at the New InstaGENI Site and one sliver at the GPO requesting 1 VM at each aggregate. Nodes at each site will be on the !OpenFlow shared VLAN 1750.  The VMs will be used to exchange traffic and slivers will be deleted upon completions.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
     40This confirmation test will create a sliver at the New InstaGENI Site and one sliver at the GPO requesting 1 VM at each aggregate. In addition, the New Site will inter-operate with !OpenFlow slivers that include a Meso-scale site and an Emulab !OpenFlow nodes on the !OpenFlow shared VLAN 1750.  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:
    4041
    41  1. List resources at the Aggregate Manager to determine available resources at GPO InstaGENI and at New Site InstaGENI. Write compute resources RSpecs.
    42  2. List resources at the InstaGENI New Site FOAM, at GPO InstaGENI FOAM, and at each intermediate FOAM aggregate to determine available resources.  Write RSpecs.
    43  2. Create slice, and createsliver at FOAM aggregate.
    44  3. Create sliver at the GPO InstaGENI and the New Site InstaGENI compute resource aggregate requesting 1 VM at each site.
    45  3. Login to compute resources allocated to the sliver and exchange traffic.
    46  4. Delete sliver, and verify that resources are released by checking listresources available details.
     42 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.
     43 2. List resources at the intermediate FOAM aggregates and at Meso-scale aggregate to determine available resources.  Write remaining RSpecs.
     44 2. Create slice, and create slivers at core and Meso-scale FOAM aggregates.
     45 3. Create slivers at the GPO, Emulab, and New Site InstaGENI aggregate requesting 1 shared VLAN VM at each site.
     46 4. Create compute resource sliver at Meso-scale site.
     47 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.
     48 6. Delete slivers, and verify that resources are released by checking listresources available details.
    4749
    4850== IG-CT-5 - Experiment Monitoring ==