Bug 2234479

Description of problem (please be detailed as possible and provide log
snippests):

RFE: automation around OSD removal to avoid Data Loss

We have support cases (at least 1 per week) where customers remove OSDs across nodes, failure domains

Examples of what is driving this behavior:

- There are too many disk resources allocated to Ceph backing store, merely taking 1 or 2 back from each OSD host
- There are too many OSD requiring too much memory and CPU resources, swapping out 4 x 512 GiB disks for 1 x 2 TiB disk
- There is a new VMWare data store, therefore migrating all Ceph OSDs from data store x to new OSDs in data store Y

There is nothing stopping customers from removing an OSD. At least there is nothing in place that a --force won't overcome.

The request is some automation be created to do the work listed above, maybe even more. I realize this is not a trivial request. Just the same, maybe we start with, the automation which simply explains not to manually remove OSDs and directs the administrator to review a KCS link before moving forward. Anything to get started and help administrators not to inadvertently abuse their Ceph Backing Storage. We can create a KCS (agreed upon by Eng/Dev/CS) as the landing spot for such requests.

The ultimate goal should be automation which does all the work


Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?


Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

BR
Manny