Comment 1 for bug 1548489

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?