Machine placement doesn't support existing machines

Bug #1454720 reported by Jorge Niedbalski
10
This bug affects 1 person
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.

Tags: sts

Related branches

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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.