openstack/openstack-helm-infra
Code Issues Proposed changes
9cab29ba0c
openstack-helm-infra/mariadb
History
Zhipeng Liu d82325edf7 Fix ipv6 address cannot be parsed in mariadb-ingress pod 
There is a bug in nginx.tmpl that it will not enclose ipv6
addresses in square brackets resulting in them being unable to
be parsed.

Test pass on both ipv4 and ipv6 simplex setup for StarlingX
project

Change-Id: I16e586f5d8e3dfcb5e94f0486409c9637ba197b2
Signed-off-by: Zhipeng Liu <zhipengs.liu@intel.com>
2020-05-06 01:53:36 +00:00
..
files Fix ipv6 address cannot be parsed in mariadb-ingress pod 2020-05-06 01:53:36 +00:00
templates Fix MariaDB Backup Problems 2020-04-24 14:03:59 +00:00
values_overrides Mariadb: Add ingress network policy overrides 2020-03-17 20:00:42 +00:00
.helmignore MariaDB: Move chart to openstack-helm-infra 2018-09-04 18:57:53 -05:00
Chart.yaml Replace git.openstack.org URLs with opendev.org URLs 2019-05-31 01:52:10 +00:00
README.rst MariaDB: Move chart to openstack-helm-infra 2018-09-04 18:57:53 -05:00
requirements.yaml MariaDB: Move chart to openstack-helm-infra 2018-09-04 18:57:53 -05:00
values.yaml Fix MariaDB Backup Problems 2020-04-24 14:03:59 +00:00

README.rst

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