Hacker News Reader

I don't really understand how having a larger minimum purchase unit (entire rack vs rack unit) is a USP. Your comments explain the emphasis on tighter integration across the stack, but it doesn't clearly show why this is a benefit.

What are the problems people are having with existing systems (like Vxrail), and how does Oxide fix those? What stories are you hearing?

View on HN

> I don't really understand how having a larger minimum purchase unit (entire rack vs rack unit) is a USP.

For some organizations cattle-like pizza boxes or chassis with blade systems are still not cattle-like enough. By making the management unit the entire rack you can reduce overhead (at least compared to a rack of individual servers, even if they are treated like cattle).

There are vendors that will drop ship entire (multiple) racks pre-wired and pre-configured for various scenarios (especially HPC): just provide power, (water) cooling, and a network uplink.

I wouldn't say that a larger purchase unit is a USP; it is an underlying reason why other USPs are able to be delivered. This is an engineering focused place, so I tended to focus on the engineering aspects.

My sibling commentor just left a great answer to your second question, so I'll leave that one there :)

Reply on news.ycombinator.com