This patch set is based on [0] that also fixed up a handful of Bionic-
specific changes required for the gates to pass.
[0] https://review.openstack.org/#/c/649698/
Co-Authored-By: ghanshyam <gmann@ghanshyammann.com>
Change-Id: I217a27c53eec2a51ddbea7226a23042558c5946b
This begins to split the fluent-logging chart into two separate
charts, one for fluentbit and one for fluentd. This is to help
isolate each chart and its dependencies better, and to treat each
service as its own entity.
This also moves the job for creating Elasticsearch templates to
the Elasticsearch chart, as the elasticsearch chart should have
ownership of creating the templates for its indices.
This also performs some general cleanup of values keys that are
not currently used
Change-Id: I827277d5faa62b8b59c5960330703d23c297ca47
Signed-off-by: Steve Wilkerson <sw5822@att.com>
This adds the helm-toolkit function for defining the update
strategy for the elasticsearch-data statefulset and sets the chart
default to RollingUpdate
Change-Id: Ia10ea7bf000474e597bdb36778118a96d85b93c1
This updates the ClusterRole object for fluentd by removing a
duplicate rules: key and also adds 'get' to the list of verbs for
the "" apiGroups (as it's required for the kubernetes metadata
plugin)
Change-Id: Ia901d9fe9a0784038f0f882297c64afcce58ca7e
This is to update correct user id in security context for
cephfs provisoner pod as there is no user with 99 exist
in the container.
Change-Id: I1bbe46df555b35b8afe636327fa83015fd784db0
This removes the utilities for generating the fluentd, fluentbit,
and parser configuration files from yaml and moves to instead
consume the configuration files as strings from the values.yaml.
This allows for easier creation and maintenance of configuration
files for fluentd and fluentbit, as the utilities became unwieldy
with complex configuration files.
This necessitated the removal of the core test executed by the
charts helm tests, but this would be required as we move to split
the charts regardless
Change-Id: Ied4a76bbdf58b54a6d702db04a7120b64f54dcac
Signed-off-by: Steve Wilkerson <sw5822@att.com>
This updates the Elasticsearch chart to use the elasticsearch-s3
image built from the openstack-helm-images Dockerfile instead of
using the previous image from a personal repository
Change-Id: I4d6b18aea11920de33ce1f4b63d39c18cd2b98d3
This is to remove invalid key "userSecretName" for
cephfs storageclass as we are having toruble to provision
a pvc with cephfs storageclass with "userSecretName" key .
Failed to provision volume with StorageClass
"cephfs": invalid option "userSecretName"
Change-Id: Ide52987c9f8ef8fc2327bf30747395e70dc05f99
In an Edge environment without a distributed storage environment, it
should be able to store rabbitmq data in the local path as well.
This patch added an option to use it in a more diverse environment.
Change-Id: Ia3c0dfaa58c237e424197f1406bd66fb991bea18
Story: 2005753
Task: 33455
Changed use_local_path_for_single_pod to use_local_path_for_single_pod_cluster
in values.yaml. It was a bug
Change-Id: I88c3fe6c2bbab87baec3ec7d1d94501d6fd741eb
This fixes the elasticsearch-logging service by removing the
LoadBalancer type configuration from the service template. This
was mistakenly added in a previous change
Change-Id: Id2f866147c2dcccc10c83bd54094d54cf3bd227b
There is currently an issue with deploying single
pod mysql clusters in which restarting or killing
the pod will result in a crashloopbackoff.
The mysql data is indeed lost and the start script
(thinking the cluster was alive before
due to the grastate configmap) tries to restore
the cluster instead of bootstrapping it.
Due to this, if the mysql pod is killed or restarted
in the CI, we will lose all the mysql data, will not
recover, and this results in a broken environment.
When volume.use_local_path_for_single_pod.enabled value
is set to true, which we will apply on single node/single
pod testing, this patch will deploy a local volume
for mysql at the location specified under
volume.use_local_path_for_single_pod.host_path
The data will be kept intact in case
there is a pod restart, as it can read the data again,
and recover itself.
When it is false, which is the default for non-CI,
nothing changes, and an empty dir is used. This
data WILL be lost upon restart, so it is advised
to use volumes instead for production purposes,
by setting Values.volume.enabled to true.
task: 28729
Change-Id: I6ec0bd1087eb06b92ced7dc56ff5b6a156aad433
- Update ceph-client chart to
1) By default, enable ceph-client helm test. Update enabler
key in values.yaml to follow pattern as in other charts
2) Add needed dependancy for ceph-client helm tests
3) Update helm test script to reduce output and update
error msgs
4) Removed unwanted ENV variables SPECS and EXPECTED_POOLMINSIZE
- Update gate scripts to run helm test command
Change-Id: I6a0e4f5107e49dac081ac2037bcc0f9c0864793f
Ceph issues a HEALTH_WARN status in cluster log when the available
disk space of the monitor’s data store is lower than or equal to this percentage.
This is to decrease the value from default value 30% to 15%.
Change-Id: Id412969f1dfb08b07356747f13aa31f00b41130d
This removes the use of blkid to find disk partitions and their
associated partition UUIDs. Instead /proc/partitions is parsed
to enumerate disk partitions and sgdisk is used to extract their
partition UUIDs. This prevents a race condition from causing a
deadlock between ceph-osd and krbd when deploying ceph-osd pods.
Change-Id: I875f8c0565ce6efb7cd2052725af37dec3bb3a59
This change creates a snippet in helm-toolkit for specifying
the maxUnavailable and maxSurge values under rollingUpdate for
statefulsets. This can be utilized then by charts that contain
statefulsets.
Change-Id: I6f48cf1d2faf78b56103525771e3d4c3ecdc6db6
We now have a process for OSH-images image building,
using Zuul, so we should point the images by default to those
images, instead of pointing to stale images.
Without this, the osh-images build process is completely not
in use (and completely opaque to deployers), and updating the
osh-images process or patching its code has no impact on OSH.
This should fix it.
Change-Id: Ic00bd98c151669dc2485cd88e0e8c2ab05445959
This PS permits read-only filesystems to back the containers by setting
the default to true
Additionally /run is uniformly applied across all long running pods
as a memory backed emptydir
Change-Id: Ia7344e2c8caa1f25101bf30445cdfe277f89c143
Currently the weight value is hardcoded for anti-affinity type
preferredDuringSchedulingIgnoredDuringExecution. This ps updates
the htk function to retrieve the weight value from the configured
setting if it exists, or default to use the original hardcoded
value of 10 if it is not set (for backward compatibility).
Change-Id: I98c8b05ed7861c9c17e9c32569f53bde6ac2579d
This ps exposes the anti-affinity weight value, including
default, that will be consumed by the updated htk function.
Change-Id: Id8eb303674764ef8b0664f62040723aaf77e0a54
