A lot of people don’t upgrade for new features but instead they have been told the railway track ahead is running out and you better jump soon if you want to maintain security.
3 Likes
I understood your point. The thing is, we’ve all seen features be completely reworked, changed, removed, etc in the span of even a year. Over the last 3 years there have been several major changes to the apps system. Dragonfish introduces a laughably untested replacement feature replacing Virtualization entirely. The fact is, if someone is waiting just until the feature they want matures or becomes stable, whatever feature they are waiting for might not exist in a years’ time, so better to just be ready to stay on it forever - hence my originally included option.
Edit:
The point I was trying to make before which you might have missed (it was above when I leaned into the guinea pig thing) is the choices we have been given are all bad. No one is trying to shake responsibility for a choice they made by offering you legitimate criticism in this thread.
There is some good news coming… a different topic that 6 month cycles.
In the meantime keep using 24.10.2.2… its a perfectly fine release and recommended for Conservative users.
1 Like
So either a) stick with 24.10 SCALE for another 6 months, as it remains fully supported until 25.10.2 CE or b) move to 25.04.1 CE now and get a feel for the virtualization feature.
Both can be right depending on how one uses the feature.
For me 25.04 CE was right. I could try an LXC and confirm that yep, ZFS on NVMe still sucks, keep doing dedicated machines with xfs for database work.
But that’s because I’m a home user. SMB and two apps (Plex and Foundry VTT), and that’s it. Virtualization only to, well, see above.
Part of the deal we get with community versions of TrueNAS is to have an understanding of our own needs and choose versions accordingly. I know, that’s a tall ask for many.
On the 6 month cadence: It’s aggressive; I like it. I haven’t seen breaking changes. I believe Dan when he says he has: I likely don’t encounter any because I use so few features of the product. Storage, SMB, 2 apps (one custom). My hardware is from 2018 and not changing. There is zero reason to touch it, unless it breaks.
I think a 6 month cadence straddles the divide well: Users who want to be conservative can be updating once a year. 24.10.2 to 25.10.2, that sort of thing. Users who like seeing new features have the option of following the releases more closely.
Some stuff can’t happen in an appliance. It will never be a “rolling release”. Yes that means NVidia drivers won’t be available the moment new hardware is.
I agree that it’s been a bit of a wild ride. From the outside it looks as if iX was trying for hyperconverged, got no traction with that, and gave up on the idea. First the tech to SCALE went (no more k3s, no ceph to replace glusterfs), then the name changed to CE to reflect that horizontal scale was off the table. I can’t fault them for trying for hyperconverged, and changing tack when they realized it was out of reach.
1 Like
Well I’d just like to thank everyone for their contributions on this thread. I personally have found it very insightful.
I think it’s fair to say if we didn’t already know that TrueNAS is used in a variety of different ways and with that comes a variety of different requirements.
As Steve Jobs famously said “You can please some of the people some of the time”.
Big thanks as always to the TrueNAS team.
1 Like
I think that many of the arguments previously made could be made regardless of what version I (or anyone else) currently use of TrueNAS. Would hate to see those get lost in the smokescreen of “just use version XXX.”
I guess my question would be how many issues have people had when upgrading? If the number is very low, then I do not see every 6 months as an issue. That said, I’m early on in this journey, I think I’ve only updated once, I think I’m still on 24.04 (mostly because I’m worried something will get hosed (thanks microsoft for instilling this paranoia into my brain))
Personally? None. Even the k3s to Docker migration went smoothly.
I think you’ve missed the boat now with app migrations, cut off was June 1st for those. If you use apps, prepare for some extra work since you’re still on 24.04.
It’d be reasonable to plan a move to 24.10.2 so you don’t get “stuck”.
While the software doesn’t keep you from jumping versions, the supported upgrade paths are to the next version. So let’s say you plan and plan and then eventually you want to get to 25.10.2. That’s three upgrades: 24.10.2, fix apps; 25.04.2, VMs gone but don’t act on it; 25.10.2, recreate VMs.
That’s one reason I’ve personally been doing the 6 month cadence: It feels a little easier to do one upgrade at a time, rather than do two or three in a row.
But if I had VMs in addition to apps, I’d be on 24.10.2 right now, wait for 25.10.2, then do two upgrades before recreating those VMs from their zvols.
The app migration cutoff was well advertised. As well as it could be: Forums, YouTube, Reddit - not much more that can be done. Hopefully you don’t use apps, and that’s why you felt comfortable staying on 24.04.
Just listened to TTT and have to roll back some of my comments. I didn’t understand the unofficial EOL policy. I thought it was “we deprecate old-old-stable when stable has reached dot two”, e.g. 25.04.2 means 24.04 no longer receives security updates.
But that’s not it. It’s “we deprecate old-stable when stable has reached dot two”, e.g. 25.04.2 means 24.10.2.2 no longer receives security updates.
That puts “VMs are now experimental” into a different light. It also means CE users that want security patches - and you should want them - will upgrade every 6 months.
There’s a teaser for alleviation of VM suffering, more detail next week.
There’s mention that a paid LTS CE could be a thing if enough people want it. So if you want it, can I suggest: Vote for Add an LTS CE subscription option, and leave a comment as to how much you’d pay.