Unnamed repository; edit this file 'description' to name the repository. https://git.platform-os.org/openstack/kolla.git/atom?h=stable%2F2025.2 2025-06-06T16:40:23+00:00 2025-06-06T16:40:23+00:00 Doug Szumski doug@stackhpc.com 2025-06-06T16:36:53+00:00 urn:sha1:0aaefd2dfeabb18a722fce4002d825671a012671 Since this exporter is no longer developed, and is not used in Kolla Ansible, remove it immediately. A replacement has been proposed in change #951971. Change-Id: Ie47aed221d04bbb2b50ccfbd7c398e6ab6022442 2025-04-22T16:32:38+00:00 Piotr Parczewski piotr@stackhpc.com 2025-03-26T14:34:21+00:00 urn:sha1:ac79bc9b67823eab6d6e9a027a65261096cfcc19 Needed-by: https://review.opendev.org/c/openstack/kolla-ansible/+/945611 Change-Id: I4113976db743d3c5c4ff62f2876e224888f05a36 2024-11-15T08:04:30+00:00 Michal Arbet michal.arbet@ultimum.io 2022-02-15T12:50:59+00:00 urn:sha1:11f65c6c1d3bfd6a12f8e71d778d46d635010449 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 2024-09-02T20:56:03+00:00 Zuul zuul@review.opendev.org 2024-09-02T20:56:03+00:00 urn:sha1:57dd38f365fd7dcd48aab66c219f562a8a1cafc6 2024-08-27T08:20:40+00:00 Bartosz Bezak bartosz@stackhpc.com 2024-08-27T08:20:40+00:00 urn:sha1:a8c7df6ea8b1dee2aa1199f1957384e3718c5317 The cAdvisor update change [1] mistakenly added a reno to the wrong folder. Moving it back to the correct folder would accidentally add it to the master branch. Therefore, the reno is being removed. [1] https://review.opendev.org/c/openstack/kolla/+/704018 Change-Id: I876f3c88c5bcd3c0a7c776796e9870c8512f90e2 2024-08-23T09:10:53+00:00 Bartosz Bezak bartosz@stackhpc.com 2024-08-23T09:10:07+00:00 urn:sha1:a2c07b3c2bdfe16e4f2ebe52616b08189f6b5af7 The prometheus-msteams project is no longer maintained [1]. As a result we are removing its associated container images from our repository. Users are encouraged to switch to the native Prometheus Alertmanager integration with Microsoft Teams [2], which offers ongoing support and features. [1] https://github.com/prometheus-msteams/prometheus-msteams/issues/343 [2] https://prometheus.io/docs/alerting/latest/configuration/#msteams_config Change-Id: I66421b14668722607b58865a2ad100204fd387f7 2024-08-07T14:43:07+00:00 Michal Arbet michal.arbet@ultimum.io 2024-08-07T14:39:27+00:00 urn:sha1:44acae38943185a6bcc6abfad24ba87839fce28a This patch fixed build of prometheus-ovn-exporter when building with --image-name-prefix option. Closes-Bug: #2076249 Change-Id: I5ba67d6e4bbe1b6d6caa842715b56720a027dc76 2024-04-17T06:19:11+00:00 Christian Berendt berendt@osism.tech 2024-02-20T07:55:55+00:00 urn:sha1:986293e9d45b4bb5d18ce9cc942790b248549221 The Tinkoff/libvirt-exporter is archived. Latest release in December 2022. The inovex/prometheus-libvirt-exporter is an active fork that will most probably become a prometheus community exporter in the future [1]. Unfortunately this exporter is not 100% compatible with Tinkoff exporter that we are using currently [2]. [1]: https://github.com/prometheus-community/community/issues/50 [2]: https://github.com/inovex/prometheus-libvirt-exporter/issues/22 Change-Id: Icc8a3651d601ab45d448c9d252ca6155219d21cf 2024-02-21T08:26:52+00:00 Michal Nasiadka mnasiadka@gmail.com 2024-02-14T13:02:50+00:00 urn:sha1:750a137815f1ca58c7e65d23e9d63403ea282b1a Move most curl sources to sources.py, so it can be automatically updated in future. This also makes overriding the versions/locations/sha256 easier. Change-Id: Ib3497fe96162ae190e5c113cacaaa3ef8334f590 2024-02-15T15:57:52+00:00 Doug Szumski doug@stackhpc.com 2024-02-15T15:26:32+00:00 urn:sha1:b276a9cdb52502a9abe1b0f3cf866d952f201b5d - The source code is no longer maintained [1] - HAProxy provides its own Prometheus metrics source [2] - In Kolla Ansible, we have merged support for using the built in metrics source [3] For these reasons, particularly the first, we should remove it immediately. [1] https://github.com/prometheus/haproxy_exporter [2] https://www.haproxy.com/blog/haproxy-exposes-a-prometheus-metrics-endpoint [3] https://review.opendev.org/c/openstack/kolla-ansible/+/877118 Change-Id: Ia30e0fc367841df3726562b57b57df0f6fbb3a81