Cinder/Horizon support a (currently disabled) workflow that creates a Cinder volume in concert with VM creation. That suggests a possible new process for managing storage:
- We rearrange flavors such that all flavors have the same ephemeral disk size (e.g. 20 Gb)
- Any use-cases that require more storage are handled via attachable volumes.
- We provide some modest puppet automation for common workflows (e.g. 'format attached ceph volume with one partition an xfs and mount on /srv)
A few advantages:
- Cinder storage has quotas, so we'd be able to manage tenant storage use without having to use flavor as a proxy
- Users would be nudged in the direction of creating more cattle-like VMs since important storage would persist outside of VM crashes/rebuilds