Rejection of peer join.
Michael Van Der Beek
michael.van at antlabs.com
Thu Sep 28 09:20:33 UTC 2017
Great! Thanks Stuart. Appreciate the advise!
Regards,
Michael
-----Original Message-----
From: stuart at stuartbishop.net [mailto:stuart at stuartbishop.net] On Behalf Of Stuart Bishop
Sent: Thursday, September 28, 2017 3:59 PM
To: Michael Van Der Beek <michael.van at antlabs.com>
Cc: juju at lists.ubuntu.com
Subject: Re: Rejection of peer join.
On 28 September 2017 at 10:09, Michael Van Der Beek <michael.van at antlabs.com> wrote:
> Hi Stuart,
>
> Thanks for your insight. Greatly appreciate it.
>
> Last thing, when you said " I'm generally deploying charms to bare
> metal and using local disk", Does that mean you manually install a
> machine with Ubuntu, then in juju add-machine ssh:user@<machine ip> Then juju deploy --to <machine #> ?
Manually installing a machine with Ubuntu would work, but we provision the machine with MAAS. We then add it to an OpenStack Juju model using 'juju add-machine' as you suggest (the 'manual provider'). This lets us mix OpenStack VMs and bare metal in the same model. The downside is we have to handle network issues and firewall rules to the bare metal units ourselves. I expect we will change to using cross model relations when they are available between clouds, so we use a MAAS model for the bare metal units and connect them to OpenStack units in an OpenStack model. Ideally we could mix and match units from different cloud providers in the same model, but I believe that is a long way off.
--
Stuart Bishop <stuart.bishop at canonical.com>
More information about the Juju
mailing list