This PS moves to use the current ga version for kubernetes daemonsets,
additionally any remaining deployments that were using the
`extensions/v1beta1` have been updated to `apps/v1`.
Story: 2002205
Task: 21735
Depends-On: If9703162dc472af1e6096bf2b9062802fd5ce8ab
Change-Id: Iba4e3d2798c54639e077b80999e669c79b616c6f
Signed-off-by: Pete Birley <pete@port.direct>
This PS moves to use the current ga version for kubernetes deployments.
Story: 2002205
Task: 21735
Depends-On: Icb4e7aa2392da6867427a58926be2da6f424bd56
Change-Id: I062a8a29dff70427ee9bcf09f595011b3611b0b1
Signed-off-by: Pete Birley <pete@port.direct>
This updates the prometheus mysql exporter mysql user job
dependencies to the correct key. It was set incorrectly, resulting
in a circular dependency upon itself
Change-Id: I961924b240b35da4b4a997bdacd189ad870a05b4
When removing helm-toolkit from OSH and swithcing to use the
toolkit from OSH-Infra, the image declaration function was missed.
Depends-On: I2f2012590d81ffcb159d49d8a76eedd4441744cd
Change-Id: I0f1118bb748f3fe1b6bb73acfc00e77c5cca9c7d
Signed-off-by: Pete Birley <pete@port.direct>
This PS removes $dependencies from
- monitoring/prometheus/exporter-deployment.yaml
- monitoring/prometheus/exporter-job-create-user.yaml
as $dependencies cause render error.
Change-Id: I38e176d25f735c9a6712497d20a3310e438a48a1
This PS adds the local registry image managment to OSH from OSH-Infra.
With this the delta between helm-toolkits in the Repo's is removed,
allowing the toolkit from OSH-Infra to be used and the one from OSH
to be depreciated.
Change-Id: If5e218cf7df17261fe5ef249d281f9d9637e2f6a
Co-Authored-By: Pete Birley <pete@port.direct>
This PS adds a fronting tcp proxy with A/P to the backends. This
Change removes the issue of DB deadlocks when using multi-master
galera databases.
Change-Id: I3294d4e9d9258a98692292fa5da16505bfa9ecd6
This patch set tidies up the existing charts. Fixes include:
* add release_group key in yaml
* fix indentation inconsistency issue
* clean up the ldap chart's value.yaml to be consistent with mariaDB
Change-Id: Ibd9d86603ebc6c6c31c596dc0af523eb71c083d0
Signed-off-by: Tin Lam <tin@irrational.io>
Move to v0.3.1 of kubernetes-entrypoint which has 2
breaking changes to pod dependencies, and also adds support for
depending on jobs via labels.
Change-Id: I49d2cea11fbe5c5919ae22a020b877ebbb285992
Recent versions of MariaDB (10.1.31, 10.2.13) have a regression that
breaks clustering. See https://github.com/MariaDB/server/pull/457 and
4e6dab94d0
for an in depth explanation.
We need 10.2.13+ for Barbican to function correctly (see bug #1734329)
but we also need the fix above to support MariaDB clustering.
This work-around can be removed later on when MariaDB 10.2.x releases
contain the needed script fix.
Thanks to Sam Yample <sam@yaple.net> for helping track this down.
Change-Id: Ifd09d7effe7d382074ca9e6678df36bdd4bce0af
This reverts commit 81bf5f3656f12b6f8279329edcf91ef63e7a6b5f back to
MariaDB 10.1.23 which we know works with clustering enabled
(pod.replicas.server > 1).
Change-Id: Ibf70dbab78f03d32e1ec96e99ac8db59d23cb96e
This version is already being used by some charts, so this brings the
rest of the charts in line and allows them to use a new feature,
pod dependencies, that this version provides.
Change-Id: Ie8289eb09b31cd8f98c2c5b4dd5bbe469078e6d8
There was a bug in MariaDB 10.2.12 and lower, that prevent
upgrade DB schema for Openstack Barbican service.
Change-Id: Ib47d1c5060d93f63ac9d4f7d32b25642d801dd15
Closes-Bug: 1734329
This PS moves static dependencies under a 'static' key to allow
expansion to cover dynamic dependencies.
Change-Id: I38990b93aa79fa1f70af6f2c78e5e5c61c63f32c
This PS moves the default image in OSH for most services to use LOCI
and also provides a Kolla gate for newton openstack.
Change-Id: Ice6cb9f89bc3ce6e8280e580d215aedda9e71904
* Changed podManagementPolicy to parallel in order to allow recovery
from secondary or third master
After rebooting the whole cluster on purpose or after a power failure
a primary node the cluster can synchronize with is required. This is
usually done automatically by selecting the node with the highest
transaction id. The current implementation of the stateful set starts
the nodes in sequence, preventing the start of further nodes if the
process terminates with error state. Because of this, the cluster may
not come up if the first or second node are not in primary state.
* Elects first node started in primary state as bootstrap source.
* Display warnings and runs mysqld with wsrep-recover on crashed nodes
* Introduces FORCE_RECOVERY argument for crash recovery
In case the primary selection failed, the cluster bootstrap process
must be manually initiated from the most advanced node (highest
committed transaction id). This information is available from the
grastate.dat file in case of a clean shutdown. On crashed nodes an
InnoDB recovery is required to get the last committed transaction id.
start.sh will handle both cases and gives instructions on how to
recover the cluster on a hard failure. If FORCE_RECOVERY was set to
the name of a POD (mariadb-0, mariadb-1, ...), the bootstrap process
will be initiated from the specified node.
DocImpact
Closes-Bug: #1716461
Change-Id: I96a8cb52124f64920a7d9cf21a8924ede78ebf7b
kubernetes does clustering for us and with persistent robust PVs
clustering of mariadb isn't useful for most people by default
Change-Id: I460c00c141ffe7d93af5ec09d1599cb8eaa9dcf7
Remove 'connect_timeout' which defined in the '[client]' section which
surprisingly affects mysqldump by causing it to fail as it doesn't
understand this; we're not doing anything that depends on having this
value so this is safe.
This now means mysqldump works (as expected) and we can use the
packaged/pod version of mysqldump for backup purposes.
Change-Id: I9142969e4b8576b19353c063586dd11f91875f0b
LocalWords: mysqldump
This moves the prometheus exporters for services into a directory
in the chart themselves. This keeps the monitoring services
coupled to the services theyre meant to monitor. This changes the
chart directory structure to include a monitoring/ directory to
host any monitoring requirements (not just prometheus exporters)
Change-Id: Ic5f46a7e9a2a773a837ff399b8730782cf89f1de
This PS enables storage ownership management on pod start, which
is required for some PVC providers/provisioners.
Change-Id: Idb4bd20104815efb241ed163daddf27f8bd2b559
This reverts commit 4675a2a63dc23935f491e0205333c897ea594ff8.
Until the following is fixed, we should stick with 10.1:
* https://bugs.launchpad.net/barbican/+bug/1734329
Change-Id: If62b527efefeda7dfa10324562916d2054d8889e
This PS simplifys the db start and init script, increasing
robustness of the mariadb chart on low end hardware. It also
removes some unrequired annotations and moves to more explicit
qualification of the clustering variables.
Change-Id: I6cff5fb6ccfdcc6c82203b0e5eff445ee98bc298
This ps brings mariadb inline with the other charts in openstack
helm. It organizes the values trees, removes an unused duplicate
resource tree, and adds the keys for enabling specific manifests
Change-Id: I6f331d51802968620da18b687dc2f9dfa58cdd79
This PS updates the values file layout for images to allow simple
parsing of the images in use by charts, allowing them to be queried
and modified much more simply. By moving the image tags to a 'tags'
key, we can extend the options used simply to accomodate extra
options simply (eg prefixing the tag for use with an internal
registry) or pre-pulling the images to reduce chart deploy failure.
Change-Id: I9ec1dbb00d997ab6cb021bf0b698f7aae740e95d
Give mariadb time to start up and probe only as much as needed. This
avoids premature health warnings.
Change-Id: I5427cb26dc6a788123bdfac925e6d94321aabb1f
Kubernetes 1.8 is stricter about the feilds in a secrets manifest,
this PS updates OpenStack-Helm to be compliant.
Change-Id: I9e19d07060d8517e0f4fd3056013191b1b4ba2da
This PS adds namespace and fqdn support to endpoint lookup functions,
it also permits over-riding of the puplic endpoint for ingress.
Change-Id: Ib61c5c00a214d75fe85fbffe9080c2ae88bd8cb9
Correct some spelling errors in files ：
mariadb/templates/etc/_00-base.cnf.tpl,tools/gate/funcs/kube.sh
Change-Id: Ie6d7f2b90a8d569663452d00565af2789bbb377e
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 MariaDB start script remove templated values
from being directly inserted into the script. It also moves the
root connection params to a secret to prevent the root password
being exposed in logs.
Change-Id: I10977ef267877a5913bf265280ff5439c7bf268c
Fixes the reference to mariadb replicas used when adding pods to
the mariadb cluster. This was causing nodes to not be added to
the cluster properly
Change-Id: I9df586c8939e241ea58d933652c767542fd364ff
This PS updates the pod affinity function to allow customisation by
operators at the point of deployment.
Change-Id: I8b7b2f584e990e068051d9a6d5cc7b1e1adb5aa5
This enhances the stability and recovery of ceph by leveraging
hostNetworking for monitors as well as OSDs, and enables the
K8S_HOST_NETWORK variable within ceph-docker. This enhancement should
allow recovery of monitors from a complete downed cluster.
Additionally, ceph's generic "ceph-storage" node label has been
split out for mon, mds, and osd.
Co-Authored-By: Larry Rensing <lr699s@att.com>
Change-Id: I27efe5c41d04ab044dccb5f38db897cb041d4723
This PS move s the replicas key to be under the pod key in the values.
It brings further consolation of related configuration params to be
nested under common keys across all charts.
Change-Id: I420b06debd0a62ba5d83497be43ff6c49c49d339
This patchset enforces stricter file permission on *-etc configmap and
sets readOnly flag to true in a number of charts.
Change-Id: I233689a5d56dd1352e0d81997a94b4cdd6bed5d2
Signed-off-by: Tin Lam <tin@irrational.io>
