Changes between Version 9 and Version 10 of GAPI_AM_API_ISSUES

Timestamp:

05/07/12 10:47:36 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

GAPI_AM_API_ISSUES

@@ -13 +13 @@
 
 == Overall Issues ==
+ 1. Missing RSpec extension definition for specifying the operational states and methods supported by an aggregate / resource type
  2. No way to modify a reservation at an aggregate for a slice without deleting and recreating it
   * Proposal: See the [wiki:GAPI_AM_API_DRAFT UpdateSliver proposal]
- 5. Tickets
+ 3. Tickets
   * Proposal: See the [wiki:GAPI_AM_API_DRAFT Tickets proposal]
- 6. Define privileges required for each operation
+ 4. Define privileges required for each operation
   * But see the ABAC proposal and DRAFT proposal L
- 7. Clarify use of error codes, possibly add more detailed codes
+ 5. Clarify use of error codes, possibly add more detailed codes
    * Proposal: Add more specific error codes for credential issues, specific bad argument cases
 || 18   || MISSINGARGS  || "Required argument(s) missing" || 
@@ -40 +41 @@
      * Proposal: Should be same as 'was never here'.
     * That slice was here but was shutdown
- 8. Should {{{am_type}}} and the RSpec {{{type}}} and prefixes for new options, etc be the same?
+ 6. Should {{{am_type}}} and the RSpec {{{type}}} and prefixes for new options, etc be the same?
   * Should the RSpec {{{type}}} fields be the {{{am_type}}} values defined for return codes? 
    * Remove 'openflow' as unused here?
@@ -47 +48 @@
    * Should the prefixes be the {{{am_type}}} values
   * Proposal: Yes to all the above
- 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?
- 10. Operations that return false: what does that really mean? Not an error but ???
+ 7. 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?
+ 8. Operations that return false: what does that really mean? Not an error but ???
  
 == !GetVersion Issues ==
@@ -66 +67 @@
 
 == Delete Issues ==
- 2. What happens to resources if your credential expires? Does the AM delete them for you?
+ 1. What happens to resources if your credential expires? Does the AM delete them for you?
   * Proposal: AM deletes them for you - de-allocates the resources. (Required? Or may?)
- 3. If there was never a slice here, or you already deleted your resources at this AM, what does the AM return?
+ 2. If there was never a slice here, or you already deleted your resources at this AM, what does the AM return?
   * Proposal: True, indicating all resources (none) have been freed.
 
 == Status Issues ==
 See changes proposed for version 3 which address these.
- 2. Further specify what kinds of things go in specific {{{geni_resources}}} 
- 3. Further specify what kinds of things this method might optionally additionally include and still be consistent with the intent
+ 1. Further specify what kinds of things go in specific {{{geni_resources}}} 
+ 2. Further specify what kinds of things this method might optionally additionally include and still be consistent with the intent
 
 == Renew Issues ==
- 2. Specify the behavior if you fail to renew and the reservation expires
+ 1. Specify the behavior if you fail to renew and the reservation expires
   * Proposal: AM deletes the reservation, de-allocates the resources. (Required? May?)
- 3. Specify the behavior if you try to renew past the life of your credential(s).
+ 2. Specify the behavior if you try to renew past the life of your credential(s).
   * Proposal: Fails with {{{OUTOFRANGE}}}
- 4. Specify the behavior if there are no local resources in that slice
- 5. Is it legal to try to 'renew' your sliver until earlier than the previous expiration time, shortening your reservation? Some aggregates at least allow this now.
+ 3. Specify the behavior if there are no local resources in that slice
+ 4. Is it legal to try to 'renew' your sliver until earlier than the previous expiration time, shortening your reservation? Some aggregates at least allow this now.
   * Proposal: This is legal. Aggregates should support this, but that support is not required.