lxd and constraints

[Mike Pontillo]

On Thu, Jan 12, 2017 at 12:40 PM, Nate Finch <nate.finch at canonical.com>
wrote:

> The problem with trying to figure out how much "unused" RAM a host has is
> that it gets thrown out the window if you ever deploy any unit to the host
> machine, or if you deploy a unit in a container without a RAM constraint.
> Those units may then use as much RAM as they want.
>

Right, that's why I said the idea might be naive. But I would ask how
difficult it would be to change the design so that the amount of "unused"
resources is persisted. (Probably persisted along with the ratios, so the
calculation is consistent across deployments. You might want some ratios to
be application-specific, such as if you know you want to deploy a very
large database, but that use case can probably be accomplished with
constraints?)

In any case (depending on where you specify the ratio), you may always have
a situation where new units can use as much RAM as they want.

Regards,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20170112/91e0a7b4/attachment.html>