Ceph » ceph-volume

The current project layout wasn't intended to support beyond a similar matrix to that of ceph-disk:

• bluestore
• filestore
• dmcrypt

The addition of LVM and features like:

• carving out new LVs from existing VGs when provisioning
• multi-provision of OSDs given a group of devices
• LVM-like technologies like VDO and dmcache support

means that the current approach is no longer suitable to sustain that type of expansion. The new layout should allow to easily detect a path towards execution
instead of dealing with multiple logical casing within a single path. So instead of:

devices/lvm/prepare.py

We would have something like:

devices/lvm/prepare/bluestore/dmcrypt.py
devices/lvm/prepare/bluestore/main.py
devices/lvm/prepare/filestore/dmcrypt.py
devices/lvm/prepare/filestore/main.py

This would allow to easily extend new functionality, without affecting the logical implementation of the other supported scenarios.