ca508

8 ms·

1.
by ca508 1y ago
been following engine from afar for a while, super cool to see it on HN. didn't see it had a free plan, will try it out.
2.
by ca508 1y ago
Yep! We have two roles open https://railway.com/careers#open-positions - Datacenters and Infra that might be of interest to you. Idk if many of us use LinkedIn so not the best way to get in touch. Can I share the email on y
3.
by ca508 1y ago
> the dots aren’t connected between a lot of the aspects presented that's on me (author); I tried to cut the content down to a manageable post size that covered some interesting stuff - but probably dropped the connective tissue in
4.
by ca508 1y ago
Author here; RAM is so much more expensive than disk though. Two 500G M.2 NVMes for a RootFS in RAID1 are basically max ~$150 which is I think much cheaper than a single 64G DDR5 ECC RAM module [I don't have exact numbers on me, but EC
5.
by ca508 1y ago
author here; Claude use here was pure laziness - and personally, I found it quite funny that it worked. We could sample pixels and try and build that detection, but $<1c per run to write a prompt and get some json was too hilarious not t
6.
by ca508 2y ago
There's a fork called nautobot that tries to add-in automation. Most things we wanted to do with either meant we had to go writing django plugins and trying to interface with their APIs (and fight with the libs). Overall just hammering
7.
by ca508 2y ago
It's a fair question. What Oxide are building is cool, but it's too custom/monolithic for us to risk. We're more likely to look at OCP racks/chassis down the road.
8.
by ca508 2y ago
We currently pass on our cloud egress costs to users via the current pricing. We'll be publishing a pricing update soon as part of our migration - and egress [and some other things] will be coming down.
9.
by ca508 2y ago
We have a distributor we work with - just because it makes import/export a lot easier. But we get to interface directly with Supermicro for the technical/design stuff, and they're super awesome. If you're looking in the
10.
by ca508 2y ago
the good news on this is that we've got a tonne of deep-dive material on networking and whitebox switches we cut from this post. We'll definitely be talking more about this soon (also cos' BGP is cool).
11.
by ca508 2y ago
correct; I think the first version of our tool sprung up in the space of a couple of weekends. It wasn't planned, my colleague Pierre who wrote it just had a lot of fun building it.
12.
by ca508 2y ago
We talked to a few, I think they're called MSPs? We weren't super impressed. We decided to YOLO it. There are probably great outfits out there, but it's hard to find them through the noise. We're mostly software and syst
13.
by ca508 2y ago
All valid points - and our ideas for Gen 2 sound directionally similar - but those are at crayon drawing stage. When we started, we didn't have much of an idea about what the rack needs to look like. So we chose a combination of things
14.
by ca508 2y ago
ah that's my bad - I wrote this in Dec, we only published in Jan. Obv. missed updating that. Timeline wise; - we decided to go for it and spend the $$$ in Oct '23 - Convos/planning started ~ Jan '24 - Picked the vendors
15.
by ca508 2y ago
oh yes we want to; I even priced a couple out. Most of the SKUs I found were pretty old, and we couldn't find anything compelling to risk deploying at the scale we wanted. It's on the wishlist, and if the right hardware comes alon
16.
by ca508 2y ago
Long running hosts at the moment, but we can drain most workloads off a specific host/rack if required and reschedule it pretty fast. We have the advantage of having a custom scheduler/orchestrator we've been working on for y
17.
by ca508 2y ago
we evaluated a lot of commercial and oss offerings before we decided do go build it ourselves - we still have a deploy of netbox somewhere. But our custom tool (Railyard) works so well because it integrates deeply into the our full software
18.
by ca508 2y ago
> It would be nice to have a lot more detail I'm going to save this for when I'm asked to cut the three paras on power circuit types. Re: standardising layout at the rack level; we do now! we only figured this out after site #2
19.
by ca508 2y ago
We didn't find many good up-to-date resources online on the hardware side of things - kinda why we wanted to write about it. The networking aspect was the most mystical - I highly recommend "BGP in the datacenter" by Dinesh D
20.
by ca508 2y ago
We built some internal tooling to help manage the hosts. Once a host is onboarded onto it, it's a few button clicks on an internal dashboard to provision a QEMU VM. We made a custom ansible inventory plugin so we can manage these VMs t