Feature request - set weights per osd and possible improvement of crushmap customisation
Bug #1750567 reported by
John Lewis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph OSD Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
Currently, the latest stable version of the Ceph Osd charm (255) does support setting an initial weight, however weight cannot be set per osd. Can this feature be added?
https:/
Also, I've been told there is existing functionality to customise the crushmap, although I cannot see it, and that this functionality may need to be extended for certain customer use cases (for instance, mixed SSD/SATA storage). Can this also be given consideration too?
Changed in charm-ceph-osd: | |
milestone: | none → 18.05 |
importance: | Undecided → Medium |
tags: | added: sts |
Changed in charm-ceph-osd: | |
milestone: | 18.05 → 18.08 |
Changed in charm-ceph-osd: | |
milestone: | 18.08 → none |
Changed in charm-ceph-osd: | |
status: | New → Triaged |
To post a comment you must log in.
Per the documentation on the charm, crush-initial- weight is designed for bringing new OSDs in with a reduced weight, with the assumption that the administrator will slowly increase the weight of the new OSDs to the ceph default of 1/TB of capacity.