Changes between Version 12 and Version 13 of GENIRacksHome/InstageniRacks/SiteConfirmationTests


Ignore:
Timestamp:
10/31/12 13:46:54 (11 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GENIRacksHome/InstageniRacks/SiteConfirmationTests

    v12 v13  
    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 some basic administrative capabilities.  The experiments defined for the Confirmation Tests assume that Omni tools are used for all AM API operations.  Also these tests may replace the GPO InstaGENI rack with the Utah InstaGENI rack if needed.
     5As new InstaGENI sites are deployed to campuses, the GPO will 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.
    66
    77
    88== IG-CT-1 - Access to New Site VM resources ==
    99
    10 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:
     10The InstaGENI Confirmation Test IG-CT-1 creates a sliver at the New Site InstaGENI 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.  Following is the sequence of operations for this test at the new InstaGENI Rack:
    1111
    1212 1. Get AM API version, verify that ProtoGENI_version is same or newer than existing racks.
    13  2. List resources at the New Site SM to determine available resources for experiment. Write RSpec.
    14  3. Create slice, and then create sliver at New Site aggregate requesting 4 VMs.
    15  4. Login to compute resources allocated to the sliver and exchange traffic.
    16  5. Renew sliver at New Site and verify expiration changes.
    17  5. Delete sliver, and verify that resources are released by checking listresources available details.
     13 2. List resources at the New Site AM to determine available resources for use in this experiment. Write resource RSpec requesting 4 VMs.
     14 3. Create a slice named IG-CT-1, and then create sliver at New Site aggregate requesting the 4 VMs.
     15 4. Login to each of the compute resources allocated to the sliver and exchange ping traffic to verify connectivity.
     16 5. Renew slice and sliver. Verify expiration changes.
     17 6. Delete sliver and verify that resources are released by checking listresources details.
    1818 
    1919== IG-CT-2 - Access to New Site raw pc and VM resources ==
    2020
    21 This confirmation test will create a sliver at the Aggregate Manager requesting a 1 raw pc 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:
     21This confirmation test creates a sliver at the Aggregate Manager requesting a one raw pc node and one VM at the new InstaGENI site. The VM and raw pc resources are used to exchange traffic. Slivers are deleted upon completion.  Following is the sequence of AM operations for this test at the new InstaGENI Rack:
    2222
    2323 1. List resources at the Aggregate Manager to determine VM and raw pc available resources for experiment. Write RSpec.
    24  2. Create slice, and create sliver at site aggregate requesting 1 VM and 1 raw pc at he site.
    25  3. Login to resources allocated to the sliver and exchange traffic.
    26  4. Delete sliver, and verify that resources are released by checking listresources available details.
     24 2. Create slice, and create sliver at site aggregate requesting 1 VM and 1 raw pc at the site.
     25 3. Login to each of the resources allocated to the sliver and exchange traffic.
     26 4. Delete sliver and verify that resources are released by checking listresources available details.
    2727
    2828== IG-CT-3 - Multiple sites experiment  ==
    2929
    30 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 exchange traffic and slivers will be deleted upon completions.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
     30This confirmation test creates a sliver at the New InstaGENI Site and one sliver at the GPO requesting 1 VM at each aggregate. The VMs exchange traffic and slivers are deleted upon completions.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
    3131
    32  1. List resources at the Aggregate Managers to determine available resources for experiment at GPO InstaGENI and at New InstaGENISite. Write RSpecs.
    33  2. Create slice, and create slivers at each site aggregate requesting 1 VM.
    34  3. Login to resources allocated to the slivers and exchange traffic.
    35  4. Delete slivers, and verify that resources are released by checking listresources available details.
     32 1. List resources at the Aggregate Managers to determine available resources for experiment at GPO InstaGENI and at New InstaGENI Site. Write RSpecs.
     33 2. Create slice and create slivers at each site aggregate requesting 1 VM.
     34 3. Login to each of the resources allocated to the slivers and exchange traffic.
     35 4. Delete slivers and verify that resources are released by checking listresources available details.
    3636
    3737== IG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
    3838
    39 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 completion.  Following is the sequence of AM operations for this test at each InstaGENI Rack:
     39This confirmation test creates a sliver at the New InstaGENI Site with one VM on shared VLAN 1750. This New Site sliver inter-operates with !OpenFlow slivers that include: a Meso-scale site, an ExoGENI site, and a PG Utah !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:
    4040
    41  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.
    42  2. List resources at the intermediate FOAM aggregates and at Meso-scale aggregate to determine available resources.  Write remaining RSpecs.
    43  2. Create slice, and create slivers at core, ExoGENI and Meso-scale FOAM aggregates.
    44  3. Create slivers at the GPO, Emulab, and New Site InstaGENI aggregate requesting 1 shared VLAN VM at each site.
     41 1. List resources at the Aggregate Managers to determine available resources at GPO InstaGENI, New Site InstaGENI, Meso-scale site, ExoGENI Site, and at the PG Utah site. Write  resources RSpecs requesting shared nodes at InstaGENI and PG Utah aggregates. Write compute resource RSpec to request nodes at Meso-scale site.
     42 2. List resources at the intermediate core FOAM aggregates and at Meso-scale aggregate to determine available resources.  Write remaining RSpecs.
     43 2. Create slice and create slivers at core aggregates, ExoGENI, and Meso-scale FOAM aggregates.
     44 3. Create slivers at the GPO InstaGENI, PG Utah, and New Site InstaGENI aggregate requesting 1 shared VLAN VM at each site.
    4545 4. Create compute resource sliver at Meso-scale site.
    46  5. Login to compute resources at New Site InstaGENI, GPO InstaGENI, Emulab, ExoGENI, and Meso-scale sites and exchange traffic with each of the other remotes.
    47  6. Delete slivers, and verify that resources are released by checking listresources available details.
     46 5. Login to each of the compute resources at New Site InstaGENI, GPO InstaGENI, Emulab, ExoGENI, and Meso-scale sites and exchange traffic with each of the other remotes.
     47 6. Delete slivers and verify that resources are released by checking listresources available details.
    4848
    4949== IG-CT-5 - Experiment Monitoring ==
    5050
    51 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 [https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl GMOC monitoring] site for the new Site:
     51While 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 [https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl GMOC monitoring] site for the new Site:
    5252
    5353 1. New Site compute resources aggregate show up in the list of aggregates and provides the following details:   [[BR]]
    … …  
    6262 2d. Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics, OF Datapath and Sliver Statistics.    [[BR]]
    6363
    64 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 exist at the time of site deployment.  More details about available monitoring features can be found at <<<INSERT_LINK_HERE>>
     64Note 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 can be found at <<<INSERT_LINK_HERE>>
    6565
    6666
    6767== IG-CT-6 - Administrative Tests ==
    6868
    69 Confirmation 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.
     69Confirmation 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.
    7070
    71 As a GPO Admin user, the following administrative tasks will be verified:
     71As a GPO Admin user, the following administrative tasks are verified:
    7272 1. Access each rack node (head node and worker nodes) via control network interface with SSH and execute a sudo command.
    7373 2. Access infrastructure devices such as  switches, remote PDU, and other components via control network interface with SSH.