When Adding a Reservation Group
In the attempt to add a new reservation group, the license server determines the total feature counts required by all the reservation entries within the new group. If the totals cannot be satisfied by counts not reserved to other reservation groups on the license server, the entire new group is rejected.
Example Allocations When Adding a New Reservation Group
The examples described in this section use the following reservations to pre-allocate the licenses in the server’s license pool. All these reservations are being created in the single new reservation group payroll.
|
{ "name" : "payroll", "reservations" : [ { "hostId": { "value" : "111A11AAA11A", "type" : "ETHERNET" }, "reservationEntries": [ { "featureName": "f1", "featureVersion": "1.0", "featureCount": 1 }, { "featureName": "f3", "featureVersion": "1.0", "featureCount": 2 } ]}, { "hostId": { "value" : "222A22AAA22A", "type" : "ETHERNET" }, "reservationEntries": [ { "featureName": "f3", "featureVersion": "1.0", "featureCount": 1 } ]}, { "hostId": { "value" : "Joe", "type" : "USER" }, "reservationEntries": [ { "featureName": "f3", "featureVersion": "1.0", "featureCount": 3 }]} ]} |
Example 1: Sufficient Feature Counts
In this example, a license server is allocated 1 count of f1 and 8 counts of feature f3 from the back office. When processing the new reservation group, the license server does the following:
| • | Determines that a total of 1 count of f1 is required (for device 111A11AAA11A). |
| • | Determines that a total of 6 counts of f3 is required—2 counts for device 111A11AAA11A, 1 count for device 222A22AAA22A, and 3 counts for user Joe. |
| • | Reserves 6 counts of f3 and 1 count of f1. |
| • | Keeps 2 unreserved counts of f3 available for any request on a first-come-first-served basis. |
Example 2: Insufficient Feature Counts
If a license server is allocated 1 count of f1 and 4 counts of f3, it does the following when the reservations are posted:
| • | Determines that a total of 1 count of f1 is required (for device 111A11AAA11A). |
| • | Determines that a total of 6 counts of f3 are required—2 counts for device 111A11AAA11A, 1 count for device 222A22AAA22A, and 3 counts for user Joe. |
| • | Rejects the entire reservation group since only 4 counts of f3 are available. |
Example 3: Features Not in the License Pool
If a license server is allocated no (0) counts of f1 but is allocated 8 counts of f3, it rejects the entire reservation group since f1 is not available in the license pool.