| 167 | | b) MDOD registry. Use UNIS lookup service? Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]] |
| 168 | | |
| 169 | | c) MDOD creation and editing service. [[BR]] |
| 170 | | |
| 171 | | d) Object (e.g., Measurement Data Object or I&M Service) names; need a public reference; consider DataCite [[BR]] |
| 172 | | |
| 173 | | e) Object registry, with names and public key. [[BR]] |
| 174 | | |
| 175 | | 2) Who: Jason Zurawski (Internet2); Ezra Kissel (U Delaware); Eric Boyd (Internet2); Chris Small (GEMINI, IU); Scott Jensen (Indiana U); Larry Lannom (CNRI); LEAD Giridhar Manepalli (CNRI); Deniz Gurken (GIMI, UH); Harry Mussman (GPO) [[BR]] |
| | 167 | b) Want to extend MDOD to cover all types of objects, i.e., software images. (NetKarma) |
| | 168 | |
| | 169 | c) Want to use MDOD schema to define Event Record schema. (NetKarma) |
| | 170 | |
| | 171 | d) MDOD registry. Use UNIS lookup service? Use DOR registry? Include in iRODS? Consider IF-MAP server? [[BR]] |
| | 172 | |
| | 173 | e) MDOD creation and editing service. [[BR]] |
| | 174 | |
| | 175 | f) Object (e.g., Measurement Data Object or I&M Service) names; need a public reference; consider DataCite [[BR]] |
| | 176 | |
| | 177 | g) Object registry, with names and public key. [[BR]] |
| | 178 | |
| | 179 | |
| | 180 | |
| | 181 | 2) Who: Jason Zurawski (Internet2); Ezra Kissel (U Delaware); Eric Boyd (Internet2); Beth Plale (IU); Chris Small (GEMINI, IU); Scott Jensen (Indiana U); Larry Lannom (CNRI); LEAD Giridhar Manepalli (CNRI); Deniz Gurken (GIMI, UH); Harry Mussman (GPO) [[BR]] |
| 236 | | a) Towards Max Ott's vision for experiment support [[BR]] |
| 237 | | |
| 238 | | b) Consider INSTOOLS portal service [[BR]] |
| 239 | | |
| 240 | | c) Define portal service for GIMI tools, with multiple functions. [[BR]] |
| 241 | | |
| 242 | | d) Can these portal services be merged? [[BR]] |
| 243 | | |
| 244 | | e) How can these services be shared by GEMINI? [[BR]] |
| 245 | | |
| 246 | | f) Are these portal services really a combination of gateway and user workspace services, with various available tools?[[BR]] |
| 247 | | |
| 248 | | g) How are partitions for different users managed? [[BR]] |
| 249 | | |
| 250 | | h) Can partictions be assigned to users using WINLAB login service? |
| 251 | | |
| 252 | | 2) Who: Jim Griffioen and/or Charles Carpenter (U Kentucky); Christoph Dwertmann (NICTA); Chris Small, for NetKarma (Internet2); Ahmed El-Hassany (IU); Jeanne Ohren (GPO) [[BR]] |
| 253 | | |
| 254 | | |
| 255 | | === 4.9) User Workspace and Archive Services === |
| | 242 | a) Towards Max Ott's vision that provides a unified environment for experiment support [[BR]] |
| | 243 | |
| | 244 | b) GENI User Workspace Service is a container for a wide range tools including: experiment control tools; portal tools; measurement analysis and presentation tools |
| | 245 | |
| | 246 | c) Is a Linux OS environment with files system, certificate and credential stores |
| | 247 | |
| | 248 | d) Linux environment can be hosted on server dedicated to user; shared among multiple users in an organization; shared among multiple GENI users. |
| | 249 | |
| | 250 | e) Many tools interact with GENI aggregates using GENI APIs |
| | 251 | |
| | 252 | f) Many tools have a user interface, i.e.,a web interface |
| | 253 | |
| | 254 | g) Many tools call other tools through published APIs. |
| | 255 | |
| | 256 | h) Having all tools in the same container with a certificate store minimizes effort to gain authorizations. |
| | 257 | |
| | 258 | i) Would prefer a service useful with both GIMI and GEMINI tools [[BR]] |
| | 259 | |
| | 260 | j) Should compare with CNRI prototype User Workspace service |
| | 261 | |
| | 262 | k) Operations plan for GENI User Worksapce service |
| | 263 | |
| | 264 | 2) Who: Jim Griffioen and/or Charles Carpenter (U Kentucky); Max Ott (NICTA); Christoph Dwertmann (NICTA); Chris Small, for NetKarma (Internet2); Ahmed El-Hassany (IU); Jeanne Ohren (GPO) [[BR]] |
| | 265 | |
| | 266 | |
| | 267 | === 4.9) Archive Service === |
