openstack/openstack-helm
Code Issues Proposed changes
d4f7fa5775
openstack-helm/mariadb
History
Seungkyu Ahn d4f7fa5775 Add galera sync method option 
Galera has a copule of options to sync mariadb cluster.
Default value is mysqldump which is slow, except for small data-sets, but is the most tested option.
rsync option is much faster than mysqldump on large data-sets.
So add --wsrep_sst_method value.

Change-Id: Ide03801b2472fa3d4f76bbe32e75bf6e618ac7e1
2017-04-24 02:07:19 +09:00
..
templates Add galera sync method option 2017-04-24 02:07:19 +09:00
.helmignore Adding MariaDB 2016-11-18 16:34:36 +01:00
Chart.yaml Update chart.yaml to be consistent across repo 2017-04-16 11:21:07 -05:00
README.md Corrected project name in README files 2017-04-12 15:31:38 -05:00
requirements.yaml Rename common chart, and update all references to functions within it. (#167) 2017-02-14 16:52:38 -08:00
values.yaml Add galera sync method option 2017-04-24 02:07:19 +09:00

README.md

openstack-helm/mariadb

By default, this chart creates a 3-member mariadb galera cluster.

This chart leverages StatefulSets, with persistent storage.

It creates a job that acts as a temporary standalone galera cluster. This host is bootstrapped with authentication and then the WSREP bindings are exposed publicly. The cluster members being StatefulSets are provisioned one at a time. The first host must be marked as Ready before the next host will be provisioned. This is determined by the readinessProbes which actually validate that MySQL is up and responsive.

The configuration leverages xtrabackup-v2 for synchronization. This may later be augmented to leverage rsync which has some benefits.

Once the seed job completes, which completes only when galera reports that it is Synced and all cluster members are reporting in thus matching the cluster count according to the job to the replica count in the helm values configuration, the job is terminated. When the job is no longer active, future StatefulSets provisioned will leverage the existing cluster members as gcomm endpoints. It is only when the job is running that the cluster members leverage the seed job as their gcomm endpoint. This ensures you can restart members and scale the cluster.

The StatefulSets all leverage PVCs to provide stateful storage to /var/lib/mysql.

You must ensure that your control nodes that should receive mariadb instances are labeled with openstack-control-plane=enabled, or whatever you have configured in values.yaml for the label configuration:

kubectl label nodes openstack-control-plane=enabled --all