chronid

10 ms·

61.
by chronid 3y ago
Please no! When I last worked with physical servers we were replacing tpms all the time...
62.
by chronid 3y ago
Some kind of cost shedding to the application owner (in many enterprises this is not the infra owner) is definitely needed otherwise everything becomes critical. "Everything is critical" should sound a million alarm bells in the m
63.
by chronid 3y ago
I do, and I'm not a security researcher (not really). If nothing else, it's fun to see who pokes you, even if I don't actually follow up on it.
64.
by chronid 3y ago
I think there's a bit of "they could" but also something that is considered very little in many contexts unless you have experienced the contrary: integration is costly and integrating properly sometimes is more work than doi
65.
by chronid 3y ago
The same reason cloud is all the rage. It has its uses, hype is behind it and the marketing ignores its caveats. The main issue I have with it is simple: in my experience you cannot really debug some classes of issues ("we had intermit
66.
by chronid 3y ago
In infrastructure we build dashboards. And then we build systems to tell us something wrong, and when something is wrong we go and look at the dashboard. Looking at dashboards all day to spot issues is a (pointless) nightmare.
67.
by chronid 3y ago
This goes on every day even in our field, from small things (like infra being blamed for everything at first so the application teams can go home) to the biggest involving criminal investigation: if you have nothing to lose from not doing i
68.
by chronid 3y ago
The japanese rights holders for the logo and the japanese company (?) making it at least disagree I think. The name and logo if nothing else are pretty recognizable and memorable. I know nothing about features, but they seem to be collabo
69.
by chronid 3y ago
The company behind it is called gehirn to add more fun to the story. :)
70.
by chronid 3y ago
My 2c: you can get things right, but most of the time you won't, for many reasons - technical, logistical, cultural or merely political. Sometimes you don't control these reasons. So you are now left with managing risk. It's
71.
by chronid 3y ago
Spoiler: it won't. I never worked too closely with TPMs, just looked at the code in a previous employer because it was adjacent to mine and helped tprefactor some of it. Settings them up was kinda nightmarish considering all the failur
72.
by chronid 3y ago
I have been fighting this in my current position, with some success with some teams and far less success with others (who are now fighting with the distributed monolith they have created). Ironically the ex-faanmg folks are all pro-monolith
73.
by chronid 3y ago
Definitely have multiple replicas, and recreate misbehaving ones, saving logs and data for later analysis. If you can't have that (and budget allows) keep unhealthy replicas alive and pull them off the load balancers. In my experience
74.
by chronid 3y ago
You need better observability or tooling then. Operation teams (and automation) have usually a primary mandate of availability above all, not to investigate any possible failure.
75.
by chronid 4y ago
I am in that condition, so personal experience here: - i do most meetings with internal stakeholders to understand needs and changes, and document them - i do most "architecting", as i have most context on the systems my team is r
76.
by chronid 4y ago
Multi-AZ is a requirement on production level loads if you cannot sustain prolonged downtime. Datacenters do end up completely dying now and then, you really want to have a good strategy in that case. Or not, if that's not required.
77.
by chronid 4y ago
Building your own datacenter is hard (think the logistics for just keeping the lights on). Even if you don't own/manage the building but simply buy the hardware (and spares, and DC ops) from HP/Dell/EMC and friends thing
78.
by chronid 4y ago
> Teams never seem to understand how to alert on stuff. Ive been paged for things going off, that might indicate a problem, then you get stuck sticking around because someone else wants to just wait and see what happens. "We should
79.
by chronid 4y ago
I would add a "there is time reserved to write automation to reduce toil". I have a fair bit of experience in teams with developers hating oncall and the critical issues happen in two camps generally: - In some cases the org was
80.
by chronid 5y ago
Note those are anycast addresses, my guess is the DNS server gives out addresses for FB names pointing your traffic to the POP the DNS server is part of. If the POP is not able to connect to the rest of Facebook's network, the POP stop
81.
by chronid 5y ago
The EU commission is voted in by the EU governments. The EU council is made by the EU governments. EU citizens elect MEPs. There is no accountability because no one holds them to account and people repeat what you just wrote like gospel,
82.
by chronid 5y ago
My interpretation is that it's advocating for counting the thing that matter , not the consequence (e.g., the "SEV" event). The problem is your availability being <X%, your API responding >Xs Y% of the time, not "
83.
by chronid 6y ago
> Is that not what the person who originally posted the content being moderated is doing? The person that posted the content does not expect a random person from the internet to see a video of his children because it was accidentally fla
84.
by chronid 6y ago
> IIRC, Netflix OSS published some tools quite some time ago to support multiple DNS providers but I don't know/remember if they tackled the availability problem. The classic way of doing this is AXFR (your own DNS server is a
85.
by chronid 6y ago
> If not, and you own the physical capacity yourself, wouldn't you do away with CloudFlare entirely? Cost could be an issue. We had something similar (not in the same context) in a company I worked for before. We could shift traffic
86.
by chronid 7y ago
Fun fact, this has been an issue since 2011: https://support.google.com/calendar/forum/AAAAd3GaXpEE7zPvtA...
87.
by chronid 7y ago
Why not asking them during the interview process? Have them "drive" you through the resolution of one of the issues that you expect could happen. See how they behave and what they try - they may not necessarily have the complete c
88.
by chronid 8y ago
Google also has all that and now and then their network explodes anyway when they do configuration changes. :) Certain configurations at a big enough scale are dangerous, just because you could hit a terrible corner case when you rolled out
89.
by chronid 8y ago
> It wasn’t Trump winning that did it, it was that Trump won with the assistance of data that Facebook was unable to properly protect. I agree that Facebook is certainly a convenient scapegoat to hide all the other issues that plagued th
90.
by chronid 8y ago
In 2008 and 2012 FB got praised for being the platform that Obama used to win the elections - I remember multiple articles about it (and someone from the Obama campaign later admitted that they did the same thing that got the CA scandal sta

More ›