ec40ed3cbb
An unwitting user may apply the KOLLA_CEPH_OSD[_CACHE]_BOOTSTRAP label to a partition assuming it will only use that partition for Ceph, and end up wiping out their disk. This change adds a layer of checking to this scenario to try and help avoid a disaster scenario. Closes-Bug: 1599103 DocImpact Change-Id: Ibb9fb42f87a76bc02165ec0b93b60234bad8747a
21 lines
791 B
YAML
21 lines
791 B
YAML
---
|
|
prelude: >
|
|
There any multiple options available to an operator
|
|
with regards to how they wish to provision devices
|
|
for use with Ceph OSDs. One of those is to co-locate
|
|
the data and journal on a disk, which is done by
|
|
marking a partition on that disk with
|
|
`KOLLA_CEPH_OSD[_CACHE]_BOOTSTRAP`.
|
|
If an unwitting user happened to confuse this with
|
|
the partition based approach, they could wipe out
|
|
their entire disk, resulting in data loss.
|
|
features:
|
|
- The Ceph bootstrap will now pause requesting
|
|
confirmation from the operator if it detects a
|
|
bootstrap label on a disk with more than one
|
|
partition.
|
|
An operator may override this behaviour by
|
|
setting the Ansible variable
|
|
'ceph_osd_wipe_disk' to
|
|
'yes-i-really-really-mean-it'.
|