Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Oxide Computer: Docs

docs.oxide.computer

Post reply on HN
Print view View original

101–110 of 160 posts

Re: Oxide Computer: Docs

#101

Post by 59nadir »

wmf wrote: post #62
mwcampbell wrote: post #60

I'm a little surprised that, according to the docs, "the Oxide rack does not come with any preloaded machine images" [1]. But I guess it makes sense that the initial, early-adopter customers wouldn't have a problem with rolling their own VM images. I'm at least glad that Oxide didn't decide to start by only allowing VMs that use a pre-defined set of pre-made images in some custom format. [1]: https://docs.oxide.compu…

The preloaded images would all be Solaris anyway. ;-)

Surely Illumos? Solaris is probably dead to most people involved, a husk of what it was and could have been.

Re: Oxide Computer: Docs

#102

Post by bcantrill »

Aurornis wrote: post #96
EvanAnderson wrote: post #10

Everything about Oxide's gear sounds like fun. I imagine it must be a bit like what working with minicomputers in 70s thru the 90s was like. I did a little work in the late 90s with Alpha-based machines. I was impressed at those machines didn't seem like the hack-job crap that PC-based stuff was (with simulated chips from the early 1980's hiding out in dark corners because "compatibility") and still is today. I'm bet…

> I imagine it must be a bit like what working with minicomputers in 70s thru the 90s was like. I had a chance to talk to someone who worked at Oxide once. I got excited because my experience matches up nicely with their products on several levels. The person got excited as well and started talking about how to interview there, but the conversation got kind of weird. They kept emphasizing how important it was to not…

This conversation strikes me as unlikely on several levels. First, no one would have coached you on "how to interview at Oxide" because that's not where the process starts -- it starts with you preparing your materials.[0] (Our review of the materials constitutes ~95% of our process.) Second, we have always been very explicit about compensation (that is, we ourselves brought it up early in conversations); no one at Oxide would tell you to "not bring it up" because everyone at Oxide knows that it is a subject dealt with early in the process. And finally, this is all assuming that you were talking to someone before March 2021, when we published our blog post on it.[1] After the blog post, compensation simply doesn't come up: everyone has seen it -- and indeed, our approach to compensation is part of what attracted them to the company!

[0] https://docs.google.com/document/d/1Xtofg-fMQfZoq8Y3oSAKjEgD...

[1] https://oxide.computer/blog/compensation-as-a-reflection-of-...

Re: Oxide Computer: Docs

#103

Post by bcantrill »

Aurornis wrote: post #92
tiffanyh wrote: post #27

Earlier quoted context omitted.

> As someone who's only dealt with commodity server hardware, these specs make me salivate Commodity servers have the same specs. Here’s a reseller of SuperMicro servers, where you can buy similar compute on the cheap. https://www.siliconmechanics.com/systems/servers/rackform

> Commodity servers have the same specs. Probably not a coincidence. It would be interesting to know which ODM they partnered with for the hardware. I've done some work with SuperMicro in the past. Some of their boards come with extensive headers and customization options right out of the box. They're also happy to work on board level customizations with the right contracts in place.

We didn't work with an ODM: the ODMs were unwilling to contemplate some of the most basic things we needed (e.g., replacing the BMC with a much lighter weight service processor, having a true root-of-trust, etc.) -- let alone the more things we wanted to do (e.g., our own switch). The compute sled and the switch are both of our own design and look nothing like what you'll find from an ODM; if you're curious in the details, we have discussed them quite a bit in our Oxide and Friends podcast.[0][1][2]

[0] https://oxide-and-friends.transistor.fm/episodes/tales-from-...

[1] https://oxide-and-friends.transistor.fm/episodes/the-sidecar...

[2] https://oxide-and-friends.transistor.fm/episodes/bringup-lab...

Re: Oxide Computer: Docs

#104

Post by jna_sh »

benjaminwootton wrote: post #100
pxc wrote: post #98

Earlier quoted context omitted.

> high contrast dark themes are difficult to read for people with astigmatism. Are you yourself affected by this? I have astigmatism and I keep hearing this, but I've never experienced it. If you are affected, do you keep your screen at high brightness? I'm wondering if it doesn't happen to me only because my astigmatism is mild, or if the fact that I tend/have to keep my screens at relatively low brightness plays a…

I was about to ask the same question. I think I have moderate astigmatism and find dark mode easier on the eyes.

I have astigmatism and loathe dark mode. I find low contrast and soft colours easiest.

Re: Oxide Computer: Docs

#105

Post by sam_bristow »

ThinkBeat wrote: post #50

Can you configure your Oxide mainframe for different uses? Like max it out with 90% being GPUs? I like the idea, though it may be dumb, if you could fill it with different types of processors for what you need. Sort of like chiplets but at a different scale

I don't believe they have any GPU option in this initial rack. In one of the podcasts they said something about none of the GPU vendors being open enough to allow the kind of deep integration they're going for. It might change in future of course.

Re: Oxide Computer: Docs

#106

Post by littlestymaar »

throwaway2037 wrote: post #93
solarkraft wrote: post #29

Finally I actually understand what they're building. Now I must ask: Why? On-prem servers aren't a new invention. The market seems pretty saturated (and shrinking). Virtualization isn't a new invention either. The market seems pretty well served, at least commercially. Can the integration of both be a convincing enough advantage? The management UI certainly looks nice; it's something I'd like to have on my KVM box at…

Stupid question (no trolling, I promise): Could this product be valuable to public cloud vendors, like AWS, Google, Oracle, IBM, etc? Or even medium sized ones, like Linode? My thinking: Could this be the cloud inversion moment akin to TSMC and outsourcing semi-conductor manuf?

For big vendors, no. Because what oxide does is basically sell the kind of server that the hyperscalers have been building for themselves internally. But for smaller cloud provider, who aren't running custom hardware made for hyperscale and are instead using of the shelf servers with all their flaws, then it could make a lot of sense.

Re: Oxide Computer: Docs

#107

Post by alexgartrell »

bcantrill wrote: post #102
Aurornis wrote: post #96

Earlier quoted context omitted.

> I imagine it must be a bit like what working with minicomputers in 70s thru the 90s was like. I had a chance to talk to someone who worked at Oxide once. I got excited because my experience matches up nicely with their products on several levels. The person got excited as well and started talking about how to interview there, but the conversation got kind of weird. They kept emphasizing how important it was to not…

This conversation strikes me as unlikely on several levels. First, no one would have coached you on "how to interview at Oxide" because that's not where the process starts -- it starts with you preparing your materials.[0] (Our review of the materials constitutes ~95% of our process.) Second, we have always been very explicit about compensation (that is, we ourselves brought it up early in conversations); no one at O…

The person to whom you are replying clearly meant (IMO) that you shouldn’t ask for more compensation or you will make people act defensive. Frankly, your reply reads a little defensive so maybe that’s not awful advice?

It also seems like this was a spontaneous initial conversation and not part of the process, so I’m not sure why you are suggesting that they made it up.

Re: Oxide Computer: Docs

#108

Post by masklinn »

codetrotter wrote: post #15
wmf wrote: post #12

Earlier quoted context omitted.

Estimates in the previous thread were at least half a million.

Yeah that’s about 100x more than I can afford exactly. I think I will go back to my little collection of RPi Compute Module machines. And maybe some day in the very distant future I can buy big boy servers lol

Depending on your exact wants, I think there was an LTT video recently on how you can purchase older server blades for very reasonable prices, and upgrade them using also reasonably priced used server-grade CPUs and RAM. Obviously you won’t have the bang of new hardware, but if what you want to do is play around with enterprise-class systems…

Re: Oxide Computer: Docs

#109

Post by gary_0 »

alexgartrell wrote: post #107
bcantrill wrote: post #102

Earlier quoted context omitted.

This conversation strikes me as unlikely on several levels. First, no one would have coached you on "how to interview at Oxide" because that's not where the process starts -- it starts with you preparing your materials.[0] (Our review of the materials constitutes ~95% of our process.) Second, we have always been very explicit about compensation (that is, we ourselves brought it up early in conversations); no one at O…

The person to whom you are replying clearly meant (IMO) that you shouldn’t ask for more compensation or you will make people act defensive. Frankly, your reply reads a little defensive so maybe that’s not awful advice? It also seems like this was a spontaneous initial conversation and not part of the process, so I’m not sure why you are suggesting that they made it up.

I didn't realize there are two ways of looking at it until your comment. It didn't occur to me that if you randomly have Oxide on a list of 40 other companies to apply to, and you expect to talk to them about compensation as you would with most others, you're going to have a weird time because they have an uncommon policy.

But on the other hand, Oxide is very up-front about it, and their CTO is happy to go on HN and chat about it. So not knowing about it makes you look like you didn't do your research before the interview, or knowing about it and trying to force the issue anyways makes you look kind of arrogant (if you don't agree with it, you can just not apply).

Re: Oxide Computer: Docs

#110

Post by rhinoceraptor »

javajosh wrote: post #19

I'm particularly impressed with their anti-tamper measures. "For each server sled, shine a light into the cubby to look for any physical tampering or damage." https://docs.oxide.computer/guides/system/rack-installation-...

    The rack also comes with built-in security features to ensure all hardware and software are genuine Oxide products:

    purpose-built hardware root of trust (RoT) – present on every Oxide server and switch – cryptographically validates that its own firmware is genuine and unmodified
    encryption of data at rest via internal key management system built on the RoT
    trust quorum establishment at boot time to ensure the cryptographically-derived rack secret is verified before unlocking storage
https://docs.oxide.computer/release-notes/system/1-0-0
Post reply on HN