Machine placement doesn't support existing machines
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-deployer |
Fix Released
|
Undecided
|
Jorge Niedbalski |
Bug Description
[Rationale]
There are scenarios (such as MAAS deployments ) on which you have pre-allocated machines
with custom settings.
Currently using the v3 bundles juju-deployer doesn't allows to place a service on a machine different than 0 or specify a new container for deploy this machine.
Since the introduction of v4 bundles ( already supported on juju-deployer ) is possible to place
a service into a specific machine, container or even create a new lxc container.
However, it forces the creation of new machines or containers. The specific case on which you already have a deployed machine, and you don't want to create/allocate a new one for the service is not covered.
This bug tracks that functionality.
Related branches
- Tim Van Steenburgh (community): Approve
-
Diff: 187 lines (+110/-12)4 files modifieddeployer/action/importer.py (+40/-11)
deployer/deployment.py (+7/-1)
deployer/tests/test_data/v4/container-existing-machine.yaml (+42/-0)
deployer/tests/test_importer.py (+21/-0)
Changed in juju-deployer: | |
assignee: | nobody → Jorge Niedbalski (niedbalski) |
status: | New → In Progress |
description: | updated |
Changed in juju-deployer: | |
status: | In Progress → Fix Released |
status: | Fix Released → Fix Committed |
Changed in juju-deployer: | |
milestone: | none → 0.5.0 |
Changed in juju-deployer: | |
status: | Fix Committed → Fix Released |
tags: | added: sts |