Public bug reported:
Hello,
LXD is currently being developed on a monthly release schedule where we
push out a stable release every 4 weeks (so technically slightly faster
than monthly).
I uploaded LXD 2.1 to the archive a couple weeks back so before Ubuntu
16.10 releases, upstream will be tagging LXD 2.2 and 2.3.
Most of our focus is on bugfixing and performance improvement which made the
bulk (90%+) of the commits in LXD 2.1. We however still have a few features we
except to land in one of those two LXD releases before Ubuntu 16.10 goes out.
- AppArmor profile stacking and namespacing. This is a pretty trivial
change on the LXD side but is currently blocked on a bunch of kernel
issues in the 16.04 and 16.10 kernels which the AppArmor team is
actively working on. This will also need a newer CRIU version (see
below).
- CRIU stable releases. CRIU releases monthly and most if not all of
the changes are basically bugfixes to support serialising more user
space tasks. We plan on syncing new releases of CRIU from Debian, all
the way to release (after testing). CRIU is currently in universe and
will remain there for 16.10.
- Support work for the LXD snap. We may need to do some changes here
and there in LXD to have it snap better. Those changes would be included
in our next releases. I however don't expect those to affect the user
experience for deb users.
- Support work for running snaps inside LXD. The bulk of this should be
the AppArmor stacking work and CRIU update to support said work. We'll
first land all of this in a feature release of LXD in Yakkety before
eventually including this in our LTS branch for Xenial.
- New network management API and user experience. This is the BIG
feature we'll be working on before 16.10 releases. We have a full spec
on it and will be implementing this over the next couple of weeks. This
will effectively migrate the lxdbr0 bridge currently created and managed
through a bunch of debconf scripts I wrote, to having LXD itself manage
bridges.
This should have no impact on existing users as we will transition
the existing bridge over to a LXD managed bridge during upgrade and our
existing configuration tool "lxd init" will simply drop the current
configuration distro patch in favor of the upstream configuration steps.
- Random bits and pieces from the community. Those includes a few extra
convenience flags to existing commands, such as recursive file copy and
download, more resource reporting in the API, a few more config options
and knobs here and there, ...
We commit not to do any backwards incompatible change to the REST API
within the 2.x series (1.0 API) and we will not be making any backwards
incompatible change to the command line interface for 16.10 either.
With frequent upstream releases and our current CI environment, we
believe we can land those changes in Ubuntu 16.10 without breaking
anything or affecting our downstreams. Landing those stable releases
will also reduce the maintenance burden upstream by just having Yakkety
update to the latest stable release rather than needing to backport
bugfixes. We will obviously provide 9 months support on LXD 2.3 to
support Ubuntu 16.10 when it releases.
** Affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618159
Title:
[FFe] Feature Exception for LXD in Ubuntu 16.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1618159/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
