Version 2 (modified by, 13 years ago) (diff)


Monitoring & Management

Monitoring focuses on areas of shared interest across GENI:

  1. Tools to aid people with responsibilities (e.g. campuses who have signed the aggregate agreement)
  2. Lower burden on monitoring done multiple places (e.g. monitoring MyPLC happens at lots of campuses)
  3. Coordination when we rely on each other (e.g. debugging a VLAN path across multiple networks)
  4. Monitoring that is truly GENI-wide (e.g. GMOC DB is currently acting as a shared repo of data)
  5. Monitoring of GENI racks

Management focuses on the ability to control GENI resources (in particular GENI racks).

As GENI scales during Spiral 4, monitoring and management will mature in a manner that scales to include new campuses and new racks.

GEC 11 Monitoring Mini-Workshop focused exclusively on what is required in the short term.

Starting with the lead up to GEC12, discussion is expanding to management and developing a longer term software monitoring plan.

Spiral 4 schedule leverages existing software to define long-term requirements for monitoring/mgmt software:

  • At GEC12: Agree on long-term requirements for monitoring/mgmt software
  • At GEC13: Agree on APIs & Architecture
  • GEC14: Working software
  • GEC15: deploy mature monitoring at many campuses/racks


GEC11 Summary

The first half of the monitoring mini-workshop included presentations on the current status of what tools are used and what data is collected as part of monitoring today. The second half of the workshop was a discussion about issues of interest to the community including: what OpenFlow stats are available and the difficulty of current OpenFlow Opt-In, the importance of privacy and incorporating privacy into the design now, and concerns about how campuses could share data without necessarily giving others admin access to their resources. This community will be working to address these issues in the coming months.

Detailed notes are on the GEC11 wiki.