Re: One instance manual provider
I'm looking at this area of code at the minute (lp:1642295). The documentation might be trying to work to the code's apparent assumption that there will be only one controller machine, and that machine will be the only one in the controller model. (Also note this manual HA bug lp:1642618.) I don't think sharing the controller model and machine for workloads is a great drama, but you may find some manual clean-up to do when you go to destroy the controller. On Mon, Dec 05, 2016 at 03:09:24PM +, 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 controller > juju deploy --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 > 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 -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: One instance manual provider
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 world. But yeah, it's a work-around. Charles Butler - Juju Charmer Come see the future of modeling your datacenter: http://jujucharms.com On Mon, Dec 5, 2016 at 11:20 AM, Nate Finch wrote: > 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 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 machines. >> >> On Mon, Dec 5, 2016 at 9:27 AM Rick Harding >> 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 >> >> > -- > 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
Re: One instance manual provider
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 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 machines. > > On Mon, Dec 5, 2016 at 9:27 AM Rick Harding > 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 > > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: One instance manual provider
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 controller > juju deploy --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 > 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 > -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
Re: One instance manual provider
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 machines. On Mon, Dec 5, 2016 at 9:27 AM Rick Harding 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
Re: One instance manual provider
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
One instance manual provider
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
