| 30 | | Provide a way for a GENI user (e.g., experimenter or operator) to access a wide variety of "GENI User Portal Services", where each portal service provides an interface (e.g., API or GUI) to the user. [[BR]] |
| 31 | | |
| 32 | | Together, the "GENI User Portal Services" should provide all of the functions the user needs to setup and run their experiment, then gather, analyze and present the measurement data. [[BR]] |
| | 30 | 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]] |
| | 31 | |
| | 32 | 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 the measurement data. [[BR]] |
| 65 | | == 6) GENI User Portal Services Uses Cases == |
| 66 | | |
| 67 | | [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/GENIExperimenterPortalServiceUseCases.pdf Portal services use cases] (Jeannie Ohren, GPO) [[BR]] |
| 68 | | |
| 69 | | Use Cases: |
| 70 | | – User’s window into GENI [[BR]] |
| 71 | | – Conveniently and easily manage GENI resources, I&M data, and experiment results [[BR]] |
| 72 | | – A place to control the experiment [[BR]] |
| 73 | | – Works for both short/small (weeks-months?) and long/large (months-years?) experiments [[BR]] |
| 74 | | – A place to get to necessary GENI experimenter tools such as Flack, GUSH, OMNI [[BR]] |
| 75 | | – A place to store and retrieve experiment results and analysis (Lab notebook?) [[BR]] |
| 76 | | – MAP (Measurement, Analysis, Presentation) [[BR]] |
| 77 | | – Manages moving I&M data to archive (iRODS?) with metadata (MDOD?) [[BR]] |
| 78 | | – Allows the public to access published experiment results (or is this a separate interface?) [[BR]] |
| 79 | | |
| 80 | | |
| 81 | | == 7) GENI User Workspace Service Configuration == |
| | 65 | == 6) Uses Cases == |
| | 66 | |
| | 67 | [http://groups.geni.net/geni/attachment/wiki/InstMeasTopic_4.8PortalService/GENIExperimenterPortalServiceUseCases.pdf User services use cases] (Jeannie Ohren, GPO) [[BR]] |
| | 68 | |
| | 69 | – User’s window into GENI [[BR]] |
| | 70 | – Conveniently and easily manage GENI resources, I&M data, and experiment results [[BR]] |
| | 71 | – A place to control the experiment [[BR]] |
| | 72 | – Works for both short/small (weeks-months?) and long/large (months-years?) experiments [[BR]] |
| | 73 | – A place to get to necessary GENI experimenter tools such as Flack, GUSH, OMNI [[BR]] |
| | 74 | – A place to store and retrieve experiment results and analysis (Lab notebook?) [[BR]] |
| | 75 | – MAP (Measurement, Analysis, Presentation) [[BR]] |
| | 76 | – Manages moving I&M data to archive (iRODS?) with metadata (MDOD?) [[BR]] |
| | 77 | – Allows the public to access published experiment results (or is this a separate interface?) [[BR]] |
| | 78 | |
| | 79 | |
| | 80 | == 7) User Workspace Service Configuration == |
| 85 | | Linux OS environment: [[BR]] |
| 86 | | - On server: [[BR]] |
| 87 | | - Dedicated to user, i.e., a desktop server [[BR]] |
| 88 | | - In an organization (e.g., BBN), shared by multiple users in the organization [[BR]] |
| 89 | | - In GENI infrastructure, shared by multiple users [[BR]] |
| 90 | | - How are partitions for different users assigned? using GENI resource assignment process? [[BR]] |
| 91 | | – With login for the user [[BR]] |
| 92 | | - Includes file system [[BR]] |
| 93 | | – Includes certificate and credential stores [[BR]] |
| 94 | | – Includes various services/tools dedicated to this user, with programmatic and web interfaces [[BR]] |
| 95 | | - With interfaces/APIs between services tools [[BR]] |
| 96 | | - See Testbed Portal System Requirements above for an example [[BR]] |
| 97 | | - Prefer programmatic interface/API to allow coordination between services, and scripts [[BR]] |
| 98 | | - Prefer web interfaces to allow users to view topology, measurement data, events and trends [[BR]] |
| | 84 | Persistent Linux OS environment dedicated to a user: [[BR]] |
| | 85 | - On a server: [[BR]] |
| | 86 | - Dedicated to user, i.e., a desktop server [[BR]] |
| | 87 | - In an organization (e.g., BBN), shared by multiple users in the organization [[BR]] |
| | 88 | - In GENI infrastructure, shared by multiple users [[BR]] |
| | 89 | - How are partitions for different users assigned? using GENI resource assignment process? [[BR]] |
| | 90 | – With a login for the user [[BR]] |
| | 91 | - Includes a file system for the user[[BR]] |
| | 92 | – Includes certificate and credential stores for the user[[BR]] |
| | 93 | – Includes various services/tools dedicated to this user, with programmatic and web interfaces [[BR]] |
| | 94 | - With interfaces/APIs between services tools [[BR]] |
| | 95 | - See Testbed Portal System Requirements above for an example [[BR]] |
| | 96 | - Prefer programmatic interface/API to allow coordination between services, and scripts [[BR]] |
| | 97 | - Prefer web interfaces to allow users to view topology, measurement data, events and trends [[BR]] |
| | 98 | - Persistent data available to user includes: |
| | 99 | - Certificates and credentials |
| | 100 | - Experiment scripts |
| | 101 | - Experiment topology descriptions (RSpecs) |
| | 102 | - Measurement data and MDODs (metadata) |
