wiki:IMInteroperability

Version 3 (modified by Jeanne Ohren, 6 years ago) (diff)

--

Interoperability of I&M tools on racks

The primary goal of this effort is to get the GIMI and GEMINI tools working on both InstaGENI and ExoGENI racks. To work toward this goal, we need to address items in the following areas:

  • Tools
    • Slice creation (Flack/Flukes/Omni)
    • Presentation/Orchestration (GENI Desktop/Labwiki)
    • Archival (iRODS)
  • Resources
  • Images
  • Rspecs
  • Configuration
    • initialize/instrumentize
    • postboot scripts
  • Testing
    • What are the basic use cases?
  • Certificates
    • We should be able to use certificates issued by all four of these authorities for both sets of tools
      • Utah emulab, UKY emulab, PGENI, GENI Portal

Mailing lists

These lists should be used for help on questions or issues with each of the racks. Subscribing to each of these lists will allow you to see the latest questions, answers, known issues and scheduled downtime related to each of the racks.

Known differences between racks

ExoGENI InstaGENI
Virtualization technology KVM openvz
Images requires separate filesystem/kernel/ramdisk images, highly recommended to add NEuca guest extensions, must run on KVM Because VMs are openvz containers, must be same OS as hypervisor (Fedora)
Data plane IPs doesn't auto-assign IPs when not specified in request auto-assigns IPs when not specified in request
Login information Not available in manifest until resources are active Available as soon as resources are provisioned

GIMI on InstaGENI

Tools

  • Slice creation
    • Flack
    • Omni
  • Presentation/Orchestration
    • Labwiki
    • OMF/OML

Resources

No known resource restrictions identified yet.

Images

  • Create custom VM image
  • Fedora
    • common Ubuntu image not expected until July

Rspecs

  • Convert current tutorial RDF to rspec
  • Test the rspec on InstaGENI using both Flack and omni

Configuration

  • Convert postboot functionality into execute service script

Certificates

  • Certificates not yet used for Labwiki

Testing

GEMINI on ExoGENI

Tools

Resources

What are the resource restrictions for GEMINI? What resources are available on ExoGENI?

Images

Rspecs

  • How does ExoGENI handle GEMINI extensions?
    • Outstanding issue: ORCA is not able to pass thru extensions that is does not know about to the manifest. This includes Flack and GEMINI extensions.
    • Let's discuss a more general 'measurement' extension for RSpecs usable by GIMI and GEMINI. We can add an NDL extension to support it in ORCA /ib
  • Convert current tutorial rspec to RDF
  • Test the RDF on ExoGENI using Flukes
  • Test the rspec on ExoGENI using omni
  • Test the rspec on ExoGENI using Flack when it is ready

Configuration

  • Test the initialize/instrumentize scripts work on ExoGENI nodes
  • Ahmed has tested converting ExoGENI manifest into UNIS schema

Certificates

Login Instrumentize
Utah Emulab
UKY Emulab
PGENI
GENI Portal

Testing

Task List

ID Description Assignee Status Notes
1 Create custom GEMINI image for ExoGENI Ezra and Hussam Color(#B0E0E6, In Progress)?
2 Create custom GIMI image for InstaGENI Mike and Cong Color(#B0E0E6, In Progress)?
3 Convert current GIMI tutorial RDF to rspec Jeanne Color(#B0E0E6, In Progress)?
4 Test the GIMI rspec on InstaGENI using both Flack and omni Jeanne and Luisa
5 Convert postboot functionality into execute service script Mike and Cong Color(#B0E0E6, In Progress)?
6 Determine basic use cases for testing both sets of tools
7 Test the GEMINI rspec on ExoGENI using omni Ezra Color(#B0E0E6, In Progress)?
8 Test the rspec on ExoGENI using Flack Ezra Color(#B0E0E6, In Progress)?
9 Determine if initialize and instrumentize can get everything it needs from the ExoGENI manifest Hussam
10 Look into possible common measurement extensions for ExoGENI Ilia, Ezra, and Mike Color(#B0E0E6, In Progress)?
11 Add support for GENI Portal certificates in GENI Desktop Hussam Color(#B0E0E6, In Progress)?

Attachments (1)

Download all attachments as: .zip