Weekly status for the week of the 28th to the 3rd of September 2017.
The main focus for this past week has been the preparation for LXC 2.1.
We’ve now issued a call for testing and expect it to release tomorrow (Tuesday).
On the LXD side of things, we’ve been working through bug reports quite a bit, did some internal refactoring and been slowly working our way through our stable branch backlog.
As for the LXD snap, a new lxd-migrate tool has been written which will allow users to move data from an existing LXD installation over to the LXD snap, updating all needed database entries and storage specific data in the process. This is currently only available in the edge channel as we’re still working on manual and automated testing for this feature.
If you’re attending any of those and want to talk to us, let us know!
Details on what we’ll be doing over there can be found here).
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.
This article originally appeared at the Linux Containers forum
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…