…but aside from iX’ ill-conceived endorsement of and partnership with Linus, as discussed in LTT DOES NOT fork TrueNAS, “TrueNAS for Dummies” is an intriguing idea, and I’m cautiously optimistic about it (though any involvement of Linus makes me less so). But why target it at the very niche market of YouTube content creators? This is an honest question–is there anything in HexOS that’s really unique to that application?
If there isn’t–and I really can’t imagine what would be unique to that application on a NAS, other than perhaps some of the apps–it seems unwise to suggest that HexOS has such a narrow application.
I highly encourage you to check out our blog post where we explain this in greater detail, but the short answer is that TrueNAS is always there. Our management lives at https://deck.hexos.com (our UI). At any point in time if you want to connect to the SCALE webUI, you can do so exactly as you can on a normal TrueNAS SCALE system.
And yes, if someone wants to use us as a “quick start” platform for TrueNAS SCALE and then switch to native SCALE UI for management after we get them going, they can. It’s on us to provide enough value in the solution to keep users wanting to use our solution past that point.
Wait, so to use HexOS on my own machine, I need to manage it through your servers? I realize I wasn’t your target market anyway, but I’d expect this to be a deal-breaker for pretty much everyone (if I wanted to depend on a cloud service, I could just put my data there).
If your Internet is down, HexoS system still works for SMB, Plex, etc. Its just standard TrueNAS operation. The data plane is unimpacted.
However, if your Internet is down, you cannot use the easy Hexos UI and add new Apps or disks. In an emergency, you can use the TrueNAS UI. So, the control plane is impacted, but has a backdoor. Its not really a negative.
Almost by definition, anyone on this thread is not a candidate for HexOS without a a major lapse of memory.
I thought you guys knew this networking stuff (you’re better than I am that’s for sure) but wouldn’t it just be like a relay server or UPnP thing? I would imagine their server just sends packets from their server to yours and your server just unpacks the packets and executes the contents (what protocol would that be?). I can imagine how I would write the thing, in my head, but I have no idea how you’d get the stuff back and forth (smarter people than I come up with the stuff). …If there are any engineers reading this, I am imagining a hybrid of the PVM model. Their server is the dispatcher sending task packets (packed with commands, and stuff …“NEWCOMMAND”, “DONE”, “TERMINATE”, etc.).
typedef enum ptype {NEWTASK, DATA, BROADCAST, DONE,
TERMINATE, BARRIER} packet_t;
typedef struct {
int compid;
int taskid;
packet_t type;
int length;
} taskpacket_t;
Charge for Enterprise HA, and charge subscriptions for Easy-Mode, but allow Free-For-All for everything in between.
And it seems to me that it may work… which is GOOD for TrueNAS as it provides an income stream to justify the development of all those neat non-enterprise features… you know… like docker compose support in the UI/middleware
In 2017 HP brought Nimble Storage for $1.09 billion primarily for its call home telemetry system allowing Nimble to monitor systems remotley, predict failures and more easily support customers. Essentially they knew about your problem before you did. HP quickly embedded this system into all their other storage products. The knowledge Nimble had built up over the years made this system very intelligent and very valuable. My guess is that this is how HexOS will work.
