Merge branch 'test'

Author: maxadamo

README.md

@@ -1,152 +1,15 @@
 # galera_maxscale
 
-#### Table of Contents
+#### Module Deprecation Notice
 
-1. [Description](#description)
-1. [Setup - The basics of getting started with galera_maxscale](#setup)
-    * [Beginning with galera_maxscale](#beginning-with-galera_maxscale)
-1. [Usage - Configuration options and additional functionality](#usage)
-1. [Reference - An under-the-hood peek at what the module is doing and how](#reference)
-1. [Limitations - OS compatibility, etc.](#limitations)
-1. [Development - Guide for contributing to the module](#development)
+Please consider using the new module [galera_proxysql](https://forge.puppet.com/maxadamo/galera_proxysql).
 
-## Description
+The new module makes use of Percona instead of MariaDB.
 
-This module sets up and bootstrap Galera cluster and optionally MaxScale Proxy.
-The status of the cluster is checked at run time through the fact `galera_status` and puppet will attempt to re-join the node in case of disconnection.
-If puppet fails to recover a node you can use the script `galera_wizard.py` provided with this module.
-MaxScale Proxy will be set up on 2 nodes (no more, no less) with Keepalived.
+I came to this decision after having observed the followings:
 
-- if you want only the Galera cluster you need _at least_ 3 servers and 3 ipv4 (and optionally 3 ipv6)
-- if you want the full stack you need _at least_ 5 servers and 6 IPv4 (and optionally 6 IPv6)
-
-Initial State Snapshot Transfer is supported only through Percona XtraBackup (on average DBs I see no reason to use `mysqldump` and `rsync` since the donor would be unavailable during the transfer: see [Galera Documentation](http://galeracluster.com/documentation-webpages/sst.html)).
-The backup provided with this modules is indeed poor, but it can be considered as an example if you want to start using Percona XtraBackup.
-
-**When bootstrapping, avoid running puppet on all the nodes at same time.** You need to bootstrap one node first.
-
-**stay tuned:** since the module is at an early stage, for the time being it will receive frequent updates.
-
-
-Read at (actual) **limitations** in the paragraph below.
-
-
-## Setup
-
-### Beginning with galera_maxscale
-
-To setup Galera:
-
-```puppet
-class { '::galera_maxscale':
-  root_password    => $root_password,
-  sst_password     => $sst_password,
-  monitor_password => $monitor_password,
-  maxscale_hosts   => $maxscale_hosts,
-  maxscale_vip     => $maxscale_hosts,
-  galera_hosts     => $galera_hosts,
-  trusted_networks => $trusted_networks,
-  manage_lvm       => true,
-  vg_name          => 'rootvg',
-  lv_size          => $lv_size;
-}
-```
-
-To setup MaxScale:
-```puppet
-class { '::galera_maxscale::maxscale::maxscale':
-  trusted_networks => $trusted_networks,
-  maxscale_hosts   => $maxscale_hosts,
-  maxscale_vip     => $maxscale_vip,
-  galera_hosts     => $galera_hosts;
-}
-```
-
-Once you have run puppet on every node, you can manage or check the cluster using the script:
-```
-[root@test-galera01 ~]# galera_wizard.py -h
-usage: galera_wizard.py [-h] [-cg] [-dr] [-je] [-be] [-jn] [-bn]
-
-Use this script to bootstrap, join nodes within a Galera Cluster
-----------------------------------------------------------------
-  Avoid joining more than one node at once!
-
-optional arguments:
-  -h, --help                 show this help message and exit
-  -cg, --check-galera        check if all nodes are healthy
-  -dr, --dry-run             show SQL statements to run on this cluster
-  -je, --join-existing       join existing Cluster
-  -be, --bootstrap-existing  bootstrap existing Cluster
-  -jn, --join-new            join existing Cluster
-  -bn, --bootstrap-new       bootstrap new Cluster
-  -f, --force                force bootstrap new or join new Cluster
-
-Author: Massimiliano Adamo <maxadamo@gmail.com>
-```
-
-## Usage
-
-The module will fail on Galera with an even number of nodes and with a number of nodes lower than 3.
-
-To setup a Galera Cluster (and optionally a MaxScale cluster with Keepalived) we need a hash. If you use hiera it will be like this:
-
-```yaml
-galera_hosts:
-  test-galera01.example.net:
-    ipv4: '192.168.0.83'
-    ipv6: '2001:123:4::6b'
-  test-galera02.example.net:
-    ipv4: '192.168.0.84'
-    ipv6: '2001:123:4::6c'
-  test-galera03.example.net:
-    ipv4: '192.168.0.85'
-    ipv6: '2001:123:4::6d'
-maxscale_hosts:
-  test-maxscale01.example.net:
-    ipv4: '192.168.0.86'
-    ipv6: '2001:123:4::6e'
-  test-maxscale02.example.net:
-    ipv4: '192.168.0.87'
-    ipv6: '2001:123:4::6f'
-maxscale_vip:
-  test-maxscale.example.net:
-    ipv4: '192.168.0.88'
-    ipv4_subnet: '22'
-    ipv6: '2001:123:4::70'
-```
-
-If you do not use ipv6, just skip the `ipv6` keys as following:
-```yaml
-galera_hosts:
-  test-galera01.example.net:
-    ipv4: '192.168.0.83'
-  test-galera02.example.net:
-    ipv4: '192.168.0.84'
-  test-galera03.example.net:
-... and so on ..
-```
-
-you need an array of trusted networks/hosts (a list of ipv4/ipv6 networks/hosts allowed to connect to MySQL socket):
-```yaml
-trusted_networks:
-  - 192.168.0.1/24
-  - 2001:123:4::70/64
-  - 192.168.1.44
-... and so on ...
-```
-
-## Reference
-
-
-
-## Limitations
-
-- minor version supports only latest and installed (in other words, only major versions are supported)
-- init script management can be improved
-- not yet tested on ipv4 only (it should work)
-
-## Development
-
-Feel free to make pull requests and/or open issues on [my GitHub Repository](https://github.com/maxadamo/galera_maxscale)
-
-## Release Notes/Contributors/Etc. **Optional**
+1. percona repository is still needed to use percona tools
+1. the preferred method for SST is Percona-extrabackup
+1. maxscale started throwing coredumps
+1. a bug in the extrabackup-v2 script appeared all of a sudden and I had to roll-back to extrabackup
+1. With Percona only 1 repository is needed. With MariaDB 3 repositories were needed (1 for Percona, 1 for MariaDB, 1 for MaxScale).

files/client.cnf

@@ -4,11 +4,6 @@
 #
 
 [client]
-socket=/var/lib/mysql/mysql.sock
+socket = /var/lib/mysql/mysql.sock
 # commenting out prompt as it cause mysqladmin failure
 # and script status will not work
-
-# This group is not read by mysql client library,
-# If you use the same .cnf file for MySQL and MariaDB,
-# use it for MariaDB-only client options
-[client-mariadb]

templates/clustercheck_script.erb renamed to files/clustercheck

@@ -10,7 +10,7 @@
 # Based on the original script from Unai Rodriguez
 #
 
-source <%= @config_dir %>/clustercheck
+source /etc/sysconfig/clustercheck
 
 if [[ $1 == '-h' || $1 == '--help' ]];then
     echo "Usage: $0 <user> <pass> <available_when_donor=0|1> <log_file> <available_when_readonly=0|1> <defaults_extra_file>"

files/my.cnf

@@ -0,0 +1,11 @@
+#
+# The Percona XtraDB Cluster 5.7 configuration file.
+#
+#
+# * IMPORTANT: Additional settings that can override those from this file!
+#   The files must end with '.cnf', otherwise they'll be ignored.
+#   Please make any edits and changes to the appropriate sectional files
+#   included below.
+#
+#!includedir /etc/percona-xtradb-cluster.conf.d/
+!includedir /etc/my.cnf.d/