help text for juju set-constraints needs improving
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Reed O'Brien |
Bug Description
e.g.:
Usage: juju set-constraints [options] <service> <constraint>
Summary:
Sets machine constraints for a service.
Options:
-m, --model (= "")
Model to operate in
Details:
Sets constraints for a service, which are used for all new machines provisioned for that service. They can be viewed with `juju get-constraints`.
By default, the model is the current model.
Service constraints are combined with model constraints, set with `juju set-model-
Constraints for a specific model can be viewed with `juju get-model-
This command requires that the service to have at least one unit. To apply constraints to the first unit set them at the model level or pass them as an argument when deploying.
Examples:
juju set-constraints mysql mem=8G cpu-cores=4
juju set-constraints -m mymodel apache2 mem=8G arch=amd64
See also: get-constraints
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.0-rc1 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta5 → none |
milestone: | none → 2.0-beta5 |
I'm not sure the second example shown is valid.
It certainly doesn't match the usage. I think it should have the double quotes removed.