1 / 8

Upcoming GENI Architecture Topics: The Future of Experiment Management with Gush

Upcoming GENI Architecture Topics: The Future of Experiment Management with Gush. Jeannie Albrecht David Irwin. Current Gush Capabilities. Manage experiments on PlanetLab , ProtoGENI , & ORCA Describe experiments using XML

delu
Download Presentation

Upcoming GENI Architecture Topics: The Future of Experiment Management with Gush

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Upcoming GENI Architecture Topics:The Future of Experiment Management with Gush Jeannie Albrecht David Irwin

  2. Current Gush Capabilities • Manage experiments on PlanetLab, ProtoGENI, & ORCA • Describe experiments using XML • Gush controller (running on experimenter’s local computer) manages execution on GENI resources via Gush clients running remotely • Automatically install required software • (Loosely) synchronize phases of execution across resources • Automatically respond to common failures using simple recovery mechanisms • Provide very basic slice/sliver management features

  3. Gush Assumptions • Slices/slivers exist with proper credentials in place before using Gush • SSH access to resources • Unix-based execution environment • Specialized “low level” network settings are configured before using Gush • No need to interact with/manipulate rspecs from within Gush

  4. Lessons Learned • Supporting experimentation across 3 different control frameworks is challenging • Even with common API, each CF interprets API slightly differently • Providing a single “resource” abstraction for all 3 CFs requires some simplifying assumptions (can’t always take advantage of CF-specific features)

  5. Lessons Learned • Supporting a constantly changing API is frustrating • Hard to innovate when so much time is spent rewriting parsing code • …but this is probably unavoidable

  6. Lessons Learned • K.I.S.S. • Experimenters who are new to GENI get overwhelmed by our terminology and do not know where to begin • Experimenters need a simple, common way to run “hello world” experiments on GENI resources • Most project websites are not geared towards novice experimenters • RSPECs are still very confusing…

  7. Lessons Learned • Experiment management should not be confused with slice/sliver management • Tools that try to “do it all” are too complicated for novice experimenters • There should be easy-to-use tools for slice/sliver management, and easy-to-use tools for experiment management • Design users tools that work with other user tools

  8. “Future” Capabilities of Gush • Main goal: Continue to support experimentation on PlanetLab, ProtoGENI, and ORCA • Ongoing work in Gush: • Improve mechanisms for failure recovery • Increase usability by simplifying configuration • Improve logging for easier debugging • Support for mobile resources with intermittent network connectivity

More Related