wiki:IMInteroperability

Version 2 (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
    • Which should I be able to use 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

What are the resource restrictions for GIMI? What resources are available on instaGENI?

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

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

  • Do the initialize/instrumentize scripts work on ExoGENI nodes?
  • Can initialize/instrumentize get everything it needs from the ExoGENI manifest?

Task List

ID Description Assignee Status Notes
1 Create custom GEMINI image for ExoGENI
2 Create custom GIMI image for InstaGENI
3 Convert current GIMI tutorial RDF to rspec
4 Test the GIMI rspec on InstaGENI using both Flack and omni
5 Convert postboot functionality into execute service script
6 Determine basic use cases for testing both sets of tools
7 Convert the current GEMINI tutorial rspec to RDF
8 Test the GEMINI RDF on ExoGENI using Flukes
9 Test the GEMINI rspec on ExoGENI using omni
10 Test the rspec on ExoGENI using Flack Blocked on Flack functionality
11 Determine if initialize and instrumentize can get everything it needs from the ExoGENI manifest
12
13
14
15

Attachments (1)

Download all attachments as: .zip