wiki:GENIRacksHome/InstageniRacks/SiteConfirmationTests

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

--

InstaGENI New Site Confirmation Tests

As new InstaGENI sites are deployed, the GPO will complete a series of InstaGENI (EG) 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.

IG-CT-1 - Access to New Site VM resources

This InstaGENI Confirmation Test, IG-CT-1, will create a sliver at the site InstaGENI 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 InstaGENI 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.

IG-CT-2 - Access to New Site raw pc and VM resources

This confirmation test will create a sliver at the Aggregate Manager requesting a 1 baremetal node and 1 VM at the new InstaGENI site. The VM and raw pc 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 InstaGENI Rack:

  1. List resources at the Aggregate Manager to determine VM and raw pc available resources for experiment. Write RSpec.
  2. Create slice, and createsliver at site aggregate requesting 1 VM and 1 raw pc 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.

IG-CT-3 - Multiple sites experiment

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:

  1. List resources at the Aggregate Manager to determine available resources for experiment at GPO InstaGENI and at New InstaGENISite. Write RSpecs.
  2. Create slice, and createsliver at each site aggregate requesting 1 VM.
  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.

IG-CT-4 - Multiple sites OpenFlow experiment

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:

  1. List resources at the Aggregate Manager to determine available resources at GPO InstaGENI and at New Site InstaGENI. Write compute resources RSpecs.
  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.
  3. Create slice, and createsliver at FOAM aggregate.
  4. Create sliver at the GPO InstaGENI and the New Site InstaGENI 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.

IG-CT-5 - Experiment Monitoring

While each of the above experiments are being run, GMOC monitoring will be reviewed to ensure accuracy. Monitoring tests will verify the following show up at the GMOC monitoring site for the new Site:

  1. New Site compute resources aggregate show up in the list of aggregates and provides the following details:
    1a. Aggregate Name, Type, Last Update, Version, POP, and Organization.
    1b. List of active slivers.
    1c. List of Resources.
    1d. Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics.
  2. New Site FOAM resources aggregate show up in the list of aggregates and provides the following details:
    2a. Aggregate Name, Type, Last Update, Version, POP, and Organization.
    2b. List of active slivers.
    2c. List of Resources.
    2d. Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics, OF Datapath and Sliver Statistics.

More details about available monitoring features can be found at <<<INSERT_LINK_HERE>>

IG-CT-6 - Administrative Tests

Confirmation Tests will be executed for administrative task by GPO staff. These tests assume that the GPO staff has administrative accounts on the newly deployed rack. GPO staff will report to the site about test results and existing GPO accounts.

As a GPO Admin user, the following administrative tasks will be verified:

  1. Access to each rack node (head node and worker nodes) via control network interface with SSH and execute a sudo command.
  2. Access infrastructure devices such as switches, remote PDU, and other components via control network interface with SSH.
  3. Access remote console for all rack hosts.
  4. Check FOAM version installed (admin:get-version)
  5. Check FOAM configuration (config:get-value) show that certain parameters are set, such as site.admin.email, geni.site-tag, email.from, others.
  6. Execute FOAM commands to show sliver details
  7. Check FlowVisor version installed
  8. Verify FlowVisor list of devices, active slices.
  9. Verify FlowVisor setting (fvctl getConfig <some_param>)

Attachments (6)

Download all attachments as: .zip