Changes between Version 1 and Version 2 of GENIRacksHome/CloudLab/SiteConfirmationTests
- Timestamp:
- 05/20/15 15:00:47 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIRacksHome/CloudLab/SiteConfirmationTests
v1 v2 1 1 = !CloudLab New Site Confirmation Tests = 2 2 3 Upon completion of the [wiki:GENIRacksHome/RacksChecklist GENI Rack Site Installation Checklist] for new !CloudLab sites, the GPO will also complete a series of InstaGENI (IG) Site Confirmation Tests (CT) to validate Meso-scale specific features for the newly deployed site. These confirmation tests verify experimenter access to network and compute resources at the newly installed InstaGENI site, the ability to monitor the site, and some basic administrative capabilities. The experiments defined for the Confirmation Tests assume that Omni tools are used for all AM API operations. Also some tests may replace the GPO InstaGENI rack with the Utah InstaGENI rack if needed. See the '''[wiki:GENIRacksHome/InstageniRacks/ConfirmationTestStatus InstaGENI New Site Confirmation Tests Status]''' page for details about sites that have been tested.3 Upon completion of the [wiki:GENIRacksHome/RacksChecklist GENI Rack Site Installation Checklist] for new !CloudLab sites, the GPO will also complete a series of !CloudLab (CL) Site Confirmation Tests (CT) to validate experimenter access to network and compute resources at the newly installed !CloudLab site, the ability to monitor the site, and some basic administrative capabilities. The experiments defined for the Confirmation Tests assume that Omni tools are used for all AM API operations. See the '''[wiki:GENIRacksHome/CloudLab/ConfirmationTestStatus CloudLab New Site Confirmation Tests Status]''' page for details about sites that have been tested and for test logs. 4 4 5 5 6 6 == CL-CT-1 - Access to New Site VM resources == 7 7 8 The !CloudLab Confirmation Test CL-CT-1 creates a sliver at the New Site InstaGENIaggregate 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:8 The !CloudLab Confirmation Test CL-CT-1 creates a sliver at the New Site CloudLab 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: 9 9 10 10 [[Image(CL-CT-1.jpg)]] … … 45 45 Following is the sequence of AM operations for this test at each !CloudLab Rack: 46 46 47 1. List resources at the Aggregate Managers to determine available resources for experiment at GPO !CloudLab and at New InstaGENISite. Write RSpecs.47 1. List resources at the Aggregate Managers to determine available resources for experiment at GPO !CloudLab and at New CloudLab Site. Write RSpecs. 48 48 2. Create slice and create slivers at each site aggregate requesting 1 VM. 49 49 3. Login to each of the resources allocated to the slivers and exchange traffic. … … 67 67 Following is the sequence of AM operations for this test at each !CloudLab Rack: 68 68 69 1. List resources at the Aggregate Managers to determine available resources at GPO !CloudLab, New Site InstaGENI, Meso-scale site, ExoGENI Site, and at the PG Utah site. Write resources RSpecs requesting shared nodes at InstaGENIand PG Utah aggregates. Write compute resource RSpec to request nodes at Meso-scale site.69 1. List resources at the Aggregate Managers to determine available resources at GPO !CloudLab, New Site !CloudLab, Meso-scale site, ExoGENI Site, and at the PG Utah site. Write resources RSpecs requesting shared nodes at !CloudLab and PG Utah aggregates. Write compute resource RSpec to request nodes at Meso-scale site. 70 70 2. List resources at the intermediate core FOAM aggregates and at Meso-scale aggregate to determine available resources. Write remaining RSpecs. 71 71 2. Create slice and create slivers at core aggregates, ExoGENI, and Meso-scale FOAM aggregates. 72 3. Create slivers at the GPO !CloudLab, PG Utah, and New Site InstaGENIaggregate requesting 1 shared VLAN VM at each site.72 3. Create slivers at the GPO !CloudLab, PG Utah, and New Site !CloudLAb aggregate requesting 1 shared VLAN VM at each site. 73 73 4. Create compute resource sliver at Meso-scale site. 74 74 5. Login to each of the compute resources at New Site !CloudLab, GPO InstaGENI, Emulab, ExoGENI, and Meso-scale sites and exchange traffic with each of the other remotes.