This PS adjusts the MariaDB chart to use the same endpoint values
layout as used in other openstack-helm components. It also removes
credentials and params from the configmaps and moves them to secrets
and env vars as appropriate.
Change-Id: I9116be7c46cdd16c743ca2784878f3de65665f8c
Addresses consistency issues that appear with autoincrement fields in
the existing chart, as demonstrated in [1]. It should allow automatic
recovery of 2 out of the 3 (default) cluster members.
It does not address automatic recovery of a complete shutdown of all
cluster nodes.
[1] https://review.openstack.org/#/c/465977/
Change-Id: I84c86e1862f03a6d381bf219b821ea3636049f0b
This can be enabled with:
helm install --name mariadb --set development.enabled=true local/mariadb
This will ensure only a single replica is used and that PVCs (which
require a persistent volume solution) like ceph are not used. Instead
this flag enables a single replica with hostDir storage using the
host path defined in values.yaml which defaults to the following:
/var/lib/openstack-helm/mariadb
This is a major refactor of the mariadb chart. A few things
are accomplished:
* The chart template layout is updated to match our keystone
chart, providing a more structure to the chart.
* The chart was updated to leverage StatefulSets, which requires
Kubernetes 1.5, and helm 2.1.0.
* The bootstrapping process was completely overhauled to support
the unique constraints of statefulsets, namely that they come up
one by one, needing the previous to be in a ready state before
the next is provisioned.
* The references to {{ .IP }} we removed and replaced with POD_IP
environmental passing and address binding was fixed in several
places for wsrep functionality. This may explain several oddities
with the previous setup causing mysterious and intermittent
database consistency issues.
