Multi-tenancy for resource groups

Edit online

The capabilities provided with resources groups enhances support for the creation of a multi-tenancy environment. Tenants have authority to issue Copy Services requests to resources that are created and managed by the multi-tenancy manager.

Partitioning between tenants is limited to the logical subsystem level. Figure 1 shows an example of how the system administrator can manage volumes on the same unit for multiple clients using resource groups.
Figure 1. Example of a multi-tenancy configuration.
Notes:
  •  1  Tenant 2 (FB LPAR) is limited by volume group 2 and volume 21, 22, and 23.
  •  2  A mix of CKD and FB is contained in the same resource group. Copying between volume pairs is limited to within resource group 2. Copy operations are not allowed between FB and CKD volumes. A FICON LPAR can use the z/OS distributed data backup feature.

It is not required that a system administrator configure resource groups functions when code is installed which supports resource groups. The default policy settings for preexisting user IDs and resources does not change the behavior of the storage unit from that of a unit which has no resource groups support. There is no change to the behavior of commands and scripts.

The use of resource groups to specify new policies does not require changes to existing scripts, and does not affect commands issued unless they violate the specified policies. Use of resource groups with or without new policies does not affect the performance of the storage unit.

For more CLI commands and details of additional uses for scope limiting functions, see the IBM® DS8000® Command-Line Interface User's Guide.