The Incus team is pleased to announce the release of Incus 6.7!
This is another one of those pretty well rounded releases with new features and improvements for everyone from standalone users to those running a small homelab all the way to large scale cluster users, there’s something for everyone!
The highlights for this release are:
- Easy access to the Incus web interface
- Automatic cluster re-balancing
- DHCP renewal for OCI containers
- Partial instance/volume refresh
- Configurable columns, formatting and refresh time for incus top
- Support for DHCP address ranges in OVN networks
- Changing of parent device for physical networks
- Aditional QMP helpers in QEMU scriptlet
- Additional QEMU log file for QMP commands
- New get_instances_count command for placement scriptlet
- Support of formatting in incus admin sql command
The full announcement and changelog can be found here.
And for those who prefer videos, here’s the release overview video:
You can take the latest release of Incus up for a spin through our online demo service at: https://linuxcontainers.org/incus/try-it/
And as always, my company is offering commercial support on Incus, ranging from by-the-hour support contracts to one-off services on things like initial migration from LXD, review of your deployment to squeeze the most out of Incus or even feature sponsorship. You’ll find all details of that here: https://zabbly.com/incus
Donations towards my work on this and other open source projects is also always appreciated, you can find me on Github Sponsors, Patreon and Ko-fi.
Enjoy!
Github
Twitter
LinkedIn
Mastodon
RSS feed
In the zapply repos the webui is named the canonical ui. For this reason, I’ve been reluctant to rely on it. Does this mean that incus intends to ship its own webui? Should I consider the webui an integral component of incus (even if today it might still be in its infancy)?
Incus basically serves any UI that’s put into /opt/incus/ui/.
I do build and package a slightly modified version of Canonical’s LXD UI as incus-ui-canonical but we may also be adding other options in the future as there are quite a few other UI projects that have been built around the LXD and Incus API.
In general, it’s fair to assume that incus-ui-canonical is maintained. I build it, I test it and I use it for my customers.
We also have a few folks actively working on fixes and improvements to it, so it’s in pretty good shape.
That said I can certainly see us moving to a different UI over the coming years as relying on something designed for LXD will grow harder and harder to maintain over time as the two projects diverge.
Great. Thanks. That’s what I was hoping to hear.