Changes between Version 5 and Version 6 of GEC12MesoScaleMonitoring

11/22/11 12:18:51 (10 years ago)



  • GEC12MesoScaleMonitoring

    v5 v6  
    2626  * (1 hr incl. discussion) Monitoring/Mgmt Requirements - Sarah Edwards, GPO
     28=== Session Summary ===
     30Links to appropriate section of the [  Detailed Notes] are included below.
     32'''Sarah Edwards''' of the GPO introduced the session.
     34There were two goals for the session:
     35 1. Keep talking about day-to-day issues and problems, as we did at GEC11
     36 2. Look ahead to where GENI is headed. We need to be able to provide inputs
     37    so that other parts of GENI will address monitoring needs, and so
     38    we don't ignore any important pieces.
     40'''Josh Smift''' of the GPO [ spoke] about FOAM, the new !OpenFlow Aggregate Manager (AM). 
     41 * Version 0.6 will migrate to campuses on November 21. 
     42 * FOAM addresses three pain points identified at the last GEC:
     43  * improved data mapping between FV slices, GENI slivers, GENI slices, and experimenters allows much improved monitoring;
     44  * an automated approval engine make approval (aka !OpenFlow Opt-In) easier; and,
     45  * FOAM reduces the size of the flowspace (eg the GPO saw an improved by a factor of 30).
     47'''Camilo Viecco''' (of Indiana U/GMOC) did a [ demonstration] of how to use SNAPP to find and visualize monitoring data from the GMOC DB.
     48 * Camilo demonstrated the new [ Portal] interface to SNAPP which allows you to browse the data by meso-scale participant.
     49 * In addition, Camilo demonstrated how to use search in [ SNAPP] (eg to find all data related to a single slice).
     51'''Chaos Golubitsky''' of GPO [ spoke] about Topology in the Mesoscale.
     53Chaos discussed two solved problems which can cause an experimenter's topology to not match their expectations.  Monitoring in both the near and long terms needs to address problems like these.
     55'''Sarah Edwards''' of the GPO provided an [ overview] of top-down GENI monitoring requirements. 
     56Sarah presented a top-down analysis of monitoring and management requirements, to ensure we cover all the key areas and focus on areas that will become problems, not just areas that are currently a problem. Monitoring and management in GENI must support
     57 * cross-GENI monitoring,
     58 * troubleshooting and event escalation,
     59 * quickly identifying and addressing security events, and
     60 * emergency stop,
     61 * all while ensuring all parties follow defined policies,
     62 * and preserve both experimenter and end user privacy.
    2865=== Background Reading ===
    2966 * [ GMOC Monitoring Portal]