Actually, point is, why not give a more reasonable default out of box so that user does not have to customize it using cloud-init at all.
Thanks Vivek On Fri, Sep 04, 2015 at 05:19:07PM +0000, Muayyad AlSadi wrote: > Then cloud init > > On Fri, Sep 4, 2015, 8:18 PM Vivek Goyal <[email protected]> wrote: > > > Sure. But all these are manual steps. Trying to give better defaults > > out of the box. > > > > Thanks > > Vivek > > > > On Fri, Sep 04, 2015 at 05:14:53PM +0000, Muayyad AlSadi wrote: > > > You can do live expand of xfs, to take all the space type > > > > > > xfs_growfs / > > > > > > So you should do something like > > > > > > qemu-img resize myimg.qcow2 +20G > > > > > > then boot it then type > > > > > > xfs_growfs / > > > > > > Or use cloud init > > > > > > > > > On Fri, Sep 4, 2015, 8:04 PM Vivek Goyal <[email protected]> wrote: > > > > > > > Not sure what you are trying to say? > > > > > > > > Thanks > > > > Vivek > > > > > > > > On Fri, Sep 04, 2015 at 04:59:08PM +0000, Muayyad AlSadi wrote: > > > > > It's xfs so it will just expand. > > > > > > > > > > On Fri, Sep 4, 2015, 7:51 PM Vivek Goyal <[email protected]> wrote: > > > > > > > > > > > Hi, > > > > > > > > > > > > Virtual size of qcow2 f22 atomic size is 6G. I am wondering if > > there is > > > > > > a reason behind such small size. Will 10G be a better default. > > > > > > > > > > > > Right now out of 6G, 3G is consumed by rootfs. We also setup thin > > pool > > > > > > for docker which will consume 40% of free space (or 2G minimum). > > Some > > > > > > people are finding that out of box, there is not enough space for > > thin > > > > > > pool and 3G free space gets exhausted pretty fast. > > > > > > > > > > > > Is it a good idea to bump up default virtual size to 10G? > > > > > > > > > > > > Thanks > > > > > > Vivek > > > > > > > > > > > > > > > > > >
