The patch deletes deprecated cmd.run function which actually
was defined in salt 2016 as alias for cmd.shell therefore this
change supports backward compatibility.

Change-Id: Idbbf869dfafb39d3bf90cdcb05e626cd563ce8e2
Related-Prod: 17056

There is wrong assumption that when server pillar is
defined the node is galera master, we need to check
actually that it is enabled.

Change-Id: I594c3fbdb1dfc829e7750c2fb1a6d4f5593074b2

When SSL enabled, /etc/mysq directory is created by salt.minion
state with 700 permissions. It prohibits mysql from reading config
file as normal mode is 755. This patch ensures that mode for
/etc/mysql and /etc/mysql/ssl have correct rights.

Change-Id: Icc2a43e7a56c60d30a716f29f0a9ec28c6549429
Related-Prod: ROD-16782

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: Ib5db9f151baaf3fa0bca97a5457cf836bc57b88c

This reverts commit 73fe802ded9054d2a9e18f83b163565ff425a9b3, reversing
changes made to 13c9ec76aa.

This patch fixes broken dependencies installed via
python-mysqldb which needs mysql-common-5.7.

Signed-off-by: Ondrej Vasko <ondrej.vaskoo@gmail.com>

Change-Id: I60e68e7cb4060c1b42789b2b17f21e325d9dfd92

Change-Id: I07624681c53cef53de6c72de97a53b96ea52381b

Change-Id: Ib8850b9251ac5165c25ab08d23a01db4a02fbdae

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

Change-Id: Id0bb8f6b6091289275864bf4dd6a6890d11b4782

Change-Id: Id77cd6da330fe986844b3331edd514819471e67a

Change-Id: I88e3591eaa018406c48dd790ce946a9f783aa758

We need to be sure that enabled param is defined and set to True
during a state applying.

Change-Id: I19cd4c834f254d76d6b521d983d05b227c048065

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

Change-Id: I4de34ad6db6805235966ebcca6fe43ea1faaea42

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: I9daada1cf87873d602d415642bbc4bd32d8e2d52

command called by service.dead state:
systemd-run --scope systemctl stop mysql.service

More common way is to shut down service using known credentials

Change-Id: I2abe7eeea850333139587347039b1de8a6ea486f

Change-Id: Ia6873c44f4e5b179a6c4a545fbf4b45c978812ea

The tag is equal to the address of the server which is quite useless
when using a Unix socket address.

Change-Id: Ia87c30f8ff2176f923982d70b712b10ec6e97f56
Depends-On: I538dbb24602a8ad4aece0a74445db47810099bb9

Change-Id: I34d6d8146489bab30e5ee621e3b8d01fe7ff819b

Change-Id: Iec2d27cc4fdab9ba7772e9c26be66ba54f5aadfc
Depends-On: Ice4f38abfb0d870c56763dfeda2140032fa752a1

Change-Id: I6047d632a2bfeb6525ac60092436ccd5334671e4

Change-Id: I9638c66d1a204a54e25144c4dfe43d5cf5ba135c

Change-Id: I2856f50977b1959801d66e7bc73fe54d24d43801

It comes as dependency from main wsrep packages and it differs
between versions of OS.

Change-Id: I2b50edaa19e52009766bca9fa31c566f59ff9319

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

Change-Id: I295da792349f5864a484e3eb318342dcc31fffab

Change-Id: I91f55d599f5291f34bfa81f55dafd6734606e1cc

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

Bug: After deployment of linux formulas and salt states
/etc/security/limits.conf are not applying, as result connections
to mysql failed with error (pymysql.err.OperationalError)
(1040, u'Too many connections')

Solution: create mysql.overide, where ulimit is set to 102400

Closed-bug: PROD-8427

Because the cluster isn't managed by Pacemaker, using
majority_of_members is misleading.

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