Feature #3119
Updated by Anonymous over 11 years ago
DH cookbooks do this by setting a node attribute that maps osd.id -> desired action, one of the actions is destroy.
That does run into the annoyances of using Chef as an RPC mechanism, requires admin to manage id->node mapping, etc.
Try to solve this with a core product feature, then make that interop well with Chef/ceph-deploy/Juju.
Once destroyed, osd hotplugging MUST NOT create a new OSD on that disk automatically. That is, the lifecycle is
<pre>
blank --ceph-disk-prepare--> prepared
prepared --ceph-disk-activate--> active
{prepared, active} --ceph-disk-destroy?--> blank
</pre>
(the last arrow goes to blank, not to prepared)