Changes between Version 2 and Version 3 of DRAFT_GAPI_AM_API_ISSUES
- Timestamp:
- 12/06/11 11:58:17 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DRAFT_GAPI_AM_API_ISSUES
v2 v3 15 15 1. Add a state diagram in the [wiki:DRAFT_GAPI_AM_API_V2#SliverStatus SliverStatus] section to indicate that a component starts in {{{configuring}}}, can go from {{{configuring}}} to either {{{ready}}} or {{{failed}}}, and can go from {{{ready}}} to {{{failed}}}. {{{failed}}} is a terminal status. 16 16 * More generally, we need to define the state of the resources before/after each operation. Diagrams help. 17 1. No way to modify a reservation at an aggregate for a slice without deleting and recreating it17 2. No way to modify a reservation at an aggregate for a slice without deleting and recreating it 18 18 * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetC:UpdateSliver1 UpdateSliver proposal] 19 1. No way to delete or renew part of a reservation at an aggregate separate from other parts19 3. No way to delete or renew part of a reservation at an aggregate separate from other parts 20 20 * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetD:SliversandSliverGroups Sliver group proposal] 21 1. Method names suggest you are operating on slivers, but really you are operating on all slivers at an aggregate in a slice21 4. Method names suggest you are operating on slivers, but really you are operating on all slivers at an aggregate in a slice 22 22 * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetD:SliversandSliverGroups Sliver group proposal] 23 1. Tickets23 5. Tickets 24 24 * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetE:Tickets1 Tickets proposal] 25 1. Define privileges required for each operation25 6. Define privileges required for each operation 26 26 * But see the ABAC proposal 27 1. Clarify use of error codes, possibly add more detailed codes27 7. Clarify use of error codes, possibly add more detailed codes 28 28 * Proposal: Add more specific error codes for credential issues, specific bad argument cases 29 29 || 18 || MISSINGARGS || "Required argument(s) missing" || … … 46 46 * Proposal: Should be same as 'was never here'. 47 47 * That slice was here but was shutdown 48 1. Should {{{am_type}}} and the RSpec {{{type}} and prefixes for new options, etc be the same?48 8. Should {{{am_type}}} and the RSpec {{{type}}} and prefixes for new options, etc be the same? 49 49 * Should the RSpec {{{type}}} fields be the {{{am_type}}} values defined for return codes? 50 50 * Remove 'openflow' as unused here? … … 53 53 * Should the prefixes be the {{{am_type}}} values 54 54 * Proposal: Yes to all the above 55 1. We do not define the semantics of supplying a list of credentials: are they additive to accumulate privileges? Or must 1 credential supply all needed privileges?56 1 . Operations that return false: what does that really mean? Not an error but ???55 9. We do not define the semantics of supplying a list of credentials: are they additive to accumulate privileges? Or must 1 credential supply all needed privileges? 56 10. Operations that return false: what does that really mean? Not an error but ??? 57 57 58 58 == !GetVersion Issues ==