Changes between Version 5 and Version 6 of AaronHelsinger/GAPI_AM_API_DRAFT


Ignore:
Timestamp:
03/22/12 14:18:33 (7 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AaronHelsinger/GAPI_AM_API_DRAFT

    v5 v6  
    3838 - [#ChangeSetD:Sliver-specificoperations Change Set D: Slivers]: Change methods to clarify that there may be multiple slivers per slice at an AM, and to allow operating on individual slivers
    3939 - [#ChangeSetE:Tickets Change Set E: Tickets]: Add methods using tickets to do negotiated reservations
    40  - [#ChangeSetF1:DefineSliverStates Change Set F1]: Define sliver states, and the state changes that various methods cause
    41  - [#ChangeSetF2:ActOnSlivers Change Set F2]: Add a new general !ActOnSlivers method allowing AMs to support AM and resource-type specific operations
     40 - [#ChangeSetF1:DefineSliverStates Change Set F1]: Superceded by F3 and F4: Define sliver states, and the state changes that various methods cause
     41 - [#ChangeSetF2:ActOnSlivers Change Set F2]: Superceded by F3 and F4: Add a new general !ActOnSlivers method allowing AMs to support AM and resource-type specific operations
     42 - [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3]: Sliver Allocation States and methods
     43 - [#ChangeSetF4:SliverOperationalStatesandmethods Change Set F4]: Sliver Operational States and methods
    4244 - ADOPTED: [#ChangeSetG:Credentialsaregeneralauthorizationtokens. Change Set G]: Generalize the credentials argument, allowing ABAC support
    4345 - Change Set H: Clarify: A second call to !CreateSlivers without an intervening !DeleteSlivers is an error.
     
    189191
    190192For an alternative proposal, see: http://www.protogeni.net/trac/protogeni/wiki/AM_API_proposals
     193
     194A proposal for allocation states (below) may supercede this. See [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3].
    191195
    192196== Motivation ==
     
    404408A later alternative proposal, see http://lists.geni.net/pipermail/dev/2012-March/000721.html
    405409
    406 At the GEC13 coding sprint, a variant on the above was approved. It is documented here as Change Set F3.
     410At the GEC13 coding sprint, a variant on the above was approved. It is documented here as [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3].
    407411
    408412A variant on the operational states proposal is defines as Change Set F4 and documented here: https://openflow.stanford.edu/display/FOAM/GENI+-+PerformOperationalAction
     
    493497Currently, !SliverStatus returns a single {{{geni_status}}} for the entire slice at this aggregate. With this change, the top-level allocation status for the slice is not defined, and that field is not required.
    494498
     499Open Questions:
     500 - What about an !UpdateAllocations method, similar to !UpdateTickets or !UpdateTransactions from other similar proposals, for modifying allocated resources in place, without losing allocated resources?
     501
    495502== Change Set F4: Sliver Operational States and methods ==
    496503This proposal was discussed on the geni-dev mailing list: http://lists.geni.net/pipermail/dev/2012-March/000743.html
     
    503510 - What are the defined operational states, and GENI standard actions for transitions?
    504511 - Does the API specify how operational state of slivers rolls up to the state of the slice at the aggregate?
    505  - Make option names and returns consistent between this change set and change set F3
     512 - Make option names and returns consistent between this change set and [#ChangeSetF3:SliverAllocationStatesandmethods change set F3]
    506513
    507514{{{