| | 34 | |
| | 35 | == Synopsis of Session == |
| | 36 | |
| | 37 | First combined I&M and Monitoring GEC session. |
| | 38 | |
| | 39 | There is lots of data being collected in GENI using a variety of tools. We want to share tools and data. |
| | 40 | |
| | 41 | First, shared background on Monitoring and I&M tools: |
| | 42 | * '''Kevin Bohan''' demoed GMOC monitoring of GENI slices, resources, and aggregates |
| | 43 | * '''Anirban Mandal''' described an XMPP based pub-sub service using GENI client authentication |
| | 44 | * '''Martin Swany''' described GEMINI support for active measurements |
| | 45 | * '''Prasad Calyam''' provided a case study of experimenter use of active measurement |
| | 46 | |
| | 47 | Second, discussed common concerns. |
| | 48 | |
| | 49 | '''Jeanne Ohren''' set the stage by describing some known open questions then lead a discussion ... |
| | 50 | |
| | 51 | Three (perhaps unsurprising) issues in common: |
| | 52 | 1. Clock synchronization |
| | 53 | 2. Consistent shared naming |
| | 54 | 3. Authentication |
| | 55 | |
| | 56 | There are actually 2 distinct types of authentication of interest to this group: |
| | 57 | 1. GENI user accessing resources |
| | 58 | 2. machine to machine data sharing |
| | 59 | |
| | 60 | Consistent shared naming |
| | 61 | * Example: unique naming of slices |
| | 62 | - URN is human-readable, UUID is unique over time |
| | 63 | - So standardize on both (URN and UUID) |
| | 64 | - AM API v3, monitoring and at least one I&M project have adopted this convention |
| | 65 | * Consistent naming for describing topologies |
| | 66 | - Monitoring, I&M, & stitching communities interested |
| | 67 | - Some ideas may exist and we will discuss after GEC. |
