As a new (home) user of the community edition I find this very interesting, because I hadn’t realized this. Indeed looking at the URL TrueNAS SCALE - Linux-based Open Source Storage Infrastructure v. 24.04 “Dragonfish” is still the “advertised” version.
However on the download page ( Download TrueNAS SCALE - Data Storage Software ) v. 24.10.1 is advertised as the current stable version.
So there appears to be a disconnect/contradiction here…
On a more general note: Can you provide any info, as to which (sub release) version is suitable for which audience, e.g. yy.mm.0 is suitable for audience a, yy.mm.1 is suitable for audience b, etc.?
@HoneyBadger Thank you so much for that pointer. That matrix of course also explains and resolves the seeming contradiction that I mentioned in my previous post, that is different web pages are just targeted toward a different audience.
I believe so, but the current big caveat is that the /var/lib/incus directory gets wiped on updates, thus losing configurations made outside the middleware.
With the new TrueNAS versioned API, it is probably better to think about a Terraform provider for TrueNAS 25.04. As @Stux indicated, TrueNAS is designed to have all configuration go through its API (whether its WebUI or directly).
I would think that is probably fine as terraform maintains its own state and is designed to reconcile that state with real infra on every run. But worth testing.
I would only use Terraform to provision VMs and LXCs, not configure Incus itself.
This made me reference the API docs for 24.04 and read about the API switch. I see websocket still referenced but not Rest. I built a few Rest calls from Home Assistant to TrueNAS to dashboard HD temps, pool status and smart events. Will Rest be fully removed from the API in Fangtooth?
Edit should have read more before posting, sorry. I see it’s depreciated and then will be removed in a future release. Thanks!
So since CORE is retiring, and i’m still running CORE. Will this version provide a more easy migration away from CORE? Mainly some way to convert jails to the new format and keep most settings the same? I was held back upgrading because i basically needed to reconfigre everyhting besides mounting the pools.
Nor is a general solution particularly feasible to automate. Absolute best case would be to throw the jails into a FreeBSD VM to keep them running as-is, and even that would be tricky.
I can see I should concentrate some on potential migration from Core to Scale, much as this old dog doesn’t want to learn new tricks (when I looked at FreeBSD/FreeNAS 15 or so years ago, given its background and the level of support from IX, I thought it would be my last fresh OS…).
Can you please put a little flesh on those “bare bones steps’ statements” with the essential steps they comprise for a two-jail migration?
