[[PageOutline]] = T4) GENI I&M Testing Environment = Platform Targets [[BR]] Experiment and Measurement Orchestration Tools [[BR]] Interfaces/Protocols Between Tools and Services [[BR]] == 1) Goals == Provide a concise definition of the GENI environment for acceptance testing and operating GENI I&M tools. [[BR]] Define a step-by-step process for the GEMINI and GIMI tools sets over Spirals 4, 5 and 6 such that: [[BR]] They deliver useful tools in each spiral [[BR]] They eventually provide tools that can be included in slices built with any type of GENI hosts [[BR]] Included GENI hosts should be those provided by ExoGENI and InstaGENI racks, as soon as they are available [[BR]] == 2) Tasks == Define the environment where the GENI I&M tools must operate and will be tested, including: [[BR]] User tools and services for experiment and measurement, setup and orchestration [[BR]] Interfaces/protocols/APIs between user tools and GENI aggregates [[BR]] Included GENI aggregtaes, with enumerated topologies [[BR]] == 3) Team == LEAD Harry Mussman (GPO) [[BR]] Martin Swany (IU) [[BR]] Jim Griffioen (U Kentucky) [[BR]] Ilia Baldine, for ExoGENI racks (RENCI) [[BR]] ?, for InstaGENI racks (?) [[BR]] David Irwin (UMass Amherst) [[BR]] Mike Zink (UMass Amherst) [[BR]] Christoph Dwertmann (NICTA) [[BR]] Tom Mitchell (GPO) [[BR]] Aaron Helsinger (GPO) [[BR]] Vic Thomas (GPO) [[BR]] [[BR]] == 4) Meetings == (organized calls or meetings before GEC13?) [[BR]] Review conclusions in pre-meeting at GEC13 Review with working team at GEC13 == 5) Open Issues == == 6) Spiral-by-Spiral Goals for GENI I&M Testing Environment == Define a step-by-step process for the GEMINI and GIMI tools sets over Spirals 4, 5 and 6 such that: [[BR]] They deliver useful tools in each spiral [[BR]] They eventually provide tools that can be included in slices built with any type of GENI hosts [[BR]] GENI hosts should include those provided by ExoGENI and InstaGENI racks, as soon as they are available [[BR]] Start where they are now: [[BR]] GEMINI is based on LAMP and INSTOOLS, that have been demonstrated/used on Emulab/protoGENI resources [[BR]] GIMI is based on OML, that has operated in the OMF environment. However, a GIMI co-PI (Ilia Baldine) is also PI of the ORCA and ExoGENI projects [[BR]] Goals for Spiral 4: By the end of Spiral 4, GEMINI tools will test/operate in slices built in Emulab/protoGENI/InstaGENI environment [[BR]] By the end of Spiral 4, GIMI tools will test/operate in slices built in ORCA/ExoGENI environment [[BR]] As much as possible, the two groups will use common user tools and common interfaces/protocols/APIs [[BR]] As much as possible, the two groups will avoid arrangements customized to one environment [[BR]] Both groups will be ready to provide tutorials on their capabilities starting at GEC-14. [[BR]] Not yet defined: support for PlanetLab/InstaGENI environment [[BR]] Goals for Spiral 5: 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 together in one slice) [[BR]] 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 together in one slice) [[BR]] Goals for later: [[BR]] Both GEMINI and GIMI tools will test/operate in slices built with both Emulab/protoGENI/InstaGENI and ORCA/ExoGENI environments. However, this requires stitching functions that are not currently available. [[BR]] == 7) GENI I&M Testing Environment for Spiral 4 and Beyond == Interfaces/protocols/APIs between user tools and GENI aggregates [[BR]] Must use GENI AM API v2 and GENI rspec v3, as the common way to acquire resources, load images/software and setup connectivity User tools and services for experiment and measurement, setup and orchestration [[BR]] Must use Gush with OMNI as the common tools to acquire resources, load images/software, setup connectivity and manage processes[[BR]] May use OMF Experiment Controller (EC) to orchestrate experiment/application [[BR]] These are to be used because they can be driven by scripts, which are essential to repeatable regression testing of I&M tools[[BR]] Included GENI aggregates, with enumerated topologies [[BR]] Emulab/protoGENI/InstaGENI, for servers or VMs, with VLANs between hosts, and IP to backbone/Internet[[BR]] ORCA/ExoGENI, for servers or VMs, with VLANs between hosts, and IP to backbone/Internet[[BR]] PlanetLab/InstaGENI, for VMs, with IP to backbone/Internet[[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_04.jpg, 110%)]] [[BR]] === 7.1) Interfaces/protocols/APIs between User Tools and GENI Aggregates === Spiral 4 interfaces/protocols/APIs between user tools and GENI aggregates [[BR]] Must use GENI AM API v2 and GENI rspec v3, as the common way to acquire resources, load images/software and setup connectivity [[BR]] Spiral 5 interfaces/protocols/APIs between user tools and GENI aggregates [[BR]] When will GENI AM API v3 be defined? what can be done with it? UpdateSliver? [[BR]] When will GENI rspec v4 be defined? what can be done with it? [[BR]] When will external stitching be possible? [[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_06.jpg, 110%)]] [[BR]] === 7.2) User Tools and Services for Experiment and Measurement, Setup and Orchestration === Essential user tools and services for experiment and measurement, setup and orchestration [[BR]] Must use Gush with OMNI as the common tools to acquire resources, load images/software, setup connectivity and manage processes[[BR]] May use OMF Experiment Controller (EC) to orchestrate experiment/application [[BR]] These are to be used because they can be driven by scripts, which are essential to repeatable regression testing of I&M tools[[BR]] Have defined a Linux "User Environment" to hold various user tools; see topic T8) [[BR]] User tools may have GUI and/or API interfaces [[BR]] Environment provides a place to run scripts, e.g., to run regression tests of I&M tools [[BR]] Environment provides a place to store keys/certificates/credentials, so that scripts can run without manual intervention [[BR]] "User Environment" also holds other useful tools, that can also be tested in this environment [[BR]] Portal to GUIs (GEMINI/INSTOOLS) [[BR]] Directory Archive service (CNRI) [[BR]] MDOD Creator/Editor service (CNRI and GPO) [[BR]] MC/MAP services (GIMI) [[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_05.jpg, 110%)]] [[BR]] === 7.3) Emulab/protoGENI/InstaGENI Aggregates === Emulab/protoGENI/InstaGENI, for servers or VMs, with VLANs between hosts, and IP to backbone/Internet[[BR]] Utah Emulab/protoGENI cluster [[BR]] I2 backbone protoGENI cluster (p/o Utah cluster) [[BR]] Kentucky Emulab/protoGENI cluster [[BR]] BBN Emulab/protoGENI cluster? [[BR]] BBN InstaGENI rack, when available [[BR]] Northwestern InstaGENI rack, when available [[BR]] Node options supported? [[BR]] Connectivity options supported? [[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_07.jpg, 110%)]] [[BR]] === 7.4) Environment for GEMINI GEC-13 Demo === Tentative plan as shown [[BR]] FLACK tool with GUI interface MAY be used, IF it is run in User Workspace: [[BR]] To compose rspec for desired slice, which is then passed to Gush/OMNI to acquire resources [[BR]] To present topology of current slice [[BR]] It should NOT be used to acquire resources [[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_08.jpg, 110%)]] [[BR]] === 7.5) ORCA/ExoGENI Aggregates === ORCA/ExoGENI, for servers or VMs, with VLANs between hosts, and IP to backbone/Internet[[BR]] RENCI ORCA cluster [[BR]] Duke ORCA cluster [[BR]] UNC ORCA cluster [[BR]] Texas ORCA cluster [[BR]] RENCI ExoGENI rack, when available [[BR]] BBN ExoGENI rack, when available [[BR]] Node options supported: [[BR]] Servers, at some sites [[BR]] VMs at all sites, using OpenStack, with NEuca [[BR]] Many images, from "ImageProxy" web server [[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_09.jpg, 110%)]] [[BR]] Connectivity options supported: [[BR]] VLANs with aggregate (inta-site) [[BR]] VLANs accross backbone (inter-site) [[BR]] See "regression test suite for ORCA network code" [[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_10.jpg, 110%)]] [[BR]] === 7.6) Environment for GIMI GEC-13 Demo === Tentative plan as shown [[BR]] FLUKES tool with GUI interface MAY be used, IF it is run in User Workspace: [[BR]] To compose rspec for desired slice, which is then passed to Gush/OMNI to acquire resources [[BR]] To present topology of current slice [[BR]] It should NOT be used to acquire resources [[BR]] Consider doing the same with FLACK tool [[BR]] [[Image(Visio-030212_UseCases_Projects_Figures_Page_11.jpg, 110%)]] [[BR]]