The following updates have been made in this release:
- Power® Enterprise Pools 2.0 is renamed as IBM Power Systems Private Cloud with Shared Utility Capacity. In CMC, IBM Power Systems Private Cloud with Shared Utility Capacity is referred to as Power Enterprise Pools 2.0 or Enterprise Pools 2.0.
- This release adds Enterprise Pools 2.0 support for both tracking (but not metering) Red Hat Enterprise Linux CoreOS and for automatically running Refresh Capacity daily.
- The ability to retrieve information via APIs is introduced with this release. You can use the CMC API to get resource consumption information for Enterprise Pools 2.0.
- Metering for Red Hat Enterprise Linux is available and requires one of the following subscriptions:
- Red Hat Enterprise Linux 8 for Power with Smart Management, Premium (up to 4 cores and 4 LPARs) Subscription or Subscription/RH Support, including Extended Update Support and High Availability for Power features (required) – 5639-RH8
- Red Hat Enterprise Linux 7 for Power with Smart Management, Premium (up to 4 cores and 4 LPARs) Subscription or Subscription/RH Support, including Extended Update Support features (required) – 5639-RLE
- Red Hat Enterprise Linux for SAP Solutions for Power, Premium (up to 4 cores and 4 LPARs) Subscription or Subscription/RH Support – 5639-RHS
All systems that are expected to share Base RHEL subscription entitlement resources within a pool must have the same Red Hat subscription product and add-on features.
To enable your Red Hat subscriptions as base and metered capacity resources within a Power Enterprise Pool 2.0 environment, IBM or Business Partner Sales teams must order 5799-RP2 "Red Hat Enablement for Power Private Cloud/Pools 2.0”and include i-listed PRPQ P91342.
- Support is added for the Power E1080. You can add a Power E1080 to a Power Enterprise Pool 2.0 that has Power E980.
- In prior releases, when budgeting was enforced it was necessary to set a monthly budget to be more than zero to achieve sharing of resources between the systems in the pool due to throttling always being in effect. As of this release, you can set a monthly budget to zero and still enable resource sharing between systems in a pool. When the first metered minute for the current month is consumed:
- When budgeting is enforced, the systems are throttled to use only base capacity gradually over the next 4 days and notification of pool throttling is sent.
- A "Monthly Budget Met" notification indicates that current month's budget is reached.