TrueCommand 2.2 is now available

[eturgeon]

Greetings Community,

We are pleased to announce the release of TrueCommand 2.2. This release has many new Improvements, features, and bug fixes. See the Release Notes for more details.

Release Notes: https://www.truenas.com/docs/truecommand/tcreleasenotes/
Installation Instruction: https://www.truenas.com/docs/truecommand/tcgettingstarted/install/#install-options
Documentation: https://www.truenas.com/docs/truecommand/
Blog: https://www.truenas.com/blog/truecommand-2-2-makes-its-debut-enabling-clustering/

If you have suggestions for improvements to TrueCommand, please open up tickets on the TrueCommand Bug Tracker.

 

[NickF]

Hi All,

What is the use-case for this feature? I just watched the video and I am confused.

First, the default brick layout is tantamount to a Raid-0 or a ZFS stripe. The TrueNAS UI won't even let you make a pool with that layout without accepting that you understand the risks that it entails. Yet, for clustering, the default stance is one where if one system goes down, you will lose your data, with NO warning whatsoever. That should NOT be the default setting and there SHOULD BE a warning.

Second, if when you are mounting the share from the user perspective you have to pick one of the hosts, what benefit have we gotten? Even if we did pick a more sane Gluster brick layout, we don't have any high availability from the mount point perspective. So in essence, if you picked a replicated Gluster volume, even though your data is there, if one of the hosts went down you might not be able to access it. Without some sort of active-passive shared IP ala something like VRRP, this is basically a waste of time unless there is a benefit I am not seeing. Sure you can do static load balancing, but that's not exactly scalable.

 

[aervin]

Thanks for the questions and feedback @NickF . I'd just like to point out that the UI in the video is out of date in some respects. For example, the Distributed volume type is no longer an available option (for the reasons you rightly point out). Instead, the default selection is now the Dispersed type.

 

[Heracles]

Too bad that DNS redundancy is still not addressed... It is not only important for my environment but I consider it is of high important for enterprise class users... Hope TC-1812 / TC-2027 will be addressed sooner than later.