| | 1 | == Tendrils to the Services/Substrate WG == |
| | 2 | |
| | 3 | See [SubstrateOverlap Substrate Overlap], Notes From Substrate WG meeting 10/10/07 |
| | 4 | |
| | 5 | Summary of what Substrate needs from Services Group: |
| | 6 | * Need the workflow cases to extend down into the substrate. |
| | 7 | * GIMS (GENI instrumentation and measurement system), management hooks for researchers: need desires from Services. |
| | 8 | * Resource requirements: descriptions, granularity, parameters, etc. |
| | 9 | * Programmability requirements: what level of control, granularity, dependencies, interfaces, which resources are invoked and which are programmable? |
| | 10 | * What do requests look like, how are services bundled? |
| | 11 | * Are things invoked, or programmed? |
| | 12 | |
| | 13 | Substrate provides to Services: |
| | 14 | * What resources are available to slices. |
| | 15 | * What level of programmability is possible on different components and their associated resources. |
| | 16 | |
| | 17 | GIMS: |
| | 18 | * Measurement is a triangle between substrate/OMIS/services |
| | 19 | * Substrate supports collection of measurements and a place to keep the results |
| | 20 | * Services tells us how much and when, and then OMIS gets involved. |
| | 21 | |
