Displaying 1 to 3 from 3 results

our-postgresql-setup - PostgreSQL clustering with corosync/pacemaker test environment

  •    Shell

This repo is an extracted version of how we run PostgreSQL clusters at GoCardless.It helps you quickly spin up a 3-node cluster of PostgreSQL, managed by Pacemaker, and proxied by PgBouncer.

hawk - A web-based GUI for managing and monitoring the Pacemaker High-Availability cluster resource manager

  •    Javascript

Hawk provides a web interface for High Availability clusters managed by the Pacemaker cluster resource manager. The current goal of the project is to provide a complete management interface to the HA cluster, both in the form of a flexible REST API as well as a modern client frontend using the API. Hawk is always accessed via HTTPS, and requires users to log in prior to providing access to the cluster. The same user privilege rules apply as for Pacemaker itself: You need to log in as a user in the haclient group. The easiest thing to do is to assign a password to the hacluster user, and then to log in using that account. Note that you will need to configure this user account on every node that you will use Hawk on.

PAF - PostgreSQL Automatic Failover: High-Availibility for Postgres, based on Pacemaker and Corosync

  •    Perl

High-Availibility for Postgres, based on industry references Pacemaker and Corosync. Pacemaker is nowadays the industry reference for High Availability. In the same fashion than for Systemd, all Linux distributions moved (or are moving) to this unique Pacemaker+Corosync stack, removing all other existing high availability stacks (CMAN, RGManager, OpenAIS, ...). It is able to detect failure on various services and automatically decide to failover the failing resource to another node when possible.