IBM z13s, Technical Manual

Page: 460 / 588

432
IBM z13s Technical Guide
11.6.2 Ensemble definition and management
The ensemble starts with a pair of HMCs that are designated as the primary and alternate
HMCs, and are assigned an ensemble identity. The zEnterprise CPCs and zBXs are then
added to the ensemble through an explicit action at the primary HMC.
Ensemble Membership Flag
The Ensemble Membership Flag feature, FC 0025, is associated with a HMC when a z13s
server is ordered.
The new Create Ensemble task allows the Ensemble Administrator user to create an
ensemble that contains CPCs and zBXs (Model 004) as members along with images,
workloads, virtual networks, and storage pools.
If a z13s server is entered into an ensemble, the CPC Details task on the SE and the HMC
reflects the ensemble name.
The Unified Resource Manager actions for the ensemble are conducted from a single primary
HMC. All other HMCs that are connected to the ensemble can run system management tasks
(but not ensemble management tasks) for any CPC or zBX Model 004 within the ensemble.
The primary HMC also can be used to run system management tasks on CPCs that are not
part of the ensemble. These tasks include Load, Activate, and so on.
The ensemble-specific managed objects include the following objects:
򐂰 Ensemble
򐂰
Members
򐂰
Blades
򐂰
BladeCenters
򐂰
Hypervisors
򐂰
Storage resources
򐂰
Virtual servers
򐂰
Workloads
When another HMC accesses an ensemble node’s CPC, the HMC can perform the same
tasks as though the CPC were not a part of an ensemble. A few of those tasks are extended
so that you can configure certain ensemble-specific properties. You can, for example, set the
virtual network that is associated with Open Systems Adapters (OSAs) for an LPAR. Showing
ensemble-related data in certain tasks is allowed. Generally, if the data affects the operation
of the ensemble, the data is read-only on another HMC.
z/VM V6R3 and Unified Resource Manager: Because of the IBM cloud strategy and
adoption of OpenStack, the management of z/VM environments in zManager is now
stabilized and will not be further enhanced.
zManager will not provide systems
management support for z/VM 6.3 and later releases
. However, zManager continues to
play a distinct and strategic role in the management of virtualized environments that are
created by the integrated firmware hypervisors (PR/SM, PowerVM, and x hypervisor, which
is based on KVM) of zEnterprise.