lxd provider doesn't honour memory constraints

[Menno Finlay-Smits]

When using the lxd provider passing something like "--constraints mem=2G" to add-machine or deploy doesn't have any effect on container created. It is reasonable to expect that this would affect the memory seen by the container.

[Cheryl Jennings (cherylj)]

Possibly a dup of bug #1397201, but would need to go through the code to confirm.

[Anastasia (anastasia-macmood)]

Removing 2.1 milestone as we will not be addressing this issue in 2.1.

[Sandor Zeestraten (szeestraten)]

Is anyone picking this up? Being able to set memory limits/constraints for lxd containers is kind of essential when running a lot of lxd containers (such as OpenStack charms) on a single box.

I saw the thread in https://lists.ubuntu.com/archives/juju-dev/2017-January/006269.html, but the guy in charge of implementing is gone it seems.

[John A Meinel (jameinel)]

Nobody is currently working on this. People objected to it being part of our existing constraints syntax (which generally defines minimums rather than maximums), which meant finding a new syntax, which then stalled and the person who had been working on it is no longer at Canonical.

Right now it is not on our immediate roadmap.

[Joseph Phillips (manadart)]

Constrains support landed in version 2.4.1

[Felipe Reyes (freyes)]

Pull Request: https://github.com/juju/juju/pull/8926
Commit: https://github.com/juju/juju/commit/d7a27f7c38c7bab606e9a8acebb6437d397ee553

[Joseph Phillips (manadart)]

Change above was actually for *provider* constraints on the develop branch.

The work for machine containers that underpins it landed in:
https://github.com/juju/juju/pull/8869

There was a later small change under:
https://github.com/juju/juju/pull/8891

For provider constraints in 2.4, see:
https://github.com/juju/juju/pull/8933

[Felipe Reyes (freyes)]

Joseph, thanks for the references ;)