[ceph-users] Re: Adding device class to CRUSH rule without data movement

2025-03-15 Thread Hector Martin
What the command I pasted did was (after diffing the CRUSH map output): - Move all the IDs from the main tree into the hdd class parallel tree - Assign fresh IDs to the main tree - Change all the "step take default" to "step take default class hdd" in every CRUSH rule Moving the IDs over is what

[ceph-users] Re: Adding device class to CRUSH rule without data movement

2025-03-15 Thread Hector Martin
Aha, that's what I was looking for! And indeed, it seems to do exactly what I thought of doing, just move the bucket IDs. I mistakenly thought this functionality was for people who already had multiple parallel hierarchies in their crush tree, but it also works for a single default hierarchy. This

[ceph-users] Re: Adding device class to CRUSH rule without data movement

2025-03-14 Thread Anthony D'Atri
I haven’t used reclassify in a while, but does the output look like the below, specifying the device class with item_name ? { "rule_id": 3, "rule_name": "tsECpool", "type": 3, "steps": [ { "op": "set_choo

[ceph-users] Re: Adding device class to CRUSH rule without data movement

2025-03-14 Thread Eugen Block
The crushtool would do that with the --reclassify flag. There was a thread here on this list a couple of months ago. I’m on my mobile, I don’t have a link for you right now. But the docs should also contain some examples, if I’m not mistaken. Zitat von Hector Martin : Hi, I have an old