Changes between Version 7 and Version 8 of GeniRspec


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

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniRspec

    v7 v8  
    55This topic was the focus of one of the software engineering sessions at GEC10: [wiki:GEC10RSpec GEC10 Meeting]
    66
    7 Much work remains.
     7== GEC RSpecs Engineering Meeting ==
    88
     9At GEC10 there was a community discussion of how to talk in a common language about resources. For example, without a common way to
     10describe what resources an aggregate provides, it is much harder for experimenters to reason about which resources to use.
     11
     12Ilia 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
     14=== Community Agreement ===
     15The session concluded with community agreement on three points:
     16 * The community will work to agree on common semantics
     17  * Ilia has proposals for layer 2 network resources and compute resources, and has recruited community members for other areas; thanks in advance to Max Ott, Hongwei Zhang, Martin Swany, Mike Zink, and Rob Sherwood. These individuals, and others who volunteer to help, will produce ontologies to represent the agreements.
     18 * GENI will use ProtoGENI RSpec V2 as the format on the wire
     19  * New concepts will be represented as PG RSpec extensions, allowing free addition and evolution of new concepts as needed.
     20 * Aggregates can use Translators to convert between formats
     21  * Ilia is building one between PG and Orca formats.
     22
     23=== Next Steps ===
     24For all of these, community involvement is key. Email dev@geni.net or Aaron Helsinger (ahelsing at geni.net) to get involved. Results will be published to dev@geni.net and to the GENI wiki to keep everyone informed of progress.
     25==== Agree on Concepts ====
     26 * Align edge compute resource concepts, starting with Ilia's proposal.
     27 * 4 key semantic extensions
     28  * Wireless (Max Ott, Hongwei Zhang)
     29  * Measurement (Martin Swany)
     30  * Storage - physical & cloud (Mike Zink)
     31  * !OpenFlow flowspace (Rob Sherwood)
     32 * Produce ontologies for possible ratification at GEC11
     33  * The same groups will produce and present these agreements
     34
     35==== Adopt Schemas ====
     36 * Once the semantics of these things are agreed to, Jon Duerig, Ilia and the GPO will assist in representing these as PG extensions
     37 * Revisit PG schemas
     38  * Change more attributes to be elements as needed
     39  * Make some types less opaque as needed
     40  * Ensure base is extensible for the known needed extensions
     41  * Jon Duerig of ProtoGENI will handle this
     42 * Once adopted, RSpec schemas will be maintained by the community, along with the AM API.
     43 * Modify the AM API specification to require that RSpecs are in the PG RSpec V2 format
     44  * Aaron Helsinger and the GPO will handle this, when the support infrastructure is in place
     45==== Implement Translators ====
     46 * Write and deploy translators as necessary (coordinate with Ilia for a start - ibaldin at renci.org)
     47 * Enable conversion as a GENI-wide service
     48  * Replicating Ilia's converter as necessary
     49 * Test full PG/Orca interoperability by GEC11
     50 * Build a thin PL/PG translation layer at PL (Andy Bavier, Tony Mack, Jon Duerig)
     51 * Other translators as necessary
     52
     53