this bug covers the vaultlocker use case, where the charm very much knows that /var/lib/nova will be on a separate block device and as such can also add the required systemd unit configuration overrides to ensure that nova-compute starts after the mount location has been mounted.
I'm concerned that there might also be use cases where /var/lib/nova is controlled by MAAS configuration and mounted during boot, before the charm even gets installed.
this bug covers the vaultlocker use case, where the charm very much knows that /var/lib/nova will be on a separate block device and as such can also add the required systemd unit configuration overrides to ensure that nova-compute starts after the mount location has been mounted.
I'm concerned that there might also be use cases where /var/lib/nova is controlled by MAAS configuration and mounted during boot, before the charm even gets installed.