IBM Z and LinuxONE - IBM Z - Group home

IBM Cloud Provisioning & Management for z/OS - Multiple Sysplex

  

IBM Cloud Provisioning and Management delivered multiple sysplex support in z/OS V2R3 and z/OS V2R4 releases with PTF UI66660 (z/OS V2R4) and PTF UI66659 (z/OS V2R3).

 

This support enables system programmers to create and manage Cloud Provisioning and Management domains which can be used to provision software service instances on systems in multiple sysplexes. Before this enhancement, Cloud Provisioning and Management domains could be used to provision software service instances on systems only in the local sysplex.

 

To provide multiple sysplex support Cloud Provisioning and Management utilizes capabilities in z/OSMF for a primary z/OSMF to communicate with secondary z/OSMF systems. Therefore, it is necessary to perform the setup to enable the z/OSMF-to-z/OSMF communication and to enable single sign-on between z/OSMF systems. For details see the z/OS Management Facility Configuration Guide, https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.izua300/IZUHPINFO_SSOSetup.htm.  There is additional information in the help topic "Establishing a single sign-on environment" in the z/OSMF server on-line help.

 

When creating a domain, the ability to include systems from non-local/remote sysplexes is now provided.  This is not available with the default domain since a unique default domain exists in Cloud Provisioning and Management on each z/OSMF system.  Systems are designated in a domain by system definitions in the primary z/OSMF Systems Settings task.  The nickname of the system is used to add the system to the domain. 




When the domain is created on the primary z/OSMF by administrator, a managed (by primary) domain is created on the secondary z/OSMF automatically.



As with domains, the same is true for tenants and templates, when created on the primary z/OSMF by administrator, a managed (by primary) entity is created on the secondary z/OSMF automatically.

 

When creating a resource pool, the “system selection for provisioning” option specifies how, and which systems can be used for provisioning.  The systems that are in the domain can be included. When the resource pool is created on the primary z/OSMF by administrator, the managed (by primary) resource pool is created on the secondary z/OSMF based on the systems specified for provisioning in the resource pool on the primary. 

 

Note that for network resources in the domain and the associated resource pools, the configuration for the network resources must be done from the Network Configuration Assistant task in z/OSMF on each sysplex i.e. on primary z/OSMF as well as on each applicable secondary z/OSMF.

 

The provision of a software service instance in a secondary z/OSMF happens when a template test run or run operation is done from the primary z/OSMF and the target system is in a remote sysplex.  The workflow for provisioning executes in the sysplex for the target system.




Actions on the software service instance provisioned on the remote sysplex, such as start, stop, and deprovision, are initiated from the primary z/OSMF.  The workflow or command for the action executes on the secondary z/OSMF in the sysplex for the target system.