3 ms·
I envy the AWS users who enjoyed the rolling reboots (which were AZ aware!) across a small minority of the EC2 fleet. (~10%, yeah?) At some point on Sunday, I'
by oasisbob 12y ago
I envy the AWS users who enjoyed the rolling reboots (which were AZ aware!) across a small minority of the EC2 fleet. (~10%, yeah?)
At some point on Sunday, I'm going to be picking the pieces of our entire stack.
Rackspace doesn't even offer anything like availability zones.
The last major maintenance they scheduled was over the July 4th weekend -- wasn't happy with that one either.
- lvh 12y agoRe: availability zones; while technically true, I'm not sure that's a fair comparison. Rackspace provides uptime guarantees for the internal network per monthly billing period, and they do actually organize the DC in cells (and yes, they do the roll-outs cell-aware). Those cells are simply not end-user visible (AFAIK).
- notatoad 12y agoif the "cells" aren't visible in such a way that you can distribute your application across them, it doesn't really matter that they exist.
- lvh 12y agoHow so? It seems like a sufficiently smart comp^H^H^H^Hservice could figure out how to distribute machines across them, even if the user doesn't know they exist. Turns out it's a moot point anyway, because cells are client-visible, and have been contributed upstream to OpenStack as a Nova extension.
- oasisbob 12y agoIt's not a moot point. Just because cell info is in Nova doesn't mean it's publicly visible. The only way we find out about cell locality is when our account rep gives us an updated spreadsheet. We've inquired about this several times. If you happen to actually use the Rackspace public cloud and know a specific API call we're missing, I'd love to hear it.
- oasisbob 12y agoFor this particular maintenance, we're being told that Rackspace will be proceeding with all cells in a region, in parallel. They will not be respecting cell boundaries.