juju set-constraints [options] <application> <constraint>=<value> ...
Sets machine constraints for an application.
--debug (= false)
Equivalent to --show-log --logging-config==DEBUG
-h, --help (= false)
Show help on a command or other topic.
--logging-config (= "")
Specify log levels for modules
--quiet (= false)
Show no informational output
--show-log (= false)
If set, write the log file to stderr
--verbose (= false)
Show more verbose output
-B, --no-browser-login (= false)
Do not use web browser for authentication
-m, --model (= "")
Model to operate in. Accepts
[<controller name>:]<model name>|<model UUID>
Sets constraints for an application, which are used for all new machines
provisioned for that application. They can be viewed with
juju get- constraints.
By default, the model is the current model.
Application constraints are combined with model constraints, set with
juju set-model-constraints, for commands (such as ‘juju deploy’) that
provision machines for applications. Where model and application constraints
overlap, the application constraints take precedence.
Constraints for a specific model can be viewed with
juju get-model- constraints.
This command requires that the application have at least one unit. To apply
the first unit set them at the model level or pass them as an argument
juju set-constraints mysql mem=8G cores=4 juju set-constraints -m mymodel apache2 mem=8G arch=amd64
get-constraints get-model-constraints set-model-constraints
Last updated 9 months ago.