[FFe] Let's get LXD 2.0 final in Xenial

Thanks for the heads-up, this sounds mostly fine. I take it that this is being coordinated with nova-compute-lxd and juju (whose local provider is also moving to LXD)?

> Replacement of lxcbr0 by lxdbr0

What's the rationale for this? This sounds a bit like change for change's sake -- lxcbr0 has been around for a long time including LTS releases, and by now third-party software or admins might depend on the name and use it to communicate with containers. Will the "lxc" package go away? Is this meant to not provide direct networking between "plain" LXC and LXD containers any more?

lxc will still provide lxcbr0 just as it always did, so there won't be a regression for any normal LXC user.

For LXD, the lxd package itself will provide a separate bridge specifically for LXD called lxdbr0. That bridges comes configured with IPv6 link-local only and LXD acts as a basic http proxy on it by default.
That means that containers can be started out of the box and will be able to reach http hosts but will not themselves have a global IPv4 or IPv6 address.

This is to avoid a current issue we've got with lxcbr0 where the 10.0.3.x/24 subnet we use may be used somewhere else on the user's network, therefore masking the real subnet and preventing any connection to it. That's been a serious problem ever since we added lxd to all cloud images and something we absolutely need to address.

With our solution, any pure LXD user will only have lxdbr0 on their system which by default will only use IPv6 link local addresses so cannot possibly conflict with anything. It's then up to the user to run "dpkg-reconfigure lxd" and setup IPv4 or IPv6 connectivity on the bridge the way they want (and since we're using debconf, preseeding is also possible).

Existing users of LXC will not see any difference as the lxc1 package where all the lxc-* tools are, will keep providing the lxcbr0 bridge as it always did with the same configuration it always did.

As for the other packages, the lxc package as of earlier today is now a transitional meta package to lxc1, the lxc1 package provides all the lxc-* tools as well as the lxc init scripts, which includes lxc-net and therefore lxcbr0.
The bits that LXD need are now entirely contained in liblxc1 and lxc-common, both of which can be installed without pulling lxc1.

LXD provides a lxc2 meta package which installs lxd and lxd-client, we will not be switching lxc to point to lxc2 with 16.04 as that would be way too big a change and we need people to start migrating on their own.

And yes, the nova-lxd team is aware of the upcoming changes (in fact the resource limit part was at their request) and the Tycho on the LXD team is the one working on the JuJu LXD port so that part's covered too.

Thanks for the clarifications! FF approved.

On Mon, Feb 22, 2016 at 09:02:53PM -0000, Stéphane Graber wrote:
> And yes, the nova-lxd team is aware of the upcoming changes (in fact the
> resource limit part was at their request) and the Tycho on the LXD team
> is the one working on the JuJu LXD port so that part's covered too.

Indeed, I will work with juju to make sure that things work with 2.0.0
final.

This bug was fixed in the package lxd - 2.0.0-0ubuntu1

---------------
lxd (2.0.0-0ubuntu1) xenial; urgency=medium

  * New upstream release (2.0.0) (LP: #1548489):
    - client: Add a json format option to "lxc list".
    - client: Recommend running lxd init
    - lxd: Allow setting security.privileged when nested
    - client: Filter on expanded config rather than local config
    - client: Fix wrong mode being passed by file push
    - client: Show the snapshot name instead of the path
    - client: Tweak help messages
    - client: Update Japanese translation
    - core: Don't let umask mess with modes
    - core: Fix uid, gid and mode of retrieved files
    - core: zfs: Clean any leftover snapshot
    - core: zfs: Ignore non-LXD paths in user count
    - doc: Mark API as stable for release
  * lxd-bridge: Don't fail on missing /etc/default/lxd-bridge

 -- Stéphane Graber <email address hidden> Mon, 11 Apr 2016 15:31:52 -0400