Changes between Version 5 and Version 6 of GAPI_AM_API_ISSUES

04/27/12 10:26:53 (9 years ago)
Aaron Helsinger




    v5 v6  
    1515 1. Add a state diagram in the [wiki: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  * See [wiki:GAPI_AM_API_DRAFT#ChangeSetF:SupportAMandresource-typespecificmethods. Change Set F]
    1718 2. No way to modify a reservation at an aggregate for a slice without deleting and recreating it
    1819  * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetC:UpdateSliver1 UpdateSliver proposal]
    1920 3. No way to delete or renew part of a reservation at an aggregate separate from other parts
    20   * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetD:SliversandSliverGroups Sliver group proposal]
     21  * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetD:Sliver-specificoperations Sliver specific operations proposal]
    2122 4. Method names suggest you are operating on slivers, but really you are operating on all slivers at an aggregate in a slice
    22   * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetD:SliversandSliverGroups Sliver group proposal]
     23  * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetD:Sliver-specificoperations Sliver specific operations proposal]
    2324 5. Tickets
    2425  * Proposal: See the [wiki:GAPI_AM_API_DRAFT#ChangeSetE:Tickets1 Tickets proposal]
    2526 6. Define privileges required for each operation
    26   * But see the ABAC proposal
     27  * But see the ABAC proposal and DRAFT proposal J
    2728 7. Clarify use of error codes, possibly add more detailed codes
    2829   * Proposal: Add more specific error codes for credential issues, specific bad argument cases
    7172== !CreateSliver Issues ==
     73Note this method gets removed by change sets proposed for version 3.
    7274 1. Define the behavior if you call !CreateSliver twice for the same slice. PG says you return REFUSED. !PlanetLab accepts it though. What about {{{ALREADYEXISTS}}}?
    7375|| `REFUSED`       || Slice already exists; must be deleted first (ie you called !CreateSliver twice without a !DeleteSliver in between) ||
    7476   * Proposal: {{{ALREADYEXISTS}}}
     77   * But see also the new Allocate and Provision methods proposed
    7578 2. Define the behavior if the AM can only give you some of what you requested
    7679  * Proposal: {{{TOOBIG}}}?
    7780 3. Define status of sliver(s) immediately on success of this method (need a diagram?)
     81  * See Change Set F
    7882 4. Define how many sliver(s) this creates
     83  * See Change Set D
    7984 5. Note there is no way to see the expiration time of your resources
    8085  * Proposal: include in manifest
     86  * See instead Change Sets I and M
    8187 6. Point to restrictions on slice names, sliver names?
    8288  * Min 3 characters?
    8389  * Max? 19? More?
    8490  * Only characters in set: {{{'^[a-zA-Z][-\w]+$'}}} ?
     91  * See Change Set K
    8693== !DeleteSliver Issues ==
     94Note this method changes with proposals for version 3.
    8795 1. What is failure (return false) as opposed to an Error?
    8896  * Define status (relative to !SliverStatus or ...) of the sliver(s) after success, failure, or error. Diagram?
    95103== !SliverStatus Issues ==
     104See changes proposed for version 3 which address these.
    96105 1. Are the {{{configuring}}}, {{{ready}}}, etc strings case-sensitive?
    97106  * Proposal: no
    104113 1. All resources indicated by the supplied URN should be renewed to the given time, or else the entire call should fail. We don't specify that currently.
    105114  * Proposal: Add that requirement
     115  * See `geni_best_effort`
    106116 2. Specify the behavior if you fail to renew and the reservation expires
    107117  * Proposal: AM deletes the reservation, de-allocates the resources. (Required? May?)
    115125 1. What is the state of resources after this? Startable? Is there a procedure for this?
    116126  * Proposal: Not restartable, not de-commissioned, not reservable, not accessible by the experimenters
     127  * See proposals for version 3
    117128 2. What happens if you call this twice?
    118129 3. What happens if the slice has nothing local?
    119130 4. What does a false return mean?
    120131  * Proposal: Drop that as valid: return true or an error