Changes between Version 5 and Version 6 of GEC12GeniAmAPI
- Timestamp:
- 11/28/11 10:10:46 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GEC12GeniAmAPI
v5 v6 17 17 * [wiki:GAPI_AM_API_DRAFT#ChangeSetA RSpecs are GENI V3 schema XML documents] 18 18 * [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] 21 21 * Rob Ricci 22 22 * Andy Bavier … … 33 33 * Adopt change set A for inclusion in AM API version 2: RSpecs are GENI schema XML 34 34 * Adopt change set B part 1 for inclusion in AM API version 2: 35 * All methods include a new 'options' XML RPC struct argument with no required values, supporting aggregate innovation35 * All methods include a new 'options' XML-RPC struct argument with no required values, supporting aggregate innovation 36 36 * 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 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 entries37 * 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 38 38 * We will continue to discuss details on some parts of change set B part 2, to finalize AM API version 2: 39 39 * This discussion to continue at the coding sprint … … 41 41 * 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?) 42 42 * How are GENI error codes documented? A wiki page? 43 * How are new aggregate-specific options or returns documented? XML RPC introspection? New !GetVersion entries?43 * How are new aggregate-specific options or returns documented? XML-RPC introspection? New !GetVersion entries? 44 44 * Define GENI error codes 45 45 * Continue discussion of !UpdateSliver, slivers and sliver groups, and the addition of tickets on the geni developer mailing list … … 52 52 * Change set A (RSpecs are XML) was adopted without discussion 53 53 * Change set B part 1 (new options argument) was adopted with minor discussion. 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: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: 55 55 * We must agree to and document GENI error codes 56 56 * 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?