Restore command line placement.
Bug #860966 reported by
Kapil Thangavelu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| pyjuju |
Won't Fix
|
Undecided
|
Kapil Thangavelu | ||
Bug Description
There are several folks who would like to see its restoration. Both for
flexibility down the road and more immediately as mechanism to conserve
machine resources. The alternative of modifying environment config between
deploys is suboptimal. Its being used for example in reducing the number of
machines required for openstack. Although future use of ideal policies (limited
number of machines) is suboptimal, there are other placement policies taking
into account machine resources or cross availability zone for which this option
would be ideal.
Related branches
lp:~hazmat/pyjuju/cli-placement-restore
- Gustavo Niemeyer: Needs Fixing
-
Diff: 450 lines (+143/-56)12 files modifiedjuju/control/add_unit.py (+13/-4)
juju/control/deploy.py (+10/-4)
juju/control/tests/test_add_unit.py (+36/-0)
juju/control/tests/test_deploy.py (+33/-1)
juju/providers/common/base.py (+4/-6)
juju/providers/common/tests/test_base.py (+2/-5)
juju/providers/dummy.py (+4/-6)
juju/providers/lxc/__init__.py (+2/-5)
juju/providers/lxc/tests/test_provider.py (+2/-7)
juju/providers/tests/test_dummy.py (+4/-7)
juju/state/placement.py (+19/-0)
juju/state/tests/test_placement.py (+14/-11)
| Changed in juju: | |
| assignee: | nobody → Kapil Thangavelu (hazmat) |
| milestone: | none → eureka |
| status: | New → In Progress |
Revision history for this message
| Kapil Thangavelu (hazmat) wrote | #1 |
| Changed in juju: | |
| status: | In Progress → Won't Fix |
To post a comment you must log in.
seems better to not hide this behavior behind placement, and instead to offer direct machine placement.