Thread regarding IBM layoffs

Great news!

I say it's just about time for another town hall to BS all the id--t sheep again.

“We sincerely apologize for any inconvenience that this incident may have caused” Just think of the revenue lost from IBM customers outage! .. Since IBM has laid off all their most talented talent and replaced them with junior, On the cheap Indians... what can you expect! Their the Blockbuster video of IT. Yet, a complacent Board of Directors continue to keep a Captain who obviously ran into a iceberg many miles ago at the helm! Albeit berkshire hathaway and many other investors wished they had never heard of Indian Business Machines!

IBM reveals how it broke its own cloud

IBM reveals how it broke its own cloud

IBM has revealed the causes of a three-hour service disruption in July that saw its consoles either perform painfully slowly or become unavailable.

An “Incident RFO” (reason for outage) document sent to customers explained that “… while conducting maintenance on internal systems, IBM Cloud Engineers inadvertently restarted some Virtual Server Instances (VSIs) which were hosting applications for customer accounts.”

Clouds are supposed to be rather more resilient than that, so the start of the incident signals a certain immaturity in the Big Blue cloud.

The explanation continues: “Once the VSIs completed their restarts, several of the services on the VSIs did not automatically restart and were preventing customers from accessing their accounts, logging in to their consoles or receiving timeout errors.”

Again, this is not the kind of thing one expects from a top-tier cloud. And the explanation gets even worse, for IBM, by revealing that “IBM Cloud Engineers began investigating and determined several VSIs were attempting to connect to the same API server which had an improper configuration.”

Which sounds like IBM’s cloud all-but-DDoSed itself, and did so to a server that both wasn’t ready to handle the traffic coming its way and didn’t failover to another resource.

IBM staffers eventually figured things out and restored service. Fortunately, the incident took place on a Sunday, US time, so many users would have been spared the problem.

“To prevent future instances,” the RFO concludes, “IBM cloud engineers have updated the build documentation and have instituted code to prevent all VSIs from restarting at the same time to prevent the API server from becoming overloaded.”

“We sincerely apologize for any inconvenience that this incident may have caused” is the signoff in the incident report."

Big Blue’s cloud does have impressive global presence, but analysts rate it as lagging rivals in terms of both features and suitability for enterprise use. A major rebuild of the cloud is in the works, but is many months behind schedule. Mistakes such as those that led to this incident must surely therefore be very unwelcome as IBM prioritises cloud products.

IBM Cloud is dying.

But the Board is blind & deaf.

What to say, what to say??? I am speechless...