Add a New Reservation Group
The following shows an example of reservation definitions (in JSON format) that might be posted to define a new reservation group—in this case, a group named support, containing reservation entries for two reservations, one for hostid 7A7A77AAA77A and one for hostid Joe:
|
{ "name" : "support", "reservations" : [ { "hostId": { "value" : "7A7A77AAA77A", "type" : "ETHERNET" }, "reservationEntries": [ { "featureName": "f1", "featureVersion": "1.0", "featureCount": 1 }, { "featureName": "f2", "featureVersion": "1.0", "featureCount": 2 } ]}, { "hostId": { "value" : "Joe", "type" : "USER" }, "reservationEntries": [ { "featureName": "f3", "featureVersion": "1.0", "featureCount": 3 }]} ]} |
When this reservation information is processed without any errors, the license server does the following:
| • | Creates the reservation group support if it does not yet exist. If it does exist, an attempt to add another group named support will fail. |
| • | Adds the two new reservations—one for hostid 7A7A77AAA77A (RID 193) and one for hostid JOE (RID 196)—to the reservation group support. |
Note:A given hostid can be used only once not only within a given reservation group but within the entire reservation posting. An attempt to add a reservation group that includes a hostid already existing in another group will fail.
| • | Creates two reservation entries for hostid 7A7A77AAA77A—a reservation for 1 count of feature f1 and a reservation for 2 counts of feature f2. |
| • | Creates one reservation entry for 3 counts of feature f3 for hostid JOE. |
Errors that Cause Rejection of New Reservation Groups
When a new reservation group is processed during the posting phase, the entire group is rejected if any of following errors exist.
| • | A group name is repeated within the reservation posting. A group name must be unique within the entire reservation posting. |
| • | A hostid is used in more than one reservation group. A given hostid can be used only once, not only within a given group, but within the entire reservation posting. |
| • | A hostid is missing. A group reservation cannot be created without at least one reservation, defined by a hostid and its reservation entries. Additionally, reservation entries not associated with a reservation cause the entire reservation group to be rejected. |
| • | A reservation has no reservation entries associated with it. |
| • | A reservation entry is invalid. For example, the entry might be missing a feature name, version, or reserved count, or the specified reserved count is less than or equal to zero. |
| • | The feature or feature version specified in a reservation entry is not found in the license pool. |
| • | The feature specified in a reservation entry is expired or has not yet started. |
| • | The feature specified in a reservation entry is a metered feature. |
| • | The license server has an insufficient count of a given feature to fulfill the total requested count for that feature across all reservation entries within the entire group. For more explanation, see the later section License Allocation on the Server. |