Hi everyone, In luminous we added the crush device classes that automagically categorize your OSDs and hdd, ssd, etc, and allow you write CRUSH rules that target a subset of devices. Prior to this it was necessary to make custom edits to your CRUSH map with parallel hierarchies for each OSD type, and (similarly) to disable the osd_crush_update_on_start option. As Dan has noted previously, transitioning from a legacy map to a modern one using classes in the naive way will reshuffle all of your data. He worked out a procedure do do this manually but it is delicate and error prone. I'm working on a tool to do it in a robust/safe way now. However... I want to make sure that the tool is sufficiently general. Can anyone/everyone who has a customized CRUSH map to deal with different OSD device types please send me a copy (e.g., ceph osd getcrushmap -o mycrushmap) so I can test the tool against your map? Thanks! sage _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |