Hard to use non-default LXD bridge

[Björn Tillenius]

I'm trying to use the LXD provider in Juju 2.0, and more specifically I need it to use a specific bridge, which isn't the default lxdbr0 one.

In LXD, this is easy. I just edit the default profile to use another bridge.

To get Juju to use my bridge is a lot harder, though. With beta3 it was quite easy, I just had to name it lxcbr0 and it worked. beta6 seems to be looking at what the default bridge is in the default profile (which is good), but then it seems to insist that it's configured in /etc/default/lxd-bridge. No matter what I tried, it complained that the lxd bridge wasn't configured.

What did work, though, was to manually edit /etc/default/lxd-bridge and change it to say the bridge is enabled (without restarting the lxd-bridge service). Then bootstrap will succeed, and after that I can revert the changes to /etc/default/lxd-bridge.

So it seems it is possible not to use the default lxd bridge, but you have to trick Juju to believe the default bridge is configured. Surely there has to be simpler way?

[John A Meinel (jameinel)]

We should support setting "lxd-bridge" as part of configuration (juju bootstrap --config lxd-bridge=XXX) but we I don't believe we support that yet.

[james beedy (jamesbeedy)]

Whats the status on this? any?

[Cheryl Jennings (cherylj)]

We're going to discuss this as part of the usability work at the juju sprint this week.

[Adam Stokes (adam-stokes)]

conjure-up users faces this issue as well:

https://github.com/ubuntu/conjure-up/issues/37

[BlueT - Matthew Lien - 練喆明 (bluet)]

I'm facing similar problem.

I followed this HowTo https://bayton.org/2016/05/lxd-zfs-and-bridged-networking-on-ubuntu-16-04-lts/ and changed the br0 name to **lxdbr0**.
LXD runs perfectly with br0 (with external DHCP server), so containers can get an IP in my network and we can connect into it.

With `conjure-up openstack` and the option "OpenStack with Nova-LXD", Clouds choose "localhost", after a short bootstraping screen then it says my lxdbr0 is not enabled...

[chrisaw (home-6)]

I am facing the same problem and haven't yet even been able to work around it.

In my case conjure-up doesn't even start trying to bootstrap - just bombs out straight away with an error stating that my lxd network interface isn't configured.

Does look like this is related to juju and the issue stated above.

Does anyone have any other workarounds to try for now to at least get myself running?

Thanks!

[Cheryl Jennings (cherylj)]

@chrisaw - did you run `dpkg-reconfigure lxd` to set it up?

[Adam Stokes (adam-stokes)]

@chrisaw you'll want to make sure that at the very least lxdbr0 is up, it may require a simple 'lxc list' to activate the socket the first time. Also make sure you're user is in the lxd group.

@cheryl, is it possible to get a more definitive eta when we think this can be addressed?

[Cheryl Jennings (cherylj)]

Being able to specify an alternate bridge for the lxd provider is probably a 2.1 item. I'll bring it up again in today's release call to see if there's a chance it could be included in 2.0.0.

[Adam Stokes (adam-stokes)]

Hi Cheryl,

Any word on if this would make it into 2.0.0? More and more conjure-up users are hitting this

Thanks
Adam

[Dimiter Naydenov (dimitern)]

Fix proposed https://github.com/juju/juju/pull/5871

[Ryan Beisner (1chb1n)]

In the context of manual-provider, this issue appears to still exist. See https://bugs.launchpad.net/juju/+bug/1655224

[Ryan Beisner (1chb1n)]

The following related bug is really the root cause for our use case here. If it didn't exist, we wouldn't have to try to munge the bridges ahead of Juju:

"manual provider lxc/lxd units are behind NAT, fail by default"
https://bugs.launchpad.net/juju/+bug/1614364