openstack-helm

mirror of https://github.com/optim-enterprises-bv/openstack-helm.git synced 2025-12-27 18:24:45 +00:00

Files

Pete Birley e7abfee16d MariaDB: Update start script to be more robust

This PS updates the MariaDB start script remove templated values
from being directly inserted into the script. It also moves the
root connection params to a secret to prevent the root password
being exposed in logs.

Change-Id: I10977ef267877a5913bf265280ff5439c7bf268c

2017-07-29 23:05:20 +00:00

templates

MariaDB: Update start script to be more robust

2017-07-29 23:05:20 +00:00

.helmignore

Adding MariaDB

2016-11-18 16:34:36 +01:00

Chart.yaml

Mariadb: Update to use endpoint values layout and lookups

2017-07-03 13:17:48 +00:00

README.rst

Update remaining markdown docs to RST

2017-05-22 10:56:51 +02: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

Update pod affinity to allow customisation

2017-07-28 15:02:47 +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