Changes between Version 50 and Version 51 of AaronHelsinger/GAPI_AM_API_DRAFT
- Timestamp:
- 04/18/12 08:43:27 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AaronHelsinger/GAPI_AM_API_DRAFT
v50 v51 130 130 Similarly, such an aggregate would return an error from Describe if you request a set of sliver URNs that is only some of the `geni_provisioned` slivers. 131 131 132 - `geni_allocate` A string, one of fixed set of possible values. Default is `geni_single`. This option defines whether this AM allows adding slivers to aslices at an AM (i.e. calling Allocate() multiple times, without first deleting the allocated slivers). Possible values:132 - `geni_allocate` A string, one of fixed set of possible values. Default is `geni_single`. This option defines whether this AM allows adding slivers to slices at an AM (i.e. calling Allocate() multiple times, without first deleting the allocated slivers). Possible values: 133 133 - `geni_single`: Performing multiple Allocates without a delete is an error condition because the aggregate only supports a single sliver per slice or does not allow incrementally adding new slivers. This is the AM API v2 behavior. 134 134 - `geni_disjoint`: Additional calls to Allocate must be disjoint from slivers allocated with previous calls (no references or dependencies on existing slivers). The topologies must be disjoint in that there can be no connection or other reference from one topology to the other.