Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More StackHPC OpenStack tests #1296

Draft
wants to merge 6 commits into
base: stackhpc/2023.1
Choose a base branch
from

Conversation

markgoddard
Copy link
Contributor

  • CI: Add Grafana and OpenSearch Dashboards variables for SOT
  • CI: Add Docker and SELinux variables for SOT
  • CI: Separate monitoring vs host test execution in SOT
  • SOT: Support OpenSearch and Dashboards TLS
  • ci-multinode: Add internal interface to seed
  • DNM: Slim CI, pin sot_version

There are currently two types of tests in StackHPC OpenStack Tests:
service-level tests such as those for monitoring, and host-level tests
such as those for Docker and SELinux. We should execute the
service-level tests from a single remote host, while the host-level
tests should be executed on each of the overcloud hosts.

This means that we now get several results files, so it becomes
important to provide a summary of failures.
This is required for StackHPC OpenStack tests to access OpenSearch and Prometheus.
@markgoddard markgoddard self-assigned this Sep 19, 2024
@markgoddard
Copy link
Contributor Author

This isn't too far off. The aio job has passed. It would take more effort to get it working on a multinode, but is not a million miles away.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant