The focus of this week has been preparing for our trip to Brussels where we’ll be spending 3 days all working together on LXD before attending and presenting at FOSDEM.
@brauner is making good progress on preparing for the liblxc 3.0 release, moving all the various language bindings and tools out of the main tree and into separate repositories.
@monstermunchkin has also been busy working on our refreshed tooling for generating LXC and LXD images which will be replacing the dated template shell scripts in 3.0.
On the LXD side, @freeekanayaka is hard at work fixing a number of remaining rough edges around the clustering branch and working with @stgraber to get things going through CI and in shape so it can be merged very soon.
We’ve also been fixing a number of issues here and there to keep CI going and have been pushing a number of bugfixes and improvements to the LXD snap.
We’re all looking forward to seeing some of you in Brussels later this week!
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.
proxydevice failing in the snap.
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.
criuin the snap, protected by a new snap property (
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…