| 27 | |
| 28 | Shu Huang (RENCI) [[BR]] |
| 29 | |
| 30 | Tasks |
| 31 | * Design and deploy GENI Storage and Archive Service for use by all GENI services. |
| 32 | * Provide functions similar to the Measurement Data Archive (MDA) service prototype, designed by CNRI. |
| 33 | * Use to store all types of experiment artifacts (not just measurement data), and identify objects to be moved to a long-term archive. |
| 34 | * Implement using the iRODS data grid service, by defining rules (interfaces) to provide the necessary GENI functions. [[BR]] |
| 35 | |
| 36 | Design goals and approach |
| 37 | * [wiki:InstMeasTopic_4.9ArchiveService status at GEC13] [[BR]] |
| 38 | * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides at GEC13] [[BR]] |
| 39 | * iRODS service has been established at RENCI [[BR]] |
| 40 | * iRODS service has been established at Univ of Kentucky [[BR]] |
| 41 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx iRODS configuration at GEC14] [[BR]] |
| 42 | * Proposed configuration? [[BR]] |
| 43 | * Operations plan? [[BR]] |
| 44 | |
| 45 | Current implementation and next steps |
| 46 | |
| 47 | |
| 48 | Open issues |
| 49 | * Who is lead? [[BR]] |
| 50 | * Will all iRODS services be federated, for redundancy? |
| 51 | * How to move data to service: move file; move SQL DB; or? [[BR]] |
| 52 | * How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.[[BR]] |
| 53 | * How are partitions for different users managed? [[BR]] |
| 54 | * How is authorization for a user done? [[BR]] |
| 55 | * How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
| 56 | * How will the GEMINI project use the iRODS service? [[BR]] |
| 57 | * Will other parts of GENI want to use the iRODS service? [[BR]] |
| 58 | * Do we need a breakout session for further discussion? when? [[BR]] |
| 59 | |
| 60 | Team |
| 61 | * Shu Huang (RENCI), GIMI project, lead |
| 62 | * ? (?), GEMINI project |
| 63 | * Giridhar Manepalli (CNRI) |
| 64 | * Harry Mussman and Jeanne Ohren (GPO) |
| 65 | |
| 66 | |
| 67 | === T5) Digital Objects, Identifiers and Descriptors === |
| 68 | 9:05am [[BR]] |
| 69 | |
| 70 | Giridhar Manepalli (CNRI) [[BR]] |
| 71 | |
| 72 | |
| 73 | |
| 74 | === T10) I&M Service-to-Service Authentication and Authorization === |
| 75 | 9:25am [[BR]] |
| 76 | |
| 77 | Ezra Kissel (IU) [[BR]] |
| 78 | |
| 79 | |
| 80 | |
| 81 | |
| 82 | == 3) Goals for the next 4 months == |
| 83 | 9:45am [[BR]] |
| 84 | |
| 85 | Harry Mussman (GPO) [[BR]] |
| 86 | |
| 87 | Goals |
| 88 | * Both GIMI and GEMINI tools should be available to Users during this period [[BR]] |
| 89 | * Acceptance testing continued by the GPO (Jeanne Ohren) [[BR]] |
| 90 | * Bug tracking system, plus periodic bug fixes, continued (who are leads?) [[BR]] |
| 91 | * How can we facilitate feedback from Users, after EVERY use? [[BR]] |
| 92 | |
| 93 | * Both GIMI and GEMINI must provide a high level of support to Users [[BR]] |
| 94 | * Tutorials must be kept up-to-date and operational, so that Users can teach themselves. (who are leads?) [[BR]] |
| 95 | * Instructions must be continuously refined, to make the tools easier to use. (who are leads?) [[BR]] |
| 96 | * Requested tool extensions must be gathered from users, based upon their experience. (who are leads?) [[BR]] |
| 97 | * Users with advanced requirements must be found, better identify gaps in the tools. How? (who are leads?) [[BR]] |
| 98 | * Tool extensions must be proposed by the teams, and reviewed with the users. How? (who are leads?) [[BR]] |
| 99 | * A list of tool extensions needs to be developed for inclusion into v1.1, due at GEC15. (who are leads?) [[BR]] |
| 100 | |
| 101 | * Persistent multi-user services must be reliably available to all Users [[BR]] |
| 102 | * User Worksapce (Jeanne Ohren) [[BR]] |
| 103 | * XML messaging service (who is lead?) [[BR]] |
| 104 | * iRODS archive service (who is lead?) [[BR]] |
| 105 | * IREEL analysis and presentation service (who is lead?) [[BR]] |
| 106 | * INSTOOLS portal-to-GUIs service (who is lead?) [[BR]] |
| 107 | * Unified Network Information Service (UNIS) (who is lead?) [[BR]] |
| 108 | |
| 109 | |
| 110 | Discussion |
| 111 | * Do we have leads identified for all items? [[BR]] |
| 112 | |
| 113 | |
| 114 | == 4) Adjourn == |
| 115 | 10:00am [[BR]] |
| 116 | |
| 117 | |
| 118 | = I&M References = |
| 119 | |
| 120 | |
| 121 | |
| 122 | == GENI I&M Architecture and Tools: Goals, Overview and Status == |
| 123 | |
| 124 | * GIMI I&M tool set design [[BR]] |
| 125 | * Based on OML, provides basic host and active network measurements [[BR]] |
| 126 | * Ready for use on ExoGENI racks; successful tutorial [[BR]] |
| 127 | * Introduces XML messaging service, iRODS archive service, IREEL(lab wiki) portal service; use by others? iRODS by GEMINI [[BR]] |
| 128 | * Spiral 5 goals: also work with InstaGENI racks, WiMAX sites [[BR]] |
| 129 | |
| 130 | * GEMINI I&M tool set design [[BR]] |
| 131 | * Based on INSTOOLS and perfSONAR/LAMP, provides basic host and active network measurements [[BR]] |
| 132 | * Ready for use on InstaGENI/protoGENI racks ; successful tutorial [[BR]] |
| 133 | * Introduces portal to GUIs service, UNIS unified ntwk info service; use by others? [[BR]] |
| 134 | * Spiral 5 goals: also work with ExoGENI racks [[BR]] |
| 135 | |
| 136 | * Need simplified MDOD measurement data object descriptor schema [[BR]] |
| 137 | * Also service for creation and editing of MDOD [[BR]] |
| 138 | * Possible extensions to other GENI objects, events [[BR]] |
| 139 | |
| 140 | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/071112%20I%26M%20GEC14%20Wrap-Up%20Agenda.ppt slides] [[BR]] |
| 141 | |
| 142 | |
| 143 | |
| 144 | === GIMI I&M Tools: Goals, Overview and Status === |
| 145 | |
| 146 | '''PI''' Michael Zink, University of Massachusetts at Amherst (mailto:zink@ecs.umass.edu) [[BR]] |
| 147 | '''Co-PI''' Max Ott, NICTA (mailto:max.ott@nicta.com.au) [[BR]] |
| 148 | '''Key personnel''' Ilia Baldine, RENCI (mailto:ibaldin@renci.org) [[BR]] |
| 149 | |
| 150 | [wiki:GIMI GIMI wiki] [[BR]] |
| 151 | [http://gimi.ecs.umass.edu/ GIMI website at UMass Amherst] [[BR]] |
| 152 | |
| 153 | Goals [[BR]] |
| 154 | * Starts with OML, and provides easy-to-use tools for GENI environment [[BR]] |
| 155 | |
| 156 | * First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS, and provides basic node-to-node connectivity tests using ping and iperf [[BR]] |
| 157 | * Second focus: I&M use cases for infrastructure measurement [[BR]] |
| 158 | * Later focus: add sensor measurement data, carried in data network [[BR]] |
| 159 | |
| 160 | * Spiral 4 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
| 161 | * Later, support: WiMAX sites [[BR]] |
| 162 | * Spiral 5 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
| 163 | |
| 164 | * Introduces XML messaging service, with pub/sub, in public IP space [[BR]] |
| 165 | * Introduces iRODS service, as a measurement data archive. [[BR]] |
| 166 | * Introduces IREEL portal service, for measurement data analysys and presentation. [[BR]] |
| 167 | |
| 168 | |
| 169 | Summary: [[BR]] |
| 170 | |
| 171 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GIMI%20GEC%2014%20I%26M%20Session.pptx GIMI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
| 172 | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial GIMI v1.0 tutorial] [[BR]] |
| 173 | |
| 174 | |
| 175 | |
| 176 | === GEMINI I&M Tools: Goals, Overview and Status === |
| 177 | |
| 178 | '''PI''' Martin Swany, Indiana University (mailto:swany@iu.edu) [[BR]] |
| 179 | '''Co-PI''' Chris Small, Indiana University (mailto:chsmall@indiana.edu) [[BR]] |
| 180 | '''Co-PI''' James Griffioen, University of Kentucky (mailto:griff@netlab.uky.edu) [[BR]] |
| 181 | '''Co-PI''' Zongming Fei, University of Kentucky (mailto:fei@netlab.uky.edu) [[BR]] |
| 182 | |
| 183 | [wiki:GEMINI GEMINI wiki] [[BR]] |
| 184 | |
| 185 | Goals [[BR]] |
| 186 | |
| 187 | * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]] |
| 188 | * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]] |
| 189 | * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]] |
| 190 | |
| 191 | * First focus: I&M use cases for infrastructure measurement [[BR]] |
| 192 | * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential [[BR]] |
| 193 | * Show how to monitor clusters/racks [[BR]] |
| 194 | * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]] |
| 195 | |
| 196 | * Second focus: I&M use cases for experiments [[BR]] |
| 197 | * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]] |
| 198 | * Show how to gather customized data from applications (as provided by OML Client) [[BR]] |
| 199 | |
| 200 | * Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
| 201 | * Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
| 202 | |
| 203 | * Continues INSTOOLS portal service, to find GUIs [[BR]] |
| 204 | * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology [[BR]] |
| 205 | |
| 206 | Summary [[BR]] |
| 207 | |
| 208 | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Overview%20and%20Direction-GEC14.pptx GEMINI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
| 209 | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GEMINITutorial GEMINI v1.0 tutorial] [[BR]] |
| 210 | |
| 211 | |
| 212 | |
| 213 | |
| 214 | |
| 215 | == Persistent Multi-user I&M Services == |
| 216 | |
| 217 | |
| 218 | Goals [[BR]] |
| 219 | * Use by both GIMI and GEMINI tools sets [[BR]] |
| 220 | * Use by other parts of GENI [[BR]] |
| 221 | * Identify need for further reviews and discussions [[BR]] |
| 222 | |
| 223 | |
| 224 | === S1) GENI (XML) Messaging Service === |
| 225 | |
| 226 | === S2) GENI Storage and Archive Service (based on iRODS) === |
| 227 | 9:15am [[BR]] |
54 | | === T5) Digital Objects, Identifiers and Descriptors === |
55 | | 9:05am [[BR]] |
56 | | |
57 | | Giridhar Manepalli (CNRI) [[BR]] |
58 | | |
59 | | |
60 | | |
61 | | === T10) I&M Service-to-Service Authentication and Authorization === |
62 | | 9:25am [[BR]] |
63 | | |
64 | | Ezra Kissel (IU) [[BR]] |
65 | | |
66 | | |
67 | | |
68 | | |
69 | | == 3) Goals for the next 4 months == |
70 | | 9:45am [[BR]] |
71 | | |
72 | | Harry Mussman (GPO) [[BR]] |
73 | | |
74 | | Goals |
75 | | * Both GIMI and GEMINI tools should be available to Users during this period [[BR]] |
76 | | * Acceptance testing continued by the GPO (Jeanne Ohren) [[BR]] |
77 | | * Bug tracking system, plus periodic bug fixes, continued (who are leads?) [[BR]] |
78 | | * How can we facilitate feedback from Users, after EVERY use? [[BR]] |
79 | | |
80 | | * Both GIMI and GEMINI must provide a high level of support to Users [[BR]] |
81 | | * Tutorials must be kept up-to-date and operational, so that Users can teach themselves. (who are leads?) [[BR]] |
82 | | * Instructions must be continuously refined, to make the tools easier to use. (who are leads?) [[BR]] |
83 | | * Requested tool extensions must be gathered from users, based upon their experience. (who are leads?) [[BR]] |
84 | | * Users with advanced requirements must be found, better identify gaps in the tools. How? (who are leads?) [[BR]] |
85 | | * Tool extensions must be proposed by the teams, and reviewed with the users. How? (who are leads?) [[BR]] |
86 | | * A list of tool extensions needs to be developed for inclusion into v1.1, due at GEC15. (who are leads?) [[BR]] |
87 | | |
88 | | * Persistent multi-user services must be reliably available to all Users [[BR]] |
89 | | * User Worksapce (Jeanne Ohren) [[BR]] |
90 | | * XML messaging service (who is lead?) [[BR]] |
91 | | * iRODS archive service (who is lead?) [[BR]] |
92 | | * IREEL analysis and presentation service (who is lead?) [[BR]] |
93 | | * INSTOOLS portal-to-GUIs service (who is lead?) [[BR]] |
94 | | * Unified Network Information Service (UNIS) (who is lead?) [[BR]] |
95 | | |
96 | | |
97 | | Discussion |
98 | | * Do we have leads identified for all items? [[BR]] |
99 | | |
100 | | |
101 | | == 4) Adjourn == |
102 | | 10:00am [[BR]] |
103 | | |
104 | | |
105 | | = I&M References = |
106 | | |
107 | | |
108 | | |
109 | | == GENI I&M Architecture and Tools: Goals, Overview and Status == |
110 | | |
111 | | * GIMI I&M tool set design [[BR]] |
112 | | * Based on OML, provides basic host and active network measurements [[BR]] |
113 | | * Ready for use on ExoGENI racks; successful tutorial [[BR]] |
114 | | * Introduces XML messaging service, iRODS archive service, IREEL(lab wiki) portal service; use by others? iRODS by GEMINI [[BR]] |
115 | | * Spiral 5 goals: also work with InstaGENI racks, WiMAX sites [[BR]] |
116 | | |
117 | | * GEMINI I&M tool set design [[BR]] |
118 | | * Based on INSTOOLS and perfSONAR/LAMP, provides basic host and active network measurements [[BR]] |
119 | | * Ready for use on InstaGENI/protoGENI racks ; successful tutorial [[BR]] |
120 | | * Introduces portal to GUIs service, UNIS unified ntwk info service; use by others? [[BR]] |
121 | | * Spiral 5 goals: also work with ExoGENI racks [[BR]] |
122 | | |
123 | | * Need simplified MDOD measurement data object descriptor schema [[BR]] |
124 | | * Also service for creation and editing of MDOD [[BR]] |
125 | | * Possible extensions to other GENI objects, events [[BR]] |
126 | | |
127 | | [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/071112%20I%26M%20GEC14%20Wrap-Up%20Agenda.ppt slides] [[BR]] |
128 | | |
129 | | |
130 | | |
131 | | === GIMI I&M Tools: Goals, Overview and Status === |
132 | | |
133 | | '''PI''' Michael Zink, University of Massachusetts at Amherst (mailto:zink@ecs.umass.edu) [[BR]] |
134 | | '''Co-PI''' Max Ott, NICTA (mailto:max.ott@nicta.com.au) [[BR]] |
135 | | '''Key personnel''' Ilia Baldine, RENCI (mailto:ibaldin@renci.org) [[BR]] |
136 | | |
137 | | [wiki:GIMI GIMI wiki] [[BR]] |
138 | | [http://gimi.ecs.umass.edu/ GIMI website at UMass Amherst] [[BR]] |
139 | | |
140 | | Goals [[BR]] |
141 | | * Starts with OML, and provides easy-to-use tools for GENI environment [[BR]] |
142 | | |
143 | | * First focus: I&M use cases for experiments, with default OML Client in nodes that gathers passive measurements like INSTOOLS, and provides basic node-to-node connectivity tests using ping and iperf [[BR]] |
144 | | * Second focus: I&M use cases for infrastructure measurement [[BR]] |
145 | | * Later focus: add sensor measurement data, carried in data network [[BR]] |
146 | | |
147 | | * Spiral 4 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
148 | | * Later, support: WiMAX sites [[BR]] |
149 | | * Spiral 5 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
150 | | |
151 | | * Introduces XML messaging service, with pub/sub, in public IP space [[BR]] |
152 | | * Introduces iRODS service, as a measurement data archive. [[BR]] |
153 | | * Introduces IREEL portal service, for measurement data analysys and presentation. [[BR]] |
154 | | |
155 | | |
156 | | Summary: [[BR]] |
157 | | |
158 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GIMI%20GEC%2014%20I%26M%20Session.pptx GIMI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
159 | | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GIMIv1.0Tutorial GIMI v1.0 tutorial] [[BR]] |
160 | | |
161 | | |
162 | | |
163 | | === GEMINI I&M Tools: Goals, Overview and Status === |
164 | | |
165 | | '''PI''' Martin Swany, Indiana University (mailto:swany@iu.edu) [[BR]] |
166 | | '''Co-PI''' Chris Small, Indiana University (mailto:chsmall@indiana.edu) [[BR]] |
167 | | '''Co-PI''' James Griffioen, University of Kentucky (mailto:griff@netlab.uky.edu) [[BR]] |
168 | | '''Co-PI''' Zongming Fei, University of Kentucky (mailto:fei@netlab.uky.edu) [[BR]] |
169 | | |
170 | | [wiki:GEMINI GEMINI wiki] [[BR]] |
171 | | |
172 | | Goals [[BR]] |
173 | | |
174 | | * Includes LAMP code and features in GEMINI tools, to provides flexible tools based on perfSONAR for active infrastructure measurements [[BR]] |
175 | | * Includes INSTOOLS code and features in GEMINI tools, to gather basic host measurements [[BR]] |
176 | | * Later, integrates LAMP and INSTOOLS code and features into new code base for GEMINI tools. [[BR]] |
177 | | |
178 | | * First focus: I&M use cases for infrastructure measurement [[BR]] |
179 | | * Include sharing of data with other users (e.g., operators), at an interface with authorization using a GENI credential [[BR]] |
180 | | * Show how to monitor clusters/racks [[BR]] |
181 | | * Show how to measure Layer 2 and OpenFlow paths (with input from OnTimeMeasure project) [[BR]] |
182 | | |
183 | | * Second focus: I&M use cases for experiments [[BR]] |
184 | | * Gather basic host measurements (as was done by INSTOOLS using SNMP) [[BR]] |
185 | | * Show how to gather customized data from applications (as provided by OML Client) [[BR]] |
186 | | |
187 | | * Spiral 4 supported aggregates: protoGENI/Emulab servers/VMs and InstaGENI (HP) racks [[BR]] |
188 | | * Spiral 5 supported aggregates: ORCA servers/VMs and ExoGENI (RENCI) racks [[BR]] |
189 | | |
190 | | * Continues INSTOOLS portal service, to find GUIs [[BR]] |
191 | | * Continues LAMP local and global Unified Network Information Service (UNIS), to register available measurement data, and network topology [[BR]] |
192 | | |
193 | | Summary [[BR]] |
194 | | |
195 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/GEMINI%20Overview%20and%20Direction-GEC14.pptx GEMINI architecture, design and status at GEC14; plan for GEC-14 tutorial; next steps during Spiral 5] [[BR]] |
196 | | * For more information, attend or audit [http://groups.geni.net/geni/wiki/GEMINITutorial GEMINI v1.0 tutorial] [[BR]] |
197 | | |
198 | | |
199 | | |
200 | | |
201 | | |
202 | | == Persistent Multi-user I&M Services == |
203 | | |
204 | | |
205 | | Goals [[BR]] |
206 | | * Use by both GIMI and GEMINI tools sets [[BR]] |
207 | | * Use by other parts of GENI [[BR]] |
208 | | * Identify need for further reviews and discussions [[BR]] |
209 | | |
210 | | |
211 | | === S1) GENI (XML) Messaging Service === |
212 | | |
213 | | === S2) GENI Storage and Archive Service (based on iRODS) === |
214 | | 9:15am [[BR]] |
215 | | |
216 | | Shu Huang (RENCI) [[BR]] |
217 | | |
218 | | Tasks |
219 | | * Establish iRODS service(s), and define rules (interfaces) to provide GENI measurement data archive functions. [[BR]] |
220 | | |
221 | | Summary |
222 | | * [wiki:InstMeasTopic_4.9ArchiveService status at GEC13] [[BR]] |
223 | | * [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T9b%29%20%20gec13_irods_im_anirban.pptx slides at GEC13] [[BR]] |
224 | | * iRODS service has been established at RENCI [[BR]] |
225 | | * iRODS service has been established at Univ of Kentucky [[BR]] |
226 | | * [http://groups.geni.net/geni/attachment/wiki/GEC14Agenda/IMDesignTopics/irods-gec14-1.pptx iRODS configuration at GEC14] [[BR]] |
227 | | * Proposed configuration? [[BR]] |
228 | | * Operations plan? [[BR]] |
229 | | |
230 | | Discussion |
231 | | * Who is lead? [[BR]] |
232 | | * Will all iRODS services be federated, for redundancy? |
233 | | * How to move data to service: move file; move SQL DB; or? [[BR]] |
234 | | * How is persistent object identifier (i.e., handle) generated? also registered? and later resolved? Include necessary Object Identifier (OI) service.[[BR]] |
235 | | * How are partitions for different users managed? [[BR]] |
236 | | * How is authorization for a user done? [[BR]] |
237 | | * How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
238 | | * How will the GEMINI project use the iRODS service? [[BR]] |
239 | | * Will other parts of GENI want to use the iRODS service? [[BR]] |
240 | | * Do we need a breakout session for further discussion? when? [[BR]] |
241 | | |