Maybe I missed it but in regards to the TrueNAS Enterprise updates, they used to be a little behind the FreeNAS updates will this continue to be the case so we can find some of those edge case bugs before multi terabyte setup's run into them?TrueNAS CORE 12.0 will go through the same ALPHA, BETA, RC1, RELEASE states that FreeNAS has gone through. There will be no changes to the software update process or the information available. The process will be more efficient within iXsystems, and we expect to deliver our users more with the same resources we have today. TrueNAS CORE 12.0 is planned for release in Q3 2020, which will be a much shorter development cycle for a release of this magnitude, thanks to this change.
This will be landing in the next week or so, sit tight. UI needed some work to fully enable encrypted datasets.Anyone tried this yet? I just tried to create a new dataset and encryption is not working, is there a place where I can provide a key first rather than auto generation?
Error: Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 349, in run
File "/usr/local/lib/python3.7/site-packages/middlewared/job.py", line 386, in __run_body
rv = await self.method(*([self] + args))
File "/usr/local/lib/python3.7/site-packages/middlewared/schema.py", line 973, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/middlewared/plugins/pool.py", line 608, in do_create
middlewared.service_exception.ValidationErrors: [EINVAL] pool_create.encryption_options.key: Please provide a key or select generate_key to automatically generate a key when passphrase is not provided.
Correct. We're still working out some of the specific details as to the lag time between Core / Enterprise, but we still are planning on doing this. Mostly we've gotta settle on how the upgrade trains will be handled, since they can be installed from the same base ISO.Maybe I missed it but in regards to the TrueNAS Enterprise updates, they used to be a little behind the FreeNAS updates will this continue to be the case so we can find some of those edge case bugs before multi terabyte setup's run into them?
good to hear, makes me feel better. I was thinking about it too and the only easy way was to have Enterprise report to a different update server than core. I have no idea how feasible that is however.Correct. We're still working out some of the specific details as to the lag time between Core / Enterprise, but we still are planning on doing this. Mostly we've gotta settle on how the upgrade trains will be handled, since they can be installed from the same base ISO.
The latest nightlies (and soon ALPHA1) are based on openzfs/zfs master, with a few additional local commits to add some features that have not been merged yet upstream, etc. It may be too early to call openzfs/zfs master "OpenZFS 2.0" yet, but the FreeBSD support is not one of the local commits anymore. :)With the Alpha next week well now 2 days time, will it ship with OpenZFS 2.0? Or at least a version of it?
Also with current ZFS implementation once 12 comes out will it upgrade to OpenZFS 2.0 just fine?
I'm in the process of setting up FreeNAS so just wanna make sure I get it right.
From the blog:Paid-for support
"Supported platforms" really is key. When you look at the requests for help on this forum, a lot of it, but a lot, comes down to enterprising, not enterprise, hardware builds. *badum-bish* From Realtek NICs to RAID cards to consumer boards with non-ECC memory to running FreeNAS as a VM on virtual drives (Lord Ha' Mercy!), if it can halfway run FreeNAS, people will attempt it. And that's great, that spirit of tinkering is definitely part of FreeNAS! It'd kill paid support though.TrueNAS Enterprise will enable an extended feature set using a license key on supported platforms.
Paid per-incident support would basically make it worth doing outside of just operating system sales. Microsoft, for example, makes their bread on support tickets, not operating system sales. The price point for the OS is such as to get a token 'buy in' cost more or less to size their support.From the blog:
It'd kill paid support though.