Correct. Putting the constraints on the machines is equivalent to doing:
juju add-machine --constraints mem=4gb
juju deploy mysql --to $MACHINE
Rather than doing:
juju deploy mysql --constraints mem=4gb
Constraints on an Application will affect all new units of an application,
but constraint
I think I see *my* issue here. I have placed the constraints on the
machines (to which the charms are mapped) in my bundle, and not on the
actual applications themselves. I guess I shouldn't expect the constraints
to be associated with the charms in that case. Does this sound correct?
On Thu, Mar
On 17/03/17 14:23, James Beedy wrote:
Currently, if I scale the units of my application, the new units do not
have the same constraints as the previously deployed units.
Well, I certainly think they should be carrying over the constraints as
the constraints are set on the application, not the
