asynchronous MySQL replication between two different clusters

[Tytus Kurek]

The percona-cluster charm is currently missing a support for asynchronous MySQL replication between two different clusters. In addition to bug 1773160 it makes impossible to replicate databases across geographically-distributed sites. However, according to the upstream community [1] MySQL replication should be used for multi-datacenter deployments, so this bug has a higher priority.

A typical use case would be OpenStack Designate database replication for DNS records replication purpose. I already have an initial patch working. I will submit it for a review once tested and polished.

[1] https://www.percona.com/resources/mysql-white-papers/high-level-multi-datacenter-mysql-high-availability

[Tytus Kurek (tkurek)]

Fix proposed to branch: master
Review: https://review.openstack.org/#/c/576792/

[Tytus Kurek (tkurek)]

I wrote a blog post which describes the implemented feature in details:

http://tkurek.blogspot.com/2018/06/how-to-replicate-databases-between-two_11.html

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/576792
Committed: https://git.openstack.org/cgit/openstack/charm-percona-cluster/commit/?id=e116b1ef869888999560b80a828a52c5807b283f
Submitter: Zuul
Branch: master

commit e116b1ef869888999560b80a828a52c5807b283f
Author: Tytus Kurek <email address hidden>
Date: Wed Nov 21 17:06:22 2018 +0100

    MySQL asynchronous replication

    This patchset implements new relations: "master" and "slave" based
    on a common "mysql-async-replication" interface which are used for
    the purpose on enabling MySQL asynchronous replication between
    multiple Percona XtraDB Clusters.

    Change-Id: I94710bff17091516875c81ca769d8078ef5efd10
    Closes-Bug: 1776171