On Tue, Sep 10, 2013 at 1:01 AM, Nate Finch wrote:
> I'm pretty interested in this, actually, since I want to be able to use
> juju to deploy charms to a VPS I have... but even with this change, it's
> not workable, because we can't manually choose a machine to bootstrap to.
> Needing an AWS machi
On Mon, Sep 9, 2013 at 9:39 PM, Andreas Hasenack wrote:
> Here is what I just tried with juju-core trunk (r1772):
>
Thanks for trying it out.
> $ sudo $(which juju) bootstrap
> $ juju status
> environment: local
> machines:
> "0":
> agent-state: started
> agent-version: 1.15.0.1
>
I'm also quite interested in this, however, I don't think your idea of
listing IP addresses in the environments yaml is the way to go. I really
like the add-machine functionality. I look forward to seeing how the
bootstrap problem is overcome, as it appears based on Andrew's first email
they are wo
I'm pretty interested in this, actually, since I want to be able to use
juju to deploy charms to a VPS I have... but even with this change, it's
not workable, because we can't manually choose a machine to bootstrap to.
Needing an AWS machine (or similar) as machine 0 is pretty much a deal
breaker.
Marco - no reason we can't do both. :) The nice thing about putting a list
in environments.yaml is that it makes the workflow the same as the other
providers. It also means that you don't have to go look up an external list
of IP addresses when you want to add a new service on a new machine. Think
On Sun, Sep 8, 2013 at 10:47 PM, Andrew Wilkins <
andrew.wilk...@canonical.com> wrote:
> Hello everyone,
>
> As was noted in the 1.13.3 release notes thread, we did not announce one
> the major features that made it into the release (manual provisioning).
> This was intentional as we have not writ
