openstack/kolla.git/docker/grafana, branch stable/2026.1

grafana: install Prometheus datasource plugin

2026-09-16T13:06:37+00:00

Closes-Bug: #2165921 Change-Id: Ib4a0d7185ccc64900b4068dd74995dbf1ba6823c Signed-off-by: Piotr Milewski (cherry picked from commit aece83cc507ac587769ae61d011161d462dafb1d)

Remove deprecated AngularJS plugins from Grafana

2024-12-13T19:13:08+00:00

Change-Id: Id81ce23fed7c19211aa8b15abce185d990be8389

Add mechanism for patching files in containers

2024-11-15T08:04:30+00:00

This patch adds a way to patch files in a Docker image built by Kolla. This is very useful for several reasons, specifically: - Custom modifications - The stable branch of some library has a fix but no pip package has been released - Eliminates the need to package your own pip packages - Eliminates the need to invent your own versioning to prevent upstream versioning - Eliminates the need to manage a pip server - In other words, it eliminates the need to get a wheel into the image and install it manually using any method not previously mentioned It is also highly desirable because, although Kolla can replace the source for a service with a custom URL for a tarball or its own Git repo, it cannot do this for dependencies pulled from pip. I would also like to point out that this is a feature with its own code path and works only if the user "inserts" a patch into the folder patches/docker-image/something.patch and creates an analogous series file for patch source code. Simply said, this code will never interfere with the upstream build process since this feature is not intended for use in upstream. It is rather meant for downstream users who know what they are doing. Now they just have an option to patch their images. Everything works on all layers of the Docker image and stores a report of applied patches which can then be seen in /etc. This mechanism is similar as debian patch quilt. Change-Id: I61d0790c5d4d070b7ea9e8c99c0a76ff5d22bf9d

Change logic for plugins in grafana image build

2024-06-28T00:19:10+00:00

Co-authored-by: Will Szumski Change-Id: I2b1c95395aeefb2ccb1d8edf415eee0f98c52190

Fix missing grafana opensearch datasource

2023-08-21T16:26:10+00:00

The grafana opensearch datasource was missing from the docker image. This commit installs the datasource plugin. Change-Id: Ia3a39c975abf815a66765f2f98c4789d6cec33d7

grafana: remove SHA1 workaround

2023-01-18T06:39:30+00:00

Change-Id: I08fe2827bc58baa95d396daf28de1079e3df4f77

Remove monasca, kafka, storm and zookeeper.

2022-12-06T12:58:10+00:00

Monasca, kafka, storm and zookeeper have been removed in kolla-ansible [1],[2]. [1]: https://review.opendev.org/c/openstack/kolla-ansible/+/861392 [2]: https://review.opendev.org/c/openstack/kolla-ansible/+/865029 Change-Id: I0958a9353bc4585c4f65a1d316328a0e80b0b8b7

grafana: ignore SHA1 gpg key on CentOS Stream 9 (and family)

2022-09-27T08:17:15+00:00

RHEL 9 refuses to use SHA1 gpg keys. Grafana team still did not handled key upgrade: https://github.com/grafana/grafana/issues/41036 Change-Id: Id963271103ce1397b7a5498d032e8f797edfcc70

grafana: drop check for not supported architectures

2022-04-21T18:53:25+00:00

Kolla supports only AArch64 and x86-64 so there is no need to check for other architectures. Change-Id: I44e45492bcbdd56a5c985ba84bad66202c9fde55

Adjust permissions on _extend_start files.

2022-04-11T15:22:24+00:00

Explicitly set the permissions on the kolla-toolbox kolla_extend_start file. Also, since all extend_start files are sourced rather than executed, the executable bits are now cleared throughout the project. Change-Id: I5c2deb4a2e33575d57c852089f856a9acc6818d0