| 53 | | [http://groups.geni.net/geni/attachment/wiki/Gec7InstMeasWGAgenda/griffioen%20%20instools_imwg_gec7.pdf Overview, explanation of demo, review of GENI I&M architecture topics] [[BR]] |
| | 53 | [http://groups.geni.net/geni/attachment/wiki/Gec7InstMeasWGAgenda/griffioen%20%20instools_imwg_gec7.pdf INSTOOLS: Instrumentation Tools for a ProtoGENI Prototype] [[BR]] |
| | 54 | |
| | 55 | Goals:[[BR]] |
| | 56 | + Integrate Univ of Kentucky Emulab into ProtoGENI (completed in year 1)[[BR]] |
| | 57 | + Reimplement Univ of Kentucky Edulab instrumentation and measurement tools to work in the ProtoGENI environment.[[BR]] |
| | 58 | + Support automatic generation of instrumentation and measurement infrastructure on a per-slice basis.[[BR]] |
| | 59 | |
| | 60 | Structure:[[BR]] |
| | 61 | + Measurement Points[[BR]] |
| | 62 | + Measurement Controller[[BR]] |
| | 63 | |
| | 64 | Functional Components[[BR]] |
| | 65 | 1. Setup: deploy and initialize topology-specific software and services[[BR]] |
| | 66 | 2. Capture: capture measurement data[[BR]] |
| | 67 | 3. Collection: move data to processing/storage environments[[BR]] |
| | 68 | 4. Storage: store data on a temporary, short term, long term, and archival basis[[BR]] |
| | 69 | 5. Processing: filter, convert, aggregate, summarize, etc., data[[BR]] |
| | 70 | 6. Presentation: present data to users in meaningful ways[[BR]] |
| | 71 | 7. Access Protection: protect resources and data[[BR]] |
| | 72 | 8. Measurement Control: Dynamically control the above components[[BR]] |
| | 73 | |
| | 74 | Note: Conventional network management solutions exist for 2. through 8.[[BR]] |
| | 75 | |
| | 76 | Mapping functions to proposed services:[[BR]] |
| | 77 | 1. Setup – MO?[[BR]] |
| | 78 | 2. Capture - MP[[BR]] |
| | 79 | 3. Control – MO?[[BR]] |
| | 80 | 4. Collection - MC[[BR]] |
| | 81 | 5. Storage - MDA[[BR]] |
| | 82 | 6. Processing - MAP[[BR]] |
| | 83 | 7. Access Control – MO?[[BR]] |
| | 84 | 8. Presentation - MAP[[BR]] |
| | 85 | |
| | 86 | Measurement data schema:[[BR]] |
| | 87 | + Data-specific formats will exist at multiple times and places but should be invisible to the generic measurement infrastructure[[BR]] |
| | 88 | + Should leverage expertise of those with experience in this area (DatCat, PerfSONAR, etc).[[BR]] |
| | 89 | |
| | 90 | Measurement plane:[[BR]] |
| | 91 | + Virtual interfaces abound in GENI. [[BR]] |
| | 92 | - Unknown how virtual interfaces map to physical NICs.[[BR]] |
| | 93 | + Shared paths are OK, but require QoS.[[BR]] |
| | 94 | - Setting up QoS planes is challenging; particularly if planes are per-slice.[[BR]] |
