Got incus-deploy to a state where it can now reliably deploy #Ceph, #OVN and #Incus in just a few minutes, taking care of all the clustering bits and resulting in a fully functional environment! https://asciinema.org/a/654385
#Incus 6.0 LTS is finally out!
This will be supported until June 2029 and now offers a great migration path for anyone still on LXD 5.0.
We've got a detailed announcement including a brief description of Incus itself, what's new for anyone coming from LXD 5.0 and of course what's new for existing Incus users!
@stgraber are there any plans to fork pylxd and make it "pyincus", so it works with #Incus?
I use pylxd in my Python backup script (https://github.com/ThomasLeister/lxd-backup) to create and delete snapshots. Right now it's preventing me from switching my productions servers to Incus, because I need a working backup script.
Probably pylxd can be forked and it's mostly a "rename job" afterwards? Before I fork it myself, I just wanted to ask you if you have any plans related to that 🙂
I was wondering about that odd "I am leaving #Canonical" blogpost by @stgraber some months ago and with this talk it all makes sense: relicensing and kicking out the community of #lxd is pretty hostile and caused the inevitable immediate fork as #incus .
And so it begins... Canonical just merged a pull request into #LXD including 3 of my changes from #Incus with me clearly listed as the author despite me having specifically declined to sign the CLA that's supposedly required for all contributions to their project... https://github.com/canonical/lxd/pull/12709
"'"[…] Canonical re-licensed LXD […] Because LinuxContainers community can't lean on to LXD, they've decided not to build and publish LXD images anymore. Non-LTS LXD will gradually start losing access to these images immediately in 2024, while LTS LXD is allowed until ~April-May of 2024 to have a fair chance migrating into #Incus LTS, which is expected to be out in April 2024. […]"'"
@stgraber just observed that it looks like #Canonical is going down the route of marking #Incus changes as still staying under Apache2, as a way to get our changes while preventing us from taking theirs. Now to see what they'll do about the CLA... https://github.com/canonical/lxd/pull/12675
Just migrated my last #LXD cluster over to #incus!
This was the scariest one as that's the production cluster running my BGP routers and all the Linux Containers infrastructure, but lxd-to-incus took care of it and 20min later everything was back online!