brandon

In my experience with modest specifications, you can source servers from tier 1 vendors (Dell, HPE, etc) with 5 years of support for less than a 1 year commitment for the roughly equivalent AWS or GCE instances (without prepayment).

The monthly opex to house and power and cool those servers isn't _negligible_, but if you're doing back of napkin math comparing MRCs to Cloud you can just deduct the costs from their bandwidth charges that have been marked up 10,000%

Most of the stuff that makes the distribution different from Debian Testing is tightly coupled with Google's internal infrastructure and generally uninteresting (or unuseful) to users writ large. Just run Debian!

Based on the pictured bezel, it looks like they've got three rows 3.5" 14TB SATA drives up front in 14th generation carriers. Best guess would be something like an R740XD2 which has 26 total drive bays per 2U.

> Nobody at Google has a need to raise a ticket with some ops group in Bengaluru to partition a Kafka topic, renew a certificate, bridge two VPCs, or any of that type of thing.

Except when your team wanted to initially onboard with GOOPS and your request sat in Buganizer for 2 weeks waiting for someone to triage. Uh oh — we're turning down this service next quarter, you will need to go start this onboarding process again with its replacement.

Or when you needed quota in a cell where your product area didn't have Flex. Maybe you can set up a VC with your PARM? Does next week work for your launch plan? Hopefully they can do something for you!

Or when your logs access request sat in GUTS for a month because both of the approvers were on vacation and no, there's not an escalation path.

Or when you needed to change a firewall rule for a project your team inherited which for some reason runs on GCE. Make sure you bring your Ariane link when you open your request. Have ISE reviewed your code? No? ISE currently have a quarter-long backlog, so we're not sure we can grant your firewall exception.

None of these examples are contrived; the weight of the operational bureaucracy is staggering. It may well be that this stuff is felt more on the SRE/Security side around production launches than on the SWE side for experimentation or iterative development, but I struggle with the idea that Google is nimble.

I'm curious about what specific thing is signaling to you that your Steam password has been cracked. (I assume you mean brute forced?)

It's significantly more likely that you've been keylogged or phished if attackers are actually accessing your Steam account with passwords of that complexity.

This is likely aimed at $device_manufacturer that wants to put a cellular modem into their device for remote telemetry (uploading a tiny payload every 24 hours for the lifetime on the device). There's a lot of attention in the docs towards "fleets" — they aren't expecting you to just buy one.

Do you have a make/model or link for the valve? I went all-in on Z-Wave and am similarly interested in controlling drip-lines.