Changes between Version 6 and Version 7 of GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-MON-2

03/05/13 15:26:38 (8 years ago)



  • GENIRacksHome/InstageniRacks/AcceptanceTestStatus/IG-MON-2

    v6 v7  
    33= Detailed test plan for IG-MON-2: GENI Software Configuration Inspection Test =
    5 ''This page is GPO's working page for performing IG-MON-2.  It is public for informational purposes, but it is not an official status report.  See [wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus] for the current status of InstaGENI acceptance tests.''
     5This page captures status for the test case IG-MON-2, which verifies the ability to determine software configuration in the InstaGENI racks. For overall status see the [wiki:GENIRacksHome/InstageniRacks/AcceptanceTestStatus InstaGENI Acceptance Test Status] page.
    7 ''Last substantive edit of this page: 2012-07-08''
     7''Last update: 2013-03-05''
    9 == Page format ==
    11  * The status chart summarizes the state of this test
    12  * The high-level description from test plan contains text copied exactly from the public test plan and acceptance criteria pages.
    13  * The steps contain things i will actually do/verify:
    14    * Steps may be composed of related substeps where i find this useful for clarity
    15    * Each step is either a preparatory step (identified by "(prep)") or a verification step (the default):
    16      * Preparatory steps are just things we have to do.  They're not tests of the rack, but are prerequisites for subsequent verification steps
    17      * Verification steps are steps in which we will actually look at rack output and make sure it is as expected.  They contain a '''Using:''' block, which lists the steps to run the verification, and an '''Expect:''' block which lists what outcome is expected for the test to pass.
     10== Test Status ==
    19 == Status of test ==
     12|| '''Step''' || '''State'''           ||  '''Tickets''' || '''Notes'''                        ||
     13|| 1          || [[Color(green,Pass)]] ||                ||                                                                 ||
     14|| 2          ||                       ||                || ready to test now that !OpenFlow and shared VLANs are available ||
     15|| 3          ||                       ||                || ready to test now that FOAM is available                        ||
     16|| 4          ||                       ||                || ready to test now that FOAM is available                        ||
    21 || '''Step''' || '''State'''           || '''Date completed''' || '''Open Tickets''' || '''Closed Tickets/Comments'''                                   ||
    22 || 1          || [[Color(green,Pass)]] || 2012-05-17           ||                    ||                                                                 ||
    23 || 2          ||                       ||                      ||                    || ready to test now that !OpenFlow and shared VLANs are available ||
    24 || 3          ||                       ||                      ||                    || ready to test now that FOAM is available                        ||
    25 || 4          ||                       ||                      ||                    || ready to test now that FOAM is available                        ||
     19|| '''State Legend'''                     || '''Description'''                                                    ||
     20|| [[Color(green,Pass)]]                  || Test completed and met all criteria                                  ||
     21|| [[Color(#98FB98,Pass: most criteria)]] || Test completed and met most criteria. Exceptions documented          ||
     22|| [[Color(red,Fail)]]                    || Test completed and failed to meet criteria.                          ||
     23|| [[Color(yellow,Complete)]]             || Test completed but will require re-execution due to expected changes ||
     24|| [[Color(orange,Blocked)]]              || Blocked by ticketed issue(s).                                        ||
     25|| [[Color(#63B8FF,In Progress)]]         || Currently under test.                                                ||
    27 == High-level description from test plan ==
    29 This test inspects the state of the GENI AM software in use on the rack.
    31 === Procedure ===
    33  * A site administrator uses available system data sources (process listings, monitoring output, system logs, etc) and/or AM administrative interfaces to determine the configuration of InstaGENI resources:
    34    * How many experimental nodes are available for bare metal use, how many are configured as OpenVZ containers, and how many are configured as !PlanetLab containers.
    35    * What operating system each OpenVZ container makes available for experimental VMs.
    36    * How many unbound VLANs are in the rack's available pool.
    37    * Whether the ProtoGENI and FOAM AMs trust the slice authority, which will be used for testing.
    38  * A site administrator uses available system data sources to determine the configuration of !OpenFlow resources according to FOAM, InstaGENI, and !FlowVisor.
    40 === Criteria to verify as part of this test ===
    42  * VI.12. A public document describes all the GENI experimental resources within the rack, and explains what policy options exist for each, including: how to configure rack nodes as bare metal vs. VM server, what options exist for configuring automated approval of compute and network resource requests and how to set them, how to configure rack aggregates to trust additional GENI slice authorities, whether it is possible to trust local users within the rack. (F.7)
    43  * VI.13. A public document describes the expected state of all the GENI experimental resources in the rack, including how to determine the state of an experimental resource and what state is expected for an unallocated bare metal node. (F.5)
    44  * VII.11. A site administrator can locate current configuration of flowvisor, FOAM, and any other OpenFlow services, and find logs of recent activity and changes. (D.6.a)
     28= Test Plan Steps =
    4630== Step 1: determine experimental node allocations ==
    48 '''Using:'''
     32This step will verify the ability to determine VM in use as well as VMs available as follows:
    4934 * On boss and ops, use available system data sources (process listings, monitoring output, system logs, etc) and/or AM administrative interfaces (Emulab UI, testbed database) to determine the experimental state of each node.
    5035 * For each OpenVZ node found, determine what operating system that node makes available to users.
    52 '''Verify:'''
    53  * The site administrator can determine how many nodes are allocated for OpenVZ or !PlanetLab use, and how many are available for experimental use, right now.
     37As a site admin login to, select "red dot" mode and select pulldown "Experimentation"->"Node Status", which will show this page:
    55 === Results of testing step 1: 2012-05-17 ===
     39[Image (IG-MON-2-nodes.jpg)]].
    57  * As a site admin:
    58    * Browse to []
    59    * Login
    60    * Enter red dot mode
    61    * The white dots in the "Up?" column and lack of Name/PID/EID info show that pc1, pc2, and pc4 are available for experimenter use, and are not in use right now
    62    * pc3 and pc5 are in use.  Of these:
    63      * pc5 is in an special experiment, `emulab-ops/shared-nodes`, and is running the OS `FEDORA15-OPENVZ-STD`.  It's a reasonable guess that this is the OpenVZ shared node, which provides Fedora 15 VMs to experimenters.  Browsing to [], corroborate that by finding the setting:
    64 {{{
    65 tb-set-node-sharingmode $vhost1 "shared_local"
    66 }}}
    67      * pc3 is not special.  It is an experimental node which is in use.
    68    * Thus, a site admin can learn that the current allocation is 1 OpenVZ node, 0 !PlanetLab nodes, and 4 experimental nodes.
    69  * As an experimenter, run:
    70 {{{
    71 omni -a listresources -o
    72 }}}
    73  and view the output.  Learn the following things:
    74    * the node entry for pc3 has a field showing it's unavailable (this is "true" for e.g. pc1):
    75 {{{
    76        <available now="false"/>   
    77 }}}
    78    * the node entry for pc5 contains these lines (10034 is the OSID for FEDORA15-OPENVZ-STD, though i don't know how you'd know that as an experimenter.  But "pcshared" seems like a clue):
    79 {{{
    80        <emulab:fd name="pcshared" violatable="true" weight="1.0"/>   
    81        <emulab:fd name="OS-10034" weight="0.5"/>   
    82 }}}
    83    * also, the node entry for pc5 contains 49 slots of type "pcvm", whereas the other nodes contain 50.  I bet that is a clue to how many VMs pc5 thinks it can run, since i have one VM allocated on there right now (that is, i bet pc5 thinks it can allocate 50 VMs):
    84 {{{
    85       <hardware_type name="pcvm">
    86           <emulab:node_type type_slots="49"/>
    87       </hardware_type>
    88 }}}
     41On the resulting page select "physical" from the tabular view listing across the top of the panel. This will show all physical systems in the rack, along with the OS running on those nodes.
     45The above shows:
     46 * pc3 is in used by an experiment (EID) named "jbstmp"
     47 * pc4 and pc5 are available
     48 * pc1 and pc2 are part of the "shared-nodes" experiment used to reserve the PCs that provide VMs.
     50To determine what VMs are in use, while still in the Experimentation"->"Node Status" page (in red dot mode) select "virtual" from the tabular view across the top of the panel, which will provide a list of VMs in use in the rack:
    9055== Step 2: determine rack VLAN configuration ==