- Joined
- Nov 25, 2013
- Messages
- 7,776
FreeBSD, Bastille, Ansible ... hey, even iocage exists and "just works" if you want to migrate your TrueNAS jails to stock FreeBSD. Migrating to more active and better architected Bastille can be done afterwards.
EuroBSDCon was in driving distance for a change and I missed it? Damn it.EuroBSDCon 2023 in Coimbra, Portugal.
It's the single most important conference for me and my professional life every year. This year in Dublin. Sláinte!EuroBSDCon was in driving distance for a change and I missed it? Damn it.
I would prefer Bastille to be honest. I really enjoy having ZFS and all the SMART checking, replication, monitoring, and so forth from the GUI. Stock FreeBSD would work, but there's a lot of manual work required to get things streamlined. SNMP server, SMART checking, etc...FreeBSD, Bastille, Ansible ... hey, even iocage exists and "just works" if you want to migrate your TrueNAS jails to stock FreeBSD. Migrating to more active and better architected Bastille can be done afterwards.
And they still have not answered the very fundamental question of how to address updates that involve complex config changes and manually invoked commands. Like Nextcloud.I've had too much grief with SCALE. It near impossible to set up something like Meshcentral and services that are "config-heavy" and require a config file to manage properly.
Sad, but fair. Thanks @Kris Moore.
I guess the trick will be finding a way to match the driver reliability for Intel/LSI cards under Linux that were reached in FreeBSD.
Thats fair. I'm sure we can look back and find ways to have improved communication around this.@Kris Moore that's absolutely fair, but I think what left us a bad taste in our mouths was the PR around it. And I also believe that the great success of SCALE was at least in part due to iX's commitment not to fix certain things in CORE; I'm not saying that's the main factor, but a concurrent one.
My lack of optimism about SCALE is due to how Linux works in general and its integration of ZFS.
Thanks, @Kris Moore. What's your idea for app life cycle management? This has been a sore point in CORE plugins for years and as I pointed out in now way rooted in the underlying technology stack. Users (rightfully IMHO) expect that if an app/plugin like Nextcloud exists and is touted as "official", after initial installation there will be timely and painless updates to it. Even more so in this particular case when the app's entire raison d'être is to be facing the public Internet.
The strongest argument for running TrueNAS over every other, possibly commercial, NAS platform is that is also an infinitely versatile application platform. I don't trust SCALE and this helm/k3s/containerd stack enough to use it for real world workloads, yet. Take snapshots, rollback, replication and restore. Dead simple with jails.
Kind regards,
Patrick
Please let that be LXC. That would bode well to win over some of the CORE users (such as myself) that are not looking forward to having to move away from jails if we want to stick with TrueNAS.We're taking steps to provide our Jail users alternatives in the upcoming Dragonfish BETA in a few weeks. Granted, its still early and not a fully supported UI feature, but its a first step that will allow you to use a technology you may be far more comfortable with for your use case
Its Open Source, so of course forks happen. But I would caution, its a HUGE commitment. Speaking from experience, all the resources required to maintain, build, release, troubleshoot, etc. Never mind any new feature work.. Its a very non-trivial project at this point. We're talking multiple people working as full time engineers and full-time support kind of commitment required, otherwise the quality would greatly suffer over the long run. If the reason is only to maintain its base on FreeBSD, I don't see the payoff personally. Even as much as I loved FreeBSD, that's not something I could do anymore for my own passion projects like PC-BSD or TrueOS (Both FreeBSD). I needed to have a life as well. But that's just my 2C on the situation :)What is your opinion on having someone create a fork and potentially keeping up the CORE line?
What about the FreeNAS name?
Is there a solution where both parties can end up getting what they desire, be it in a fork, or something similar?