wiki:GENIRacksHome/OpenGENIRacks/AcceptanceTestStatusMay2013/OG-MON-5

Version 2 (modified by lnevers@bbn.com, 5 years ago) (diff)

--

OG-MON-5: GMOC Data Collection Test

This page captures status for the test case OG-MON-5. For additional information see the Acceptance Test Status - May 2013 page overall status, or the OpenGENI Acceptance Test Plan for details about the planned evaluation.

Last Update: 2013/05/14"

Step State Notes Tickets
Step 1 Fail No Monitoring data collection or reporting available
Step 2 Fail


State Legend Description
Pass Test completed and met all criteria
Pass: most criteria Test completed and met most criteria. Exceptions documented
Fail Test completed and failed to meet criteria.
Complete Test completed but will require re-execution due to expected changes
Blocked Blocked by ticketed issue(s).
In Progress Currently under test.

Test Steps

Evaluation Note: There is no GMOC Data Collection and no OpenGENI monitoring data reporting, unable to execute.

Step 1. Review GMOC Data Collection for OpenGENI aggregate

View the dataset collected at GMOC for the BBN and Site2 OpenGENI racks. For each piece of required data, attempt to verify that:

  • The data is being collected and accepted by GMOC and can be viewed at gmoc-db.grnoc.iu.edu
  • The data's "site" tag indicates that it is being reported for the OpenGENI rack located at the gpolab or OpenGENI site2 site (as appropriate for that rack).
  • The data has been reported within the past 10 minutes.
  • For each piece of data, either verify that it is being collected at least once a minute, or verify that it requires more complicated processing than a simple file read to collect, and thus can be collected less often.

Step 2. Review GMOC Data Reporting for OpenGENI aggregate

Verify that the following pieces of data are being reported:

  • Is each of the rack OpenGENI and VMOC AMs reachable via the GENI AM API right now?
  • Is each compute or unbound VLAN resource at each rack AM online? Is it available or in use?
  • Sliver count and percentage of rack compute and unbound VLAN resources in use.
  • Identities of current slivers on each rack AM, including creation time for each.
  • Per-sliver interface counters for compute and VLAN resources (where these values can be easily collected).
  • Is the rack data plane switch online?
  • Interface counters and VLAN memberships for each rack data plane switch interface
  • MAC address table contents for shared VLANs which appear on rack data plane switches
  • Is each rack experimental node online?
  • For each rack experimental 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.
  • For each rack experimental node configured as an OpenStack VM server, interface counters for each data plane interface.
  • Results of at least one end-to-end health check which simulates an experimenter reserving and using at least one resource in the rack.

Verify 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.