At 9:20 p.m. Friday night, PST, Rackspace sent out an email to its cloud customers alerting them of planned cloud server resets to start this weekend. This was two days after Amazon Web Services notified its customers. The reason for the do-over was soon determined to be an unspecified Xen issue, a fact that Amazon acknowledged on Thursday, a day after it alerted its users. More here on the Rackspace community page, which posted at 1:01 am. September 27.
Per the [company]Rackspace[/company] email, all standard, performance 1 and performance 2 cloud servers will be affected and Rackspace recommended that customers proactively:
- Verify all necessary services (Apache, IIS, MySQL, etc.) are configured to start on server boot
- Ensure that you have up-to-date server images and file-level backups enabled, and confirm that you have backups of all critical data
- Confirm that any unsaved changes, such as firewall rules and application configurations, are indeed saved
There is more on the Rackspace status page. To recap, on Thursday evening, Rackspace had no statement or response to questions about the Xen issue although it was pretty clear its public cloud — which relies on Xen hypervisor — would be affected.
And there’s the Rackspace reboot email on Saturday morning. They’re giving everybody even less time than AWS did. #rebootthecloud
— darron (@darron) September 27, 2014
For those who did not get the Rackspace email here’s a screen grab showing the tentative schedule:
Cloud pundit Ben Kepes, in a Forbes post, called this an example of how not to respond to a critical fault.