Darren Birkett d0bb38042e set unique galera server-id ... Each slave in a mysql replication cluster needs to have a unique 'server-id' set. This is an arbitrary integer, and often people select 1,2,3 etc. For easy deterministic uniqueness without needing to look at what you've already used, a simple filter has been created to allow for the hostname to be converted into an integer. The server ID variable has been added to the my.cnf.j2 template and the galera_server defaults/main.yml file. The generation of the server-id variable happens within the `galera-install.yml` play making it so there is no future impact in role requires. Conflicts: playbooks/plugins/filters/osa-filters.py Change-Id: Id15149e59cb03ab268bb3b7eeaf391334dfc0c01 Closes-Bug: #1479484 (cherry picked from commit 9ae6eeca8b)		2016-01-22 16:06:16 +00:00
..
cluster.cnf.j2	Templateize and change Galera SST method	2015-07-27 10:42:15 -05:00
debian.cnf.j2	Convert existing roles into galaxy roles	2015-02-18 10:56:25 +00:00
galera_pin.pref.j2	Add release pinning to galera roles	2015-04-24 16:02:59 +01:00
limits.conf.j2	Convert existing roles into galaxy roles	2015-02-18 10:56:25 +00:00
my.cnf.j2	set unique galera server-id	2016-01-22 16:06:16 +00:00
mysql_defaults.j2	Convert existing roles into galaxy roles	2015-02-18 10:56:25 +00:00