Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Block Storage backup service deployment
The Block Storage backup service is optional. It is not installed by default and must be added to the overcloud deployment.
To deploy the backup service, you need:
- A new or existing OpenStack installation
- An available storage source with a compatible backup driver: Object Storage (swift), Red Hat Ceph Storage, or NFS.
The examples in this section assume that you are deploying the back end service in a standard OpenStack environment that uses the default Pacemaker installation.
2.1. Configuring backend options
The backup service is enabled by including the cinder-backup.yaml environment file in the /usr/share/openstack-tripleo-heat-templates/environments/ directory.
The default settings in this file configure a swift back end for the Block Storage backup service with Pacemaker.
Procedure
Create a custom environment file, for example cinder-backup-settings.yaml, that contains the parameter settings for the backup service and configuration options for the driver:
Create a copy of the
cinder-backup.yamlfile and store it in the same location as other custom templates.cp /usr/share/openstack-tripleo-heat-templates/environments/cinder-backup.yaml /home/stack/templates/cinder-backup-settings.yaml
- Modify the appropriate options for the backup back end that you are using (see instructions in the sections below).
- Save the changes to the file.
2.1.1. Object storage (swift)
Swift is the default value for the CinderBackupBackend option. If you are using swift, no additional changes are required.
Example
resource_registry: OS::TripleO::Services::CinderBackup: /usr/share/openstack-tripleo-heat-templates/docker/services/pacemaker/cinder-backup.yaml # For non-pcmk managed implementation # OS::TripleO::Services::CinderBackup: /usr/share/openstack-tripleo-heat-templates/docker/services/cinder-backup.yaml parameter_defaults: CinderBackupBackend: swift
| Setting | Options | Values |
|---|---|---|
|
| swift (default) |
Swift is the default selection in the |
2.1.2. Red Hat Ceph Storage
If you are using Red Hat Ceph Storage as a backup back end, then you may change the RBD pool name used for the backup. The default value is backups.
Example
resource_registry: OS::TripleO::Services::CinderBackup: /usr/share/openstack-tripleo-heat-templates/docker/services/pacemaker/cinder-backup.yaml # For non-pcmk managed implementation # OS::TripleO::Services::CinderBackup: /usr/share/openstack-tripleo-heat-templates/docker/services/cinder-backup.yaml parameter_defaults: CinderBackupBackend: ceph CinderBackupRbdPoolName: backups
| Setting | Options | Values |
|---|---|---|
|
| ceph |
Required. Change the value to |
|
| backups (default name) | Optional. No other settings must be updated unless you are using a custom RBD pool name. |
2.1.3. NFS
To use NFS as a back end for the backup service, you must provide the NFS share to be mounted.
Example
resource_registry: OS::TripleO::Services::CinderBackup: /usr/share/openstack-tripleo-heat-templates/docker/services/pacemaker/cinder-backup.yaml # For non-pcmk managed implementation # OS::TripleO::Services::CinderBackup: /usr/share/openstack-tripleo-heat-templates/docker/services/cinder-backup.yaml parameter_defaults: CinderBackupBackend: nfs CinderBackupNfsShare: '192.168.122.1:/export/cinder/backups' CinderBackupNfsMountOptions: ''
| Setting | Options | Values |
|---|---|---|
|
| nfs |
Required. Set |
|
| Required. Enter the NFS share to be mounted. Default value is empty. | |
|
| Optional. Backup NFS mount options can be left blank. If you must specify mount options, include them here. |
2.2. Deploying the Block Storage backup service
After you create the environment file in /home/stack/templates/, log in as the stack user and deploy the configuration by running:
$ openstack overcloud deploy --templates \ -e /home/stack/templates/cinder-backup-settings.yaml
If you passed any extra environment files when you created the overcloud, pass them again here using the -e option to avoid making undesired changes to the overcloud.
For more information, see the Including Environment Files in Overcloud Creation in the Director Installation and Usage Guide and the Environment Files section of the Advanced Overcloud Customization Guide.
