Tom Parrott comments

Results 1094 comments of


                                            Tom Parrott

lxd libraries don't expose facilities to set log level

@masnax any progress with this?

lxd libraries don't expose facilities to set log level

They are all only distributed by snaps so we control the Go version, 1.21 should be fine.

lxd libraries don't expose facilities to set log level

@masnax any reason not to just switch to slog and avoid needing to dependent on LXD's logger (we will probably switch to slog too eventually), but for something as general...

lxd libraries don't expose facilities to set log level

> The initlal reason we used LXD's logger was to avoid reimplementing one for each LXD-adjacent project. All the micro-apps were designed with LXD in mind, so using the same...

LXD cluster does not return metrics for the project if none instance form that project is run on the queried node.

@tregubovav-dev is this still an issue with LXD 5.20? @simondeziel would you mind seeing if you can validate if this remains an issue?

Invalid used by url on storage pool

> Usually, images are reported as `/1.0/images/56e10b38e59e94fd87d16fb6e090747602edd5ee77d9d8ffa6db4efa5821e0a9`. > I suggest the URL should either match the format with the `1.0/images` prefix, or be filtered from the response as the image...

Changing `limits.cpu` of a container can be racy

So the application of the limit is still always taking effect, its just that there can be a short delay between the `set/unset` command returning and the limit actually being...

driver: Detect EOF in driverError

Thanks! :)

Add support for `lxc cluster failure-domain ...` commands (to make tests more reliable)

Thanks! The first step will be to get a working LXD build, take a look at https://linuxcontainers.org/lxd/docs/master/installing/#install-lxd-from-source

Add support for `lxc cluster failure-domain ...` commands (to make tests more reliable)

Cleared assignment due to inactivity