Good to see a clear and detailed explanation, the key to this is people and risk assessment, systems will fail, operators will fail to follow process, these things happen and always will.
The only way to stop issues like this is to have separate people (along with separate systems) for separate regions, you clearly cannot rely on system or process. If different people are accountable for (and limited to) different regions then these multi region issues could be eliminated.
There is a question at 21 minutes about guest clustering, I understand the feature of scale out VM's, this is cool, but is a different subject. I do understand this question was live, so not a criticism. I'm assuming not yet as a share disk would have to be defined and VM's linked to it.
Hi Doug, apologies I could have thought to rewind the video and see the timer you put in python code. Be interesting to know that it performs flawlessly when run very slowly, maybe to help confirm what is happening. Anyway, look forward to the next episode.
Thanks for the tutorial, most helpful. I've just got one question with the demonstration right at the end of the pubsub on sine wave. The listening client was quite noisy (some gaps and some unexpected peaks also) even though the example was run locally.
I'm guessing the issue is that the python script is being run as fast as possible.
If the loop was run on a timer the machine / python interpreter could sustain, then the listener wouldn't have this problem ? or am I missing something else going on.