3 ms·
> so the idea is vertical integration for on-premise server purchases? On custom OS? Why? Why would people pay a premium? As I understand it, re: vertical int
by mustache_kimono 3y ago
> so the idea is vertical integration for on-premise server purchases? On custom OS? Why? Why would people pay a premium?
As I understand it, re: vertical integration, the term is actually "hyperconverged". Here, that means it's designed at the level of the rack. Like -- there aren't per compute unit redundant power supplies. There is one DC bus bar conversion for the rack. There is an integrated switch designed by Oxide. There is one company to blame when anything inside the box isn't working.
In addition, the pitch is they're using open source Rust-based firmware for many of the core components (the base board management controller/service processor, and root of trust), and the box presents a cloud like API to provision.
If the problem is: I'm running lots of VMs in the cloud. I'm used to the cloud. I like the way the cloud works, but I need an on-prem cloud, this makes that much easier than other DIY ways to achieve (OMG we need a team of people to build us a cloud...).
- steveklabnik 3y agoThe terminology in this space is confusing, but "hyperconverged" isn't really what we're doing. I wrote about the differences here: https://news.ycombinator.com/item?id=30688865 https://news.ycombinator.com/item?id=30688865 (That said I think other than saying "hyperconverged" your broad points are correct.)
- mustache_kimono 3y ago> but "hyperconverged" isn't really what we're doing. This is fair, especially as it follows a discussion of how you're building at the rack level, which is more like a mainframe than current "hyperconverged" offerings. Recommend others read the linked post.