| 13 | | === Spiral 2 and Spiral 3 Goals (12:10pm, Mussman) === |
| 14 | | |
| 15 | | The following goals have been established by the GPO for Spiral 2. [[BR]] |
| 16 | | |
| 17 | | Goal 1: Live experiments, the central goal of Spiral 2. Support significant numbers of research experiments in the end-to-end prototype systems. The GPO expects live experimentation to begin near the end of Spiral 1, which will intensify through Spiral 2 as we begin continuous operation of the prototype systems. This will begin to give us all substantial (early) operational experience, as these experiments will help us all understand the prototypes' strengths and weakness, which will drive our Spiral 3 goals. [[BR]] |
| 18 | | Goal 2: Identity management [[BR]] |
| 19 | | Goal 3: Improved integration of data & control planes, within clusters [[BR]] |
| 20 | | Goal 4: Instrumentation [[BR]] |
| 21 | | Goal 5: Interoperability, permitting clusters to access the widest number of aggregate [[BR]] |
| 22 | | |
| 23 | | For Spiral 3, these goals are reaffirmed, and particularly: [[BR]] |
| 24 | | |
| 25 | | Goal 1: Live experiments [[BR]] |
| 26 | | Goal 2: Identity management [[BR]] |
| 27 | | Goal 5: Interoperability, permitting clusters to access the widest number of aggregate, including use of GENI AM API [[BR]] |
| | 13 | === Spiral 3 Goals (12:10pm, Mussman) === |
| | 14 | |
| | 15 | The following high-level goals have been established by the GPO for Spiral 3: [[BR]] |
| | 16 | |
| | 17 | Experiments: [[BR]] |
| | 18 | Use by outside researchers[[BR]] |
| | 19 | Use involving multiple aggregates[[BR]] |
| | 20 | Use for research experiments [[BR]] |
| | 21 | |
| | 22 | Some expected experiments using Cluster D:[[BR]] |
| | 23 | Programmable Packet Networks over Dynamic Circuit Substrate (Jeff Chase, Xiaowei Yang)[[BR]] |
| | 24 | Optical-layer experiments (BEN network, ERM sensors)[[BR]] |
| | 25 | Mobile wireless experiments (DOME)[[BR]] |
| | 26 | Sensor experiments, e.g., Nowcasting experiments, using weather data from ViSE radar, processed in local cluster and/or cloud (ViSE and DICLOUD)[[BR]] |
| | 27 | Sensor network experiments (Kansei)[[BR]] |
| | 28 | |
| | 29 | |
| | 30 | Interoperability:[[BR]] |
| | 31 | Researchers can obtain and stitch resources from multiple aggregates[[BR]] |
| | 32 | Researchers from other CFs (e.g., protoGENI) can obtain resources from Cluster D via GENI AM API [[BR]] |
| | 33 | Researchers in Cluster D can obtain resources from other CFs (e.g., protoGENI)via GENI AM API [[BR]] |
| | 34 | |
| | 35 | Some specific goals for GEC10:[[BR]] |
| | 36 | Demo experiment where Cluster D researchers obtain and stitch resources from multiple Cluster D sites (and backbone domains) using their SM.[[BR]] |
| | 37 | Demo experiment where protoGENI researchers obtain resources via GENI AM API v1.0, using RSpec resource description.[[BR]] |
| | 38 | Demo operations portal into Cluster D site, for status and logs, with connections to GMOC[[BR]] |
| | 39 | |
| | 40 | Some specific goals for GEC11: [[BR]] |
| | 41 | Demo experiment where Cluster D researchers get resources from protoGENI aggregates via GENI AM API v1.0 (or protoGENI AM API?) (using RSpec resource description)[[BR]] |
| | 42 | Demo experiment where Cluster D researchers stitch L2 connectivity across Cluster C (protoGENI), and Cluster D sites[[BR]] |
| | 43 | Demo experiment where Cluster D researchers include tools (e.g., GUSH) to help authorize, reserve and assign resources via “ORCA SM API v1.0” XMLRPC interface to their SM (like protoGENI AM API?) (same as GENI AM API v2.0? )[[BR]] |
| | 44 | |
| | 45 | |
| | 46 | === Spiral 3 Roadmap (proposed) (12:20pm, Mussman and Baldine) === |
| | 47 | |
| | 48 | Task list: |
| | 49 | Streamline Cluster D site setup and operation, including cluster (Eucalyptus) and connector (L2 switch, with full tag mapping) |
| | 50 | Streamline connectivity to Cluster D sites on campuses, via regional networks (LEARN project) |
| | 51 | |
| | 52 | Allow Cluster D researchers to obtain and stitch resources from multiple Cluster D sites, connected by backbone domain, using their SM. |
| | 53 | Plan to authenticate users in SM via InCommon/Shibboleth |
| | 54 | |
| | 55 | With other CFs, a plan for consistent names and interfaces |
| | 56 | With other CFs, a plan for resource descriptions at interoperability interfaces |
| | 57 | Plan to interop with other CFs, particularly from and to protoGENI (Cluster C) |
| | 58 | |
| | 59 | Allow GENI (e.g., protoGENI) researchers to obtain resources via GENI AM API v1.0 (using RSpec resource description) |
| | 60 | |
| | 61 | Allow Cluster D researchers to include tools (e.g., GUSH) to help authorize, reserve, assign and configure resources via “ORCA SM API v1.0” XMLRPC interface to their SM (like protoGENI AM API, same as GENI AM API v2.0? ) |
| | 62 | |
| | 63 | Plan to get resources from protoGENI aggregates via GENI AM API v1.0 (or protoGENI AM API?) (using RSpec resource description) |
| | 64 | |
| | 65 | Plan for naming and stitching L2 connectivity across Cluster C (protoGENI), and Cluster D sites |
| | 66 | |
| | 67 | Plan for operations portal into Cluster D site, including status and logs, with connections to GMOC |
| | 68 | |
| | 69 | Views: |
| | 70 | |
| | 71 | Figure 1-1) and 1-2): CLuster D Config at end of Spiral 3 |
| | 72 | |
| | 73 | Figure 2): ORCA Site Config |
| | 74 | |
| | 75 | Figure 3): Multiple ORCA Sites |
| | 76 | |
| | 77 | Figure 4): ORCA Interop with protGENI |
| | 78 | |
| | 79 | Figure 5): ORCA Experiment Flow |
| | 80 | |
| | 81 | |
| | 82 | |
