Changes between Version 1 and Version 2 of GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-MON-5


Ignore:
Timestamp:
02/26/13 20:54:25 (6 years ago)
Author:
chaos@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIRacksHome/ExogeniRacks/AcceptanceTestStatus/EG-MON-5

    v1 v2  
    77== Status of test ==
    88
    9 || '''Step''' || '''State'''           || '''Date completed''' || '''Open Tickets''' || '''Closed Tickets/Comments''' ||
     9|| '''Step''' || '''State''' || '''Date completed''' || '''Open Tickets''' || '''Closed Tickets/Comments''' ||
     10|| 1A         ||             ||                      ||                    ||                               ||
     11|| 1B         ||             ||                      ||                    ||                               ||
     12|| 2A         ||             ||                      ||                    ||                               ||
     13|| 2B         ||             ||                      ||                    ||                               ||
     14|| 3          ||             ||                      ||                    ||                               ||
     15|| 4          ||             ||                      ||                    ||                               ||
     16|| 5          ||             ||                      ||                    ||                               ||
     17|| 6          ||             ||                      ||                    ||                               ||
     18|| 7          ||             ||                      ||                    ||                               ||
    1019
    1120== High-level description from test plan ==
     
    4352=== Step 1A: download GMOC relational data objects for BBN and RCI racks ===
    4453
     54==== Overview of Step 1A ====
     55
    4556Within a python shell on a node which has gmoc.py installed and configured with a valid submission username:
    4657{{{
     
    7586=== Step 1B: download recent GMOC measurement data as XML ===
    7687
     88==== Overview of Step 1B ====
     89
    7790Pretty-print the most recent XML measurement data download from GMOC:
    7891{{{
     
    8699}}}
    87100This should yield an XML file, `recent-gmoc.xml`.
     101
     102== Step 2: verify AM reachability data ==
     103
     104=== Step 2A: verify GPO remote testing of AMs ===
     105
     106==== Overview of step 2A ====
     107
     108 * Look in recent-gmoc.xml for data reported by ashur.gpolab.bbn.com containing these tests:
     109   * geni_am_getversion
     110   * geni_am_listresources
     111   for these hosts:
     112   * rci-hn.exogeni.net ORCA
     113   * rci-hn.exogeni.net FOAM
     114   * bbn-hn.exogeni.gpolab.bbn.com ORCA
     115   * bbn-hn.exogeni.gpolab.bbn.com FOAM
     116 * Make sure each test has recent data (some non-null values)
     117
     118=== Step 2B: verify aggregate self-reporting of any data ===
     119
     120==== Overview of step 2B ====
     121
     122In the python shell:
     123{{{
     124print rcixo.last_updated
     125print rcifoam.last_updated
     126print bbnxo.last_updated
     127print bbnfoam.last_updated
     128}}}
     129Each of those dates should be a recent timestamp.
     130
     131== Step 3: verify rack compute resource reporting ==
     132
     133Fill in details of how to determine:
     134 * Is each compute or unbound VLAN resource at each rack AM online? Is it available or in use?
     135 * Is each rack worker node online?
     136 * For each rack worker node configured as an OpenStack VM server, overall CPU, disk, and memory utilization for the host, current VM count and total VM capacity of the host.
     137 * Is the rack data plane switch online?
     138
     139== Step 4: verify ORCA aggregate sliver reporting ==
     140
     141Fill in details of how to determine:
     142 * Sliver count and percentage of compute and unbound VLAN resources in use for the rack SM.
     143 * Identities of current slivers on each rack AM, including creation time for each.
     144
     145== Step 5: verify interface counter reporting ==
     146
     147Fill in details of how to determine:
     148 * Per-sliver interface counters for compute and VLAN resources (where these values can be easily collected).
     149 * Interface counters and VLAN memberships for each rack data plane switch interface
     150 * MAC address table contents for shared VLANs which appear on rack data plane switches
     151 * For each rack worker node configured as an OpenStack VM server, interface counters for each data plane interface.
     152
     153== Step 6: verify end-to-end health check ==
     154
     155 * Results of at least one end-to-end health check which simulates an experimenter reserving and using at least one resource in the rack.
     156
     157== Step 7: verify distinct user summarization ==
     158
     159Verify that per-rack or per-aggregate summaries are collected of the count of distinct users who have been active on the rack, either by providing raw sliver data containing sliver users to GMOC, or by collecting data locally and producing trending summaries on demand.