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 <foo> --to 0 Switching to the controller model is probably what you were missing, since the default model comes with no machines. On Mon, Dec 5, 2016 at 9:27 AM Rick Harding <rick.hard...@canonical.com> wrote: > 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, manually add container on > that machine, and then add that container with add-machine. > > I'm guessing there's some bits about making sure the added containers have > the ssh key you want to use for the ssh connection for add-machine. > > On Mon, Dec 5, 2016 at 3:18 PM Matthew Williams < > matthew.willi...@canonical.com> wrote: > > 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 provider here] and only spend money for one instance > > Matty > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
