Changes between Version 1 and Version 2 of GENIRacksHome/OpenGENIRacks/SiteConfirmationTests


Ignore:
Timestamp:
08/25/14 09:36:21 (5 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/OpenGENIRacks/SiteConfirmationTests

    v1 v2  
    33= OpenGENI New Site Confirmation Tests =
    44
    5 Upon completion of the [wiki:GENIRacksHome/RacksChecklist 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 Meso-scale specific 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.  Also some tests may replace the GPO OpenGENI rack with the Utah OpenGENI rack if needed. See the '''[wiki:GENIRacksHome/OpenGENIRacks/ConfirmationTestStatus OpenGENI New Site Confirmation Tests Status]''' page for details about sites that have been tested.
     5Upon completion of the [wiki:GENIRacksHome/RacksChecklist 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 '''[wiki:GENIRacksHome/OpenGENIRacks/ConfirmationTestStatus OpenGENI New Site Confirmation Tests Status]''' page for details about sites that have been tested.
    66
    77
     
    1414Following is the sequence of operations for this test at the new OpenGENI Rack:
    1515
    16  1. Get AM API version, verify that ProtoGENI_version is same or newer than existing racks.
     16 1. Get AM API version, verify that GRAM version is same or newer than existing racks.
    1717 2. List resources at the New Site AM to determine available resources for use in this experiment. Write resource RSpec requesting 4 VMs.
    1818 3. Create a slice named OG-CT-1, and then create sliver at New Site aggregate requesting the 4 VMs.
    19  4. Wait for the sliver to reach the "ready" state. Immediately after it reaches the ready state, determine allocated hostname. 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.
    20  5. Login to each of the compute resources allocated to the sliver and exchange ping traffic to verify connectivity.
    21  6. Renew slice and sliver. Verify expiration changes.
    22  7. Delete sliver and verify that resources are released by checking listresources details.
     19 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.
     20 5. Login to the compute resources allocated  and collect iperf UDP, TCP and ping statistics.
     21 6. Delete sliver and verify that resources are released by checking listresources details.
    2322
    24 ''Note'': This test originally used OpenVZ VM, but after the introduction of Xen VM support all VMs were modified to Xen.
    2523 
    2624== OG-CT-2 - Access to New Site Raw PC and VM resources ==
     25
     26'''NOTE: This test cannot be executed because there are no Bare Metal nodes in OpenGENI racks at this time'''
    2727
    2828This 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:
     
    3232Following is the sequence of AM operations for this test at the new OpenGENI Rack:
    3333
    34  1. List resources at the Aggregate Manager to determine VM and raw pc available resources for experiment. Write RSpec.
     34 1. List resources at the Aggregate Manager to determine VM and PC available resources for experiment. Write RSpec.
    3535 2. Create slice, and create sliver at site aggregate requesting 1 VM and 1 raw pc at the site.
    36  3. Login to each of the resources allocated to the sliver and exchange traffic.
     36 3. Login to each of the resources allocated and collect iperf UDP, TCP and ping statistics.
    3737 4. Delete sliver and verify that resources are released by checking listresources available details.
    3838
    3939== OG-CT-3 - Multiple sites experiment  ==
    4040
    41 This confirmation test creates a 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:
     41This 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:
    4242
    4343[[Image(OG-CT-3.jpg)]]
    44 
    45 Depending on the site, there may also be regional networks in the path from the site to Internet2 or NLR included in the test.
    4644
    4745Following is the sequence of AM operations for this test at each OpenGENI Rack:
     
    4947 1. List resources at the Aggregate Managers to determine available resources for experiment at GPO OpenGENI and at New OpenGENI Site. Write RSpecs.
    5048 2. Create slice and create slivers at each site aggregate requesting 1 VM.
    51  3. Login to each of the resources allocated to the slivers and exchange traffic.
     49 3. Login to each of the resources allocated  and collect iperf UDP, TCP and ping statistics.
    5250 4. Delete slivers and verify that resources are released by checking listresources available details.
    5351
    5452== OG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
    5553
    56 '' '''Note:'''  For sites not supporting Meso-scale, network stitching tests will be executed that use !OpenFlow.  See the [wiki:GeniNetworkStitchingConfirmationTests GENI Network Stitching Confirmation Tests]'' page for details.''
     54'' '''Note:'''  Network stitching tests will be used to set up the underlying connections in this test.
    5755
    58 This confirmation test creates a sliver at the New OpenGENI 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.  Each of the VMs exchange traffic, and slivers are deleted upon completion.   The test topology used is shown here:
     56This 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:
    5957
    6058[[Image(OG-CT-4.jpg)]]
    6159
    62 ''Note'':[[BR]]
    63 (1) This test originally used OpenVZ VM, after the introduction of Xen VM support all VMs were modified to Xen. In order to collect most reliable performance results, eventually the hosts were eventually modified to dedicated hosts (raw-pc).
    64 
    65 (2) Depending on the site, there may also be regional networks in the path from the site to the !OpenFlow core networks on Internet2 or NLR included in the test.  This note applies to all multi-site topologies used in the Site Confirmation Tests.
    66 
    6760Following is the sequence of AM operations for this test at each OpenGENI Rack:
    6861
    69  1. List resources at the Aggregate Managers to determine available resources at GPO OpenGENI, New Site OpenGENI, Meso-scale site, ExoGENI Site, and at the PG Utah site. Write  resources RSpecs requesting shared nodes at OpenGENI and PG Utah aggregates. Write compute resource RSpec to request nodes at Meso-scale site.
    70  2. List resources at the intermediate core FOAM aggregates and at Meso-scale aggregate to determine available resources.  Write remaining RSpecs.
    71  2. Create slice and create slivers at core aggregates, ExoGENI, and Meso-scale FOAM aggregates.
    72  3. Create slivers at the GPO OpenGENI, PG Utah, and New Site OpenGENI aggregate requesting 1 shared VLAN VM at each site.
    73  4. Create compute resource sliver at Meso-scale site.
    74  5. Login to each of the compute resources at New Site OpenGENI, GPO OpenGENI, Emulab, ExoGENI, and Meso-scale sites and exchange traffic with each of the other remotes.
    75  6. Delete slivers and verify that resources are released by checking listresources available details.
    76 
     62 1. List resources at all Aggregate Managers to determine available resources. Write resources RSpecs for all aggregates.
     63 2. Create slice and create slivers at each aggregates.
     64 3. Login to each of the compute resources at New Site OpenGENI and collected iperf TCP, UDP and ping statistics between all end-points.
     65 4. Delete slivers and verify that resources are released by checking listresources available details.
    7766
    7867== OG-CT-5 - Experiment Monitoring ==
     
    10392 2. Access infrastructure devices such as  switches, remote PDU, and other components via control network interface with SSH.
    10493 3. Access remote console for all rack hosts.
    105  4. Check FOAM version installed (admin:get-version)
    106  5. Check FOAM configuration (config:get-value) show that certain parameters are set, such as site.admin.email, geni.site-tag, email.from, others.
    107  6. Execute FOAM commands to show sliver details
    108  7. Check !FlowVisor version installed
    109  8. Verify !FlowVisor list of devices, active slices.
    110  9. Verify !FlowVisor setting (fvctl getConfig <some_param>)
     94
    11195----
    11296{{{