Skip to content

Instantly share code, notes, and snippets.

@samrocketman

samrocketman/jenkins_high_availability.md

Last active September 16, 2020 14:36
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save samrocketman/7f383087aa4a368ce570aaa21441c7f2 to your computer and use it in GitHub Desktop.
Save samrocketman/7f383087aa4a368ce570aaa21441c7f2 to your computer and use it in GitHub Desktop.
Download ZIP
Researching on Jenkins in a high availability configuration.
Raw
jenkins_high_availability.md

References:

Jenkins HA diagram

A way I could do live disaster recovery across coastal regions to keep Jenkins highly available. The stack in the diagram is documented at -> https://clusterlabs.org/

I'm also researching others' experiences of DRBD over WAN.

If DRBD over WAN is not desirable, then it's quite possible that I could lean on lsyncd as an alternative for synchronizing over WAN.

To support HA I could have agents in both coastal regions (east/west). This way, if a full failover occurs because a datacenter is lost, then I would still be able to depend on half of my agent capacity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment