Feature request - set weights per osd and possible improvement of crushmap customisation

Bug #1750567 reported by John Lewis
8
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://jujucharms.com/ceph-osd/#charm-config-crush-initial-weight

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
Revision history for this message
Chris MacNaughton (chris.macnaughton) wrote :

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.

James Page (james-page)
Changed in charm-ceph-osd:
milestone: 18.05 → 18.08
James Page (james-page)
Changed in charm-ceph-osd:
milestone: 18.08 → none
James Page (james-page)
Changed in charm-ceph-osd:
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.