text
stringlengths
0
2.68k
**Cliff Biffle:** Which is good.
**Adam Stacoviak:** 100%.
**Jerod Santo:** Well, we'll let you get back to it.
**Cliff Biffle:** Alright.
**Jerod Santo:** Thanks for chatting with us. It's been awesome.
**Cliff Biffle:** Yeah, my pleasure.
**Adam Stacoviak:** We appreciate it.
**Break**: \[27:28\]
**Adam Stacoviak:** What is the update on the update?
**Dave Pacheco:** Well, let's see... We're working on shipping the first version of what we call a self-service update for the Oxide rack. So today, the process for updating the Oxide system, including the control plane and everything, involves a support process where our support engineers are getting on the system thr...
**Jerod Santo:** How long have you been working on that?
**Dave Pacheco:** I've been working on it for about two years.
**Jerod Santo:** How long has Oxide been working on that?
**Dave Pacheco:** We needed an update process for our MVP. And so that started before that and finished before that, because we launched before that... But that's the process that we use today, the support-based process.
**Jerod Santo:** This is like an upgraded rewrite.
**Dave Pacheco:** Kind of, yeah. So the idea behind the first version of update was what we called the minimum upgradeable product, which was Mupdate... And so the idea here is that, you know, it's an MVP, we're shipping it really as fast as we can... But there's a lead time between when you deliver software to the fac...
So the priority there was about having a robust support procedure for recovering the software on any one of our compute sleds. And that's something that we knew we needed even separately from update. And so that's why it came first, was this idea - like, we need the ability to recover a sled (one of our compute sleds) ...
**Jerod Santo:** Gotcha.
**Dave Pacheco:** And actually, even that - there are a bunch of building blocks involved in that; what I've come to call dynamic reconfiguration of the system. So having the ability for any component to come and go while the system is running is kind of a prerequisite for that, but it also allowed us to deliver other ...
**Jerod Santo:** Gotcha.
**Adam Stacoviak:** \[31:47\] What exactly is an update? Is it big? Is it small?
**Dave Pacheco:** That's a really good question, because --
**Adam Stacoviak:** What's happening?
**Dave Pacheco:** ...you think of the control plane as like "It's the control plane. It's just like one big piece of software", or something like that.
**Adam Stacoviak:** Sure.
**Dave Pacheco:** But actually, every single one of our -- so in a rack we've got 32 sleds, we've got two switches, and we've got a couple power shelf controllers. Every one of those has a service processor, a root of trust, and the root of trust has its own software, and the bootloader software. Then, on all the 32 sl...
**Adam Stacoviak:** It's a big deal then.
**Dave Pacheco:** Yeah. And that list I just gave doesn't even include a lot of stuff that for us gets bundled. CPU has microcode, NICs have their own firmware. For the update system, that's simplified, because it all gets part of the host OS, but there's a lot of software in the system, and it's updating all of those ...
**Adam Stacoviak:** That's nice it's a zip file. I mean, several gigs, though...
**Dave Pacheco:** It's a lot of software, yeah.
**Adam Stacoviak:** I mean, even the bandwidth cost on that. Do you measure that? Does it matter, as you grow your customer base? I mean, obviously not, because you're getting paid lots of money... But you've got to worry about those things, right? Speed to get it, accessibility...
**Dave Pacheco:** It's a good question. It's not something we've been focusing on for the most part so far. It's the kind of thing where the customer is currently going to be responsible for getting that from whatever our download site is, whether that's GitHub, to the rack.
**Jerod Santo:** \[unintelligible 00:33:58.20\]
**Dave Pacheco:** Yeah. So they might get that on their laptop, downloading it from GitHub, or something like that. And then they'll upload it to the rack.
**Adam Stacoviak:** \[unintelligible 00:34:02.17\] Nice.
**Dave Pacheco:** Yeah, that part is GitHub's problem.
**Adam Stacoviak:** It's a release. Alright, that makes sense.
**Dave Pacheco:** Yeah. And then uploading it to the rack is over their network. And we've kind of been assuming it wouldn't be an issue... That's a fair question, whether they would consider that an issue.
**Adam Stacoviak:** I was thinking about size, the file size. I guess most people can download a couple of gigs pretty easily, without it being a major problem... But some people can't.
**Dave Pacheco:** It's definitely a lot.
**Adam Stacoviak:** I've been told that before. I guess if you're --
**Jerod Santo:** Most of their customers are not...
**Adam Stacoviak:** Yeah, they're probably not having this problem. I'm solving different problems here, Jerod.
**Jerod Santo:** What about air gaps? So some people opt for an air gap.
**Dave Pacheco:** Yeah, that's really important, too. This model works pretty well for air gaps, because you, the customer, are downloading it to your laptop, and then uploading it...
**Adam Stacoviak:** No connection required.
**Dave Pacheco:** No connection to the -- the rack definitely doesn't care. It doesn't even know if it's connected to the internet. That's fine. It doesn't care.
**Jerod Santo:** Right.
**Dave Pacheco:** You could imagine a nicer experience where the rack was connected to the internet, and could see, "Oh, Oxide's just published a new thing, and I'm going to download it." And maybe I only download certain parts that I need, or I download it one part at a time... Maybe that helps with some of the bandwi...
**Adam Stacoviak:** We talked to Cliff earlier about Hubris... So when you look at Hubris, that's the operating system. You mentioned a couple of chips, every different device on there... When the update comes through, is that on top of the API of Hubris? Or is that -- how are they compared to each other, this update a...