Common: License Reconciliation Considerations for Processor-Based Licenses

IT Asset Management (Cloud)

The inventory data collected by the inventory component contains the details of the maximum and active processor threads used by each Solaris zone. If a resource pool has been configured, the maximum number of processor threads and the active number of processor threads are considered at the pool level. If no pool is configured, these properties are considered at the zone level. Wherever necessary in the virtualization hierarchy (host, pset, pool, and zone), the required resource capping is applied. For example, if a host has only 16 threads and the pool consumption sums up to 24 threads, only 16 would be considered as consumption.

To calculate the core count of a zone (when needed to cap the license consumption for Oracle and IBM licenses), the starting point is the maximum number of threads used in any non-global zone:

  1. The MaximumNumberOfLogicalThreads per non-global zone (say TZ) is obtained from the non-global zone inventory.
  2. The NumberOfThreadsPerCore for the host (say TC) is obtained from the global zone inventory.
  3. The first number is divided by the second (TZ/TC) to get the number of cores for the zone.

IT Asset Management (Cloud)