Most Server product users probably use custom storage configurations
in the installer. But that might be a wrong guess.
This is the default auto partitioning for a 2TB drive in Server:
https://drive.google.com/open?id=0B_2Asp8DGjJ9b0ViMUpPZkFoTW8
/home is obviously quite huge, and is optimal for something like a
file server. It's suboptimal for VM's, databases, and containers.
While a Btrfs layout (I can't help myself) solves the unknown space
and use case question without involving the user, there are perhaps
other suboptimals.
But Cloud Atomic ISO offers a solution. Its autopartitioning layout
reserves a large pile of free extents in the VG, not associating them
with any LV. On first boot, docker-storage-setup turns those free
extents into a thin pool LV. But the Server product could just leave
them unallocated, and the user could allocate that space however they
want post-install.
Documentation could suggest system-storage-manger or blivet-gui as
alternatives to LVM tools for allocating that space.
Comments?
--
Chris Murphy