No, this is not resolved. We still do not have a sufficient default disk allocation for DB on controller nodes.
We still need:
1) A seperate lvm for /var/lib (so it can be resized with out being taken offline)
2) Better sizing for the volume in which the DB lies
When there is tons of space on the node (and ceph isn't used) it is all given to glance for images. The DB needs a better share of the disk than ~45Gb in this configuration.
If the defalt allocation remained, but /var/lib is still moved to a lvm, we can at least online resize the volume so it's not as painful to deal with wen you run out of space.
No, this is not resolved. We still do not have a sufficient default disk allocation for DB on controller nodes.
We still need:
1) A seperate lvm for /var/lib (so it can be resized with out being taken offline)
2) Better sizing for the volume in which the DB lies
When there is tons of space on the node (and ceph isn't used) it is all given to glance for images. The DB needs a better share of the disk than ~45Gb in this configuration.
If the defalt allocation remained, but /var/lib is still moved to a lvm, we can at least online resize the volume so it's not as painful to deal with wen you run out of space.