mon: 'osd crush rename-bucket <old> <new>'
mon: add the osd crush rename-bucket command
The synopsis is:
osd crush rename-bucket name1 name2
It is made idempotent by interpreting -EALREADY as returned by
CrushWrapper::rename_bucket return as success.
The crush_rename_bucket method first checks for errors with
CrushWrapper::can_rename_bucket if there is no pending crush so that it
can return early and avoid the creation of a pending crush map.
If renaming is possible, CrushWrapper::rename_bucket is called on the
pending crush map (and creates it indirectly if it does not already
Signed-off-by: Loic Dachary <firstname.lastname@example.org>
#4 Updated by Loic Dachary almost 6 years ago
- Status changed from New to In Progress
<loicd> sage: is there a reason to restrict osd crush rename to buckets ? It seems equally simple to implement it to rename bucket or items. http://tracker.ceph.com/issues/9526 <sage> we semi-enforce that items are osd.NNN <sage> i worry that allowing anything else will introduce ambiguity (what if i rename osd.2 to osd.4?) <loicd> ok