Sync from Antelope to Caracal #1198
Merged
Conversation
This file contains hidden or 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
This change adds a new playbook, stackhpc-openstack-tests.yml, that uses the new stackhpc-openstack-tests repository to perform testing of the deployment that is not covered by Rally or Tempest. Currently this includes Prometheus and OpenSearch. The all-in-one CI test has been updated to run this new test suite, and the results are included in the test results artifact.
Previously an erroneous 'False' was appended to the artifact name.
For clouds that use an internal CA, it is necessary to provide a CA certificate to OS capacity. Co-Authored-By: Jake Hutchinson <[email protected]>
AIO Improvements
OS Capacity: Support providing a CA certificate
zed: yoga merge
A custom list of container images can be synced to the local Pulp using the stackhpc_pulp_repository_container_repos_extra and stackhpc_pulp_distribution_container_extra variables.
This fixes failures of the Kolla image build GitHub workflow.
Support synchronising custom container images
Add alerts for low available swap space
CI: Pin requests below 2.32.0
By default, kayobe-automation uses CentOS Stream 8 as the base image for its kayobe docker image. As it doesn't support python 3.8 (a requirement for the Zed release), it must be overridden to use Rocky Linux 9. (cherry picked from commit bc87579)
Inputs are not available to workflows triggered by a push. Apply a default to the base image. (cherry picked from commit 359ee38)
yoga: Use Rocky Linux 9 as a base for kayobe-automation
This brings in a useful idempotency fix for Vault deployment.
This change modifies the overcloud HashiCorp Vault playbooks to use the local Vault service rather than via HAProxy. This makes it possible to deploy and use Vault without HAProxy. This eliminates the previous bootstrapping issue where HAProxy needed to be deployed without TLS enabled while generating initial certificates. To make this work in environments with a proxy configured, https_proxy is overridden.
In the previous HAProxy config for Vault, 200, 501 and 503 were treated as healthy. This allowed for bootstrapping Vault via HAProxy, but made standby backends appear as unhealthy, leading to a Prometheus alert. We no longer bootstrap Vault via HAProxy, so we can treat 200 (active) and 429 (standby) as healthy. Co-Authored-By: Dawud Mehmood <[email protected]>
Typically the certificate is only valid for the FQDN. This will not cause a problem usually because the internal API generally uses the VIP directly rather than an FQDN.
Removing angular based dashboards
Make packet drop alert configurable
In Yoga and Zed there are 2 tests that fail due to using internal TLS but no external TLS. This breaks some URLs in API responses. This change adds them to skip lists. This should be reverted in Antelope, since it supports external TLS in multinodes.
This brings in a useful idempotency fix for Vault deployment. (cherry picked from commit bf535c6)
Upgrade loadbalancer dashboard to move away from angular
A similar change was made for Ubuntu systems in #1119, but it did not apply to Rocky 9 systems. This changes brings the two into line.
Stop changing permissions on files on Rocky 9
yoga: Bump stackhpc.hashicorp & multinode skip lists
This reverts commit ab2a532. It does not apply to Antelope since external TLS is supported in multinode.
We've been running out of space when testing upgrades in Multinode. (cherry picked from commit 3413960)
This should allow for more space for Docker images and volumes.
zed: yoga merge
2023.1: zed merge
yoga: Reduce multinode LVM volume sizes
Updating Rocky 9.4 only.
2023.1: zed merge
Fix hyperlink syntax in release notes
Rocky Linux 9.4 support
markgoddard
approved these changes
Jul 25, 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.
Sync PR to bring new changes in Antelope to Caracal, mainly RL 9.4 support.
Please ignore some Antelope configurations appearing. There's work going on the branch kolla-config-2024.1 to update all Antelope config to Caracal, that is planned to be rebased after this PR is merged.