Created
June 8, 2026 13:59
-
-
Save grahamperrin/9b831e5c84bd87027af017890f78a4ea to your computer and use it in GitHub Desktop.
Automated transcript of 'I Interviewed the CTO of TrueNAS (Why They Left FreeBSD for Linux)' on YouTube
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| { | |
| "title": "I Interviewed the CTO of TrueNAS (Why They Left FreeBSD for Linux) - YouTube", | |
| "url": "https://www.youtube.com/watch?v=xCtFeukJs-E", | |
| "sections": [ | |
| { | |
| "name": "", | |
| "lines": [ | |
| { | |
| "0:00": "What's up guys? I'm here with Chris who" | |
| }, | |
| { | |
| "0:02": "is the CTO of IX Systems. Chris, how" | |
| }, | |
| { | |
| "0:04": "long have you been with Systems?" | |
| }, | |
| { | |
| "0:06": "Gosh, almost 20 years this year. It's" | |
| }, | |
| { | |
| "0:08": "been a while. I think employee number 17" | |
| }, | |
| { | |
| "0:10": "in the record somewhere. It's It's been" | |
| }, | |
| { | |
| "0:11": "a journey." | |
| }, | |
| { | |
| "0:12": "That's awesome. Well, I've I've been" | |
| }, | |
| { | |
| "0:13": "using Freenaz since it was Freen. So," | |
| }, | |
| { | |
| "0:15": "it's what was it 11 years ago now?" | |
| }, | |
| { | |
| "0:17": "Cool. Yes." | |
| }, | |
| { | |
| "0:17": "That's awesome. It was like my first" | |
| }, | |
| { | |
| "0:18": "like true .naz operating system back" | |
| }, | |
| { | |
| "0:20": "when I was like learning like how to" | |
| }, | |
| { | |
| "0:22": "install an operating system, how to like" | |
| }, | |
| { | |
| "0:24": "work with servers." | |
| }, | |
| { | |
| "0:25": "Sure. And I ran that with over ice" | |
| }, | |
| { | |
| "0:27": "scuzzy to a VMware system back when" | |
| }, | |
| { | |
| "0:29": "before Broadcom ruined it. Um with" | |
| }, | |
| { | |
| "0:31": "VMware I had uh like most people just" | |
| }, | |
| { | |
| "0:33": "ran like Plex on their trun system. I" | |
| }, | |
| { | |
| "0:36": "wanted to make it complicated as an" | |
| }, | |
| { | |
| "0:37": "engineer. So I ran Plex on as a VM in" | |
| }, | |
| { | |
| "0:39": "YUbuntu on VMware and then I scuzzi do a" | |
| }, | |
| { | |
| "0:43": "storage target uh on my free." | |
| }, | |
| { | |
| "0:45": "You definitely had to overengineer it" | |
| }, | |
| { | |
| "0:46": "and do it that way." | |
| }, | |
| { | |
| "0:47": "I learned how not to design an" | |
| }, | |
| { | |
| "0:49": "architecture." | |
| }, | |
| { | |
| "0:49": "No, we've all been there but I have" | |
| }, | |
| { | |
| "0:50": "plenty of my own sins to speak of there" | |
| }, | |
| { | |
| "0:52": "too." | |
| }, | |
| { | |
| "0:53": "That was really awesome. So Trunz has" | |
| }, | |
| { | |
| "0:54": "really like changed a lot in the last" | |
| }, | |
| { | |
| "0:56": "couple years especially right so we we" | |
| }, | |
| { | |
| "0:58": "had that initial shift uh to this new" | |
| }, | |
| { | |
| "1:00": "idea of like we're going to have truness" | |
| }, | |
| { | |
| "1:01": "core so you know truness was on 3BSD" | |
| }, | |
| { | |
| "1:03": "historically was not on Linux and then" | |
| }, | |
| { | |
| "1:06": "we had tr scale and that was hey let's" | |
| }, | |
| { | |
| "1:08": "support Linux operating systems yes" | |
| }, | |
| { | |
| "1:10": "and then we have that decisions been" | |
| }, | |
| { | |
| "1:12": "made recently that we're actually going" | |
| }, | |
| { | |
| "1:13": "to move away from FreeBSD and focus on" | |
| }, | |
| { | |
| "1:16": "Linux" | |
| }, | |
| { | |
| "1:17": "why" | |
| }, | |
| { | |
| "1:17": "well we've gone first of all the core" | |
| }, | |
| { | |
| "1:19": "scale names have also been retired as" | |
| }, | |
| { | |
| "1:21": "part of that so it's community edition" | |
| }, | |
| { | |
| "1:22": "enterprise Community Edition is the" | |
| }, | |
| { | |
| "1:24": "successor to basically the scale" | |
| }, | |
| { | |
| "1:26": "platform, right? So what that means is" | |
| }, | |
| { | |
| "1:28": "it's a Linux base going forward. You" | |
| }, | |
| { | |
| "1:30": "asked the question why though? So it's" | |
| }, | |
| { | |
| "1:32": "been a long time coming. At the end of" | |
| }, | |
| { | |
| "1:33": "the day, we've had a lot of requests" | |
| }, | |
| { | |
| "1:35": "going back a decade plus now to run" | |
| }, | |
| { | |
| "1:37": "Linux native applications. That's" | |
| }, | |
| { | |
| "1:38": "honestly on the community side in" | |
| }, | |
| { | |
| "1:40": "particular been the number one thing" | |
| }, | |
| { | |
| "1:42": "people wanted to do on their Trnazbox" | |
| }, | |
| { | |
| "1:44": "was run Plex, run applications. I need" | |
| }, | |
| { | |
| "1:47": "to be able to do transcoding. I don't" | |
| }, | |
| { | |
| "1:48": "have support because the GPUs don't" | |
| }, | |
| { | |
| "1:49": "work. remember jails" | |
| }, | |
| { | |
| "1:51": "and they were not they were not fun." | |
| }, | |
| { | |
| "1:52": "They were not fun. Everyone's saying why" | |
| }, | |
| { | |
| "1:54": "can't I just have Docker? I want Docker" | |
| }, | |
| { | |
| "1:56": "Docker Docker. Everybody has a Linux" | |
| }, | |
| { | |
| "1:57": "container for every app under the sun." | |
| }, | |
| { | |
| "2:00": "But on FreeBSD it's kind of like ah they" | |
| }, | |
| { | |
| "2:02": "kind of work if a jail works all that" | |
| }, | |
| { | |
| "2:03": "kind of stuff. But then we were also" | |
| }, | |
| { | |
| "2:05": "seeing the trends on the enterprise" | |
| }, | |
| { | |
| "2:06": "side. The enterprise hardware drivers" | |
| }, | |
| { | |
| "2:08": "vendors were all providing top tier" | |
| }, | |
| { | |
| "2:10": "Linux support and drivers. And for BSD," | |
| }, | |
| { | |
| "2:13": "it was always a, you know, choose your" | |
| }, | |
| { | |
| "2:14": "own adventure and find the driver that" | |
| }, | |
| { | |
| "2:16": "kind of works and is supported maybe" | |
| }, | |
| { | |
| "2:18": "upstream by the vendor, maybe not. And" | |
| }, | |
| { | |
| "2:20": "it's just at the end of the day, it was" | |
| }, | |
| { | |
| "2:22": "one of those things people saw coming." | |
| }, | |
| { | |
| "2:24": "It just took some time for it." | |
| }, | |
| { | |
| "2:26": "ZFS was not as mature on Linux as" | |
| }, | |
| { | |
| "2:28": "though. So, one thing that's cool about" | |
| }, | |
| { | |
| "2:29": "this is you guys have matured that cuz" | |
| }, | |
| { | |
| "2:31": "you contribute to ZFS." | |
| }, | |
| { | |
| "2:33": "Yeah. Let me talk through the history of" | |
| }, | |
| { | |
| "2:34": "that. So, FreeBS, of course, ZFS came" | |
| }, | |
| { | |
| "2:36": "out of the Sundays and eventually got" | |
| }, | |
| { | |
| "2:38": "ported over to FreeBSD. Awesome. That" | |
| }, | |
| { | |
| "2:41": "was where it became really popular and" | |
| }, | |
| { | |
| "2:42": "stable and what made Freenaz what it" | |
| }, | |
| { | |
| "2:44": "was. And then when we decided to move to" | |
| }, | |
| { | |
| "2:46": "Linux, we took it upon ourselves to say," | |
| }, | |
| { | |
| "2:47": "\"Hey, there's this ZFS on Linux kind of" | |
| }, | |
| { | |
| "2:49": "side project that had forked off.\" We" | |
| }, | |
| { | |
| "2:52": "spent quite a bit of time, year or two," | |
| }, | |
| { | |
| "2:53": "unifying them back together. So instead" | |
| }, | |
| { | |
| "2:56": "of having a different FreeBSD and Linux" | |
| }, | |
| { | |
| "2:58": "version, they're now one common code" | |
| }, | |
| { | |
| "2:59": "base that runs on both. Meaning, of" | |
| }, | |
| { | |
| "3:02": "course, the advantage to our users and" | |
| }, | |
| { | |
| "3:03": "customers was you could migrate between" | |
| }, | |
| { | |
| "3:05": "the platforms. So you could be on a" | |
| }, | |
| { | |
| "3:07": "FreeBSD based uh trunaz 13 and then" | |
| }, | |
| { | |
| "3:10": "bring it over to trunz scale or now" | |
| }, | |
| { | |
| "3:12": "community edition same pool same" | |
| }, | |
| { | |
| "3:14": "features same code base very seamless" | |
| }, | |
| { | |
| "3:16": "that was very critical for us to get" | |
| }, | |
| { | |
| "3:18": "done right plus it's just nice to work" | |
| }, | |
| { | |
| "3:19": "out of one common unified code base as" | |
| }, | |
| { | |
| "3:21": "opposed to being like oh I got to go" | |
| }, | |
| { | |
| "3:23": "take care of the fork version now and" | |
| }, | |
| { | |
| "3:24": "it's drifting and we saw what was" | |
| }, | |
| { | |
| "3:26": "happening was ZFS on Linux was rapidly" | |
| }, | |
| { | |
| "3:29": "outpacing the FreeBSD version really" | |
| }, | |
| { | |
| "3:31": "they got features like encryption" | |
| }, | |
| { | |
| "3:33": "natively first they started stacking" | |
| }, | |
| { | |
| "3:34": "features which were not getting" | |
| }, | |
| { | |
| "3:36": "backported to the free BSD version. So," | |
| }, | |
| { | |
| "3:38": "one of the last things we wanted to do" | |
| }, | |
| { | |
| "3:40": "was kind of get those two in lock step" | |
| }, | |
| { | |
| "3:41": "so free BSD didn't get left behind. And" | |
| }, | |
| { | |
| "3:44": "something a lot of people don't" | |
| }, | |
| { | |
| "3:45": "understand about running a tech company" | |
| }, | |
| { | |
| "3:46": "is focus is tremendously important." | |
| }, | |
| { | |
| "3:49": "Oh yeah." | |
| }, | |
| { | |
| "3:49": "Right. So if you want to focus on like" | |
| }, | |
| { | |
| "3:51": "yes, you have millions of dollars of" | |
| }, | |
| { | |
| "3:53": "resources, but you're still limited. You" | |
| }, | |
| { | |
| "3:54": "still have so only so many engineers." | |
| }, | |
| { | |
| "3:55": "You still only have so much brain power" | |
| }, | |
| { | |
| "3:57": "that you can put on a product. So like" | |
| }, | |
| { | |
| "3:59": "it's a question of do we continue to" | |
| }, | |
| { | |
| "4:01": "accelerate Linux or do we stay splitrain" | |
| }, | |
| { | |
| "4:03": "and focus on a platform that is not" | |
| }, | |
| { | |
| "4:05": "ideal. Well, and if I could be" | |
| }, | |
| { | |
| "4:06": "completely transparent, that was the" | |
| }, | |
| { | |
| "4:08": "calculus we had to make, too, is I only" | |
| }, | |
| { | |
| "4:09": "have x number of developers who have x" | |
| }, | |
| { | |
| "4:11": "number of hours in any number of weeks," | |
| }, | |
| { | |
| "4:13": "right? Do I spend that time going and" | |
| }, | |
| { | |
| "4:15": "fixing things on FreeBSD, which just" | |
| }, | |
| { | |
| "4:17": "inherently natively work on Linux? Yeah." | |
| }, | |
| { | |
| "4:20": "And you kind of get for free, which" | |
| }, | |
| { | |
| "4:21": "means I can then go spend time on things" | |
| }, | |
| { | |
| "4:23": "that add value to TRNA as a storage" | |
| }, | |
| { | |
| "4:25": "appliance, things that and features" | |
| }, | |
| { | |
| "4:27": "people actually want versus I'm just" | |
| }, | |
| { | |
| "4:29": "playing catch-up perpetually to things" | |
| }, | |
| { | |
| "4:31": "that are available natively in the Linux" | |
| }, | |
| { | |
| "4:32": "ecosystem. It's cool to see like on" | |
| }, | |
| { | |
| "4:34": "Linux we're still having innovations," | |
| }, | |
| { | |
| "4:35": "right? Even on the server side with ZFS" | |
| }, | |
| { | |
| "4:37": "and you're seeing more even on the" | |
| }, | |
| { | |
| "4:38": "desktop side like Linux is about to" | |
| }, | |
| { | |
| "4:40": "explode already." | |
| }, | |
| { | |
| "4:41": "Oh, it is. I mean, we've seen this is" | |
| }, | |
| { | |
| "4:43": "the year of the Steam Deck and Steam OS" | |
| }, | |
| { | |
| "4:45": "and Linux gaining gaming market share" | |
| }, | |
| { | |
| "4:46": "and all that good stuff. And also with" | |
| }, | |
| { | |
| "4:48": "AI, that's something you can do natively" | |
| }, | |
| { | |
| "4:50": "on Linux, you know, with running O Lama" | |
| }, | |
| { | |
| "4:52": "and VMs. And because of that, you can do" | |
| }, | |
| { | |
| "4:54": "it on True Now, too, which we have a lot" | |
| }, | |
| { | |
| "4:55": "of people taking advantage of." | |
| }, | |
| { | |
| "4:56": "Why do you think it is that like no one" | |
| }, | |
| { | |
| "4:58": "else has caught up to the amazingness" | |
| }, | |
| { | |
| "4:59": "that is ZFS? Like obviously Butterfest" | |
| }, | |
| { | |
| "5:01": "has been out for a number of years." | |
| }, | |
| { | |
| "5:02": "Sure," | |
| }, | |
| { | |
| "5:03": "there's other competing file systems" | |
| }, | |
| { | |
| "5:04": "coming up now. Why is it that just" | |
| }, | |
| { | |
| "5:07": "nothing holds a candle to ZFS right now?" | |
| }, | |
| { | |
| "5:10": "Because it's just got that enterprise" | |
| }, | |
| { | |
| "5:11": "pedigree. The people who built it, I" | |
| }, | |
| { | |
| "5:13": "mean, they spent a decade hardening it," | |
| }, | |
| { | |
| "5:15": "building it, designing it from day one" | |
| }, | |
| { | |
| "5:17": "to be a file system, which I love this." | |
| }, | |
| { | |
| "5:19": "They just don't trust your hardware." | |
| }, | |
| { | |
| "5:21": "They said, the guys who originally wrote" | |
| }, | |
| { | |
| "5:22": "it said, \"We assume your hardware is out" | |
| }, | |
| { | |
| "5:24": "to screw you over.\"" | |
| }, | |
| { | |
| "5:25": "I could design" | |
| }, | |
| { | |
| "5:26": "one of the NAS that I built was for my" | |
| }, | |
| { | |
| "5:28": "church. We built uh we actually out of" | |
| }, | |
| { | |
| "5:30": "an USA chassis. Uh we officially do not" | |
| }, | |
| { | |
| "5:33": "recommend USA. Their back plans are" | |
| }, | |
| { | |
| "5:35": "awful. And we constantly had drives" | |
| }, | |
| { | |
| "5:37": "disconnecting and reconnecting. And ZFS" | |
| }, | |
| { | |
| "5:39": "handled it very well. Like like we" | |
| }, | |
| { | |
| "5:42": "actually had I think we were running" | |
| }, | |
| { | |
| "5:43": "like Raid Z2 and we had at times like" | |
| }, | |
| { | |
| "5:46": "two drives disconnect and reconnect and" | |
| }, | |
| { | |
| "5:47": "somehow the array was very grumpy but it" | |
| }, | |
| { | |
| "5:50": "didn't get corrupted" | |
| }, | |
| { | |
| "5:52": "until we lost three drives. But then" | |
| }, | |
| { | |
| "5:53": "then you know we were off at that point." | |
| }, | |
| { | |
| "5:55": "We moved over to uh some used Dell" | |
| }, | |
| { | |
| "5:58": "hardware and that was rock solid. Power" | |
| }, | |
| { | |
| "6:01": "failures, drive fail, didn't care. It" | |
| }, | |
| { | |
| "6:03": "was it was incredibly successful." | |
| }, | |
| { | |
| "6:05": "At the end of the day, ZFS is just its" | |
| }, | |
| { | |
| "6:07": "entire mission is to make sure no data" | |
| }, | |
| { | |
| "6:09": "gets corrupted. And it does that and" | |
| }, | |
| { | |
| "6:10": "does that well. Yes. And then of course" | |
| }, | |
| { | |
| "6:12": "with that as a base, then we can go" | |
| }, | |
| { | |
| "6:14": "stack features and functionality on top" | |
| }, | |
| { | |
| "6:16": "as long as that core promise is kept" | |
| }, | |
| { | |
| "6:18": "intact." | |
| }, | |
| { | |
| "6:18": "That's huge. So talking about the" | |
| }, | |
| { | |
| "6:19": "community edition of Trunaz versus the" | |
| }, | |
| { | |
| "6:22": "enterprise edition. So like what are you" | |
| }, | |
| { | |
| "6:25": "do you get keep certain features? What" | |
| }, | |
| { | |
| "6:26": "does that look like?" | |
| }, | |
| { | |
| "6:27": "So of course every company has to pay" | |
| }, | |
| { | |
| "6:29": "the bills somehow, right? And we provide" | |
| }, | |
| { | |
| "6:31": "this awesome amazing free product" | |
| }, | |
| { | |
| "6:32": "because we do have an enterprise edition" | |
| }, | |
| { | |
| "6:34": "and that's what basically allows us to" | |
| }, | |
| { | |
| "6:36": "fund and go do new innovations in NRA" | |
| }, | |
| { | |
| "6:38": "and keep paying the engineers that make" | |
| }, | |
| { | |
| "6:40": "this happen. But uh yeah, of course" | |
| }, | |
| { | |
| "6:42": "every time we I've talked about this on" | |
| }, | |
| { | |
| "6:44": "our podcast in the T3 podcast where we" | |
| }, | |
| { | |
| "6:47": "have to go through a feature evaluation." | |
| }, | |
| { | |
| "6:48": "Every time we say we're about to go" | |
| }, | |
| { | |
| "6:50": "embark on a feature we want to add to" | |
| }, | |
| { | |
| "6:51": "True, we have to look at the cost of" | |
| }, | |
| { | |
| "6:53": "developing that feature and then there's" | |
| }, | |
| { | |
| "6:55": "a cost of maintaining it potentially" | |
| }, | |
| { | |
| "6:56": "forever right through the entire" | |
| }, | |
| { | |
| "6:58": "lifespan of the product and where does" | |
| }, | |
| { | |
| "7:00": "that sit? Does it is it an enterprise" | |
| }, | |
| { | |
| "7:02": "kind of only feature? Would anybody in" | |
| }, | |
| { | |
| "7:03": "the home lab even use it? And so we go" | |
| }, | |
| { | |
| "7:05": "through all that calculus and decide" | |
| }, | |
| { | |
| "7:07": "which side of the product does it land" | |
| }, | |
| { | |
| "7:08": "on and honestly a lot of them do land on" | |
| }, | |
| { | |
| "7:11": "the community side because it makes" | |
| }, | |
| { | |
| "7:12": "sense. We want the community to use it." | |
| }, | |
| { | |
| "7:13": "our one of our pillars at Trernaz is to" | |
| }, | |
| { | |
| "7:15": "grow our community and so we're going to" | |
| }, | |
| { | |
| "7:17": "keep adding more awesomeness but at the" | |
| }, | |
| { | |
| "7:19": "same time we also want to expand as a" | |
| }, | |
| { | |
| "7:21": "business and be able to expand who we" | |
| }, | |
| { | |
| "7:24": "can hire how we can grow which allows us" | |
| }, | |
| { | |
| "7:26": "to go do the next evolution of True down" | |
| }, | |
| { | |
| "7:28": "the road. So again, it's it's a" | |
| }, | |
| { | |
| "7:30": "complicated formula to go run through" | |
| }, | |
| { | |
| "7:31": "and it's the where we have the arguments" | |
| }, | |
| { | |
| "7:33": "internally about which features go" | |
| }, | |
| { | |
| "7:35": "where, but it's a healthy thing to have" | |
| }, | |
| { | |
| "7:36": "in any open source company which is" | |
| }, | |
| { | |
| "7:39": "doing both an open premium model which" | |
| }, | |
| { | |
| "7:41": "also has an enterprise product." | |
| }, | |
| { | |
| "7:42": "And I know you guys I've seen trunaz" | |
| }, | |
| { | |
| "7:45": "non-enterprise and a lot of enterprise" | |
| }, | |
| { | |
| "7:46": "environments. It's very like what what" | |
| }, | |
| { | |
| "7:48": "are the features where someone needs to" | |
| }, | |
| { | |
| "7:49": "upgrade and step into that enterprise" | |
| }, | |
| { | |
| "7:51": "version?" | |
| }, | |
| { | |
| "7:51": "So if you're here, you're looking at the" | |
| }, | |
| { | |
| "7:52": "show today. We have our hardware on the" | |
| }, | |
| { | |
| "7:54": "floor. All that hardware is uh HA" | |
| }, | |
| { | |
| "7:56": "enabled that we're displaying here" | |
| }, | |
| { | |
| "7:57": "today. That's obviously an enterprise" | |
| }, | |
| { | |
| "7:59": "feature. There's a direct hardware" | |
| }, | |
| { | |
| "8:00": "component, but then you start adding" | |
| }, | |
| { | |
| "8:02": "other features like proactive support," | |
| }, | |
| { | |
| "8:04": "which is being able to reach home to the" | |
| }, | |
| { | |
| "8:05": "trun support team when there's an issue" | |
| }, | |
| { | |
| "8:07": "on the box, fiber channel. Um, we're" | |
| }, | |
| { | |
| "8:10": "doing some more things with ddupability." | |
| }, | |
| { | |
| "8:12": "We're doing some things with taring now" | |
| }, | |
| { | |
| "8:13": "in the new version of Trunaz for tiering" | |
| }, | |
| { | |
| "8:15": "between flash and uh spinning disc. So," | |
| }, | |
| { | |
| "8:18": "yeah, those are some of kind of the key" | |
| }, | |
| { | |
| "8:19": "ones you'll get out of box when you go" | |
| }, | |
| { | |
| "8:21": "to the enterprise solution for sure." | |
| }, | |
| { | |
| "8:22": "Very cool. So, that's about getting" | |
| }, | |
| { | |
| "8:23": "those extra cuz EFS and Trunz is already" | |
| }, | |
| { | |
| "8:25": "so stable. That's getting your extra" | |
| }, | |
| { | |
| "8:27": "nines. Yeah. Right. When you just like" | |
| }, | |
| { | |
| "8:29": "it can't go down. Absolutely. So, I was" | |
| }, | |
| { | |
| "8:31": "talking to your team yesterday about" | |
| }, | |
| { | |
| "8:32": "some of the hardware you guys are are" | |
| }, | |
| { | |
| "8:33": "showcasing. And how you do high" | |
| }, | |
| { | |
| "8:35": "availability is very different than some" | |
| }, | |
| { | |
| "8:36": "other vendors." | |
| }, | |
| { | |
| "8:37": "So, like a lot of guys will those stack" | |
| }, | |
| { | |
| "8:39": "hardware like those have more chassis." | |
| }, | |
| { | |
| "8:41": "That's that's a good solution. It's very" | |
| }, | |
| { | |
| "8:42": "easy to scale that, right? You don't" | |
| }, | |
| { | |
| "8:43": "have to have a final config in mind. You" | |
| }, | |
| { | |
| "8:46": "guys do that in the same box. What are" | |
| }, | |
| { | |
| "8:47": "some of the benefits and reasons why" | |
| }, | |
| { | |
| "8:49": "someone may want to look at doing that" | |
| }, | |
| { | |
| "8:50": "high availability with compute modules" | |
| }, | |
| { | |
| "8:53": "in the same box?" | |
| }, | |
| { | |
| "8:54": "In the same box. So at the end of the" | |
| }, | |
| { | |
| "8:55": "day it's about performance and" | |
| }, | |
| { | |
| "8:57": "reliability in the same box. It's not" | |
| }, | |
| { | |
| "8:59": "that we're scaling out over the network." | |
| }, | |
| { | |
| "9:00": "There's no extra network round trips as" | |
| }, | |
| { | |
| "9:02": "packets have to move around to make sure" | |
| }, | |
| { | |
| "9:04": "you have redundancy across multiple" | |
| }, | |
| { | |
| "9:06": "systems. Right? Same box means we can" | |
| }, | |
| { | |
| "9:08": "have an active passive architecture" | |
| }, | |
| { | |
| "9:10": "where both systems are capable of taking" | |
| }, | |
| { | |
| "9:12": "over at any moment and becoming the" | |
| }, | |
| { | |
| "9:13": "active node. Right?" | |
| }, | |
| { | |
| "9:14": "So there's a difference in latency. A" | |
| }, | |
| { | |
| "9:16": "difference in latency." | |
| }, | |
| { | |
| "9:16": "What is like what's the use case where" | |
| }, | |
| { | |
| "9:18": "someone would be okay with you know" | |
| }, | |
| { | |
| "9:19": "separate boxes doing replication?" | |
| }, | |
| { | |
| "9:22": "Yeah. that would be like your more file" | |
| }, | |
| { | |
| "9:24": "based workloads where you can take the" | |
| }, | |
| { | |
| "9:25": "latency hits. But if you're doing" | |
| }, | |
| { | |
| "9:26": "virtualization like you mentioned VMware" | |
| }, | |
| { | |
| "9:28": "at one point, you can't afford a latency" | |
| }, | |
| { | |
| "9:30": "hit. You need all those IOPS all the" | |
| }, | |
| { | |
| "9:32": "time. And so you would go and use a" | |
| }, | |
| { | |
| "9:34": "solution like this where the number of" | |
| }, | |
| { | |
| "9:36": "hops is minimized from network to" | |
| }, | |
| { | |
| "9:38": "hitting the board to hitting the discs" | |
| }, | |
| { | |
| "9:39": "and back. So, if I have a VM cluster," | |
| }, | |
| { | |
| "9:41": "right, and I'm I'm doing like uh" | |
| }, | |
| { | |
| "9:43": "real-time transactions, right?" | |
| }, | |
| { | |
| "9:44": "Transactions for my my multi-sight" | |
| }, | |
| { | |
| "9:46": "retail organization" | |
| }, | |
| { | |
| "9:47": "that, you know, a couple seconds of" | |
| }, | |
| { | |
| "9:49": "drop, right, as we're filling nodes" | |
| }, | |
| { | |
| "9:51": "might mean the difference between tens" | |
| }, | |
| { | |
| "9:53": "of thousands in revenue because we" | |
| }, | |
| { | |
| "9:54": "didn't those transactions didn't go" | |
| }, | |
| { | |
| "9:56": "through." | |
| }, | |
| { | |
| "9:56": "So, what'll happen is on our boxes, you" | |
| }, | |
| { | |
| "9:58": "won't see it as a drop. It's a pause," | |
| }, | |
| { | |
| "9:59": "but then it immediately resumes and go." | |
| }, | |
| { | |
| "10:01": "We're talking about milliseconds. Yes." | |
| }, | |
| { | |
| "10:03": "What's like what is that failover time" | |
| }, | |
| { | |
| "10:04": "right now?" | |
| }, | |
| { | |
| "10:05": "So, it'll be under 10 seconds usually." | |
| }, | |
| { | |
| "10:06": "And again, this is where you tune your" | |
| }, | |
| { | |
| "10:08": "VMware cluster. So it knows, hey, I'm" | |
| }, | |
| { | |
| "10:10": "going to ques and hold n cache until the" | |
| }, | |
| { | |
| "10:12": "other side comes back." | |
| }, | |
| { | |
| "10:13": "So it's not just man, it's not just" | |
| }, | |
| { | |
| "10:14": "having the redundancy. It's how you" | |
| }, | |
| { | |
| "10:16": "manage that failure." | |
| }, | |
| { | |
| "10:16": "It's how you manage the failure." | |
| }, | |
| { | |
| "10:17": "Correct. That's very cool." | |
| }, | |
| { | |
| "10:18": "So for example, one of the features we" | |
| }, | |
| { | |
| "10:20": "added recently is SMB for example has" | |
| }, | |
| { | |
| "10:22": "now transparent failover. So if you're" | |
| }, | |
| { | |
| "10:24": "in the middle of copying large media" | |
| }, | |
| { | |
| "10:26": "files, for example," | |
| }, | |
| { | |
| "10:27": "that's very cool." | |
| }, | |
| { | |
| "10:28": "And say you do that when you're moving" | |
| }, | |
| { | |
| "10:31": "your terabytes of B-roll and 90% done it" | |
| }, | |
| { | |
| "10:34": "just" | |
| }, | |
| { | |
| "10:34": "90% done it fails. So what you'll see" | |
| }, | |
| { | |
| "10:36": "now is instead it'll pause and then" | |
| }, | |
| { | |
| "10:38": "resume." | |
| }, | |
| { | |
| "10:39": "Very cool." | |
| }, | |
| { | |
| "10:39": "So okay fail over Windows, Mac, all that" | |
| }, | |
| { | |
| "10:42": "good stuff. Yes. Yes. NFSV4 already" | |
| }, | |
| { | |
| "10:45": "natively supports that as well. So" | |
| }, | |
| { | |
| "10:47": "you've had that for a while in case you" | |
| }, | |
| { | |
| "10:48": "didn't know. But yeah, there's some" | |
| }, | |
| { | |
| "10:50": "great functionality and of course we've" | |
| }, | |
| { | |
| "10:51": "done that on ice scuzzi for a long time." | |
| }, | |
| { | |
| "10:52": "So talking about these these enterprise" | |
| }, | |
| { | |
| "10:54": "customers cuz you guys are viewed as" | |
| }, | |
| { | |
| "10:55": "kind of the like really involved in the" | |
| }, | |
| { | |
| "10:58": "community obviously, but you are in the" | |
| }, | |
| { | |
| "10:59": "enterprise. You're in some big places. I" | |
| }, | |
| { | |
| "11:01": "know we're here in" | |
| }, | |
| { | |
| "11:03": "So I know we're here in Las Vegas." | |
| }, | |
| { | |
| "11:04": "You're in the sphere, right? You're in a" | |
| }, | |
| { | |
| "11:05": "lot of media. Tell me about you're with" | |
| }, | |
| { | |
| "11:07": "NASA. They use you guys for pulling" | |
| }, | |
| { | |
| "11:08": "imagery from satellites. That's a lot of" | |
| }, | |
| { | |
| "11:10": "data, right? A lot of data as well." | |
| }, | |
| { | |
| "11:12": "So, what other players you guys work" | |
| }, | |
| { | |
| "11:13": "with?" | |
| }, | |
| { | |
| "11:13": "Well, I'll mention one since we're" | |
| }, | |
| { | |
| "11:14": "talking media and entertainment here at" | |
| }, | |
| { | |
| "11:16": "NAB, but maybe you've heard of the NBA" | |
| }, | |
| { | |
| "11:18": "on Amazon Prime on Friday nights. Well," | |
| }, | |
| { | |
| "11:20": "we have a little system around the" | |
| }, | |
| { | |
| "11:21": "corner here, which is our F-S series" | |
| }, | |
| { | |
| "11:23": "flagship, and that's what's streaming" | |
| }, | |
| { | |
| "11:24": "those box that content on Friday nights," | |
| }, | |
| { | |
| "11:27": "which is awesome. Super cool. Again," | |
| }, | |
| { | |
| "11:28": "really neat high high-end use case, but" | |
| }, | |
| { | |
| "11:31": "all done on a truness using the same" | |
| }, | |
| { | |
| "11:33": "software that you would use at the" | |
| }, | |
| { | |
| "11:34": "community edition to show you kind of" | |
| }, | |
| { | |
| "11:36": "the enterprise level of software we're" | |
| }, | |
| { | |
| "11:38": "giving away to the community" | |
| }, | |
| { | |
| "11:39": "and which is amazing because here's" | |
| }, | |
| { | |
| "11:41": "what's cool about that. It's a genius" | |
| }, | |
| { | |
| "11:42": "marketing play, right? because you're" | |
| }, | |
| { | |
| "11:44": "actually getting the next generation of" | |
| }, | |
| { | |
| "11:46": "professionals already familiar with your" | |
| }, | |
| { | |
| "11:48": "platform and I know of examples where" | |
| }, | |
| { | |
| "11:50": "you guys have been used even in critical" | |
| }, | |
| { | |
| "11:51": "infrastructure where the people that are" | |
| }, | |
| { | |
| "11:53": "running that critical infrastructure had" | |
| }, | |
| { | |
| "11:54": "home lab and they put trunaz or freenaz" | |
| }, | |
| { | |
| "11:58": "on very bad hardware and it worked and" | |
| }, | |
| { | |
| "12:01": "it worked and so clearly it's going to" | |
| }, | |
| { | |
| "12:02": "work with your hardware" | |
| }, | |
| { | |
| "12:03": "and then it gave them confidence well if" | |
| }, | |
| { | |
| "12:05": "it runs on this piece of garbage I just" | |
| }, | |
| { | |
| "12:06": "cobbled together surely on a" | |
| }, | |
| { | |
| "12:08": "purpose-built tested validated supported" | |
| }, | |
| { | |
| "12:11": "box it'll be amazing and yes that's" | |
| }, | |
| { | |
| "12:12": "Sure. So, no, that's why again if you're" | |
| }, | |
| { | |
| "12:15": "a community user, you should rest" | |
| }, | |
| { | |
| "12:16": "assured like we're in it for the long" | |
| }, | |
| { | |
| "12:17": "haul with the community. We love our" | |
| }, | |
| { | |
| "12:19": "community because that's our number one" | |
| }, | |
| { | |
| "12:21": "marketing vehicle. It's how we get the" | |
| }, | |
| { | |
| "12:22": "name True out there." | |
| }, | |
| { | |
| "12:23": "So, why would that's obviously one" | |
| }, | |
| { | |
| "12:25": "reason, but like for an enterprise," | |
| }, | |
| { | |
| "12:26": "maybe the CTOs or the, you know, the" | |
| }, | |
| { | |
| "12:28": "CEOs, the more finance people that are" | |
| }, | |
| { | |
| "12:29": "thinking they're not hands-on with the" | |
| }, | |
| { | |
| "12:31": "technology. Why would they choose TRNA" | |
| }, | |
| { | |
| "12:33": "over a NetApp or more traditional" | |
| }, | |
| { | |
| "12:35": "vendor?" | |
| }, | |
| { | |
| "12:35": "So, you're going to look at it and say," | |
| }, | |
| { | |
| "12:37": "well, does it have the features," | |
| }, | |
| { | |
| "12:38": "performance, stability, and support I" | |
| }, | |
| { | |
| "12:40": "need? And then those folks are going to" | |
| }, | |
| { | |
| "12:41": "look at the total cost of ownership and" | |
| }, | |
| { | |
| "12:43": "go, \"Wow, why am I renewing that NetApp" | |
| }, | |
| { | |
| "12:46": "license when I could have just gone and" | |
| }, | |
| { | |
| "12:47": "gotten a Traz and gotten better" | |
| }, | |
| { | |
| "12:49": "performance for less cost. The support" | |
| }, | |
| { | |
| "12:51": "team's amazing.\" That's what's happening" | |
| }, | |
| { | |
| "12:53": "in the background is people are doing" | |
| }, | |
| { | |
| "12:54": "the calculus and saying, \"Oh, my IT" | |
| }, | |
| { | |
| "12:56": "staff's been raising it, you know," | |
| }, | |
| { | |
| "12:58": "raving about this Trunaz product for" | |
| }, | |
| { | |
| "12:59": "years.\" And when I finally go look at" | |
| }, | |
| { | |
| "13:01": "the economics of it, it's like, why am I" | |
| }, | |
| { | |
| "13:03": "throwing money away over here on" | |
| }, | |
| { | |
| "13:05": "something that does exactly the same" | |
| }, | |
| { | |
| "13:06": "thing?" | |
| }, | |
| { | |
| "13:06": "And what's the licensing model on the" | |
| }, | |
| { | |
| "13:08": "enterprise side? So it's all all" | |
| }, | |
| { | |
| "13:09": "inclusive. So you're not being nickel" | |
| }, | |
| { | |
| "13:11": "and dime. You own the hardware. You're" | |
| }, | |
| { | |
| "13:13": "not being nickeled and dime for the" | |
| }, | |
| { | |
| "13:14": "features, any of that." | |
| }, | |
| { | |
| "13:15": "So" | |
| }, | |
| { | |
| "13:16": "So that's incredibly uncommon like in in" | |
| }, | |
| { | |
| "13:18": "this industry, right? Especially in" | |
| }, | |
| { | |
| "13:19": "computing and storage. So like for those" | |
| }, | |
| { | |
| "13:21": "of you guys in the community that have" | |
| }, | |
| { | |
| "13:22": "maybe have built tras at home, you look" | |
| }, | |
| { | |
| "13:23": "at the you know the true like desktop," | |
| }, | |
| { | |
| "13:25": "what's that desktop enclosure like the" | |
| }, | |
| { | |
| "13:27": "little" | |
| }, | |
| { | |
| "13:27": "the mini" | |
| }, | |
| { | |
| "13:27": "the mini you're like this doesn't make" | |
| }, | |
| { | |
| "13:29": "any sense. And for us it doesn't. If" | |
| }, | |
| { | |
| "13:31": "you're an enthusiast, you're going to" | |
| }, | |
| { | |
| "13:32": "build your own hardware. You're going to" | |
| }, | |
| { | |
| "13:33": "buy some used DELMC hardware and build" | |
| }, | |
| { | |
| "13:35": "an AS in it. You're that's great. But" | |
| }, | |
| { | |
| "13:37": "for the enterprise where they need that" | |
| }, | |
| { | |
| "13:39": "support, they need the reliability. This" | |
| }, | |
| { | |
| "13:40": "is a I don't want to call it budget" | |
| }, | |
| { | |
| "13:42": "because it's not it's not that it's" | |
| }, | |
| { | |
| "13:44": "great hardware, but it is very cost" | |
| }, | |
| { | |
| "13:46": "effective, very low cost compared to" | |
| }, | |
| { | |
| "13:48": "traditional providers like a NetApp, um" | |
| }, | |
| { | |
| "13:50": "like Adelli." | |
| }, | |
| { | |
| "13:51": "Well, and we go to the extra enterprise" | |
| }, | |
| { | |
| "13:52": "mile too because folks don't realize how" | |
| }, | |
| { | |
| "13:54": "much work goes into producing an actual" | |
| }, | |
| { | |
| "13:56": "physical appliance box down to testing" | |
| }, | |
| { | |
| "13:58": "and working with vendors on their" | |
| }, | |
| { | |
| "14:00": "firmware versions down to the hard" | |
| }, | |
| { | |
| "14:01": "drives. you wouldn't believe the number" | |
| }, | |
| { | |
| "14:03": "of bugs and things you find in the" | |
| }, | |
| { | |
| "14:05": "firmware level that have to go be" | |
| }, | |
| { | |
| "14:06": "corrected. So you can say it's a truly" | |
| }, | |
| { | |
| "14:08": "enterprise hardened product. But that's" | |
| }, | |
| { | |
| "14:10": "all the work we do." | |
| }, | |
| { | |
| "14:11": "If you've ever built like we're learning" | |
| }, | |
| { | |
| "14:12": "this recently, so we're network" | |
| }, | |
| { | |
| "14:14": "engineers, right? We haven't built a" | |
| }, | |
| { | |
| "14:15": "server in a couple years. We're like," | |
| }, | |
| { | |
| "14:16": "\"Yeah, we're going to build a new server" | |
| }, | |
| { | |
| "14:17": "in our Hel 15.\" We had our board give up" | |
| }, | |
| { | |
| "14:18": "the ghost mid build. You guys are going" | |
| }, | |
| { | |
| "14:20": "to see that video here soon. And so just" | |
| }, | |
| { | |
| "14:22": "the there's a value in not just building" | |
| }, | |
| { | |
| "14:23": "hardware, but building hardware, testing" | |
| }, | |
| { | |
| "14:25": "it, validating because when you go" | |
| }, | |
| { | |
| "14:26": "build, you know, several thousand of" | |
| }, | |
| { | |
| "14:28": "those servers and ship them, you know, a" | |
| }, | |
| { | |
| "14:29": "one in a thousand chance something" | |
| }, | |
| { | |
| "14:31": "happens is a guarantee that a customer" | |
| }, | |
| { | |
| "14:32": "is calling you with a dead server. Yep." | |
| }, | |
| { | |
| "14:33": "And so you have to mitigate that in your" | |
| }, | |
| { | |
| "14:35": "testing and troubleshooting. So you guys" | |
| }, | |
| { | |
| "14:36": "probably do pretty extensive work." | |
| }, | |
| { | |
| "14:37": "We absolutely do. These things spend a" | |
| }, | |
| { | |
| "14:39": "lot of time in the R&D lab. They also" | |
| }, | |
| { | |
| "14:41": "spend a lot of time with early adopter" | |
| }, | |
| { | |
| "14:42": "customers and they go through a whole" | |
| }, | |
| { | |
| "14:44": "process of that hardening phase to make" | |
| }, | |
| { | |
| "14:46": "sure when you get your traz delivered," | |
| }, | |
| { | |
| "14:48": "it's going to perform. It's going to be" | |
| }, | |
| { | |
| "14:49": "at a cost that makes your CFO happy," | |
| }, | |
| { | |
| "14:51": "especially thanks to rising flash" | |
| }, | |
| { | |
| "14:53": "prices, and also makes the IT and" | |
| }, | |
| { | |
| "14:55": "technical staff and end users happy that" | |
| }, | |
| { | |
| "14:57": "the performance just kicks butt." | |
| }, | |
| { | |
| "14:58": "That's awesome. Well, Trina, it's" | |
| }, | |
| { | |
| "15:00": "awesome. Thank you for taking the time." | |
| }, | |
| { | |
| "15:02": "Absolute pleasure to see you here at" | |
| }, | |
| { | |
| "15:03": "NAB." | |
| }, | |
| { | |
| "15:04": "Great to meet you." | |
| }, | |
| { | |
| "15:04": "If you guys need storage consulting," | |
| }, | |
| { | |
| "15:05": "link down in the description. We can" | |
| }, | |
| { | |
| "15:07": "help you out and connect you with the" | |
| }, | |
| { | |
| "15:08": "folks over here at Trunz. So pleasure." | |
| } | |
| ] | |
| } | |
| ] | |
| } |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment