wiki:GENIRacksHome/ExogeniRacks/SiteConfirmationTests

Version 5 (modified by lnevers@bbn.com, 7 years ago) (diff)

--

ExoGENI Site Confirmation Tests

As new ExoGENI sites are deployed, the GPO will complete a series of ExoGENI (EG) Site Confirmation Tests (CT) to validate the installation. These confirmation tests verify access to network and compute resources at the newly installed ExoGENI site, as well as the ability to monitor the site. 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.

EG-CT-1 - Access to rack VM resources

This ExoGENI Confirmation Test, EG-CT-1, will create a sliver at the site ExoGENI aggregate which includes 4 VMs at the site. VMs will be used to exchange traffic. Resources will be released upon completion of the test. Following is the sequence of AM 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.
  2. List resources at the New Site SM to determine available resources for experiment. Write RSpec.
  3. Create slice, and then createsliver at New Site aggregate requesting 4 VMs.
  4. Login to compute resources allocated to the sliver and exchange traffic.
  5. Renew sliver at New Site and verify expiration changes.
  6. Delete sliver, and verify that resources are released by checking listresources available details.

EG-CT-2 - Access to rack bare metal and VM resources

This confirmation test will create a sliver at the ExoSM requesting a 1 baremetal node and 1 VM at the new ExoGENI site. The VM and bare metal resources will be used to exchange traffic. Slivers will be deleted upon completions. 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 resources for experiment. Write RSpec.
  2. Create slice, and createsliver at site aggregate requesting 1 VM and 1 bare metal at he site.
  3. Login to resources allocated to the sliver and exchange traffic.
  4. Delete sliver, and verify that resources are released by checking listresources available details.

EG-CT-3 - Multiple sites experiment

This confirmation test will create a sliver at the New ExoGENI 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 ExoGENI Rack:

  1. List resources at the ExoSM to determine available resources for experiment at GPO ExoGENI and at New ExoGENISite. Write RSpecs.
  2. Create slice, and createsliver at site aggregate requesting 1 VM and 1 bare metal at the site.
  3. Login to resources allocated to the sliver and exchange traffic.
  4. Delete sliver, and verify that resources are released by checking listresources available details.

EG-CT-4 - Multiple sites OpenFlow experiment

This confirmation test will create a sliver at the New ExoGENI 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 ExoGENI Rack:

  1. List resources at the ExoSM to determine available resources at GPO ExoGENI and at New Site ExoGENI. Write compute resources RSpecs.
  2. List resources at the ExoGENI New Site FOAM, at GPO ExoGENI FOAM, and at each intermediate FOAM aggregate to determine available resources. Write RSpecs.
  3. Create slice, and createsliver at FOAM aggregate.
  4. Create sliver at the GPO ExoGENI and the New Site ExoGENI compute resource aggregate requesting 1 VM at each site.
  5. Login to compute resources allocated to the sliver and exchange traffic.
  6. Delete sliver, and verify that resources are released by checking listresources available details.

EG-CT-5 - Monitoring the experiments

While the each of the above experiments are being run, available GMOC monitoring will be reviewed to ensure accuracy. For more details about the available monitoring features see <<<INSERT_LINK_HERE>>

Attachments (4)

Download all attachments as: .zip