Version 5 (modified by, 11 years ago) (diff)



Session Leaders

Ilia Baldine, RENCI
Aaron Helsinger, GPO


Wed 1:00 - 3:00 pm


This meeting will seek agreement on a proposed single common RSpec format for GENI. In order to truly allow interoperability among multiple control frameworks and aggregates, GENI requires a common language for describing resources, resource requests, and reservations - a single, well defined RSpec schema. Currently, each control framework has its own custom schema, often evolved incrementally as needs have changed. Over the years, the community has met to discuss the various alternative approaches, and their relative merits. But now it is time to make a decision and move forward. In recent weeks that discussion has become more focused. Several key stakeholders have debated various alternatives. In this meeting, they will present a proposal for a way forward resulting from this discussion, the alternatives, and open the meeting for discussion.


The proposal for the RSpec workshop led by Ilia Baldine of RENCI is that all GENI AM API calls will be in terms of ProtoGENI RSpec V2 format RSpecs, with aggregates free to use translators to continue to talk their native formats internally. Orca is already building such a converter.


  • Introduction and Background - Aaron Helsinger
  • Proposed Solution - Ilia Baldine
  • NML work at OGF, network resource abstractions; Measurement resource abstractions - Martin Swany, University of Delaware
  • Ongoing NDL work - Jeroen van der Ham, University of Amsterdam
  • Implications and Alternatives - TBD
  • Discussion (all)
  • Summary and Wrap Up - Aaron Helsinger

Background Reading

Orca RSpecs:
NDL (Orca RSpec schema):
NDL Schema:
XML vs RDF analysis by NDL team:
ProtoGENI RSpecs description:
ProtoGNEI RSpec V2:
Orca NDL-OWL RSpecs:
Orca NDL-OWL Converter:

Attachments (10)