Open Stack

On Fri, Sep 2, 2016 at 11:48 PM, Paul Bourke <paul.bourke at oracle.com> wrote:

> In our Kilo based solution we were solving this using host bind mounts,
> e.g. -v /var/lib/nova:/var/lib/nova, where the directory on the left hand
> side can be mounted wherever you like. Two major issues with this approach
> are:
>
> 1) Kolla tasks have to be refactored in many places to replace
> "nova_data:/var/lib/kolla" with "/var/lib/nova:/var/lib/nova" (easily
> solvable)
>
> 2) This appears to be incompatible with the 'drop root' work done, as even
> though /var/lib/nova is created and chowned during the build process, it's
> permissions are replaced with those of root when bind mounted from the host.
>

​Why this solve the issue?

IMHO, the root cause is that: Kolla/docker consume much capacity in
/var/lib/docker. But If we move the named volume to other place ( like
/var/lib/nova ), it will consume that disk/folder capacity.

I think the right solution should warn the end-user: you need configure a
large partition for /var/lib/docker.



-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160903/9919045f/attachment.html>