max_connections were not being applied right.

Adding wsrep_on override to my.cnf

They foobarred quite a bit in there

Change-Id: I4993f997ce3440317a286c8298ded0e96806d5bd

Galera should start normaly after reboot

Change-Id: I4f1bfb0f0ba8ef4f18bc89e8cf2bc6870a2278a2

- changed default logging to log file
- parametrized log file path
- added fluentd configuration
- introduced fluentd multi_format parser plugin

Currently error logs sent to syslog are represented
with severity ERROR, which is misleading for Notice
and Warning messages during service startup/shutdown.

Change-Id: I55106775fa54b412b50ecc10c12930445da15d03
Related-bug: PROD-21904 (PROD:21904)

Change-Id: I378af86d73e7be856abaff677e62bb9407dc8a8b
Related-Bug: PROD-20879

Change-Id: I0360c60b78be6e8ddb7d5438ca2d42da591b6387
Prod-Related: PROD-20079

Change-Id: I64dff4bbbd24985cbd4add62ad9b8e7023b1470c
Closes-Bug: PROD-20079

Change-Id: Ib3b1652ec0c8fd359cfb8008f45b002101885b1b
Closes-Bug: https://mirantis.jira.com/browse/PROD-19688

The following configuration options added:

    galera_innodb_read_io_threads: 8
    galera_innodb_write_io_threads: 8
    galera_wsrep_slave_threads: 8
    galera_xtrabackup_parallel: 4
    galera_error_log_enabled: false

Change-Id: Id1185c3a38669c37dc88806b4e9955522629ce1c
Related-Bug: https://mirantis.jira.com/browse/PROD-16528

PROD-16528

Change-Id: Iacc949fb68e323632e0ed7a60e11c44a9812e724

In case of mysql failed it shows different values for different nodes.
After this fix it ll show actual cluster size

Change-Id: I2fcb23418d6de3e03108a1c66a6ebb6ee5b64008
Closes-Bug: PROD-17416

This patch removes separate state galera.ssl as it was previously
wrongly introduced. Instead include ssl tasks to master/slave when
ssl is enabled.
This fixes missing requirements when applying separate states.
Ensure that mysql package is installed before changing group
ownership for ssl files to mysql, as group will be added by mysql
packages.

Fix ssl inital configuration. SSL settings are not applied during
service reload, we have to add them during initial galera cluster
start.

Change-Id: Iff9a268000c3e5e722cc6e197cfd223ec1015f73
Related-Prod: PROD-16695

Change-Id: I07624681c53cef53de6c72de97a53b96ea52381b

Make max_connections and innodb_buffer_pool_size configurable
through soft params instead of hard.

Change-Id: Id0bb8f6b6091289275864bf4dd6a6890d11b4782

Change-Id: Id77cd6da330fe986844b3331edd514819471e67a

Change-Id: I88e3591eaa018406c48dd790ce946a9f783aa758

The buffer_pool_size parameter should be a integer value when followed
by a memory unit (eg '1024M', not '1024.1M'). Otherwise the MySQL
doesn't start properly.

Change-Id: I5dfad49a8e44a40ae87c5e8e0b033dcd73dc2837

Usage:

  galera:
    master:
      innodb_buffer_pool_size: 1024M
    slave:
      innodb_buffer_pool_size: 1024M

If innodb_buffer_pool_size is not set then 35% of the available
ram will be allocated for the buffer pool.

Change-Id: Iaffa3f5b4ded8bc838f9d707916e360ed873c13b

Change-Id: I34d6d8146489bab30e5ee621e3b8d01fe7ff819b

Because the current timeout interval is too short in some environments.
The change also adds information messages to bootstrap scripts

Change-Id: I295da792349f5864a484e3eb318342dcc31fffab

Galera master installation hangs on installation
mysql-server-wsrep-5.6. It seems that log_error is not working,
because of next message: "mysqld_safe Can't log to error log and
syslog at the same time. Remove all --log-error configuration
options for --syslog to take effect." Using "syslog = yes" instead
of log_error makes it works without any other changes.

Change-Id: I39a8a87ed048557c19f3843b97c75469385e4978
Closes-bug: PROD-9065

This patch enables support for Grafana and provides a new dashboard.

This also installs 2 additional packages (libdbd-mysql and
python-pymysql) that are required for running the collectd plugins.

Conflicts:
	galera/master.sls
	galera/slave.sls