331–340 of 355 posts
Earlier quoted context omitted.
I'm interested, tell me more. What about Oxide attracts a homelab user?
Many homelab users are actually building things out in an effort to learn tooling that they will then use at work. Or just out of intellectual interest.
Earlier quoted context omitted.
We're working on making this easier to understand. Stay tuned! We know the last decade or so of using public cloud providers has made people forget that hardware and software are things you can own and run successfully. Oxide is exactly that. Hardware and software designed together to give you the public cloud experience on-premises. Disclaimer: I work at Oxide.
I'm the undergrad who commented earlier. I’ve been poking around the Hubris source code and it’s exactly the kind of stack I want to work on. I'm actually doing the Redox Summer of Code this year, focused on implementing an EEVDF scheduler and a performance testing harness for the kernel. From the inside, is Oxide a place where a fresh grad can actually be useful? Or is the "complexity floor" of hardware/software co-…
> From the inside, is Oxide a place where a fresh grad can actually be useful? Or is the "complexity floor" of hardware/software co-design so high that you really just need a few decades of experience to be effective?
I believe Bryan spoke about this publicly on podcast episodes in the past but the answer really is no and yes. Generally, the things we're working on at Oxide require a both depth and breadth of knowledge in various areas of the stack that early career folks don't yet possess. We also have limited bandwidth to assist early career folks because of our small company size. I know this sounds like gate keeping, but mostly everyone at Oxide wants to support early career folks. Unfortunately, the general consensus has been that we just don't have the bandwidth for it and it would be a disservice to a candidate to hire them and not support them the way they would need to be supported. That being said, we're getting bigger and will likely have more bandwidth to change this stance as time passes. If you see a role you'd be a good fit for I do recommend applying. The application process itself is valuable for the applicant.
Earlier quoted context omitted.
You would need 3-phase power too. At 208V and 15kW it'll draw over 70A peak :P. If you can wire that up in your living room, I raise my glass to you!
Nothing a licensed electrician couldn't figure out, although with 230V plugs instead and probably closer to the garage than our living room :)
Earlier quoted context omitted.
Unfortunately since they already took VC money they have to keep doing it and each time they do it they do it the VCs would own more and more and would control the business. I predict in less than 10 years Oxide exits by way of being acquired or an IPO. The enshittification would have already begun by then. > You seem very sure of yourself in how business works! I'm curious now, how did you create your $100MM++ reven…
There's a lot of confusion here about the way VC operates (or companies, for that matter), but just to clarify one point: an IPO is not an "exit" -- it is a public offering. That is, an Oxide IPO, were we to be so lucky, would be a milestone towards being the generational company that we aspire to be.
And what are you offering and why are you offering it?
Who do you think will own whatever you're offering after you go public?
Are you hoping your VCs (or you) won't sell whatever your offering when an IPO happens?
Earlier quoted context omitted.
They have been around for nearly 20 years. I viewed them as an also-ran until Broadcom decided they didn’t need any of us as VMware customers anymore. Now Nutanix seems like a viable path for on-prem VM workloads that need a new home for those who don’t want to part with an arm and a leg on licensing but can’t move to public cloud either. I’m not sure how much of that market Oxide can capture. Not sure Nutanix is sti…
Nutanix / Oxide have a VERY different market / customer base.
Given this, can you help me understand in what ways they are different?
When I went to the Nutanix website yesterday, the link showed that'd I'd previously visited them (not a surprise, I look up lots of things I see mentioned in discussions) but their website does an extremely poor job of explaining their business to someone who lacks foundational understanding, even once I'd started reading about "hyperconverged" just before.
If I could use the Oxide stack in a homelab form factor, I would be so happy...
The rack has custom Intel Tofino based switch that uses P4 to do network magic. Hard to put this in a home lab.
All I need is some financial backers and I'll happily document the whole thing on a blog and a youtube channel. Now accepting offers.
I say this every time Oxide comes up, and I know that I will never get my wish, but if they ever ventured into the "homelab" market with smaller products, they can have all my money .
I’m sure it wouldn’t be profitable for them, but I feel like having some vendor sell a ‘reference machine’ that they know could run the core OS well would be a good in between. Someone like Framework selling a workstation looking desktop in a specific reference config couldn’t be too bad. Feels like just enough to get a community started. Most tasks really don’t need bleeding edge hardware anymore, the thing could go…
Earlier quoted context omitted.
Nutanix / Oxide have a VERY different market / customer base.
I've been curious about Oxide for a year or two without fully understanding their product. People talking about the "hyperconverged" market in this thread gave me an understanding for the first time. Given this, can you help me understand in what ways they are different? When I went to the Nutanix website yesterday, the link showed that'd I'd previously visited them (not a surprise, I look up lots of things I see men…
Also check this out: https://www.linkedin.com/posts/bryan-cantrill-b6a1_unbeknown...
If you need a basic "vm platform", VMware, Proxmox, Nutanix, etc. all fit the bill with varying levels of feature and cost. Nutanix has also been making some fairly solid kubernetes plays, which is nice on hyperconverged infrastructure.
Then if you need a container platform, you go the opposite direction - Kubernetes/OpenShift and run your VMs from your container platform instead of running your containers from your VM platform.
As far as "hyperconverged"...
"Traditionally" with something like VMware, you ran a 3-tier infrastructure: compute, a storage array, and network switching. If you needed to expand compute, you just threw in another 1U-4U on the shelf. Then you wire it up to the switch, provision the network to it, provision the storage, add it to the cluster, etc. This model has some limitations but it scales fairly well with mid-level performance. Those storage arrays can be expensive though!
As far as "hyperconverged", you get bigger boxes with better integration. One-click firmware upgrades for the hardware fleet, if desired. Add a node, it gets discovered, automatically provisions to the rest of the configuration options you've set. The network switching fabric is built into the box, as is the storage. This model brings everything local (with a certain amount of local redundancy in the hardware itself), which makes many workloads blazing fast. You may still on occasion need to connect to massive storage arrays somewhere if you have very large datasets, but it really depends on the application workloads your organization runs. Hyperconverged doesn't scale compute as cheaply, but in return you get much faster performance.
Earlier quoted context omitted.
On the other hand, it's normal to have heroes, and to need to have them.
This is a child mindset, people don't need heroes. They need leaders that care about them and want to better their communities; these leaders are found within your literal neighbors, friends, and family.
Any evidence or proof? This can be said about anything, even about your comment.
Earlier quoted context omitted.
Framework desktop mainboards 128GB version. They even show a mini rack with 4 of them.
That's mini ITX hardware, not really rack-sized in the sense of a common studio rack.