using a bundle with manually added machines (redux)

[Vance Morris]

It's worse than a waste: it managed to confused the hell out of me. I had no idea that there even was a thing called "juju-deployer" that was separate from "juju deploy".

Seems to me that if a model already has machines 0 and 1 deployed, and a bundle is deployed that refers to machines 0, 1 and 2, Juju ought to automatically add a 3rd machine (2) and go to work deploying the applications. Why should the bundle care if a machine exists prior to deployment or not?

- Vance

-----stuart at stuartbishop.net wrote: -----
To: Rick Harding <rick.harding at canonical.com>
From: Stuart Bishop 
Sent by: stuart at stuartbishop.net
Date: 01/04/2017 02:56AM
Cc: Merlijn Sebrechts <merlijn.sebrechts at gmail.com>, Vance Morris/Dallas/IBM at IBMUS, "juju at lists.ubuntu.com" <juju at lists.ubuntu.com>
Subject: Re: using a bundle with manually added machines (redux)



On 3 January 2017 at 19:07, Rick Harding <rick.harding at canonical.com> wrote:
I'm looking into this. The bundle deploy feature in Juju 2.0 does not allow referring to existing machines because it breaks the reusability of the bundle. 

It would be great if Juju started supporting non-reusable bundles too. Its a waste having to support two similarly named tools that do almost the same thing. I'm not sure who is using 'juju deploy', but Amulet and Mojo both depend on 'juju deployer' for this reason. Which slows feature adoption, as juju-deployer doesn't seem to be owned by anyone and adding support for new features happens on an ad-hoc basis (my team is just now adding storage and resource support to it, needed for Mojo, so we can start using these features with actual deployments).

-- 
Stuart Bishop <stuart.bishop at canonical.com>