openstack-helm/mariadb
Alan Meadows 877e0cd46f aic-helm normalization
* As of helm 2.0.0, it no longer seems necessary to
copy a "globals.tpl" into each child chart, defines in
child charts now seem to be reliably rendered in the
parent.  This was not working correctly in 2.0.0rc2
and so after a lot of testing, the globals define
insertion has been removed from the Makefiles. Also,
includes piped to b64encode are working now, meaning
we no longer have to do Makefile magic to base64
encode successfully.  That has been removed.  Once
.Files.Get works properly in a child chart context
we can remove all Make help.

* The openstack-base chart has been renamed to common
to better reflect that it is common to everything in
aic-helm, even non-openstack projects like ceph.  All
charts now include it as a requirement.

* A first pass at a "cleaner" template directory approach
has been applied to rabbitmq as a test chart.  This allows
files such as _start_rabbit to live in their raw form
and organizes files by config vs script in 'etc' or 'bin'
directories.  If accepted, will apply to all other charts
for consistency.
2016-11-29 16:20:06 -08:00
..
templates General consistency cleanup 2016-11-25 16:27:18 -08:00
.helmignore Adding MariaDB 2016-11-18 16:34:36 +01:00
Chart.yaml Adding MariaDB 2016-11-18 16:34:36 +01:00
README.md Refactor mariadb now that rbd PVCs can be leveraged 2016-11-23 13:26:08 -08:00
requirements.lock aic-helm normalization 2016-11-29 16:20:06 -08:00
requirements.yaml aic-helm normalization 2016-11-29 16:20:06 -08:00
values.yaml General consistency cleanup 2016-11-25 16:27:18 -08:00

aic-helm/mariadb

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

PetSets would be ideal to use for this purpose, but as they are going through a transition in 1.5.0-beta.1 and not supported by Helm 2.0.0 under their new name, StatefulSets, we have opted to leverage helms template generation ability to create Values.replicas * POD+PVC+PV resources. Essentially, we create a mariadb-0, mariadb-1, and mariadb-2 Pod and associated unique PersistentVolumeClaims for each. This removes the previous daemonset limitations in other mariadb approaches.

You must ensure that your control nodes that should receive mariadb instances are labeled with openstack-control-plane=enabled:

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

We will continue to refine our labeling so that it is consistent throughout the project.