Multi-region topology

This topology is for larger test or production environments and can include multiple hypervisor environments.

This topology supports all of the IBM® Cloud Manager with OpenStack supported compute hypervisors. The specific compute hypervisors supported include:
  • KVM/QEMU
  • KVM for z Systems®
  • PowerKVM
  • PowerVC
  • z/VM®
  • Hyper-V
  • VMware
Note: The Chef client does not run on Hyper-V compute nodes since the Hyper-V Agent installer is used.

When you create this topology deployment, you need one system for the deployment server along with a single controller node for each region. You deploy a separate cloud for each region. Each region must have its own controller. You configure the multi-region topology to share the same Keystone and potentially IBM Cloud Manager - Dashboard.

If the KVM/QEMU, KVM for z Systems,PowerKVM, Hyper-V, or z/VM compute hypervisor is used, then one or more systems are also required to provide the IBM Cloud Manager with OpenStack compute nodes for the topology.

If you want to deploy a topology to manage to PowerVC, PowerVC driver services should run on the same node as the single controller node. It also requires an existing IBM Power® Virtualization Center to be available.

If you want to deploy a topology to manage to VMware, VMware driver services can run on the same node as the single controller node or on a separate node. It also requires an existing VMware vCenter to be available. If you plan to manage multiple vCenter servers, create a region for each vCenter; template images cannot be shared across multiple vCenter servers.

For better performance and easy management, configure your regions so that one kind of hypervisor exists in each region. For example, configure VMware systems to exist in one region; configure PowerVC systems to exist in another region.
Note: Having one region dedicated to each hypervisor type is not a hard requirement. You can also have compute nodes with more than one hypervisor type and hardware architecture in each region.
Communication between the IBM Cloud Manager with OpenStack components in a multi-region environment

For more information about using OpenStack to segregate your cloud, by region or availability zone, for example, see Segregating Your Cloud