Closed jan--f closed 5 years ago
This is partly the backport for #1694 witht he addition of the migration orchestration.
I have a documentation bug open. However we should note in the update release news or somewhere prominent, that users with problematic mds names need to run the migration first thing after updating DeepSea. See bsc#1138804 for doc input.
This fixes the mds names for new deployments. daemon names that would start with a digit (i.e. when a hostname starts with a digit) get a
mds.
prefix. This also adds an orchestration to migrate from the invalid names to the new naming scheme. Starting the migration with no invalid names present should not change anything, i.e. be safe to run at any time with an mds cluster present.