Changes between Version 8 and Version 9 of GeniRspec


Ignore:
Timestamp:
04/07/11 14:21:47 (8 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniRspec

    v8 v9  
    33In 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.
    44
    5 This topic was the focus of one of the software engineering sessions at GEC10: [wiki:GEC10RSpec GEC10 Meeting]
     5This 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]
    66
    7 == GEC RSpecs Engineering Meeting ==
     7== GEC10 RSpecs Engineering Meeting ==
    88
    99At GEC10 there was a community discussion of how to talk in a common language about resources. For example, without a common way to
     
    1111
    1212Ilia Baldine of RENCI and the Orca control framework proposed a 'workable path forward'. Martin Swany, Jeroen van der Ham, Rob Ricci, Rob Sherwood, Max Ott, Jeff Chase, Andy Bavier, Aaron Falk and others all contributed to a lively debate. Thanks to everyone who has been participating. In the end we agreed to negotiate a common understanding of key concepts, and then use translators to support a single format on the wire as a path forward for GENI.
     13
     14Detailed results of the meeting are on the meeting wiki page: [wiki:GEC10RSpec GEC10 Meeting]
    1315
    1416=== Community Agreement ===