Weekly status #101

distrobuilder
weekly
lxcfs
lxc
lxd

(Stéphane Graber) #1


Weekly status for the weeks of the 3rd to the 9th of June.

Introduction

This past week we went live with Busybox as an added LXD image and fixed a number of LXD and LXC issues including quite a bit of work around how we forward DNS queries around the cluster.

In the background we’re also working on a number of improvements for our LXD images, including enabling cloud-init on all images, porting Ubuntu Core to distrobuilder, improving our network SR-IOV support in LXD and various refactoring.

This week we’ll be releasing LXD 3.14 and assuming we get the backlog sorted in time, also LXC, LXCFS and LXD 3.0.4 but this may end up slipping to early next week to allow for more testing time.

Ongoing projects

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.

  • Rework of internal LXD storage handling
  • Dqlite 1.0
  • Various kernel work
  • Stable release work for LXC, LXCFS and LXD

Upstream changes

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.

LXD

LXC

LXCFS

  • Nothing to report this week

Distrobuilder

  • Nothing to report this week

Distribution work

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

  • Nothing to report this week

Snap

  • Ported edge snap to using bases (first step in porting to 18.04)

(Stéphane Graber) pinned globally #2

#3

“including enabling cloud-init on all images”

Great news!


(Phil Howard) #4

will cloud-init be in the busybox image? i’m hoping to see a very minimalist image.


(Stéphane Graber) #5

We don’t distribute busybox images through our image server but we do distribute Alpine Linux which is very close to a busybox image. I don’t know if Alpine has cloud-init, if it does, then we will enable it there so long as it doesn’t end up causing the image to jump too much in size.

Cloud-init being a python3 piece of software we do have to be a bit careful as to its impact on image size and content when added. For many it won’t be an issue as they already have python3 included, but for some of the more minimal images, that will certainly be a concern.