Changes between Version 5 and Version 6 of AaronHelsinger/GAPI_AM_API_DRAFT

Timestamp:

03/22/12 14:18:33 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

AaronHelsinger/GAPI_AM_API_DRAFT

@@ -38 +38 @@
  - [#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 
  - [#ChangeSetE:Tickets Change Set E: Tickets]: Add methods using tickets to do negotiated reservations
- - [#ChangeSetF1:DefineSliverStates Change Set F1]: Define sliver states, and the state changes that various methods cause
- - [#ChangeSetF2:ActOnSlivers Change Set F2]: Add a new general !ActOnSlivers method allowing AMs to support AM and resource-type specific operations
+ - [#ChangeSetF1:DefineSliverStates Change Set F1]: Superceded by F3 and F4: Define sliver states, and the state changes that various methods cause
+ - [#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
+ - [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3]: Sliver Allocation States and methods
+ - [#ChangeSetF4:SliverOperationalStatesandmethods Change Set F4]: Sliver Operational States and methods
  - ADOPTED: [#ChangeSetG:Credentialsaregeneralauthorizationtokens. Change Set G]: Generalize the credentials argument, allowing ABAC support
  - Change Set H: Clarify: A second call to !CreateSlivers without an intervening !DeleteSlivers is an error.
@@ -189 +191 @@
 
 For an alternative proposal, see: http://www.protogeni.net/trac/protogeni/wiki/AM_API_proposals
+
+A proposal for allocation states (below) may supercede this. See [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3].
 
 == Motivation ==
@@ -404 +408 @@
 A later alternative proposal, see http://lists.geni.net/pipermail/dev/2012-March/000721.html
 
-At the GEC13 coding sprint, a variant on the above was approved. It is documented here as Change Set F3.
+At the GEC13 coding sprint, a variant on the above was approved. It is documented here as [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3].
 
 A variant on the operational states proposal is defines as Change Set F4 and documented here: https://openflow.stanford.edu/display/FOAM/GENI+-+PerformOperationalAction
@@ -493 +497 @@
 Currently, !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.
 
+Open Questions:
+ - What about an !UpdateAllocations method, similar to !UpdateTickets or !UpdateTransactions from other similar proposals, for modifying allocated resources in place, without losing allocated resources?
+
 == Change Set F4: Sliver Operational States and methods ==
 This proposal was discussed on the geni-dev mailing list: http://lists.geni.net/pipermail/dev/2012-March/000743.html
@@ -503 +510 @@
  - What are the defined operational states, and GENI standard actions for transitions?
  - Does the API specify how operational state of slivers rolls up to the state of the slice at the aggregate?
- - Make option names and returns consistent between this change set and change set F3
+ - Make option names and returns consistent between this change set and [#ChangeSetF3:SliverAllocationStatesandmethods change set F3]
 
 {{{