This PS removes the licence header from rendered output from tiller,
significantly reducing the configmap size of charts deployed to the
cluster.
Change-Id: I5d1b246f2068f3b83bf59ba79fe8b88bbc9a6161
This PS updates the way helm-toolkit functions are named to
reference the full path they are loacted at. This should make
development and debugging easier. Addtionally unused functions
have been pruned as well.
Change-Id: I03c553f1d01bccc70c86768b416b147c90d9b2f0
Currently, rabbitmq clustering is using the autocluster plugin,
and NODE_TYPE is set to disc in default. so every nodes join cluster as disc node.
However, since there is a need for disc + ram clustering for the performance.
if change node_type from disc to ram, clustering configured as [disc + ram + ram].
Change-Id: Ie83689b0554f0f993bdffac666f0f56db8082992
Implements: blueprint rabbitmq-dns-discovery
Some useful things to note:
1. This uses a StatefulSet instead of a Deployment. The reason for this
is that when RabbitMQ uses DNS for peer discovery, the first thing it
does when trying to join a node is attempt a reverse-dns lookup.
This reverse lookup works when using a StatefulSet, but not a
Deployment.
2. The RabbitMQ configuration was updated to use the new sysctl-style
format. It seems that the new format is required to configure the
new autoclustering features. Additionally, I found that this
generate much clearer error messages than the straight erlang format.
3. I removed the `is-node-properly-clustered` test in the liveness and
readiness probes. This probe isn't directly supported in 3.7.0,
and it wasn't clear that a clustering check was appropriate for each
node.
Change-Id: Ieefbb2205bd77fbac04abcd051fb06fce62e8d97
