lp:~frankban/juju-deployer/unit-placement-fix

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:juju-deployer at revision 152

Madison Scott-Clary (community): Approve (code and qa) on 2015-08-06

Tim Van Steenburgh (community): Approve on 2015-08-06

Brad Crittenden (community): Approve (code) on 2015-08-06

Diff: 593 lines (+156/-107)

11 files modified

deployer/action/importer.py (+15/-24)
deployer/config.py (+5/-5)
deployer/deployment.py (+3/-3)
deployer/service.py (+46/-45)
deployer/tests/base.py (+36/-0)
deployer/tests/test_data/v4/container-existing-machine.yaml (+1/-1)
deployer/tests/test_data/v4/placement-invalid-number.yaml (+8/-0)
deployer/tests/test_deployment.py (+23/-10)
deployer/tests/test_guiserver.py (+7/-3)
deployer/tests/test_importer.py (+11/-15)
setup.py (+1/-1)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

159. By Francesco Banconi on 2015-08-06

Remove the reloading logic in importer.add_unit.

158. By Francesco Banconi on 2015-08-06

Checkpoint: fix some typos.

157. By Francesco Banconi on 2015-08-06

Fix the services sorting logic and improve status retrieval while adding units.

156. By Francesco Banconi on 2015-08-06

Fix machine mapping logic.

155. By Francesco Banconi on 2015-08-06

Make all the tests pass.

154. By Francesco Banconi on 2015-08-05

Do not wait minutes while testing.

153. By Francesco Banconi on 2015-08-05

Change the bundle version detection logic.

152. By Francesco Banconi on 2015-08-05

Improve unit placement validation in the case one unit is paced on an lxc on the machine of another unit.

151. By Tim Van Steenburgh on 2015-08-04

v0.5.0

150. By Tim Van Steenburgh on 2015-08-04

Allow charms to be specified using an absolute local path.

For example:

    services:
        mycharm:
            charm: /tmp/trusty/mycharm

Primary rationale for this is to allow rapid iteration on a charm's amulet
tests, without needing to commit the changes, or even have them under
revision control. For the charm under test, amulet will give deployer an
absolute path, ensuring that the version of the charm that is deployed and
tested is whatever is on disk at the time.