Over the next few hours I'll be updating the final 3 'remote' nodes JP, DE and NL to the newer 0.13.1 hack
This also includes updating the LTS OS since that's useful to do also.
No one should see any down time.
Basically I just switch the DNS, redirect everyone on JP, DE or NL to another node (after an appropriate wait), then update ... and undo it after.
The final side effect is that everyone currently on JP, DE or NL will end up on NL (that I'll do last) and only switch back to their original node, if it wasn't NL, when they reconnect themselves; since the final redirect will be back to NL from DE and everyone will be on DE by that stage.
No one mining to any other nodes, or the main pool, will be affected at all.
I'll post again when it's all complete.
Completed.
I left everyone from NL on DE coz it avoided a 3rd redirect back to NL of everyone.
90% of NL+DE are on DE, so better not to send everyone back to NL again.
Also there were about 15 users (out of 81) who didn't redirect from DE to NL when I did the DE update.
My guess would be they were connected direct via IP address (and thus cgminer wouldn't redirect)
Edit: So the final step, over the next week leading up to xmas
is testing and then updating the main pool node to 0.13.1
All other nodes are now latest LTS and 0.13.1 core (with segwit disabled)