juju ensure-availability should default to -n=3
Bug #1311083 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
Right now we have a optional parameter -n to specify how many state machines you want. It appears that the default value of 'n' is -1, and it gives you an error if you just run "juju ensure-
If we *want* to force the users to specify a value, then it should be a positional argument (juju ensure-availability 3). However, I think what we really want is to just default to 3 because we have a strong argument that it is actually the best value to use (least overhead vs actual benefit).
Related branches
lp:~jameinel/juju-core/ensure-availability-default-3-1311083
- Juju Engineering: Pending requested
-
Diff: 474 lines (+232/-65)6 files modifiedcmd/juju/ensureavailability.go (+12/-13)
cmd/juju/ensureavailability_test.go (+56/-27)
state/addmachine.go (+13/-6)
state/apiserver/client/client.go (+17/-5)
state/apiserver/client/client_test.go (+78/-12)
state/state_test.go (+56/-2)
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
