Honest slightly cynical question: most probably someone inside the responsible team said some day that it would be very stupid to host the status page inside the same infrastructure being monitored, but they were probably ignored... what should that person do now? Say "toldya!" out loud in the postmortem meeting or simply shut up and move on because reality is that we are hired to do some stupid task and not to think…
IBM Cloud was down, as well as their status page
141–150 of 201 posts
Re: IBM Cloud was down, as well as their status page
#142Earlier quoted context omitted.
Their bare metal cloud offering (SoftLayer acquisition) was actually pretty good whenever I used it about 4 years ago. Wasn’t the most intuitive API or UI but you could get a bare metal server anywhere in the world in a few minutes.
When the wind blows in the right direction. Sometimes, your server would get stuck in provisioning for hours and only get „un-stuck” after creating a support ticket. Which, I kid you not, at one of the previous jobs, wd had automated in our provisioning popeline. Good times. But when it worked, it worked. API was voodoo.
aws support create-case \
--subject "not working" \
--communication-body file://description.txtRe: IBM Cloud was down, as well as their status page
#143Re: IBM Cloud was down, as well as their status page
#144Earlier quoted context omitted.
> There were a lot of sad panda hats when you guys started to transition away. For us as well. It was so nice to have things work one day and the next and the next, although I guess they wouldn't have worked today. Favorite firefighting moment was when wdc lost half the fiber in ~ 2014, and we had to move all of our traffic out, so that there was capacity. Our guy asked why we had to move? and your guy said something…
Dunno if I should realize who toast0 is, but what service were/are you running?
Re: IBM Cloud was down, as well as their status page
#145Earlier quoted context omitted.
Do you actually have data on that or are you conjecturing? Because I would really love to see data about that if it exists somewhere.
I'm talking from experience. Most things do get post mortems, but there's a lot of crap they also don't give us post mortems for "because customer data." It's my number 1 complaint, and I fight with managers about this all the time. We have a ton of hypervisor problems, and a lot of networking issues (generally over private network) and they tend to get very very secretive about it.
The key thing is each IP 5-tuple (peerA, peerB, protocol, portA, portB) will always take the same path over their network (most likely a different path for return packets, when A and B are switched), so in order to properly probe, you need to probe on a lot of of port combos, and once you find a broken combo, you need to run MTR on those ports, so you can give them the MTR that shows the issue.
Or, if you can, have your internode protocol run on multiple connections and drop connections that are showing issues, and let a different customer file the tickets :)
(email is in my profile if you want to discuss)
Re: IBM Cloud was down, as well as their status page
#146even weather.com was down but someone broke ebay too Fastly error: unknown domain: www.ebay.com. Please check that this domain has been added to a service.
Re: IBM Cloud was down, as well as their status page
#147I generally do everything on AWS or GCP, with a little Azure sometimes for personal projects. In what world does IBM beat one of those three in anything? Generally curious - how they are able to stay competitive?
Re: IBM Cloud was down, as well as their status page
#148Earlier quoted context omitted.
Dunno if I should realize who toast0 is, but what service were/are you running?
I don't think you are expected to know who I am :) I omitted the service on purpose, but you my email is on my profile if you want to know. Apparently it was enough information for dsmcr to properly id the service though; not enough for nixgeek though, I think.
Re: IBM Cloud was down, as well as their status page
#149Earlier quoted context omitted.
Never humiliate a coworker in public. Instead say "both options were considered but ultimately it was decided to select option B for reason Y."
What if Y = ignorance?