Changes between Version 23 and Version 24 of AaronHelsinger/GAPI_AM_API_DRAFT

Timestamp:

03/29/12 15:43:05 (12 years ago)

Author:

Aaron Helsinger

Comment:

--

AaronHelsinger/GAPI_AM_API_DRAFT

@@ -60 +60 @@
 
 == Unspecified items ==
- - Semantics of start/restart after !UpdateSlivers
- - Define the ticket service classes
- - Publish ticket schema
+ - Semantics of adding or removing slivers from the full set of slivers in a slice at an aggregate
+ - An acceptable Update proposal
+ - RSpec for advertising operational states for a sliver type
  - Publish credential schema
  - Define error codes returned by new methods, conditions
@@ -87 +87 @@
 
 A competing related proposal from Gary Wong is here: http://www.protogeni.net/trac/protogeni/wiki/AM_API_proposals
+
+A further revised proposal is expected from Jon Duerig.
 
 == !UpdateSlivers ==
@@ -172 +174 @@
 Considering the clarified sliver definition, several API names are misleading. This change proposal modifies those method names to clarify that they may work with multiple slivers. Additionally, some methods can logically operate on individual slivers: this change modifies those methods' arguments to allow specifying a particular sliver.
 
+This proposal is missing a supplementary proposal of the semantics involved in operating on individual slivers, part of the slice at an AM. In particular, defining whether !CreateSlivers can be called multiple times, and the semantics of doing !DeleteSlivers or !RenewSlivers on only some of the slivers in a slice at an aggregate.
+
+'''The specifics of this proposal are superseded by proposal F3 and the proposed summary methods at the bottom of this page.'''
+
  1. Rename some existing methods to clarify that they act on 1+ slivers:
   - !CreateSliver -> !CreateSlivers
@@ -193 +199 @@
 For an alternative proposal, see: http://www.protogeni.net/trac/protogeni/wiki/AM_API_proposals
 
-A proposal for allocation states (below) may supersede this. See [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3].
+The later proposal for allocation states (below) supersedes this. See [#ChangeSetF3:SliverAllocationStatesandmethods Change Set F3].
 
 == Motivation ==