On 03/11/2016 01:50 PM, Chris Murphy wrote:
On Fri, Mar 11, 2016 at 11:07 AM, Stephen Gallagher
<sgallagh(a)redhat.com> wrote:
> What does docker-storage-setup do if there are multiple VGs on the system? Does
> it just pick one and use that, or does it take over them all?
Dunno. I still tend to poke things with a stick rather than reading code.
Dennis helped me find the autopartitioning modifier, which is in the
productimg file. This is how atomic ISO is doing it:
https://github.com/projectatomic/fedora-productimg-atomic/blob/master/ins...
Adding that to Server would be straightforward, just change the min
max sizes. This causes the rest to remain as free extents in the VG.
Ahh, I forgot there was a fedora-productimg-atomic. I was looking at
fedora-productimg-cloud and saw nothing there. Thanks for the pointer.
Hmm, reading that it isn't obvious that the leftover space would be part of a
volume group, just that 300MB are reserved for /boot and up to 3GiB are reserved
for / and then the default swap is selected. Beyond that, it's ambiguous whether
the remaining space should be part of a VG or unallocated or ???
I guess merging all of the remaining space into a single VG kind of makes sense,
but it's not explicit and unless it's documented somewhere, I'd worry about
such
assumptions breaking.