Synchronise 2023.1 with upstream #515
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Unlike other methods such as resolve(), get() does not return an Undefined object, but None. This removes 4 ansible-lint warnings in various files calling kolla_address. Closes-Bug: #2038281 Change-Id: I591a50512a954210f951c40a350ed4b9e1fc48ae (cherry picked from commit eec8b05)
Use HTTPS to scrape etcd metrics when etcd TLS is enabled. Change-Id: Iaff10d5314a8dc5b07137d93c269f1ac24cf63de Closes-Bug: #2036950 (cherry picked from commit 05df4e7)
When Neutron QoS is enabled, the QoS extension needs to be defined in the sriov_agent.ini file. Closes-Bug: #2041863 Change-Id: Id0de181df06a9e382a1483b32c12a8b5da1b71a9 Signed-off-by: German Espinoza <[email protected]> (cherry picked from commit 38b8f75)
Since switching to use HAProxy to access Prometheus OpenStack exporter, scraping would fail when using internal TLS with an FQDN (rather than an IP address) to access the API. This patch fixes the issue by using the FQDN instead of the VIP address. Change-Id: Iddbdc4190b7953e9140d0740daf57f4062ba1b76 Closes-Bug: #2008208 (cherry picked from commit c283882)
Related-Bug: #2015184 Closes-Bug: #2015184 Change-Id: I6ea0949d58e38e2cda41c9702001e7bd500f23f1 (cherry picked from commit b9f2ad9)
Implements: Kolla Ansible Closes-Bug: #2043554 Change-Id: I5648a79b4aa1960f1984a5179e3dfc3f0982c709
Closes-Bug: #2024554 Change-Id: Id6eae798784126d4dd53adef15bdce6b47b4601f (cherry picked from commit 842e758)
Change-Id: I8f25c7619c45157f6354fb42bf9f28ec194389ed (cherry picked from commit 0cc0624)
Change-Id: Ie3963f5ed20f7fb61ef2e03f0cf12a4ea1c87c9c (cherry picked from commit ba54f8c)
The wrong process name was being used. Closes-Bug: #2046268 Change-Id: I5a5d4f227205e811732331ee6e020ccea67b6fab (cherry picked from commit 693c5c8)
This implements a global toggle `om_enable_rabbitmq_quorum_queues` to enable quorum queues for each service in RabbitMQ, similar to what was done for HA[0]. Quorum Queues are not enabled by default in stable branches backports. Quorum queues are more reliable, safer, simpler and faster than replicated mirrored classic queues[1]. Mirrored classic queues are deprecated and scheduled for removal in RabbitMQ 4.0[2]. Notice, that we do not need a new policy in the RabbitMQ definitions template, because their usage is enabled on the client side and can't be set using a policy[3]. Notice also, that quorum queues are not yet enabled in oslo.messaging for the usage of reply_ and fanout_ queues (transient queues). This will change once[4] is merged. [0]: https://review.opendev.org/c/openstack/kolla-ansible/+/867771 [1]: https://www.rabbitmq.com/quorum-queues.html [2]: https://blog.rabbitmq.com/posts/2021/08/4.0-deprecation-announcements/ [3]: https://www.rabbitmq.com/quorum-queues.html#declaring [4]: https://review.opendev.org/c/openstack/oslo.messaging/+/888479 Change-Id: I6c033d460a5c9b93c346e9e47e93b159d3c27830 (cherry picked from commit 6457551) Signed-off-by: Sven Kieske <[email protected]>
Change-Id: Ibf9a9a0c18938f638c8e8b00b6017c64f1523b23 (cherry picked from commit be5dc32)
Closes-Bug: #2030467 Change-Id: I7646f929b7edc2684102ae1b5927bcc75f0c87c9 (cherry picked from commit df6096d)
…input" into stable/2023.1
We previously used ElasticSearch Curator for managing log retention. Now that we have moved to OpenSearch, we can use the Index State Management (ISM) plugin which is bundled with OpenSearch. This change adds support for automating the configuration of the ISM plugin via the OpenSearch API. By default, it has similar behaviour to the previous ElasticSearch Curator default policy. Closes-Bug: #2047037 Change-Id: I5c6d938f2bc380f1575ee4f16fe17c6dca37dcba (cherry picked from commit 5e5a2dc)
…an be used" into stable/2023.1
…late" into stable/2023.1
mnasiadka
approved these changes
Jan 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains a snapshot of 2023.1 from upstream.