Scenario: Counts Reserved By Hostid

The original reservation model consists of per-hostid reserved counts, together with the ability to get counts from the default shared pool. Reservations might look like this when expressed in a model definition:

model "model-1" {

partitions {

partition "reservation-1" {

"f" 1.0 1

}

}

on hostid("F01898AD8DD3/ETHERNET") {

use "reservation-1", "default"

accept

}

 

on any() {

use "default"

accept

}

}

Note that creating rules of access based on hostids is possible, but generally not recommended. Maintaining large lists of rules of access with the hostid condition is tedious and prone to error. Instead, consider basing the rules of access on hostname or hosttype properties or vendor dictionary key/value pairs.

Note:The hostid is specified as a value/type pair (for example, 7200014f5df0/ETHERNET). If a hostid condition does not specify the hostid type, it is assumed that the hostid is of type string.