Add support for CRUSH tiers on pool creation #150

Closed
opened 2021-12-28 03:42:32 -05:00 by joshuaboniface · 1 comment

Allow specifying a device tier (hdd, ssd, nvme) when creating Ceph storage pools.

This would need to be two-parted:

  1. Create a crush rule with the relevant map, e.g.
ceph osd crush rule create-replicated hdd_rule default host hdd
ceph osd crush rule create-replicated ssd_rule default host ssd
ceph osd crush rule create-replicated nvme_rule default host nvme

This bit must be done at pool creation time, because the device classes must already exist (i.e. OSDs of the relevant types must have already been added).

  1. Set the pool to use the relevant CRUSH rule, e.g.
ceph osd pool create slow 128 128 hdd_rule
ceph osd pool create fast 128 128 ssd_rule
ceph osd pool create blazing 128 128 nvme_rule

This would allow support for multi-tiered storage on nodes.

A default would always be present, and relevant flags/arguments for adding pools would need to be added along with a display in the pool output.

Allow specifying a device tier (`hdd`, `ssd`, `nvme`) when creating Ceph storage pools. This would need to be two-parted: 1. Create a crush rule with the relevant map, e.g. ``` ceph osd crush rule create-replicated hdd_rule default host hdd ceph osd crush rule create-replicated ssd_rule default host ssd ceph osd crush rule create-replicated nvme_rule default host nvme ``` This bit must be done at *pool* creation time, because the device classes must already exist (i.e. OSDs of the relevant types must have already been added). 2. Set the pool to use the relevant CRUSH rule, e.g. ``` ceph osd pool create slow 128 128 hdd_rule ceph osd pool create fast 128 128 ssd_rule ceph osd pool create blazing 128 128 nvme_rule ``` This would allow support for multi-tiered storage on nodes. A default would always be present, and relevant flags/arguments for adding pools would need to be added along with a display in the pool output.
joshuaboniface added the
Daemon
Client
labels 2021-12-28 03:42:32 -05:00
joshuaboniface self-assigned this 2021-12-28 03:42:32 -05:00
Author
Owner

Implemented in 0.9.47.

Implemented in 0.9.47.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: parallelvirtualcluster/pvc#150
No description provided.