| 178 | | a) Use for messages, not generalized data; assume relatively low rate. [[BR]] |
| 179 | | |
| 180 | | b) Use for OMF messages. [[BR]] |
| 181 | | |
| 182 | | c) Use for "event record messages", that can be logged. [[BR]] |
| 183 | | |
| 184 | | d) XMPP server, in public IP space. [[BR]] |
| 185 | | |
| 186 | | e) Entities connect, and are authenticated. [[BR]] |
| 187 | | |
| 188 | | f) An entity may start a pub/sub node. [[BR]] |
| 189 | | |
| 190 | | g) When an entity subscribes, a message is sent to publisher requesting authorization. [[BR]] |
| 191 | | |
| 192 | | h) Operations plan for XML Messaging Service. |
| | 170 | a) Use for messages, not generalized data; assume relatively low rate. [[BR]] |
| | 171 | b) Use for OMF messages. [[BR]] |
| | 172 | c) Use for "event record messages", that can be logged. [[BR]] |
| | 173 | d) XMPP server, in public IP space. [[BR]] |
| | 174 | e) Entities connect, and are authenticated. [[BR]] |
| | 175 | f) An entity may start a pub/sub node. [[BR]] |
| | 176 | g) When an entity subscribes, a message is sent to publisher requesting authorization. [[BR]] |
| | 177 | h) Operations plan for XML Messaging Service. [[BR]] |
| 203 | | |
| 204 | | 1) Definition of topic: [[BR]] |
| 205 | | |
| 206 | | a) Home and global Lookup Service, as defined by perfSONAR [[BR]] |
| 207 | | |
| 208 | | b) Also Topology Service? |
| 209 | | |
| 210 | | c) Global UNIS? Also Local UNIS in slice? [[BR]] |
| 211 | | |
| 212 | | d) Map MDOD into metadata that is registered [[BR]] |
| 213 | | |
| 214 | | e) Can Lookup Service be used for finding portals? [[BR]] |
| 215 | | |
| 216 | | f) Operations plan for Global UNIS. |
| | 187 | 1) Definition of topic: [[BR]] |
| | 188 | |
| | 189 | a) Home and global Lookup Service, as defined by perfSONAR [[BR]] |
| | 190 | b) Also Topology Service? |
| | 191 | c) Global UNIS? Also Local UNIS in slice? [[BR]] |
| | 192 | d) Map MDOD into metadata that is registered [[BR]] |
| | 193 | e) Can Lookup Service be used for finding web interfaces, and other types of portals? [[BR]] |
| | 194 | f) Operations plan for Global UNIS. |
| 228 | | a) Towards Max Ott's vision that provides a unified environment for experiment support [[BR]] |
| 229 | | |
| 230 | | b) GENI User Workspace Service is a container for a wide range tools including: experiment control tools; portal tools; measurement analysis and presentation tools |
| 231 | | |
| 232 | | c) Is a Linux OS environment with files system, certificate and credential stores |
| 233 | | |
| 234 | | d) Linux environment can be hosted on server dedicated to user; shared among multiple users in an organization; shared among multiple GENI users. |
| 235 | | |
| 236 | | e) Many tools interact with GENI aggregates using GENI APIs |
| 237 | | |
| 238 | | f) Many tools have a user interface, i.e.,a web interface |
| 239 | | |
| 240 | | g) Many tools call other tools through published APIs. |
| 241 | | |
| 242 | | h) Having all tools in the same container with a certificate store minimizes effort to gain authorizations. |
| 243 | | |
| 244 | | i) Would prefer a service useful with both GIMI and GEMINI tools [[BR]] |
| 245 | | |
| 246 | | j) Should compare with CNRI prototype User Workspace service |
| 247 | | |
| 248 | | k) Operations plan for GENI User Worksapce service |
| | 206 | a) Towards Max Ott's vision that provides a unified environment for experiment support [[BR]] |
| | 207 | b) GENI User Workspace Service is a container for a wide range tools including: experiment control tools; portal tools; measurement analysis and presentation tools [[BR]] |
| | 208 | c) Is a Linux OS environment with files system, certificate and credential stores [[BR]] |
| | 209 | d) Linux environment can be hosted on server dedicated to user; shared among multiple users in an organization; shared among multiple GENI users. [[BR]] |
| | 210 | e) Many tools interact with GENI aggregates using GENI APIs [[BR]] |
| | 211 | f) Many tools have a user interface, i.e.,a web interface; these are foten called portal tools [[BR]] |
| | 212 | g) Many tools call other tools through published APIs. [[BR]] |
| | 213 | h) Having all tools in the same container with a certificate store minimizes effort to gain authorizations. [[BR]] |
| | 214 | i) Would prefer a service useful with both GIMI and GEMINI tools [[BR]] |
| | 215 | j) Should compare with CNRI prototype User Workspace service [[BR]] |
| | 216 | k) Operations plan for GENI User Worksapce service [[BR]] |
| 260 | | a) Consider CNRI prototype user workspace and archive service [[BR]] |
| 261 | | |
| 262 | | b) Consider U Kentucky archive service [[BR]] |
| 263 | | |
| 264 | | c) Use iRODS service? [[BR]] |
| 265 | | |
| 266 | | d) How to move data to service: move file; move SQL DB; or? [[BR]] |
| 267 | | |
| 268 | | e) How are partitions for different users managed? [[BR]] |
| 269 | | |
| 270 | | f) How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
| 271 | | |
| 272 | | g) Operations plan for Archive Service. |
| | 228 | a) Consider CNRI prototype user workspace and archive service [[BR]] |
| | 229 | b) Consider U Kentucky archive service [[BR]] |
| | 230 | c) Use iRODS service? [[BR]] |
| | 231 | d) How to move data to service: move file; move SQL DB; or? [[BR]] |
| | 232 | e) How are partitions for different users managed? [[BR]] |
| | 233 | f) How is data in MDOD used to set archive sharing policy? what is required in MDOD? [[BR]] |
| | 234 | g) Operations plan for Archive Service. [[BR]] |
