This also moves joinWithColon to common, so a subsequent commit should remove
the _helpers.tpl template from charts which include common as a dependency.
Without those changes i wasn't able to run glance-post.
Necessary changes in order to make glance-post work.
Signed-off-by: DTadrzak <daniel.tadrzak@intel.com>
* start.sh was added back, which had requiring sourcing
* the naming convention for charts is finalized with this example
landing on configmap-*.yaml to satisfy those of us with OCD
* imagePullPolicies added for init-containers, required by
helm 2.1.0 which does not supply them by default
* imagePullPolicy requirements for init-containers in 1.5
* dependency tree specified mariadb-init, when there is only a
mariadb-seed job to depend on
* the requirements.yaml should not include any chart in this
repository other then common as that severely complicates
removing charts as all dependent elements are removed with it
* the post.sh.yaml has HOME set to /tmp which will not read
/home/ansible configuration. It was unclear if this was by
design, but /home/ansible seems like an important part of the
kolla toolbox
* the post.sh.yaml file had quoting typos, but even when they are
fixed the job/glance-post will not run to completion, complaining
of a missing kolla_keystone_service module
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.
This script allows you to have an single environmental YAML file that can be
chunked up for feeding into various subcharts. This is required as values
input into helm requires the top level namespace be stripped off. In other
words, a flat namespace. This allows a single environmental definition that
can be chunked into YAML files for subchart input.
Usage will be documented on the wiki.
