Re: [openstack-dev] [kolla] Problem regarding named volume data location

2016-09-09 Thread Steven Dake (stdake)
I believe what Pual was indicating was On 9/2/16, 12:59 PM, "Christian Berendt" wrote: > On 02 Sep 2016, at 19:04, Jeffrey Zhang wrote: > > I think the right solution should warn the end-user: you need configure a large partition for /var/lib/docker. Confirmed. The volum

Re: [openstack-dev] [kolla] Problem regarding named volume data location

2016-09-02 Thread Steven Dake (stdake)
On 9/2/16, 8:48 AM, "Paul Bourke" wrote: >Hi Kolla, > >We have been experiencing a long running issue with Kolla that I have >brought up briefly a few times, but not made too much noise about. > >I'm taking the time to write about it in the hopes that a) as a >community we may be able to s

Re: [openstack-dev] [kolla] Problem regarding named volume data location

2016-09-02 Thread Christian Berendt
> On 02 Sep 2016, at 19:04, Jeffrey Zhang wrote: > > I think the right solution should warn the end-user: you need configure a > large partition for /var/lib/docker. Confirmed. The volumes of Mongodb and of Mariadb are getting pretty big as well. Using /var/lib/nova (or /var/lib/mariadb, ..) o

Re: [openstack-dev] [kolla] Problem regarding named volume data location

2016-09-02 Thread Jeffrey Zhang
If you really want some function like this, you may need this[0] > Create named local volumes that persist in the location(s) you want! [0] https://github.com/CWSpear/local-persist On Sat, Sep 3, 2016 at 1:04 AM, Jeffrey Zhang wrote: > > On Fri, Sep 2, 2016 at 11:48 PM, Paul Bourke > wrote: >

Re: [openstack-dev] [kolla] Problem regarding named volume data location

2016-09-02 Thread Jeffrey Zhang
On Fri, Sep 2, 2016 at 11:48 PM, Paul Bourke 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) Koll

Re: [openstack-dev] [kolla] Problem regarding named volume data location

2016-09-02 Thread Michał Jastrzębski
So this is hard problem to solve without native docker support (which afaik it doesn't). One potential solution would be to write our own "named volume" mechanism that will be configurable, after all it's just bindmounted directory. However it will be hacky and costly to maintain, although in reali

[openstack-dev] [kolla] Problem regarding named volume data location

2016-09-02 Thread Paul Bourke
Hi Kolla, We have been experiencing a long running issue with Kolla that I have brought up briefly a few times, but not made too much noise about. I'm taking the time to write about it in the hopes that a) as a community we may be able to solve it, and b) if other operators start complaining