Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sudomateo
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
by
sudomateo
29d ago
Define "cooler" please.
2.
▲
by
sudomateo
29d ago
I said some of this elsewhere, but the operating system is an implementation detail since we're not selling you bare-metal compute--we're selling you on-premises cloud computing. I think you were looking at this from hardware plus
3.
▲
by
sudomateo
29d ago
Theoretically, yes. Practically, highly unlikely. Switching to Linux and KVM would gain the ecosystem benefits but Oxide would lose control of the host OS which can impact our security stance. Better to tightly integrate at this layer and e
4.
▲
by
sudomateo
29d ago
Thank you so much! There are certainly a plethora of options for Kubernetes cluster management. We see Cluster API as a vendor-agnostic way for us and our customers. Perhaps one day we'll more tightly integrate Kubernetes and the Oxide
5.
▲
by
sudomateo
1mo ago
You're completely skipping the management of the bare-metal hardware itself. Sure, you can buy a stack of whatever commodity hardware you want and run Kubernetes on bare-metal. What about updating the firmware on that hardware? What ab
6.
▲
by
sudomateo
1mo ago
It's a rack-sale computer that uses hardware and software co-design to achieve things a stack of disparate 1U servers and network switches can't. You plug in power. You connect it to your network. You get a cloud provider like con
7.
▲
by
sudomateo
1mo ago
I run this on a TuringPi board at home. I wouldn't get the TuringPi again but Talos for home use has been great. The only issue for me is I have access to Oxide so I moved most of my home lab there.
8.
▲
by
sudomateo
1mo ago
Could be whichever. Customers have expressed a desired for Longhorn given they were already using it so we started our testing there. Ultimately our CSI plugin will be the official Oxide path.
9.
▲
by
sudomateo
1mo ago
Reported internally. Thank you!
10.
▲
by
sudomateo
1mo ago
Good question. We use our own hypervisor[0] that's not KVM/QEMU. We don't have nested virtualization today so we don't follow the KubeVirt model, though we are discussing what CRDs like OxideInstance would look like for
11.
▲
by
sudomateo
1mo ago
I cover this a bit in the post. Today they are running something like Longhorn backed by Oxide storage. When we release our CSI plugin they can use that instead.
12.
▲
by
sudomateo
1mo ago
You can run the control plane at home. I have a video on how to do it. Until we make a smaller footprint that's the only way you'd get Oxide at home.
13.
▲
by
sudomateo
1mo ago
> So you’d be attaching a new volume to the running worker VM for each PVC? That's what we prototyped before local disk was released and before we started disk hot-plug work. > Could you attach a single large volume, and do path-
14.
▲
by
sudomateo
1mo ago
Totally, the out-of-tree CCM gives us a good opportunity to differentiate. Autoscaling is a requested feature, and Karpenter fits that shape naturally. The nuance is to decide where something like the Cluster API provider ends and Karpenter
15.
▲
by
sudomateo
1mo ago
We're discussing what "native Kubernetes" looks like on Oxide in the limit. There's a bunch to build, some of which is blocked on product gaps. We'll get there though! I don't necessarily want to match the pu
16.
▲
by
sudomateo
1mo ago
I'll need to record a video on what's possible today. My personal Kubernetes cluster running on Oxide uses the CCM for LoadBalancer services and NGINX Gateway Fabric for Gateway API things. I'm mostly using HTTPRoute resource
17.
▲
by
sudomateo
1mo ago
There are few paths we can take here. The CCM's primary responsibility is to implement the cloudprovider.Interface[0] which has node, route, and service controllers. However, the CCM can run arbitrary named controllers as well, giving
18.
▲
by
sudomateo
3mo ago
The sleds blind mate to power and network on the backplane so removing the sled will disconnect it. Once the sled is disconnected you pull the fan assembly out and replace it.
19.
▲
by
sudomateo
7mo ago
Hey! It's nice to see others excited about Oxide. Hubris is an area of the stack I'm not intimately familiar with, but I'll do my best to answer your questions from my perspective. > From the inside, is Oxide a place where
20.
▲
by
sudomateo
7mo ago
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 exactl
21.
▲
by
sudomateo
7mo ago
What led you to believe that this is a SaaS offering? It's not.
22.
▲
by
sudomateo
9mo ago
You're welcome. My colleague published the text for it: https://gist.github.com/david-crespo/5c5eaf36a2d20be8a3013ba...
23.
▲
by
sudomateo
9mo ago
Disclaimer: Oxide employee here. To be honest there's really no secret sauce in there. It's primarily how to get started with agents, when to abandon your context and start anew, and advice on models, monitoring cost, and prompti
24.
▲
by
sudomateo
9mo ago
Medication is littered with warning labels but humans still use it to combat illness. Social media can harm mental health yet people still use it. Pick whatever other example you'd like. There are things in life that have high risks of
25.
▲
by
sudomateo
1y ago
We're working on publishing an updating pricing page to better communicate this to the public. Stay tuned! Here's what I can knowingly share. We sell full-rack and half-rack SKUs today coming in at 1024/16TiB and 2048/32
26.
▲
by
sudomateo
1y ago
Hey! The current generation rack is compatible with the current generation compute sleds, switch, and power shelves. The next-generation compute sleds will be compatible as well. Possibly the next-generation switch but I would have to defer
27.
▲
by
sudomateo
1y ago
Similar to what others noted earlier I'm having trouble understanding exactly what you're trying to communicate here. I'll respond based to points I am clear on. Selling a customer a contract for on-premises computing and giv
28.
▲
by
sudomateo
1y ago
It's tough on both sides. I understand the disdain of receiving a "no" after putting in hours or days of effort on the materials. Candidates are welcome to ask for feedback on their application but must understand that Oxide
29.
▲
by
sudomateo
1y ago
Loved reading your experience here. Thank you for posting it. I've written about the value of an artifact in the past when people pushed back against the Oxide materials saying they are a lot of work for no guarantee. When I first appl
30.
▲
by
sudomateo
1y ago
I expected much more content here based on the title.
More ›