I don't know if a non-impactful way to change this. If any host, rack, etc
IDs change it will cause movement. If any crush rule changes where it
chooses from our the failure domain, it will cause movement.
I once ran a test cluster where I changed every host to be in its own
"rack" just to change
We're looking into switching the failure domains on several of our
clusters from host-level to rack-level and I'm trying to figure out the
least impactful way to accomplish this.
First off, I've made this change before on a couple large (500+ OSDs)
OpenStack clusters where the volumes, images,
