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


Ignore:
Timestamp:
08/25/14 09:04:10 (7 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/OpenGENIRacks/SiteConfirmationTests

    v1 v1  
     1[[PageOutline]]
     2
     3= OpenGENI New Site Confirmation Tests =
     4
     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 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.
     6
     7
     8== OG-CT-1 - Access to New Site VM resources ==
     9
     10The 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:
     11
     12[[Image(OG-CT-1.jpg)]]
     13
     14Following is the sequence of operations for this test at the new OpenGENI Rack:
     15
     16 1. Get AM API version, verify that ProtoGENI_version is same or newer than existing racks.
     17 2. List resources at the New Site AM to determine available resources for use in this experiment. Write resource RSpec requesting 4 VMs.
     18 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.
     23
     24''Note'': This test originally used OpenVZ VM, but after the introduction of Xen VM support all VMs were modified to Xen.
     25 
     26== OG-CT-2 - Access to New Site Raw PC and VM resources ==
     27
     28This 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:
     29
     30[[Image(OG-CT-2.jpg)]]
     31
     32Following is the sequence of AM operations for this test at the new OpenGENI Rack:
     33
     34 1. List resources at the Aggregate Manager to determine VM and raw pc available resources for experiment. Write RSpec.
     35 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.
     37 4. Delete sliver and verify that resources are released by checking listresources available details.
     38
     39== OG-CT-3 - Multiple sites experiment  ==
     40
     41This 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:
     42
     43[[Image(OG-CT-3.jpg)]]
     44
     45Depending on the site, there may also be regional networks in the path from the site to Internet2 or NLR included in the test.
     46
     47Following is the sequence of AM operations for this test at each OpenGENI Rack:
     48
     49 1. List resources at the Aggregate Managers to determine available resources for experiment at GPO OpenGENI and at New OpenGENI Site. Write RSpecs.
     50 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.
     52 4. Delete slivers and verify that resources are released by checking listresources available details.
     53
     54== OG-CT-4 - Multiple sites !OpenFlow experiment and interoperability ==
     55
     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.''
     57
     58This 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:
     59
     60[[Image(OG-CT-4.jpg)]]
     61
     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
     67Following is the sequence of AM operations for this test at each OpenGENI Rack:
     68
     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
     77
     78== OG-CT-5 - Experiment Monitoring ==
     79
     80While 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:
     81
     82'''NOTE: THESE TESTS STEPS WILL BE REPLACE WHEN OPS MONITORING IS AVAILABLE'''
     83
     84 1. New Site compute resources aggregate show up in the list of aggregates and provides the following details:   [[BR]]
     85 1a. Aggregate Name, Type, Last Update, Version, POP, and Organization.   [[BR]]
     86 1b. List of active slivers.   [[BR]]
     87 1c. List of Resources.   [[BR]]
     88 1d. Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics.   [[BR]]
     89 2. New Site FOAM resources aggregate show up in the list of aggregates and provides the following details:  [[BR]]
     90 2a. Aggregate Name, Type, Last Update, Version, POP, and Organization.  [[BR]]
     91 2b. List of active slivers.  [[BR]]
     92 2c. List of Resources.    [[BR]]
     93 2d. Aggregate measurement for CPU utilization, Disk Utilization, Network Statistics, OF Datapath and Sliver Statistics.    [[BR]]
     94
     95Note 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.
     96
     97== OG-CT-6 - Administrative Tests ==
     98
     99Confirmation 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.
     100
     101As a GPO Admin user, the following administrative tasks are verified:
     102 1. Access each rack node (control node and experiment nodes) via control network interface with SSH and execute a sudo command.
     103 2. Access infrastructure devices such as  switches, remote PDU, and other components via control network interface with SSH.
     104 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>)
     111----
     112{{{
     113#!html
     114Email <a href="mailto:help@geni.net"> help@geni.net </a> for GENI support or email <a href="mailto:luisa.nevers@bbn.com">me</a> with feedback on this page!
     115}}}