add documentation for Tempest #1047
Conversation
Signed-off-by: Marvin Frommhold <[email protected]>
depressiveRobot
requested review from
fkr,
garloff and
mbuechse
as code owners
|
@toothstone @berendt @chrisschwa @flyersa @fzakfeld As discussed in the SIG Std/Cert on 2026-01-15, it would be great if you could work together to create instructions on how to install and configure Tempest so that it can be used by all operators for compliance according to SCS-compatible IaaS. I already created all relevant files for the documentation, please add the instructions to the TODO: |
depressiveRobot
requested review from
berendt,
chrisschwa,
flyersa,
fzakfeld and
toothstone
depressiveRobot
added
documentation
| - id: opc-v2022.11 | ||
| name: OpenStack Powered Compute v2022.11 | ||
| url: https://opendev.org/openinfra/interop/src/branch/master/guidelines/2022.11.json |
There was a problem hiding this comment.
I don't think we can just drop OPC like that, that would break the existing versions.
There was a problem hiding this comment.
Now that I've understood that this PR is for now just meant as a guide for passing OPC, I think we should update only the url.
There was a problem hiding this comment.
Good catch, I fixed it.
depressiveRobot
changed the title
Signed-off-by: Marvin Frommhold <[email protected]>
… Powered Compute Co-authored-by: toothstone <[email protected]> Signed-off-by: Marvin Frommhold <[email protected]>
|
I feel like working on this via a PR is rather clunky, maybe we could have the main guide document in a Hedgedoc so everyone can easily contribute? |
Signed-off-by: Marvin Frommhold <[email protected]>
mbuechse
left a comment
mbuechse
left a comment
There was a problem hiding this comment.
I don't understand what's happening here. The goal of #1010 was clear: create a standard that states what we require (and yes, it's only a subset of OPC because OPC was never really feasible, only that no one noticed that) and maybe a supplement that explains how to actually perform the test. What I see now is that a new Docs folder is being created with documents that don't fall under our regular ADR scheme, and this folder is then used by the docs repo (which we control, and so far, we have put docs there), and the YAML file now doesn't reference an authoritative document but some docs page? This is quite irregular.
Caused by #1010.
As discussed in detail in the SIG Std/Cert (see minutes from 2025-07-04 onwards), OpenStack Powered Compute has been deprecated and the repositories have also been deleted. Therefore Tempest should be used as an alternative, which is the official OpenStack integration test suite. This PR updates the documentation accordingly with a step-by-step guide for operators on how to install and run Tempest tests until we will create a separate SCS standard for it.
Further related issues: