Re: [ceph-users] Changing CRUSH map ids

Thanks Greg :) For the OSDs, I understand, on the other hand for intermediate abstractions like hosts, racks and rooms, do you agree that it should currently be possible to change the IDs (always under the "one change at a time, I promise mom" rule)? Clearly, a good amount of shuffling

Re: [ceph-users] Changing CRUSH map ids

Regardless of what the crush tool does, I wouldn't muck around with the IDs of the OSDs. The rest of Celh will probably not handle it well if the crush IDs don't match the OSD numbers. -Greg On Monday, November 2, 2015, Loris Cuoghi wrote: > Le 02/11/2015 12:47, Wido den

Re: [ceph-users] Changing CRUSH map ids

On Mon, Nov 2, 2015 at 7:42 AM, Loris Cuoghi wrote: > Thanks Greg :) > > For the OSDs, I understand, on the other hand for intermediate abstractions > like hosts, racks and rooms, do you agree that it should currently be > possible to change the IDs (always under the "one

Re: [ceph-users] Changing CRUSH map ids

On 02-11-15 12:30, Loris Cuoghi wrote: > Hi All, > > We're currently on version 0.94.5 with three monitors and 75 OSDs. > > I've peeked at the decompiled CRUSH map, and I see that all ids are > commented with '# Here be dragons!', or more literally : '# do not > change unnecessarily'. > >

[ceph-users] Changing CRUSH map ids

Hi All, We're currently on version 0.94.5 with three monitors and 75 OSDs. I've peeked at the decompiled CRUSH map, and I see that all ids are commented with '# Here be dragons!', or more literally : '# do not change unnecessarily'. Now, what would happen if an incautious user would happen

Re: [ceph-users] Changing CRUSH map ids

Le 02/11/2015 12:47, Wido den Hollander a écrit : On 02-11-15 12:30, Loris Cuoghi wrote: Hi All, We're currently on version 0.94.5 with three monitors and 75 OSDs. I've peeked at the decompiled CRUSH map, and I see that all ids are commented with '# Here be dragons!', or more literally : '#