Memory constraints and lxc containers

[Mark Shuttleworth]

On 07/03/15 00:16, Stuart Bishop wrote:
> So the configuration defaults would be automatic tuning disabled, and
> manual tuning defaults set for minimal usable? That can be done today.
>
> An alternative would be for charms to specify their minimal VM
> requirements, and have juju deploy provision a container with those
> requirements unless overriden. Automatic tuning would remain the
> default, assuming we get it to use the container constraints rather
> than the host values. In the longer term, should we be aiming at this?
>
> I'm not too worried about settings used for running scripted tests, as
> the script can specify the minimal constraints. I've got the Cassandra
> tests running with settings too low to be useful for development, and
> made the default tunings a reasonable guess for a developer running a
> local instance.
>
> I think we will still need automatic tuning, so it would be nice to
> have lxcfs or similar so that option can work with lxc containers.
> PostgreSQL not having automatic tuning has always been a big problem
> for the project.
>

We're gathering charmers for a short IOM sprint soon, and I'll ask that
we discuss this topic then. Probably awkward for you to travel Stub but
we can hangout then :)

Mark