859cbbba6c
The problems at the moment with setting up SSL support with Galera are: - The keys are not used when creating users in the mysql_user Ansible module - The private key must be converted to PKCS-1 in order to work properly with Galera. - The MySQL client configuration is missing the settings that include the SSL certificates. - Hard-coding the cipher causes problems for older clients, so we instead enable SSL and let the client and server negociate the ideal cipher. This patch cleans up all of those issues, removes verbose logging from the SSL job because we have ARA to gather all the information we need and adds jobs for all the deployment platforms that we support. Change-Id: I27218c4086a50d238082895092fb8aa5e7fad807 |
||
|---|---|---|
| .. | ||
| cluster.cnf.j2 | ||
| clustercheck.j2 | ||
| debian.cnf.j2 | ||
| galera_secure_node.j2 | ||
| my.cnf.j2 | ||
| mysql_defaults.j2 | ||
| mysqlchk.j2 | ||
| systemd.environment.conf.j2 | ||
| systemd.limits.conf.j2 | ||
| systemd.restart.conf.j2 | ||
| systemd.slice.conf.j2 | ||
| systemd.timeout.conf.j2 | ||
| systemd.without-privatedevices.conf.j2 | ||
| upstart.limits.conf.j2 | ||