Changes between Version 22 and Version 23 of AaronHelsinger/GAPI_AM_API_DRAFT

Timestamp:

03/29/12 15:36:27 (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]: 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
+ - [#ChangeSetF1:DefineSliverStates Change Set F1]: Superseded by F3 and F4: Define sliver states, and the state changes that various methods cause
+ - [#ChangeSetF2:ActOnSlivers Change Set F2]: Superseded 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:SliverOperationsMethod Change Set F4]: Method to perform Sliver Operational actions
@@ -193 +193 @@
 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].
+A proposal for allocation states (below) may supersede this. See [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3].
 
 == Motivation ==
@@ -422 +422 @@
 
 == Change Set F1: Define Sliver States ==
-'''This change is superceded by Change Sets F3 and F4.'''
+'''This change is superseded by Change Sets F3 and F4.'''
 
 Currently the AM API defines several possible states as valid returns in !SliversStatus: {{{configuring}}}, {{{ready}}}, {{{unknown}}}, and {{{failed}}}. This change changes and expands that list of valid states, and explicitly defines the expected states after each AM API method call. Additionally, this change provides a mechanism for aggregates to supply their own states.
@@ -429 +429 @@
 
 == Change Set F2: !ActOnSlivers ==
-'''This change is superceded by Change Sets F3 and F4.'''
+'''This change is superseded by Change Sets F3 and F4.'''
 
 This change introduces a new method, providing a generic way to act on slivers in an AM or resource type specific way. This method shall be used to 'start' or 'stop' or 'restart' resources that have been allocated but not started by !CreateSlivers or !RedeemTicket. It may also be used to change the state of slivers (or their contained resources) in an aggregate or resource specific way. Some aggregates may use this method to change configuration details of allocated resources. This might include changing acceptable login keys.