Este conteúdo não está disponível no idioma selecionado.
Chapter 2. Example deployment: High availability cluster with Compute and Ceph
This example scenario shows the architecture, hardware and network specifications, and the undercloud and overcloud configuration files for a high availability deployment with the OpenStack Compute service and Red Hat Ceph Storage.
This deployment is intended to use as a reference for test environments and is not supported for production environments.
Figure 2.1. Example high availability deployment architecture
2.1. Example high availability hardware specifications Copiar o linkLink copiado para a área de transferência!
The example HA deployment uses a specific hardware configuration. You can adjust the CPU, memory, storage, or NICs as needed in your own test deployment.
Number of Computers | Purpose | CPUs | Memory | Disk Space | Power Management | NICs |
---|---|---|---|---|---|---|
1 | undercloud node | 4 | 24 GB | 40 GB | IPMI | 2 (1 external; 1 on provisioning) + 1 IPMI |
3 | Controller nodes | 4 | 24 GB | 40 GB | IPMI | 3 (2 bonded on overcloud; 1 on provisioning) + 1 IPMI |
3 | Ceph Storage nodes | 4 | 24 GB | 40 GB | IPMI | 3 (2 bonded on overcloud; 1 on provisioning) + 1 IPMI |
2 | Compute nodes (add more as needed) | 4 | 24 GB | 40 GB | IPMI | 3 (2 bonded on overcloud; 1 on provisioning) + 1 IPMI |
2.2. Example high availability network specifications Copiar o linkLink copiado para a área de transferência!
The example HA deployment uses a specific virtual and physical network configuration. You can adjust the configuration as needed in your own test deployment.
This example does not include hardware redundancy for the control plane and the provisioning network where the overcloud keystone admin endpoint is configured. For information about planning your high availability networking, see Section 1.3, “Planning high availability networking”.
Physical NICs | Purpose | VLANs | Description |
---|---|---|---|
eth0 | Provisioning network (undercloud) | N/A | Manages all nodes from director (undercloud) |
eth1 and eth2 | Controller/External (overcloud) | N/A | Bonded NICs with VLANs |
External network | VLAN 100 | Allows access from outside the environment to the project networks, internal API, and OpenStack Horizon Dashboard | |
Internal API | VLAN 201 | Provides access to the internal API between Compute nodes and Controller nodes | |
Storage access | VLAN 202 | Connects Compute nodes to storage media | |
Storage management | VLAN 203 | Manages storage media | |
Project network | VLAN 204 | Provides project network services to RHOSP |
2.3. Example high availability undercloud configuration files Copiar o linkLink copiado para a área de transferência!
The example HA deployment uses the undercloud configuration files instackenv.json
, undercloud.conf
, and network-environment.yaml
.
The instackenv.json
file:
The undercloud.conf
file:
The network-environment.yaml
file:
2.4. Example high availability overcloud configuration files Copiar o linkLink copiado para a área de transferência!
The example HA deployment uses the overcloud configuration files haproxy.cfg
, corosync.cfg
, and ceph.cfg
.
This file identifies the services that HAProxy manages. It contains the settings for the services that HAProxy monitors. This file is identical on all Controller nodes: ./var/lib/config-data/puppet-generated/haproxy/etc/haproxy/haproxy.cfg
.
This file defines the cluster infrastructure, and is available on all Controller nodes: ./etc/corosync/corosync.conf
.
This file contains Ceph high availability settings, including the hostnames and IP addresses of the monitoring hosts: ./etc/ceph/ceph.conf
.