The highlight of this week was the release of LXD 2.20 which introduces a number of exciting new features.
LXD 2.20 should now be available everywhere through both native packages and snap.
We also started the process of deprecating the various LXD PPAs, see below for details.
Our next milestone is LXD 2.21 in about a month which will be the last LXD release of the year and the last LXD 2.x release. Once 2.21 is out, we’ll focus on LXD 3.0 with the first alpha expected in January.
At the end of this year, we are going to stop delivering LXD through our PPAs.
This is done to cut down the amount of time we have to spend on packaging, tooling maintenance and package version tracking when dealing with issues.
The two recommended ways of getting the latest LXD feature release are:
snap install lxd
apt install -t xenial-backports lxd lxd-client
PPA users have until the end of December to transition over to one of those two, a warning message has been added to the LXD package in our PPAs, including instructions on moving to either the snap or backport package while keeping all your data in place.
The list below is feature or refactoring work which will span several weeks/months and can’t be tied directly to a single Github issue or pull request.
The items listed below are highlights of the work which happened upstream over the past week and which will be included in the next release.
This section is used to track the work done in downstream Linux distributions to ship the latest LXC, LXD and LXCFS as well as work to get various software to work properly inside containers.
Ubuntu offers all the training, software infrastructure, tools, services and support you need for your public and private clouds.
Introduction The focus for this week was on CEPH and LXD clustering, trying to get the last few remaining pieces to work together properly. We’ve tagged a couple more betas as we went through that. We’ve also spent a good chunk of time…
Introduction This past week the LXD team was meeting in Budapest, Hungary. We spent most of our times working on a number of issues targeted at the final 3.0 releases. @freeekanayaka worked with @stgraber to track down an fix a testing…
This article originally appeared on Chris Sanders’ blog MAAS is designed to run in a data center where it expects to have control of DNS and DHCP. The use of an external DHCP server is listed as ‘may work but not supported’ in the…