| 72 | |
| 73 | Goals for Spiral 5: |
| 74 | By the end of Spiral 5, GEMINI tools will test/operate in slices built in both the Emulab/protoGENI/InstaGENI and ORCA/ExoGENI environments (but not in one slice) [[BR]] |
| 75 | By the end of Spiral 5, GIMI tools will test/operate in slices built in both the Emulab/protoGENI/InstaGENI and ORCA/ExoGENI environments (but not in one slice) [[BR]] |
| 76 | Not yet defined: support for PlanetLab/InstaGENI environment [[BR]] |
| 77 | |
| 78 | Goals for later: [[BR]] |
| 79 | Both GEMINI and GIMI tools will test/operate in slices built with slices that combine both Emulab/protoGENI/InstaGENI and ORCA/ExoGENI environments. However, this requires stitching functions that are not yet available. [[BR]] |
| 80 | |
| 81 | === 6.2) Spiral 4 Test Environment === |
| 82 | |
| 83 | The environment where I&M tools must operate and will be tested by the end of Spiral 4 [[BR]] |
| 84 | |
| 85 | Interfaces/protocols/APIs between user tools and GENI aggregates [[BR]] |
| 86 | Must use GENI AM API v2 and GENI rspec v3, as the common way to acquire resources, load images/software and setup connectivity |
| 87 | |
| 88 | |
| 89 | User tools and services for experiment and measurement, setup and orchestration [[BR]] |
| 90 | Must use Gush with OMNI as the common tools to acquire resources, load images/software, setup connectivity and manage processes[[BR]] |
| 91 | May use OMF Experiment Controller (EC) to orchestrate experiment/application [[BR]] |
| 92 | These are to be used because they can be driven by scripts, which are essential to repeatable regression testing of I&M tools[[BR]] |
| 93 | |
| 94 | Included GENI aggregtaes, with enumerated topologies [[BR]] |
| 95 | Emulab/protoGENI/InstaGENI, for servers or VMs, with VLANs between hosts, and IP to backbone/Internet[[BR]] |
| 96 | ORCA/ExoGENI, for servers or VMs, with VLANs between hosts, and IP to backbone/Internet[[BR]] |
| 97 | PlanetLab/InstaGENI, for VMs, with IP to backbone/Internet[[BR]] |