Changes between Version 34 and Version 35 of GENIMonitoring


Ignore:
Timestamp:
05/31/17 11:23:23 (2 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIMonitoring

    v34 v35  
    1111== Monitoring Features ==
    1212
    13 ''<< Insert overview of feature within the monitoring system >>>''
     13The [http://genimon.uky.edu/ GENI Monitoring] system make the following types of information available:
     14
     15 * Aggregates - Monitored GENI Aggregates data is available that includes details such as allocated nodes, links and slivers at that GENI Aggregate.
     16 * Users - Users information known to the GENI Clearinghouse (ch.geni.net).
     17 * Slices - All active slices, that may or may not have resources.
     18 * Slivers - All active reservations that compute and/or network resources actively allocated.
     19 * VLANs - All VLANs in use in GENI Environment, includes both sites and AL2S VLANs.
     20 * Nodes - Allocated GENI nodes, including VM and bare metal for all monitored aggregates.
     21 * Interfaces - All nodes defined for all aggregates being monitored. Note, ExoGENI keeps historical list of interfaces, while other aggregates only list active interfaces.
     22 * Links - Active GENI network connections which map VLANs between endpoints.
     23 * Check Stores - External Check that are run by GPO and by IMinds that capture status for specific type of information, such as up/down status or stitching support.
     24 * Authorities - GENI Clearinghouse (ch.geni.net) provides valid user and slice information.
     25 * Aggregate Status - Site availability, available raw-pc and VM server statistics information. Also allows selecting aggregates by criteria like aggregate type or stitching.  See [wiki:GENIMonitoring/AggregateStatusHelp Aggregate Status] help page for more details.
    1426
    1527== GENI Monitoring API ==