第 3 章 Customizing the Block Storage service (cinder)
You can configure the Block Storage service (cinder) to control resource usage, provide different performance levels, and secure sensitive data. Configure quotas, volume types, encryption, and QoS specifications to meet diverse workload requirements and optimize your storage infrastructure.
Block Storage service customizations include:
- Quotas: you can define project-specific limits to constrain the use of Block Storage resources.
Volume types: you can define the associated settings of each volume type. By default, all volume types are public and available to all projects (tenants) but you can create a
privatevolume type to control or limit the access to it.Volume types allow you to provide different levels of volume performance for your users. You can include the following additional customization of your volume types:
- The back end that a volume uses: you can create a volume type for each supported back end. However, for volume types that do not specify a back end, the Block Storage scheduler selects the most appropriate back end.
- Configurable properties of the Block Storage back-end drivers: you can specify multiple back-end properties for the volume type by using key-value pairs called Extra Specs.
- Quality of Service (QoS) specifications: you can apply performance limits to volumes that users create by associating QoS specifications to each volume type.
- Volume encryption: you can create an encrypted volume type so that users can create encrypted volumes.
- Default volume types: you can specify which volume type is used when a cloud user creates a volume and does not specify a volume type.
-
Some Block Storage features require the creation of an internal Block Storage project or tenant that is also known as the service project, which is called
cinder-internal. - Manage or unmanage volumes and their snapshots: you can import volumes and their snapshots from other Block Storage volume services or remove them from this Block Storage volume service.
All of these customizing procedures use the CLI which is faster, requires less setup, and provides more options than the Dashboard.
3.1. Prerequisites 复制链接链接已复制到粘贴板!
-
You have the
occommand line tool installed on your workstation. -
You are logged on to a workstation that has access to the RHOSO control plane as a user with
cluster-adminprivileges. -
To use Block Storage service
cinderCLI commands, source thecloudrcfile with the command$ source ./cloudrcbefore using them. If thecloudrcfile does not exist, then you need to create it.