Changes between Version 5 and Version 6 of GEC12GeniAmAPI


Ignore:
Timestamp:
11/28/11 10:10:46 (8 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEC12GeniAmAPI

    v5 v6  
    1717  * [wiki:GAPI_AM_API_DRAFT#ChangeSetA RSpecs are GENI V3 schema XML documents]
    1818  * [wiki:GAPI_AM_API_DRAFT#ChangeSetB Add a new options argument and change method returns to a richer structure]
    19   * [wiki:GAPI_AM_API_DRAFT#ChangeSetC Add UpdateSliver to support add, modifying, or removing resources from a slice at an aggregate]
    20  * New change topic: [wiki:GAPI_AM_API_DRAFT#ChangeSetE Tickets]
     19  * [wiki:GAPI_AM_API_DRAFT#ChangeSetC:UpdateSliver1 Add UpdateSliver to support add, modifying, or removing resources from a slice at an aggregate]
     20 * New change topic: [wiki:GAPI_AM_API_DRAFT#ChangeSetE:Tickets1 Tickets]
    2121  * Rob Ricci
    2222  * Andy Bavier
     
    3333 * Adopt change set A for inclusion in AM API version 2: RSpecs are GENI schema XML
    3434 * Adopt change set B part 1 for inclusion in AM API version 2:
    35   * All methods include a new 'options' XMLRPC struct argument with no required values, supporting aggregate innovation
     35  * All methods include a new 'options' XML-RPC struct argument with no required values, supporting aggregate innovation
    3636 * We expect to also include set B part 2 in API version 2, assuming we can quickly address a few outstanding questions:
    37   * All methods return an XMLRPC struct consisting of (1) a return 'code', (2) the return 'value' from API v1, and (3) a human readable 'output' on errors, plus optional aggregate specific entries
     37  * All methods return an XML-RPC struct consisting of (1) a return 'code', (2) the return 'value' from API v1, and (3) a human readable 'output' on errors, plus optional aggregate specific entries
    3838 * We will continue to discuss details on some parts of change set B part 2, to finalize AM API version 2:
    3939  * This discussion to continue at the coding sprint
     
    4141  * Supporting multiple AM API versions: How can servers do this? Multiple URLs as at ProtoGENI? If so, how do aggregates advertise those versions/URLs? (Perhaps in !GetVersion?)
    4242  * How are GENI error codes documented? A wiki page?
    43   * How are new aggregate-specific options or returns documented? XMLRPC introspection? New !GetVersion entries?
     43  * How are new aggregate-specific options or returns documented? XML-RPC introspection? New !GetVersion entries?
    4444  * Define GENI error codes
    4545 * Continue discussion of !UpdateSliver, slivers and sliver groups, and the addition of tickets on the geni developer mailing list
     
    5252 * Change set A (RSpecs are XML) was adopted without discussion
    5353 * Change set B part 1 (new options argument) was adopted with minor discussion.
    54  * Change set B part 2 (methods return XMLRPC structs) has a few minor open questions, and should be in API version 2 if we can resolve these issues shortly:
     54 * Change set B part 2 (methods return XML-RPC structs) has a few minor open questions, and should be in API version 2 if we can resolve these issues shortly:
    5555  * We must agree to and document GENI error codes
    5656  * Error codes were proposed as integers, with the space divided by aggregate developer. That either wastes codes or limits or both, while also hiding in a translation table whose codes these are. Why not use strings?