Changes between Version 2 and Version 3 of DRAFT_GAPI_AM_API_ISSUES


Ignore:
Timestamp:
12/06/11 11:58:17 (8 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DRAFT_GAPI_AM_API_ISSUES

    v2 v3  
    1515 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.
    1616  * 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 it
     17 2. No way to modify a reservation at an aggregate for a slice without deleting and recreating it
    1818  * 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 parts
     19 3. No way to delete or renew part of a reservation at an aggregate separate from other parts
    2020  * 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 slice
     21 4. Method names suggest you are operating on slivers, but really you are operating on all slivers at an aggregate in a slice
    2222  * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetD:SliversandSliverGroups Sliver group proposal]
    23  1. Tickets
     23 5. Tickets
    2424  * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetE:Tickets1 Tickets proposal]
    25  1. Define privileges required for each operation
     25 6. Define privileges required for each operation
    2626  * But see the ABAC proposal
    27  1. Clarify use of error codes, possibly add more detailed codes
     27 7. Clarify use of error codes, possibly add more detailed codes
    2828   * Proposal: Add more specific error codes for credential issues, specific bad argument cases
    2929|| 18   || MISSINGARGS  || "Required argument(s) missing" ||
     
    4646     * Proposal: Should be same as 'was never here'.
    4747    * 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?
    4949  * Should the RSpec {{{type}}} fields be the {{{am_type}}} values defined for return codes?
    5050   * Remove 'openflow' as unused here?
     
    5353   * Should the prefixes be the {{{am_type}}} values
    5454  * 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 ???
    5757 
    5858== !GetVersion Issues ==