Ceph » ceph-volume

The rejection criteria for ceph-volume doesn't seem to include 'disks with partitions' which I'd argue it should.

Following the credo 'better safe than sorry' is probably the right way to go when dealing with data/drives.

Example:

```
snip..
sdc 8:32 0 59.6G 0 disk
└─sdc1 8:33 0 59.6G 0 part /ext/cache
sdd 8:48 0 931.5G 0 disk
├─sdd1 8:49 0 512M 0 part
│ └─md126 9:126 0 512M 0 raid1 /boot/efi
└─sdd2 8:50 0 931G 0 part
└─md127 9:127 0 1.8T 0 raid0 /
nvme0n1 259:0 0 232.9G 0 disk
├─nvme0n1p1 259:5 0 450M 0 part
├─nvme0n1p2 259:6 0 100M 0 part
├─nvme0n1p3 259:7 0 16M 0 part
└─nvme0n1p4 259:8 0 232.3G 0 part
```

The nvme is not mounted but contains data that is used for something else (not ceph).

ceph-volume inventory reports that this drive is available though.

```
Path Type Size Available Ceph Device ID Reject Reasons
/dev/nvme0n1 sdd/nvme 232G True None
/dev/md126 sdd/nvme 511M False None locked

..snip
```

furthermore I think that ceph-volume will report an error when tasked to deploy an OSD on a drive with existing partitions and/or a GPT header