Testing Percona Replication Manager (prm) with Vagrant

If you have recently attended some Percona Live events or if you have checked some slides from Yves Trudeau, you may have heard about Percona Replication Manager (PRM), a new high availability tool for MySQL.


PRM is an OCF Resource Agent for Corosync / Pacemaker that take cares of MySQL and manages the replication.

Corosync allows any number of servers to be part of the cluster using any number of fault-tolerant configurations (active/passive, active/active, N+1, etc.) It also provides messaging between servers within the same cluster.

Pacemaker manages the resources and applications on a node within the cluster.

I have created a Vagrant environment to speed up installation and testing this new solution for HA.

The url of the git repository including the Vagrant file and the puppet recipes is https://github.com/lefred/percona-prm.

You can use the CentOS 6 base box I used in the previous post (Testing Percona XtraDB Cluster with Vagrant).

In the follow “terminalcast” you can see how to deploy the setup and some basic commands to check and manage your cluster:

Share this post

Comments (2)

  • Mark Grennan

    Is the PRM based on Percona’s XraDB cluster? I think I might have blogged a HOWTO about building such a system.


    April 17, 2012 at 1:17 pm
  • Frederic Descamps

    Hi Mark,

    No it’s not, in these setup Percona XtraDB Server is used (but it can be any other MySQL version using standard replication).

    PRM works with “normal” MySQL acting as Master -> Slaves and in case of the master being evicted (intentionally or not) from the cluster the “best” slave will be promoted as Master.

    Your howto seems very interesting and it’s similar to this setup. I know Yves plans to look on how to use MHA with PRM.

    The goal of my approach here it to automate the installation and to allow everybody to test it easily.

    April 17, 2012 at 3:14 pm

Comments are closed.

Use Percona's Technical Forum to ask any follow-up questions on this blog topic.