1 / 7

Raven Provisioning Service Spiral 2 Year-end Project Review

Raven Provisioning Service Spiral 2 Year-end Project Review. Department of Computer Science University of Arizona PI: John H. Hartman, Scott Baker Students: Jude Nelson August 31, 2010. Project Summary. Raven is a suite of tools that support long-running GENI experiments:

aletta
Download Presentation

Raven Provisioning Service Spiral 2 Year-end Project Review

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. Raven Provisioning ServiceSpiral 2 Year-end Project Review Department of Computer Science University of Arizona PI: John H. Hartman, Scott BakerStudents: Jude Nelson August 31, 2010

  2. Project Summary • Raven is a suite of tools that support long-running GENI experiments: • Stork: secure package management • Only installs packages that are signed by a trusted principal • IFTD: efficient and fault-tolerant data distribution • Used to distribute packages and Raven metadata • Supports multiple protocols including HTTP, FTP, CoBlitz, BitTorrent • Automatic fail-over • Tempest: distributed package and configuration management • Enables package management actions on collections of distributed machines • Platform-specific package actions • Raven: experiment deployment tool • Simple interface for creating and deploying experiment packages • Ties all the other tools together • Owl: experiment monitoring • Simple client-side scripts collect data, store in centralized MySQL database • Data can be retrieved in HTML, XML, and JSON formats August 31, 2010

  3. Milestone & QSR Status August 31, 2010

  4. Accomplishments 1: Advancing GENI Spiral 2 Goals • Continuous Experimentation: Raven supports long-term experiments. Tempest and Stork allows packages to be installed and updated during an experiment, and an experiment’s configuration to be modified. • Instrumentation & Measurement: The Owl monitoring service is designed to measure and monitor an experiment. • Interoperability: Raven tools have been demonstrated on the PlanetLab, GpENI, VINI, and Seattle platforms, allowing a single experiment to span these platforms. • Identity Management: The Raven tools support the uniform GID format. The Raven team participated in the design of the new format. The Raven tools also have prototype compatibility with the new XML-based credentials and are awaiting deployment of those credentials on the control frameworks for further testing. August 31, 2010

  5. Accomplishments 2:Other Project Accomplishments • Participation in designing the uniform GID format. • Design and development of Canopus, a calendar-based resource allocation system to replace Sirius on the PlanetLab cluster. • Creation of a video tutorial for publishing an experiment using Raven tools. August 31, 2010

  6. Issues • Resource specification is a moving target. How do experiments specify the resources they want and learn the resources they have available across all platforms? • Lack of a uniform mechanism for ‘initscripts’ hinders rapid deployment of Stork and Tempest. Within PLC-like environments, initscripts must be manually installed by the administrator. Other control frameworks (for example, ProtoGENI) use different mechanisms, requiring a custom means of bootstrapping Stork and Tempest for each control framework. We suggest the control frameworks adopt some uniform mechanism for setting non-resource attributes like initscripts. • Determining user identity (i.e. public keys, GIDs) from within slivers differs between control frameworks and even between components within control frameworks, requiring custom code development. We suggest the control frameworks create a specification for a minimum on-component environment that includes the component GID and the allowed users’ GIDs. August 31, 2010

  7. Plans • Spiral 2 • Raven release that includes IFTD • Add authentication and security to Owl • Spiral 3 • Better GUIs for Owl and Raven • Pub/sub as a stand-alone service for experiment control • Additional Raven video tutorials • Better cross-platform support, esp. ProtoGENI • Better VINI integration, allowing VNIT topology to be specified via Raven tools • Add time-series support to Owl August 31, 2010

More Related