wiki:GENIRacksHome/OpenGENIRacks/SiteConfirmationTests

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

--

OpenGENI New Site Confirmation Tests

Upon completion of the GENI Rack Site Installation Checklist for new OpenGENI sites, the GPO will also complete a series of OpenGENI (OG) Site Confirmation Tests (CT) to validate features for the newly deployed site. These confirmation tests verify experimenter access to network and compute resources at the newly installed OpenGENI 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 OpenGENI New Site Confirmation Tests Status page for details about sites that have been tested.

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

The OpenGENI Confirmation Test OG-CT-1 creates a sliver at the New Site OpenGENI 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:

Following is the sequence of operations for this test at the new OpenGENI Rack:

  1. Get AM API version, verify that GRAM version is same or newer than existing racks.
  2. List resources at the New Site AM to determine available resources for use in this experiment. Write resource RSpec requesting 4 VMs.
  3. Create a slice named OG-CT-1, and then create sliver at New Site aggregate requesting the 4 VMs.
  4. When "ready", determine allocated hostnames. Using using a DNS server outside the aggregate, use dig command to check whether if the authoritative name servers are answering for the given domain.
  5. Login to the compute resources allocated and collect iperf UDP, TCP and ping statistics.
  6. Delete sliver and verify that resources are released by checking listresources details.

OG-CT-2 - Access to New Site Raw PC and VM resources

NOTE: This test cannot be executed because there are no Bare Metal nodes in OpenGENI racks at this time

This confirmation test creates a sliver at the Aggregate Manager requesting a one raw pc node and one VM at the new OpenGENI site. The VM and raw pc resources are used to exchange traffic. Slivers are deleted upon completion. The test topology used:

Following is the sequence of AM operations for this test at the new OpenGENI Rack:

  1. List resources at the Aggregate Manager to determine VM and PC available resources for experiment. Write RSpec.
  2. Create slice, and create sliver at site aggregate requesting 1 VM and 1 raw pc at the site.
  3. Login to each of the resources allocated and collect iperf UDP, TCP and ping statistics.
  4. Delete sliver and verify that resources are released by checking listresources available details.

OG-CT-3 - Multiple sites experiment

This confirmation test creates a stitched sliver at the New OpenGENI Site and one sliver at the GPO requesting 1 VM at each aggregate. The VMs exchange traffic and slivers are deleted upon completions. The test topology used:

Following is the sequence of AM operations for this test at each OpenGENI Rack:

  1. List resources at the Aggregate Managers to determine available resources for experiment at GPO OpenGENI and at New OpenGENI Site. Write RSpecs.
  2. Create slice and create slivers at each site aggregate requesting 1 VM.
  3. Login to each of the resources allocated and collect iperf UDP, TCP and ping statistics.
  4. Delete slivers and verify that resources are released by checking listresources available details.

OG-CT-4 - Multiple sites OpenFlow experiment and interoperability

Note: Network stitching tests will be used to set up the underlying connections in this test.

This confirmation test creates a stitched sliver at the New OpenGENI Site with VMs and an OpenFlow controller definition in the Request RSpec. This New Site sliver inter-operates with OpenFlow slivers that include: an ExoGENI site, an InstaGENI site and Clemson and GPO OpenGENI sites. Each of the VMs exchange traffic, and slivers are deleted upon completion. The test topology used is shown here:

Following is the sequence of AM operations for this test at each OpenGENI Rack:

  1. List resources at all Aggregate Managers to determine available resources. Write resources RSpecs for all aggregates.
  2. Create slice and create slivers at each aggregates.
  3. Login to each of the compute resources at New Site OpenGENI and collected iperf TCP, UDP and ping statistics between all end-points.
  4. Delete slivers and verify that resources are released by checking listresources available details.

OG-CT-5 - Experiment Monitoring

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

NOTE: THESE TESTS STEPS WILL BE REPLACE WHEN OPS MONITORING IS AVAILABLE

  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.

Note that monitoring tests verify the New Site's ability to report status monitoring data to GMOC and to validate monitoring features as they exist at the time of site deployment. More details about available monitoring features will be linked to this page as they develop.

OG-CT-6 - Administrative Tests

Confirmation Tests are also executed for administrative tasks by GPO staff. These tests assume that the GPO staff have 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 are verified:

  1. Access each rack node (control node and experiment 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.

Email help@geni.net for GENI support or email me with feedback on this page!

Attachments (4)

Download all attachments as: .zip