85 | | Goals: [[BR]] |
86 | | |
87 | | * Includes LAMP code and features into GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]] |
88 | | * Includes INSTOOLS code and features into GEMINI tools, to gather basic host measurements [[BR]] |
89 | | * Later, integrate LAMP and INSTOOLS code and features into new code base for GEMINI tools. |
90 | | |
91 | | * First focus: I&M use cases for infrastructure measurement |
92 | | * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential [[BR]] |
93 | | * Show how to monitor clusters/racks [[BR]] |
94 | | * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) |
95 | | |
96 | | * Second focus: I&M use cases for experiments [[BR]] |
97 | | * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]] |
98 | | * Show how to gather customized data from applications (as provided by OML Client) [[BR]] |
99 | | |
100 | | * Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
101 | | * Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
102 | | |
103 | | * Continues INSTOOLS portal service, to find GUIs [[BR]] |
104 | | * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology [[BR]] |
105 | | |
106 | | Martin Swany and Jim Griffioen will review: [[BR]] |
107 | | |
108 | | * Current architecture, design and status. [[BR]] |
109 | | * Plan for GEC-14 tutorial [[BR]] |
110 | | |
111 | | * Next steps, during Spiral 5 [[BR]] |
| 85 | Goals [[BR]] |
| 86 | |
| 87 | * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]] |
| 88 | * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]] |
| 89 | * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]] |
| 90 | |
| 91 | * First focus: I&M use cases for infrastructure measurement [[BR]] |
| 92 | * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential [[BR]] |
| 93 | * Show how to monitor clusters/racks [[BR]] |
| 94 | * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]] |
| 95 | |
| 96 | * Second focus: I&M use cases for experiments [[BR]] |
| 97 | * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]] |
| 98 | * Show how to gather customized data from applications (as provided by OML Client) [[BR]] |
| 99 | |
| 100 | * Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
| 101 | * Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
| 102 | |
| 103 | * Continues INSTOOLS portal service, to find GUIs [[BR]] |
| 104 | * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology [[BR]] |
| 105 | |
| 106 | Summary [[BR]] |
| 107 | |
| 108 | * Current architecture, design and status. [[BR]] |
| 109 | * Plan for GEC-14 tutorial [[BR]] |
| 110 | |
| 111 | * Next steps, during Spiral 5 [[BR]] |
141 | | Work towards Max Ott's vision for experiment support [[BR]] |
142 | | Provide a way for a GENI user (e.g., experimenter or operator) to access a wide variety of "GENI User Services", where each user service provides an interface (e.g., API or GUI) to the user. Those user services with a GUI (web) interface are often called "portal services".[[BR]] |
143 | | Together, the "GENI User Services" should provide all of the functions the user needs to setup and run their experiment, then gather, analyze and present their measurement data. [[BR]] |
144 | | These services should work together via APIs, etc., to streamline the experiment process. [[BR]] |
| 141 | * Work towards Max Ott's vision for experiment support [[BR]] |
| 142 | * Provide a way for a GENI user (e.g., experimenter or operator) to access a wide variety of "GENI User Services", where each user service provides an interface (e.g., API or GUI) to the user. Those user services with a GUI (web) interface are often called "portal services".[[BR]] |
| 143 | * Together, the "GENI User Services" should provide all of the functions the user needs to setup and run their experiment, then gather, analyze and present their measurement data. [[BR]] |
| 144 | * These services should work together via APIs, etc., to streamline the experiment process. [[BR]] |
150 | | Define, prototype, deploy and operate a GENI User Workspace. It can be hosted on a server dedicated to the user (even the user's laptop), or on a server hosting multiple user workspaces for multiple users.[[BR]] |
151 | | Gather the various "user tools" that have been implemented to date, and fit them into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure. [[BR]] |
152 | | Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators). [[BR]] |
153 | | Use the "GENI User Workspace" to test the GIMI and GEMINI tools, and during their tutorials. |
| 150 | * Define, prototype, deploy and operate a GENI User Workspace. It can be hosted on a server dedicated to the user (even the user's laptop), or on a server hosting multiple user workspaces for multiple users.[[BR]] |
| 151 | * Gather the various "user tools" that have been implemented to date, and fit them into GENI User Workspace Service so that GENI I&M users can begin to conveniently conduct experiments or instrument infrastructure. [[BR]] |
| 152 | * Optimize "user tools" and their interfaces to better meet the needs of GENI users (e.g., experimenters and operators). [[BR]] |
| 153 | * Use the "GENI User Workspace" to test the GIMI and GEMINI tools, and during their tutorials. |
166 | | Need to finalize MDOD schema, for XML file. [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD References] [[BR]] |
167 | | Want to extend MDOD to cover all types of objects, i.e., software images. (NetKarma)[[BR]] |
168 | | Want to use MDOD schema to define Event Record schema. (NetKarma)[[BR]] |
169 | | Do we need MDOD registry? Use UNIS lookup service? Include in iRODS? [[BR]] |
170 | | Need MDOD creation and editing service. (who?) [[BR]] |
171 | | Need Measurement Data Object identifiers (names); sometimes need a persistent, public reference; consider DataCite approach, which uses handle [[BR]] |
| 166 | * Need to finalize MDOD schema, for XML file. [http://groups.geni.net/geni/wiki/GEC11InstMeasWorkingSession#a2MeasurementDataObjectDescriptorMDOD References] [[BR]] |
| 167 | * Want to extend MDOD to cover all types of objects, i.e., software images. (NetKarma)[[BR]] |
| 168 | * Want to use MDOD schema to define Event Record schema. (NetKarma)[[BR]] |
| 169 | * Do we need MDOD registry? Use UNIS lookup service? Include in iRODS? [[BR]] |
| 170 | * Need MDOD creation and editing service. (who?) [[BR]] |
| 171 | * Need Measurement Data Object identifiers (names); sometimes need a persistent, public reference; consider DataCite approach, which uses handle [[BR]] |
174 | | [http://groups.geni.net/geni/wiki/InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService work in progress] [[BR]] |
175 | | v0.1 design reviewed at GEC13 [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx slides] (Giridhar Manepalli) Conclusion: too complex [[BR]] |
176 | | DRAFT simplified v0.2 design [ slides] (Harry Mussman)[[BR]] |
177 | | |
178 | | Discussion |
179 | | Who will review? Shall we have a breakout meeting on Wed, 7/11? [[BR]] |
180 | | Who will implement? [[BR]] |
181 | | How will this be included into iRODS? [[BR]] |
| 174 | * [http://groups.geni.net/geni/wiki/InstMeasTopic_4.5DescriptorsObjectsRegistriesLookupService work in progress] [[BR]] |
| 175 | * v0.1 design reviewed at GEC13 [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T5%29%20%20MDOD%20Status%20-%20CNRI.pptx slides] (Giridhar Manepalli) Conclusion: too complex [[BR]] |
| 176 | * DRAFT simplified v0.2 design [ slides] (Harry Mussman)[[BR]] |
| 177 | |
| 178 | Discussion |
| 179 | * Who will review? Shall we have a breakout meeting on Wed, 7/11? [[BR]] |
| 180 | * Who will implement? [[BR]] |
| 181 | * How will this be included into iRODS? [[BR]] |