| | 1 | = Monitoring & Management = |
| | 2 | |
| | 3 | '''Monitoring''' focuses on areas of shared interest across GENI: |
| | 4 | 1. Tools to aid people with responsibilities (e.g. campuses who have signed the aggregate agreement) |
| | 5 | 2. Lower burden on monitoring done multiple places (e.g. monitoring MyPLC happens at lots of campuses) |
| | 6 | 3. Coordination when we rely on each other (e.g. debugging a VLAN path across multiple networks) |
| | 7 | 4. Monitoring that is truly GENI-wide (e.g. GMOC DB is currently acting as a shared repo of data) |
| | 8 | 5. Monitoring of GENI racks |
| | 9 | |
| | 10 | '''Management''' focuses on the ability to control GENI resources (in particular GENI racks). |
| | 11 | |
| | 12 | As GENI scales during Spiral 4, monitoring and management will mature in a manner that scales to include new campuses and new racks. |
| | 13 | |
| | 14 | [wiki:GEC11MonitoringMiniWorkshop GEC 11 Monitoring Mini-Workshop] focused exclusively on what is required in the short term. |
| | 15 | |
| | 16 | Starting with the lead up to GEC12, discussion is expanding to management and developing a longer term software monitoring plan. |
| | 17 | |
| | 18 | Spiral 4 schedule leverages existing software to define long-term requirements for monitoring/mgmt software: |
| | 19 | * At GEC12: Agree on long-term requirements for monitoring/mgmt software |
| | 20 | * At GEC13: Agree on APIs & Architecture |
| | 21 | * GEC14: Working software |
| | 22 | * GEC15: deploy mature monitoring at many campuses/racks |
| | 23 | |
| | 24 | |
| | 25 | Links: |
| | 26 | * [wiki:MonitoringCurrentStatus Summary of data being collected by GMOC] |
| | 27 | * [http://monitor.gpolab.bbn.com/tango/ Meso-scale GENI monitoring graphs] |
| | 28 | * [http://gmoc-db.grnoc.iu.edu/api-demo Raw data on SNAPP] |
| | 29 | * [http://gmoc-db.grnoc.iu.edu/web-services/gen_api.pl Last 10 minutes of data in XML format (at GMOC)] |
