Changes between Version 8 and Version 9 of GENIRacksHome/InstageniRacks/SiteConfirmationTests


Ignore:
Timestamp:
10/30/12 16:37:19 (7 years ago)
Author:
hdempsey@bbn.com
Comment:

minor wording changes

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/InstageniRacks/SiteConfirmationTests

    v8 v9  
    33= InstaGENI New Site Confirmation Tests =
    44
    5 As 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.
    6 Also this tests may replace the GPO InstaGENI rack with the Utah InstaGENI rack if needed.
     5As 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 some basic adminstrative capabilities.  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 these tests may replace the GPO InstaGENI rack with the Utah InstaGENI rack if needed.
    77
    88
     
    1111This 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:
    1212
    13  1. Get AM API version, verify that orca_version is same or newer than existing racks.
     13 1. Get AM API version, verify that ProtoGENI_version is same or newer than existing racks.
    1414 2. List resources at the New Site SM to determine available resources for experiment. Write RSpec.
    1515 3. Create slice, and then createsliver at New Site aggregate requesting 4 VMs.
     
    2020== IG-CT-2 - Access to New Site raw pc and VM resources ==
    2121
    22 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:
     22This confirmation test will create a sliver at the Aggregate Manager requesting a 1 bare metal 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 completion.  Following is the sequence of AM operations for this test at the new InstaGENI Rack:
    2323
    2424 1. List resources at the Aggregate Manager to determine VM and raw pc available resources for experiment. Write RSpec.
     
    3838== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
    3939
    40 This confirmation test will create a sliver at the New InstaGENI Site with 1 VM on shared VLAN 1750. This New Site sliver will inter-operate with !OpenFlow slivers that include: a Meso-scale site, an ExoGENI site, and an Emulab !OpenFlow node.  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:
     40This confirmation test will create a sliver at the New InstaGENI Site with 1 VM on shared VLAN 1750. This New Site sliver will inter-operate with !OpenFlow slivers that include: a Meso-scale site, an ExoGENI site, and an Emulab !OpenFlow node.  All nodes will exchange traffic and slivers will be deleted upon completion.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
    4141
    4242 1. List resources at the Aggregate Manager to determine available compute resources at GPO InstaGENI, New Site InstaGENI, Meso-scale site, ExoGENI 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.
     
    6363 2d. Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics, OF Datapath and Sliver Statistics.    [[BR]]
    6464
    65 Note that monitoring tests will verify the New Site's ability to report status monitoring data to GMOC and to validate monitoring features as they exists at the time of site deployment.  More details about available monitoring features can be found at <<<INSERT_LINK_HERE>>
     65Note that monitoring tests will 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 can be found at <<<INSERT_LINK_HERE>>
    6666
    6767
    6868== IG-CT-6 - Administrative Tests ==
    6969
    70 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.
     70Confirmation Tests will be 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.
    7171
    7272As a GPO Admin user, the following administrative tasks will be verified:
    73  1. Access to each rack node (head node and worker nodes) via control network interface with SSH and execute a sudo command.
     73 1. Access each rack node (head node and worker nodes) via control network interface with SSH and execute a sudo command.
    7474 2. Access infrastructure devices such as  switches, remote PDU, and other components via control network interface with SSH.
    7575 3. Access remote console for all rack hosts.