Hey Folks,
I notice the docs state that at least two instances are needed for the
manual provider: https://jujucharms.com/docs/stable/clouds-manual. Some
quick playing around suggests that this is indeed the case.
Is there a technical reason why? I'd love to spin up a charm on [insert vps
provide
I'll have to test it out but I would think that you could
1) bring up a machine, create a container on it, bootstrap to that
container as the controller, create another container, and then add-machine
it as a second machine and things should work ok.
2) I wonder if you can bootstrap to a machine,
The should be no reason you can't deploy to the controller machine using
manual just like any other cloud.
juju bootstrap manual/x.x.x.x mycloud
juju switch controller
juju deploy --to 0
Switching to the controller model is probably what you were missing, since
the default model comes with no m
A one machine manual provider? Might as well just `ssh ; juju
bootstrap lxd`.
On Mon, Dec 5, 2016 at 10:09 AM Nate Finch wrote:
> The should be no reason you can't deploy to the controller machine using
> manual just like any other cloud.
>
> juju bootstrap manual/x.x.x.x mycloud
> juju switch
Except you can't expose anything deployed to lxd to the network, right?
On Mon, Dec 5, 2016, 5:49 PM Marco Ceppi wrote:
> A one machine manual provider? Might as well just `ssh ; juju
> bootstrap lxd`.
>
> On Mon, Dec 5, 2016 at 10:09 AM Nate Finch
> wrote:
>
> The should be no reason you can't
That's one thing I've done as a hacky work-around to this scenario is to
manual provider bootstrap the host as the controller, and deploy everything
but the load balancer to LXD. colocate haproxy or nginx on the controller
host and viola. You've got a single instance LXD that's reachable by the
wo
