Re: [atomic-devel] Help with testing AMI's

[Colin Walters <walters verbum org>]

On Sat, Sep 6, 2014, at 10:21 PM, Dusty Mabe wrote:
> 
> Are you aware of the issue I referred to earlier? Basically this means
> that 
> if there is more than one partition on the disk image (as is the case for
> these 
> atomic images) then it won't get resized appropriately. As a result I end
> up only
> using ~8G of disk space when I really allocated 20G, 30G, etc.. for the
> primary disk. 

Right.  This is a complex issue and gets to the fact that our Docker
storage setup is still suboptimal.

Ultimately what we want is to have a dedicated DM pool for the Docker
storage, distinct from the OS.

If we were going to be a bit more adventurous with LVM, we'd use thin
provisioning.

Regardless, we have a distinction between Docker storage and host
storage.  In that scenario, when the cloud provider allocates us say
30G, how do we proportion?  My initial take is we'd grow the Docker
storage pool, but I think ultimately this will need to be configurable
(via e.g. cloud-init?).  In the case where I'm keeping a lot of data on
the host system and using bind mounts to expose it to containers, for
example.  

A short term fix would be LVM-based default.  Hmm...wasn't there a
variant of growpart around that worked on LVM?