| 2016-03-30 15:34:39 |
Peter Matulis |
bug |
|
|
added bug |
| 2016-03-31 21:16:13 |
Cheryl Jennings |
juju-core: status |
New |
Triaged |
|
| 2016-03-31 21:16:15 |
Cheryl Jennings |
juju-core: importance |
Undecided |
Medium |
|
| 2016-03-31 21:16:17 |
Cheryl Jennings |
juju-core: milestone |
|
2.0-beta4 |
|
| 2016-04-07 19:56:25 |
Peter Matulis |
description |
e.g.:
Usage: juju set-constraints [options] <service> <constraint>=<value> ...
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 commands (such as 'deploy') that provision machines for services. Where model and service constraints overlap, the service constraints take precedence.
Constraints for a specific model can be viewed with `juju get-model-constraints`.
Examples:
juju set-constraints mysql mem=8G cpu-cores=4
juju set-constraints -m mymodel apache2 "mem=8G arch=amd64"
See also: get-constraints
get-model-constraints
set-model-constraints |
e.g.:
Usage: juju set-constraints [options] <service> <constraint>=<value> ...
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 commands (such as 'juju deploy') that provision machines for services. Where model and service constraints overlap, the service constraints take precedence.
Constraints for a specific model can be viewed with `juju get-model-constraints`.
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
get-model-constraints
set-model-constraints |
|
| 2016-04-12 16:50:49 |
Cheryl Jennings |
juju-core: milestone |
2.0-beta4 |
2.0-rc1 |
|
| 2016-04-12 21:30:07 |
Reed O'Brien |
bug |
|
|
added subscriber Nick Veitch |
| 2016-04-12 21:30:18 |
Reed O'Brien |
bug |
|
|
added subscriber Matthew Helmke |
| 2016-04-12 21:35:07 |
Reed O'Brien |
juju-core: status |
Triaged |
In Progress |
|
| 2016-04-12 21:35:10 |
Reed O'Brien |
juju-core: assignee |
|
Reed O'Brien (reedobrien) |
|
| 2016-04-13 11:45:32 |
Matthew Helmke |
description |
e.g.:
Usage: juju set-constraints [options] <service> <constraint>=<value> ...
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 commands (such as 'juju deploy') that provision machines for services. Where model and service constraints overlap, the service constraints take precedence.
Constraints for a specific model can be viewed with `juju get-model-constraints`.
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
get-model-constraints
set-model-constraints |
e.g.:
Usage: juju set-constraints [options] <service> <constraint>=<value> ...
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 commands (such as 'juju deploy') that provision machines for services. Where model and service constraints overlap, the service constraints take precedence.
Constraints for a specific model can be viewed with `juju get-model-constraints`.
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
get-model-constraints
set-model-constraints |
|
| 2016-04-13 22:29:38 |
Reed O'Brien |
juju-core: status |
In Progress |
Fix Committed |
|
| 2016-04-20 13:56:40 |
Curtis Hovey |
juju-core: status |
Fix Committed |
Fix Released |
|
| 2016-08-23 01:09:14 |
Canonical Juju QA Bot |
affects |
juju-core |
juju |
|
| 2016-08-23 01:09:14 |
Canonical Juju QA Bot |
juju: milestone |
2.0-beta5 |
|
|
| 2016-08-23 01:09:17 |
Canonical Juju QA Bot |
juju: milestone |
|
2.0-beta5 |
|
