Comment 4 for bug 1566764

I can certainly agree with that, but the mandate for LXD until now has been to not deal with network configuration itself, keeping this separate, for example using neutron on nova-lxd.

The result is that the LXD upstream code as to how to create a bridge, all it deals with is existing layer-2 interfaces.

The bridge as it will be in 16.04 is created by the Ubuntu packaging. We do carry a tiny patch against upstream which has "lxd init" trigger that packaging for the user's convenience (used to be two separate steps).

Having LXD duplicate all the questions in lxd init would mean a far bigger patch which would break should the Ubuntu packaging ever be changed without a matching change against the upstream code. It's also worth pointing out that "lxd init" isn't translated right now while the debconf questions are, so on top of the maintenance burden and risk of breakages, this would also be a regression in that regard.

I think the right way forward is to discuss having bridge setup be done by LXD itself next cycle, at which point this feature would move entirely from distro packaging into the upstream code. But it's not something we're going to rush in two weeks before final release.