Hello all,
I'd like to bring to your attention a currently broken bootstrapping scenario:
Local deployment through LXD using a standard bridge instead of the usual LXD
provided lxdbr0.
As a development vehicle, a Juju install was planned reusing the LXD-host's
network. This implies having the J
On Mon, Jan 23, 2017 at 6:54 PM Toubeau, Anthony
wrote:
> Hello all,
>
> I'd like to bring to your attention a currently broken bootstrapping
> scenario:
> Local deployment through LXD using a standard bridge instead of the usual
> LXD provided lxdbr0.
>
> As a development vehicle, a Juju install
For your workaround, where does spec.Endpoint get filled in? By the user as
part of bootstrap-contraints? or by juju as a default value? I don't see
anything in your patch, which sounds like you would have to do:
juju bootstrap --bootstrap-constraints endpoint=HOSTIP lxd ...
if you were working on
Hi everyone,
Here's the schedule for Gent:
http://cfgmgmtcamp.eu/schedule/index.html#juju
See you all in 13 days!
--
Jorge Castro
Canonical Ltd.
http://ubuntu.com/cloud/kubernetes - Pure upstream Kubernetes
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https:
On Tue, Jan 24, 2017 at 12:54 AM John Meinel wrote:
> For your workaround, where does spec.Endpoint get filled in? By the user
> as part of bootstrap-contraints? or by juju as a default value? I don't see
> anything in your patch, which sounds like you would have to do:
> juju bootstrap --bootst
