I haven't encountered any Chef code in almost ten years. For the stragglers not yet primarily on Kubernetes and Terraform, I see Ansible and some extra Terraform. Maybe I see some Salt here and there.
These are just my anecdotes, for sure, but (also anecdotal) I rarely hear of other "ops" type people using Chef, and most of the ones I know never got more than just their feet wet with Chef (the SaltStack beta was out early enough to avoid Chef).
Spam is far too obviously not speech is the thing. They will continue to use the moniker "Free Speech absolutist", and ignore you. But keep campaigning as the one lone voice with that, I'll still continue cheering you on while the rest of the world ignores your funny viewpoint that isn't believable for you to actually even have.
I'm a 3/4 black partially Jewish gay man, so you can imagine where I stand on "Free Speech absolutism". While I am for the most part on your "side", I want to stick to arguments that are persuasive.
> All four were granted anonymity because they were not authorized to publicly discuss the private chats.
Anyone with access to NSA plus various subcontractors' toolsets can "unmask" these people in like five minutes. Musk may not be "tech genius" some of the media makes him out to be, but he knows enough about how the internet and computers work (or has advisors who do) to figure that out.
Where three different disks (or storage underneath Ceph OSDs) each in separate disk silos fail?
In some earlier Ceph clusters I was responsible for I set replication to four or even five.
There was a point where I wrote an internal memo to business leaders explaining that had I not set that replication to four or five we would have been unable to meet business goals (we would have lost the contracts keeping us afloat during critical stages), but now at scale the real dollar cost of that redundancy was showing. In that memo I explained what networking we needed vs what we had, what people we needed vs what we had, and so on. I eventually got the networking gear the company needed in place and was able to hire the kind of people we needed.
For Ceph clusters I am chiefly responsible for today we have Ceph pools in each availability zone doing erasure coding (four or more parity bits) and a small service makes sure objects are copied between the distanced datacenters (availability zones).
While I do get a bit of a boner (of the Hank Hill on propane kinda vibe) on how the erasure coding is distirbuted across cabinet rows, to be fair it is a bit of an optimization.
_
> to have lower durability (say replicas are located within the same networking pod)
A network segment should never ever go down. I know in some places this is "optimistic". I can say for us it's not "optimistic" because we don't allow Ethernet protocol to "hop" anywhere. Layer-2 broadcast domains either stop at top-of-rack and the rest is layer-3 or we are using Infiniband. Stable Ethernet networks are a thing, but not using Ethernet beyond where Ethernet belongs avoids so much risk.
100% network uptime is achievable.
In some places more critical nodes are connected to three Infiniband switches with two uninterrupted power supplies dedicated to each Infiniband switch. Maybe that's "excessive", but within the last year we had to contend with a switch failure. Then a week later a datacenter provider (one that will tell you they never ever EVER lose power) for one of our availability zones was unable to provide power for over two full days.
I don't think we're ever going to have downtime or lose data. In other places this would be "optimistic", but for this deployment I have access to the resources I need to achieve the thing. The only thing that has me concerned about downtime is the current WW3 we are already in heating up.