Changes between Version 48 and Version 49 of AaronHelsinger/GAPI_AM_API_DRAFT


Ignore:
Timestamp:
04/13/12 11:58:53 (12 years ago)
Author:
Aaron Helsinger
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • AaronHelsinger/GAPI_AM_API_DRAFT

    v48 v49  
    8585A slice may have multiple slivers at a single AM. Experimenters can operate on slivers independently, if the AM supports it. AMs define slivers as groups of resources, and give them locally unique sliver_urns for identifying that group of resources.
    8686
    87 This change was briefly discussed at GEC13, and remains open for discussion. Concerns include whether aggregates can support individually operating on slivers, and whether we should make this change without that functionality.
     87This change was briefly discussed at GEC13, and remains open for discussion.
    8888
    8989See http://lists.geni.net/pipermail/dev/2012-March/000593.html as well.
    … …  
    110110== Addressable Slivers ==
    111111Considering 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.
    112 
    113 '''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.
    114 
    115 '''The specific method signature changes of this proposal are superseded by proposal F3 and the proposed summary methods at the bottom of this page.'''
    116112
    117113 1. Rename some existing methods to clarify that they act on 1+ slivers: