Red Hat Training
A Red Hat training course is available for Red Hat OpenStack Platform
3.3. Partition power recommendation for the Object Storage service
When using separate Red Hat OpenStack Platform (RHOSP) Object Storage service nodes, use a higher partition power value.
The Object Storage service distributes data across disks and nodes using modified hash rings. There are three rings by default: one for accounts, one for containers, and one for objects. Each ring uses a fixed parameter called partition power. This parameter sets the maximum number of partitions that can be created.
The partition power parameter is important and can only be changed for new containers and their objects. As such, it is important to set this value before initial deployment.
The default partition power value is 10
for environments that RHOSP director deploys. This is a reasonable value for smaller deployments, especially if you only plan to use disks on the Controller nodes for the Object Storage service.
The following table helps you to select an appropriate partition power if you use three replicas:
表3.1 Appropriate partition power values per number of available disks
Partition Power | Maximum number of disks |
10 | ~ 35 |
11 | ~ 75 |
12 | ~ 150 |
13 | ~ 250 |
14 | ~ 500 |
Setting an excessively high partition power value (for example, 14
for only 40 disks) negatively impacts replication times.
To set the partition power, use the following resource:
parameter_defaults: SwiftPartPower: 11
You can also configure an additional object server ring for new containers. This is useful if you want to add more disks to an Object Storage service deployment that initially uses a low partition power.
Additional resources
- Configure an Object Storage Ring in the Storage Guide
- The Rings in swift upstream documentation
- Modifying the Overcloud Environment in the Director Installation and Usage guide