第4章 Customizing the Storage service
The heat template collection provided by the director already contains the necessary templates and environment files to enable a basic Ceph Storage configuration.
The director uses the
/usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml environment file to create a Ceph cluster and integrate it with your overcloud during deployment. This cluster features containerized Ceph Storage nodes. For more information about containerized services in OpenStack, see Configuring a basic overcloud with the CLI tools in the Director Installation and Usage guide.
The Red Hat OpenStack director also applies basic, default settings to the deployed Ceph cluster. You must also define any additional configuration in a custom environment file:
Create the file
/home/stack/templates/. In this example, the
~/templates/storage-config.yamlfile contains most of the overcloud-related custom settings for your environment. Parameters that you include in the custom environment file override the corresponding default settings from the
~/templates/storage-config.yaml. This section contains custom settings for your overcloud. For example, to set
vxlanas the network type of the networking service (
neutron), add the following snippet to your custom environment file:
parameter_defaults: NeutronNetworkType: vxlan
If necessary, set the following options under
parameter_defaultsaccording to your requirements:
Option Description Default value
Enables the iSCSI backend
Enables the Ceph Storage back end
Sets ceph or swift as the back end for volume backups. For more information, see 「Configuring the Backup Service to use Ceph」.
Enables Ceph Storage for Nova ephemeral storage
Defines which back end the Image service should use:
Defines which back end the Telemetry service should use:
You can omit an option from
~/templates/storage-config.yamlif you intend to use the default setting.
The contents of your custom environment file change depending on the settings that you apply in the following sections. See 付録A Sample environment file: creating a Ceph Storage cluster for a completed example.
The following subsections contain information about overriding the common default storage service settings that the director applies.
4.1. Enabling the Ceph Metadata Server
The Ceph Metadata Server (MDS) runs the
ceph-mds daemon, which manages metadata related to files stored on CephFS. CephFS can be consumed through NFS. For more information about using CephFS through NFS, see File System Guide and CephFS via NFS Back End Guide for the Shared File Systems service.
Red Hat supports deploying Ceph MDS only with the CephFS through NFS back end for the Shared File Systems service.
To enable the Ceph Metadata Server, invoke the following environment file when you create your overcloud:
By default, the Ceph Metadata Server will be deployed on the Controller node. You can deploy the Ceph Metadata Server on its own dedicated node. For more information, see 「Creating a custom role and flavor for the Ceph MDS service」.