openstack/openstack-helm
Code Issues Proposed changes

Fix a few mariadb README typos

Browse Source
This commit is contained in:
Alan Meadows 2016-12-15 18:10:53 -08:00
parent b56bfa8abf
commit d18cf9fad6
1 changed files with 5 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
mariadb/README.md
View File

@ -2,19 +2,13 @@
By default, this chart creates a 3-member mariadb galera cluster.
This charge leverages StatefulSets, with persistent storage.
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.
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.
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.
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.