bluestore-wal only needed if separate to DB device
Update config.yaml to clarify that bluestore-wal should only be set
where a separate (faster) device is being used for the WAL. Otherwise,
the WAL is automatically maintained within the space of the DB device
and does not need to be configured separately.
Additionally clarify that this device is used as an LVM PV and space is
allocated for each block device based on the
bluestore-block-{db,wal}-size setting.
This change is required as Zaza underwent a split of the openstack
tests from the Zaza project, so we had to track the working branch
until that change landed. As it has landed, it is now time to use
Zaza from master again
This notification is added to allow ceph-mon to know
when ceph-osd units have upgraded in order to run
post-upgrade commands (required for certain upgrades).
- Add notify_mon_of_upgrade function that sets
ceph_release to release version.
- Refactor some hard coded strings to vars
- Set relation ceph_release when setting bootstrapped-osd
The charm was checking for the zeroth value of the return value of
list_logical_volumes. However, if no logical volumes are found it
returns an empty list.
