Page Content

How To Deploy a Replication Manager Cluster

This document explains how to deploy a Replication Manager (Repman) cluster. It is an high availability solution to manage MariaDB and MySQL GTID replication topologies. It extends new generation database proxies (ProxySQL, MaxScale) with failover and switchover capabilities.

A cluster of Replication Manager (repman) on SlapOS contains a master database instance with one or many replicated slaves databases instances. ProxySql is deployed within the cluster to manage connections to the master and slaves databases.

This document will explain the different instantiation parameters. Please refer to other documents on add a software to the SlapOS Master catalog or supplying/installing a software

Table of Content

Repman Configuration
Configure Cluster Parameters
Repman Instantiation
Webrunner Connection Parameters
Access to Repman
Repman web Interface
Repman Dashboard Interface
Repman Proxies Overview

Repman Configuration

The process of installing (supplying) a software and providing it as a service (instantiation) are the same for all software. However during instantiation each instance can be configured differently.

This section will cover the specific configuration parameters used for a Repman used for example during tutorials on extending software releases.

Repman Configuration Parameters

After selecting Services, Adding a new service, selecting MariaDB cluster (using RepMan) and the latest release, you should reach the Repman configuration page.

There are two software types available. Default is for deploying the cluster on available node partitions, whereas Replication Manager Database software type will create a new database on existing cluster. Give a name to your cluster, select Default, and fill parameters which describe how to deploy the cluster.

Configure Cluster Parameters

Go to Parameter Entry: Replication Manager Clusters Definition then enter the cluster name, for example: cluster1, then click on + button to expand the cluster parameter form. The cluster name should not contains spaces or any special characters.

Amount of databases for cluster is the number of Mariadb to deploy, the minimal value is 2 (one master and one slave database). The parameter can be changed later only to increase the amount of slaves databases.

Parameters Prefered Master Computer Guid and Slave XX Computer Guid are used to used to indicate on which server the database node will be allocated. If none of Computer Guid is specified, SlapOS will decide where the database instance will be allocated, in this case, it's possible to have two slaves databases or master and slaves databases in the same server.

You can check this documentation to learn how to configure a new server on SlapOS

If required, update others parameters you need then click on Proceed to start instantitation.

Repman Instantiation

You will be forwarded back to the list of deployed services. Note that you might have to refresh the page for your new instance to appear. Once you can see it, click on entry to open the requested instance.

You can follow the compilation by looking at the slapos-node-software.log using:

# tail opt/slapos/log/slapos-node-software.log -f

Webrunner Connection Parameters

SlapOS Interface - Repman Connection Parameters

Once connections parameters are correctly shown and URL entry shows a valid URL, the cluster is up and working. The monitoring of the instance should be also green. Url is for Replication Manager administration interface, default username is admin and you can use repman-password to login to administration interface.

db-root-password is the mariadb root password it can be used to connect to mariadb server as root. database-list will show databasse name of all requested slaves.

Access to Repman

When you go to the URL and provide login and password you should be able to access your Repman admin interface.

Repman web Interface

Deployed cluster1 is showed and the monitoring is green which mean it's running and all promisses are OK.

Repman Dashboard Interface

The dashboard page show all information about the cluster as well as the cluster health and the current SLA.

Repman Proxies Overview

Proxies tab show information and status of deployed ProxySql there is only one proxies for now per cluster.

Adding additional cluster

It's possible to add more cluster to deployed Repman instance. Access your Repman instance parameters, go to Parameter Entry: Replication Manager Clusters Definition and type the name of the new cluster. Click on + to stat to editing. Click on Save button to update parameters. SlapOS will redeploy the cluster with updated parameters.

After few minutes, Repman web interface will show the new cluster.

Thank You

Nexedi SA
147 Rue du Ballon
59110 La Madeleine
France

nexedi.com/contact