Chapter 3. Configuring the Red Hat Ceph Storage cluster for HCI

Procedure

1. Log in to the undercloud node as the stack user.

2. Configure the top level domain suffix:

     openstack overcloud ceph deploy \
             --tld "<domain_name>"

   Copy to Clipboard Toggle word wrap

   Replace <domain_name> with the required domain name.

     openstack overcloud ceph deploy \
             --tld "example.local"

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the undercloud node as the stack user.

2. Configure the name of the Ceph Storage cluster by using the following command:

   openstack overcloud ceph deploy \ --cluster <cluster_name>

   $ openstack overcloud ceph deploy \ --cluster central \

1. Log in to the undercloud node as the stack user.

2. Create a YAML format file that defines the custom network attributes called network_data.yaml.

   Important

   Using network isolation, the standard network deployment consists of two storage networks which map to the two Ceph networks:

   • The storage network, storage, maps to the Ceph network, public_network. This network handles storage traffic such as the RBD traffic from the Compute nodes to the Ceph cluster.
   • The storage network, storage_mgmt, maps to the Ceph network, cluster_network. This network handles storage management traffic such as data replication between Ceph OSDs.

3. Use the openstack overcloud ceph deploy command with the --crush-hierarchy option to deploy the configuration.

   openstack overcloud ceph deploy \
           deployed_metal.yaml \
           -o deployed_ceph.yaml \
           --network-data network_data.yaml

   Copy to Clipboard Toggle word wrap
   Important

   The openstack overcloud ceph deploy command uses the network data file specified by the --network-data option to determine the networks to be used as the public_network and cluster_network. The command assumes these networks are named storage and storage_mgmt in network data file unless a different name is specified by the --public-network-name and --cluster-network-name options.

   You must use the --network-data option when deploying with network isolation. The default undercloud (192.168.24.0/24) will be used for both the public_network and cluster_network if you do not use this option.

Procedure

1. Log in to the undercloud node as the stack user.
2. Create a standard format initialization file to configure the Ceph cluster. If you have already created a file to include other configuration options, you can add the network configuration to it.

3. Add the following parameters to the [global] section of the file:

   • public_network
   • cluster_network

   • ms_bind_ipv4

     Important

     Ensure the public_network and cluster_network map to the same networks as storage and storage_mgmt.

     The following is an example of a configuration file entry for a network configuration with multiple subnets and custom networking names:

     [global]
     public_network = 172.16.14.0/24,172.16.15.0/24
     cluster_network = 172.16.12.0/24,172.16.13.0/24
     ms_bind_ipv4 = True
     ms_bind_ipv6 = False

     Copy to Clipboard Toggle word wrap

4. Use the command openstack overcloud ceph deploy with the --config option to deploy the configuration file.

   $ openstack overcloud ceph deploy \
     --config initial-ceph.conf --network-data network_data.yaml

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the undercloud node as the stack user.

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

3. Create a configuration file to define the custom CRUSH hierarchy, for example, crush_hierarchy.yaml.

4. Add the following configuration to the file:

   <osd_host>:
     root: default
     rack: <rack_num>
   <osd_host>:
     root: default
     rack: <rack_num>
   <osd_host>:
     root: default
     rack: <rack_num>

   Copy to Clipboard Toggle word wrap
   • Replace <osd_host> with the hostnames of the nodes where the OSDs are deployed, for example, ceph-0.
   • Replace <rack_num> with the number of the rack where the OSDs are deployed, for example, r0.

5. Deploy the Ceph cluster with your custom OSD layout:

   openstack overcloud ceph deploy \
           deployed_metal.yaml \
           -o deployed_ceph.yaml \
           --osd-spec osd_spec.yaml \
           --crush-hierarchy crush_hierarchy.yaml

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the undercloud node as the stack user.
2. Create a YAML format file that defines the custom roles.

3. Deploy the configuration file:

   $ openstack overcloud ceph deploy \
           deployed_metal.yaml \
           -o deployed_ceph.yaml \
           --roles-data custom_roles.yaml

   Copy to Clipboard Toggle word wrap