Before you start to deploy IBM® Cloud Orchestrator, you must decide which deployment topology to install for the IBM Cloud Orchestrator management stack.
Supported cloud types
When planning your
installation, decide what type of cloud you want to manage: private,
public, or both (hybrid):
- For private cloud, choose the hypervisor type: Hyper-V, KVM, PowerVC, VMware, z/VM®.
- For public cloud, choose the cloud provider: IBM SoftLayer, Amazon EC2, Microsoft Azure.
- For hybrid cloud, choose the hypervisor type and the cloud provider.
Supported deployment topologies
IBM Cloud
Orchestrator supports the
following deployment topologies:
- Single-Server topology
- Single-Server with external database topology
Tip: When you have chosen the deployment topology,
review the deployment parameters that are listed in Setting and validating the deployment parameters, and identify appropriate
values for these parameters for your installation.
The images
in this topic show an example of an IBM Cloud
Orchestrator and OpenStack topology
with one OpenStack Controller and
one compute node.Single-Server topology
All of the IBM Cloud Orchestrator management components are installed on a single IBM Cloud Orchestrator Server.Figure 1. Single-Server topology
Single-Server with external database topology
The IBM Cloud Orchestrator management components are installed on a single IBM Cloud Orchestrator Server, pointing to an existing external IBM DB2® database server.Figure 2. Single-Server with
external database topology
Deployment topology components
The main
components of an IBM Cloud
Orchestrator deployment
topology are as follows:
- IBM Cloud Orchestrator Server
- This server hosts the core IBM Cloud Orchestrator management components.
- OpenStack Controllers (previously known as Region Servers)
- Each OpenStack Controller communicates
with a specific hypervisor management infrastructure:
- The Hyper-V OpenStack Controller requires one or more Hyper-V compute nodes to provide the compute resources.
- The KVM OpenStack Controller requires one or more KVM compute nodes to provide the compute resources.
- The PowerVC OpenStack Controller must connect to an existing PowerVC to provide virtual machines.
- The VMware OpenStack Controller must connect to an existing VMware Virtual Center to provide virtual machines.
- The z/VM OpenStack Controller must connect to an xCat management node on z/VM to provide virtual machines.
- Compute nodes
- [KVM or Hyper-V] The compute nodes manage the virtual machines through the interface that is provided by KVM or Hyper-V.