Ceph » devops

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

blank --ceph-disk-prepare--> prepared
prepared --ceph-disk-activate--> active
{prepared, active} --ceph-disk-destroy?--> blank

(the last arrow goes to blank, not to prepared)

and the logic that would automatically trigger ceph-disk-prepare for listed block devices (#2554) MUST NOT re-prepare it