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
Galera has a copule of options to sync mariadb cluster.
Default value is mysqldump which is slow, except for small data-sets, but is the most tested option.
rsync option is much faster than mysqldump on large data-sets.
So add --wsrep_sst_method value.
Change-Id: Ide03801b2472fa3d4f76bbe32e75bf6e618ac7e1
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.
