Changes between Version 12 and Version 13 of GeniRspec


Ignore:
Timestamp:
10/31/12 13:46:39 (7 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniRspec

    v12 v13  
    11= Resource Specification (RSpec) =
    22
    3 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. GENI has standardized now on XML documents following agreed schemas to represent resources, with aggregate or resource specific extensions supported. Ongoing work covers agreeing upon ontologies for other resource types.
     3In 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. GENI has standardized now on XML documents following agreed schemas to represent resources, with aggregate or resource specific extensions supported. The current RSpec schemas are posted on [http://www.geni.net/resources/rspec/ geni.net]. Ongoing work covers agreeing upon ontologies for other resource types.
     4
     5'''This page needs improvement, to better document what an RSpec is, how they work, and how to read or construct one.'''
    46
    57This topic was the focus of one of the software engineering sessions at GEC10, and the agenda wiki page has detailed minutes from the meeting: [wiki:GEC10RSpec GEC10 Meeting]. A summary of that meeting is below, but this session agreed to use XML RSpecs starting with the ProtoGENI v2 schemas to represent resources in GENI. We agreed to work on common ontologies.
     
    99101 - Adopt AM API revisions
    100102 - Move GENI RSpec schemas to the geni.net namespace
    101