High availability cluster merge

[vtk]

Merged conflicts for feature high-availability-cluster that was implemented by @Squiry with latest master

[pivotal-issuemaster]

@vtk Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

[pivotal-issuemaster]

@vtk Thank you for signing the Contributor License Agreement!

[mp911de]

Thanks for your effort. Creating a PR on top of another PR brings us in a weird situation as the previous PR had several comments attached and it wasn't abandoned.

[vtk]

Thanks for your effort. Creating a PR on top of another PR brings us in a weird situation as the previous PR had several comments attached and it wasn't abandoned.

No problem i can try to fix those comments

[mp911de]

@Squiry what's your opinion on this PR?

[Squiry]

My plan was to rewrite it from scratch since we need some more flexible mechanism of server-picking, so I'm not sure that there's any point in conflict resolving. But if we're going to keep interface as it is right now then we can continue in this PR.

[mp911de]

I'm also in favor of closing this PR. If you plan to rewrite yours, then probably it makes also sense to close #203 and start with a fresh PR.

[mp911de]

Closing this PR without a merge as per the previous comment.