| 336 | | a) How do we work toward's Max Ott's vision for experiment support? |
| 337 | | |
| 338 | | b) Experiment process: |
| 339 | | 1) Setup and run experiment using Experiment Control Tools, Experiment Orchestration Service and Lab Portal. |
| 340 | | 2) Setup and run measurements using services within slice, and persistent services. Option: get measurement data from persistent MP. |
| 341 | | 3) Gather MD, and observe during experiment; formulate MDOD. |
| 342 | | 4) Archive MD with MDOD. |
| 343 | | 5) Share archived MD with others, per policy included within MDOD. |
| 344 | | 6) Pull MD out of archive, to analyze and/or visualize. |
| | 336 | a) How do we work toward's Max Ott's vision for experiment support? [[BR]] |
| | 337 | |
| | 338 | b) Experiment process: [[BR]] |
| | 339 | 1) Setup and run experiment using Experiment Control Tools, Experiment Orchestration Service and Lab Portal. [[BR]] |
| | 340 | 2) Setup and run measurements using services within slice, and persistent services. Option: get measurement data from persistent MP. [[BR]] |
| | 341 | 3) Gather MD, and observe during experiment; formulate MDOD. [[BR]] |
| | 342 | 4) Archive MD with MDOD. [[BR]] |
| | 343 | 5) Share archived MD with others, per policy included within MDOD. [[BR]] |
| | 344 | 6) Pull MD out of archive, to analyze and/or visualize. [[BR]] |
| 357 | | a) Infrastructure measurement process: |
| 358 | | 1) Setup persistent or on demand infrastructure measurement slices. |
| 359 | | 2) Make passive measurements or make active measurements, and gather results. |
| 360 | | 3) Gather MD, and observe as it is gathered; formulate MDOD. |
| 361 | | 4) Store MD in collector, describe with MDOD, and register MDOD so that MD can be shared. |
| 362 | | 5) Typically share MD with Aggregate Operator, GMOC and/or Experimenters, per policy written into MDOD. |
| 363 | | 6) Pull MD out of collector, analyze and visualize. |
| 364 | | 7) Archive MD with MDOD. |
| 365 | | 8) Share archived MD with others, per policy included within MDOD. |
| 366 | | 9) Pull MD out of archive, to analyze and/or visualize. |
| 367 | | |
| 368 | | b) What support must be provided for Operator? how? [[BR]] |
| 369 | | |
| 370 | | c) Who: |
| | 357 | a) Delineate what infrastructure monitoring is and is not covered by this approach. [[BR]] |
| | 358 | 1) Yes: monitoring of clusters/racks [[BR]] |
| | 359 | 2) Yes: passive measurements of transport switches, etc. [[BR]] |
| | 360 | 3) Yes: active measurements of IP networks, of Layer 2 and OpenFlow paths [[BR]] |
| | 361 | |
| | 362 | |
| | 363 | b) Infrastructure measurement process: [[BR]] |
| | 364 | 1) Setup persistent or on demand infrastructure measurement slices. [[BR]] |
| | 365 | 2) Make passive measurements or make active measurements, and gather results. [[BR]] |
| | 366 | 3) Gather MD, and observe as it is gathered; formulate MDOD. [[BR]] |
| | 367 | 4) Store MD in collector, describe with MDOD, and register MDOD so that MD can be shared. [[BR]] |
| | 368 | 5) Typically share MD with Aggregate Operator, GMOC and/or Experimenters, per policy written into MDOD. [[BR]] |
| | 369 | 6) Pull MD out of collector, analyze and visualize. [[BR]] |
| | 370 | 7) Archive MD with MDOD. [[BR]] |
| | 371 | 8) Share archived MD with others, per policy included within MDOD. [[BR]] |
| | 372 | 9) Pull MD out of archive, to analyze and/or visualize. [[BR]] |
| | 373 | |
| | 374 | c) What support must be provided for Operator? how? [[BR]] |
| | 375 | |
| | 376 | d) Who: [[BR]] |
