| Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: If19d55a88975e6717eec2b9cac9fd28b050028e9
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
|
|
This release fixes multiple security issues [1].
[1] https://github.com/prometheus/prometheus/releases/tag/v3.5.4
Change-Id: I1ec8f15e14360422aa316779bd19195fd1f4f7a1
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
(cherry picked from commit e4114abcdaa604d243da48ea0187fd5673191eb6)
|
|
This release fixes multiple security issues [1].
[1] https://github.com/prometheus/prometheus/releases/tag/v3.5.3
Change-Id: I9f4243a40d0907639324308d84d8a860c1e54941
Signed-off-by: Piotr Milewski <vurmil@gmail.com>
|
|
|
|
|
|
Change-Id: I9d82fbcc26a8a3af2718ea8e1f2e0d87a3523579
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
|
|
Zun is broken in 2026.1, it has been released broken and there are
no reviews on the patch to fix it [1].
[1]: https://review.opendev.org/c/openstack/zun/+/982362
Change-Id: I770b9e62c66f8cc63475d51f80eecacc8415b91f
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
We no longer need to build this from source: aharivel has kindly
responded to our request to create a release:
https://github.com/openstack-k8s-operators/openstack-network-exporter/releases
Needed-By: I35b3bb10aec18a9377515e8c04d2542e712c0f12
Change-Id: Id30cab4e4bbac470f33354870fd941c3ea17815c
Signed-off-by: Doug Szumski <doug@stackhpc.com>
|
|
This exporter comes from https://github.com/openstack-k8s-operators
and will replace the existing OVN exporter which was archived at the
end of 2024.
It can gather metrics from both OVN and OVS based OpenStack clouds.
Change-Id: Idb070d5e5469abd472481f7e19614ee2a78c85d0
Signed-off-by: Doug Szumski <doug@stackhpc.com>
|
|
|
|
Change-Id: I9b6eba0c55fa9914e8db3576127f7d53c13e97d5
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Adds a new prometheus-valkey-exporter image to support
monitoring of Valkey instances.
Change-Id: Id0ad47301e48fc4e2cb1f93865a5c5d58f521467
Signed-off-by: Piotr Milewski <vurmil@gmail.com>
|
|
|
|
* prometheus-alertmanager: 0.28.1 -> 0.31.1
* prometheus-blackbox-exporter: 0.27.0 -> 0.28.0
* prometheus-cadvisor: 0.53.0 -> 0.56.2
* prometheus-elasticsearch-exporter: 1.9.0 -> 1.10.0
* prometheus-libvirt-exporter: 2.2.0 -> 2.3.1
* prometheus-memcached-exporter: 0.15.3 -> 0.15.5
* prometheus-mysqld-exporter: 0.17.2 -> 0.18.0
* prometheus-node-exporter: 1.9.1 -> 1.10.2
prometheus-mtail and prometheus-openstack-exporter were not updated as
there are no later stable releases.
Change-Id: If4f6bed2254f01eb7f9e3aec01cfc81c493ae787
Signed-off-by: Seunghun Lee <seunghun@stackhpc.com>
|
|
Change-Id: I66015b45f2c1f915e1aadc57af9c3d239e9c2472
Signed-off-by: Pierre Riteau <pierre@stackhpc.com>
|
|
Change-Id: I395cfdf22cd87a43294dbae561a8872cb0b48e1b
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
It has been marked as inactive and venus dashboard plugin is breaking
Horizon Kolla builds.
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/964860
Change-Id: I3a04487a75c04ba989fa70f2025db33308671dfb
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
MariaDB clustercheck script has not been maintained and it will not work
with MariaDB 11.4 (the next LTS version).
This is because clustercheck.sh uses ``mysql*`` commands but from
MariaDB 11.4, those commands are not supported.
The health check of MariaDB server containers will be done by new script
which comes with change [1].
Without MariaDB clustercheck, MariaDB server becomes only container image in
the family, so mariadb-base and mariadb-server dockerfiles are merged.
To avoid breaking changes, the name 'mariadb-server' is retained.
Follow-up to rename references in Kolla and K-A from 'mariadb-server' to
'mariadb' would be nice.
[1] https://review.opendev.org/c/openstack/kolla/+/962657
Change-Id: I01278f76ee82b018a854b5862f3caaa8c78a9a30
Signed-off-by: Seunghun Lee <seunghun@stackhpc.com>
|
|
MariaDB clustercheck has not been updated for a long time.
Since the script uses ``mysql*`` commands but MariaDB 11.4 (next LTS version)
does not support them, it will not work once MariaDB gets upgraded.
Added alternative MariaDB container health check script ``healthcheck.sh``
from official MariaDB docker images. [1]
This script uses ``mariadb*`` commands, so it's prone to MariaDB
upgrade.
[1] https://mariadb.com/docs/server/server-management/install-and-upgrade-mariadb/installing-mariadb/binary-packages/automated-mariadb-deployment-and-administration/docker-and-mariadb/using-healthcheck-sh
Change-Id: I7816edb6ebd8c95412a6833ea20b32193c2d1415
Signed-off-by: Seunghun Lee <seunghun@stackhpc.com>
|
|
|
|
This is required for uwsgi module usage
Change-Id: If1a078d2704fbd0b119d6c1ffc5a10aeff0a150a
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Depends-On: https://review.opendev.org/c/openstack/kolla-ansible/+/951864
Change-Id: Ie7e607c5a9c6f8c2e36aea5d52dc2ffbe97dddb3
Signed-off-by: Michal Nasiadka <mnasiadka@gmail.com>
|
|
Updates a range of monitoring and core infrastructure components
to their latest stable upstream versions to leverage new
features and bug fixes.
etcd: 3.5.16 -> 3.6.4
letsencrypt-lego: 4.20.4 -> 4.25.2
prometheus-blackbox-exporter: 0.25.0 -> 0.27.0
prometheus-cadvisor: 0.49.2 -> 0.53.0
prometheus-elasticsearch-exporter: 1.8.0 -> 1.9.0
prometheus-memcached-exporter: 0.15.0 -> 0.15.3
prometheus-mysqld-exporter: 0.16.0 -> 0.17.2
prometheus-node-exporter: 1.8.2 -> 1.9.1
prometheus-server: 3.2.1 -> 3.5.0
The Prometheus-server package has also been switched to
a Long-Term Support (LTS) version, which ensures extended
stability and security support.
Change-Id: Ib9805fb6a93a0da887918174d9994caa5f1306d3
Signed-off-by: Piotr Milewski <vurmil@gmail.com>
|
|
Bumps libvirt exporter source from v1.6.0 to v2.2.0. This fixes some
metrics that were lost when the exporter was changed from the old
"tinkoff" source to "inovex".
See also Icc8a3651d601ab45d448c9d252ca6155219d21cf
Closes-Bug: #2120639
Change-Id: Ib738325603173157b4c482f9de6d5d9cea0b758a
Signed-off-by: Alex Welsh <alex@stackhpc.com>
|
|
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
|
|
|
|
Needed-by: https://review.opendev.org/c/openstack/kolla-ansible/+/945611
Change-Id: I4113976db743d3c5c4ff62f2876e224888f05a36
|
|
* prometheus-alertmanager: 0.28.0 -> 0.28.1
Change-Id: Iec5b936ae77f2d8298803fbfe50f55b2ed69f4b3
|
|
Change-Id: I05a96f27b47a0f87bcf435872dd08ec0927232e3
|
|
Previously, the `pycadf` package did not include
configuration files, so they were manually installed
from source. However, this was fixed in pycadf's upstream
in [1], allowing us to rely on the package itself.
Additionally, the `ceilometer_api_audit_map.conf` file
has been removed, as it was dropped in pycadf's upstream
commit here [2]
[1] https://review.opendev.org/c/openstack/pycadf/+/936741
[2] https://review.opendev.org/c/openstack/pycadf/+/930971
Change-Id: I022aa4c403f08385beb83b5d0c81f8abb42eb4a7
|
|
|
|
This patch also removing copy of
ceilometer_api_audit_map.conf file as it is
now removed [1].
[1] https://review.opendev.org/c/openstack/pycadf/+/930971
Change-Id: I7c086ed5da0e3713ac15aaeaceb38f4a05b84bf0
|
|
prometheus-alertmanager: 0.27.0 -> 0.28.0
prometheus-blackbox-exporter: 0.24.0 -> 0.25.0
prometheus-cadvisor: 0.49.1 -> 0.49.2
prometheus-elasticsearch-exporter: 1.7.0 -> 1.8.0
prometheus-memcached-exporter: 0.14.2 -> 0.15.0
prometheus-mtail: 3.0.0-rc54 -> 3.0.8
prometheus-mysqld-exporter: 0.15.1 -> 0.16.0
prometheus-node-exporter: 1.7.0 -> 1.8.2
prometheus 2.50.1 -> 2.55.1
Co-authored-by: Piotr Parczewski <piotr@stackhpc.com>
Change-Id: I9359df23a41a600dd46dbc1812a54be57fd33f71
|
|
Change-Id: I979df16dea4499b470ce7a4e23df7927a5952aa7
|
|
Closes-Bug: #2091608
Change-Id: I52105f6cbf7529ce107cabf8a38a10525be7435c
|
|
This reverts commit 5af5febf50bc0a02422b437b16598570d0c5ffe3.
Reason for revert: Epoxy cycle is on
In addition to the revert skyline-apiserver aiosqlite u-c
is removed until [1] is merged, designate rootwrap.conf.sample
file has been renamed to rootwrap.conf and pycadf is bumped to 4.0.0.
[1]: https://review.opendev.org/c/openstack/skyline-apiserver/+/935604
Change-Id: I1265633f0913b7927955564fac911a682615004a
|
|
Change-Id: I5f2177b7c2edc0e35ed2e8e9bdfc4be2f262309f
|
|
Change-Id: Ic7cb4e97deb04a82fd73238adbe5b4b74a6a50a0
|
|
This makes Gnocchi work with Redis Sentinel + TLS [1][2].
[1] https://github.com/gnocchixyz/gnocchi/releases/tag/4.6.3
[2] https://github.com/gnocchixyz/gnocchi/releases/tag/4.6.4
Change-Id: Icbd001f1f487b25c4bfd6f6a78106a7f0ed1c8c8
|
|
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
|
|
It has been deprecated in Antelope cycle.
Change-Id: Ie9cc529d186b74ea3d07b0082f9c965d4aa054e9
|
|
|
|
Change-Id: Id64c04ef38bd3084dec05bf58ec10b93344f68ec
|
|
|
|
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
|
|
It's inactive and hasn't produced a 2024.1 release [1].
There are some efforts to restore Freezer, but let's remove it for now.
[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
Change-Id: If2d034789d8c1128597c9072b4e82d14f72492e0
|
|
It's inactive and hasn't produced a 2024.1 release [1].
[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
Change-Id: I387e5c345cd5ea45e9231b9ce5baf58a8d74caf9
|
|
It's inactive and hasn't produced a 2024.1 release [1].
[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
Change-Id: I7b5b032a4175c5390c9b7ff3fbd4c672adcb5325
|
|
It's inactive and hasn't produced a 2024.1 release [1].
[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
Change-Id: Iad4d850ba8f8b8446591cab883d2ad6243576926
|
|
It's inactive and hasn't produced a 2024.1 release [1].
In addition to that, there's a CVE that hasn't really been patched [2].
[1]: https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html#current-inactive-projects
[2]: https://lists.openstack.org/archives/list/openstack-announce@lists.openstack.org/thread/4FYM6GSIM5WZSJQIG4TT5Q3UBKQIHLWX/
Change-Id: Ie715eac24247c38b21382c735eb00a9b3b56f145
|