Ah, is this the exception that proves the rule that "no one was ever fired for buying IBM?" Sorry to be glib, I'm sure it's a tough time for people who were sold on their cloud platform and work on it!
Everybody's cloud goes down sometime. The big fail here was hosting their status page on the same infrastructure.
IBM Cloud was down, as well as their status page
61–70 of 201 posts
Re: IBM Cloud was down, as well as their status page
#62Honest 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…
Re: IBM Cloud was down, as well as their status page
#63Honest 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…
Don’t bite or embarrass the hand that provides you make-work... Seriously they probably tested it and it worked in theory, just not in practice and now they fix it for reals.
Or we just simply accept and making it the norm that even the lowest level of organizational governance is corrupt?
I am serious about this, because how people perceive their own rights, their own roles, their own status, their own influence and their organization's wrongdoing will influence the attitude in the long run against each and every organization in society in my opinion.
I know that I was blowing the question out of proportion, but it bugged me to ask anyway.
Re: IBM Cloud was down, as well as their status page
#64Re: IBM Cloud was down, as well as their status page
#65So what are HNers using IBM Cloud for and where do you see that it has an edge over AWS offerings (where an overlap exists, obviously)? (I figure either you’re in devops and you are putting out fires too busy to read this thread or you’re not and your work is halted because of the incident so you might have time to read and reply ;)
Re: IBM Cloud was down, as well as their status page
#66Re: IBM Cloud was down, as well as their status page
#67I 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?
They had bare metal before Packet or AWS and inter-region traffic is free.
Re: IBM Cloud was down, as well as their status page
#68Seems pretty dumb to host a status page in a way that it could go down, when it should be a static page that is trivially hosted on CDN's worldwide.
"Our cloud can never go completely down We are IBM, we have Watson..."
Re: IBM Cloud was down, as well as their status page
#69Earlier quoted context omitted.
Don’t bite or embarrass the hand that provides you make-work... Seriously they probably tested it and it worked in theory, just not in practice and now they fix it for reals.
While that is a solid advice, still it raises the question: is there such organization which corrects itself by firing the incompetent and promoting the competent instead (the "toldyouso" guy in this case)? Or we just simply accept and making it the norm that even the lowest level of organizational governance is corrupt? I am serious about this, because how people perceive their own rights, their own roles, their own…
https://www.ribbonfarm.com/2009/10/07/the-gervais-principle-...
Re: IBM Cloud was down, as well as their status page
#70Honest 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…
I would mirror the attitude of the person who said no originally. If they are receptive to feedback and clearly want to do better, I would be kind and explain why I had suggested it not be there in the first place and cite this as an example. If they were being adamant or denying it was their fault, I'd probably be really quiet and just make subtle remarks about how it would have been better if they listened.
(Was interested to see what you were up to these days, which is how I stumbled on it).