Weekly news #377

LXD News
,
1

Weekly status for the week of 16th December to 5th January.

Introduction

All of the LXD team were away for the Canonical holiday shutdown so the changes in this update all come from the week of the 16th to the 22nd December. During this period, LXD received several bug fixes and numerous smaller improvements.

Thanks to all contributors, and happy New Year.

The --format flag for lxd sql command

The lxd sql command enables administrators to query the global or local cluster member database directly.

A new --format flag has been introduced, allowing results to be formatted as sql, csv, table, compact, json or yaml.

lxd sql global 'SELECT * FROM instances' --format table

Bug Fixes

  • Optimized the efficiency of the patch that removes volatile.%.last_state.ip_addresses by consolidating it into a single query. Previously, the patch removed the key individually for each instance and snapshot to ensure intuitive logging. However, this approach could cause upgrade issues on servers with a large number of instances or snapshots.

  • Fixed an issue where the LXD incorrectly assumed consistent ordering between /sys/devices/system/cpu/cpu*/topology/physical_package_id and /proc/cpuinfo, causing failures in environments with non-sequential CPU IDs.

  • Various improvements to lxc command completion, including support for auto-completion of remotes and a fix for the storage volume show command, which incorrectly prepended the snapshots/ prefix when completing snapshot names.

All changes

The items listed below is all of the work which happened over the past week and which will be included in the next release.

LXD

LXD UI

LXD Charm

  • Nothing to report this week

LXD Terraform provider

PyLXD

Distribution work

This section is used to track the work done in downstream Linux distributions to ship the latest LXD as well as work to get various software to work properly inside containers.

Ubuntu

  • Nothing to report this week.

LXD snap

2 Likes
2

LXD 6.2-bde4d03 includes the fix for the volatile.%.last_state.ip_addresses patch and is now in latest/stable and 6/stable.

2 Likes