Create standard document for “OpenStack Powered Compute v2022.11"

[selis-osba]

The subpage https://opendev.org/openinfra/interop/src/branch/master/guidelines/2022.11.json under OpenStack Powered Compute v2022.11 https://docs.scs.community/standards/scs-compatible-iaas looks different from all the other pages and redirects to another location. This is a bit confusing – please adjust it for consistency.

[mbuechse]

@selis-osba It's already been decided that we do that.

[mbuechse]

BTW the actual reason for this is not consistency, but that we apply modifications to the original specification; see #990

[berendt]

I would like to propose to close this one. I proposed to retire the interop repository: https://review.opendev.org/c/openinfra/interop/+/962130. There is already a +2. I was not yet merged because of not yet merge dependent reviews. But this will be merged in the next weeks or so.

[mbuechse]

We had a discussion about this on Matrix and then in the relevant meetings, and concluded that we wanted to keep using the tests for the time being, albeit potentially in a slightly modified form. We can re-open the discussion for v6 of SCS-compatible IaaS. Come to the SIG again, we would be delighted :)

[berendt]

https://opendev.org/openinfra/interop is now retired. This means that https://opendev.org/openinfra/interop/src/branch/master/guidelines/2022.11.json is not longer available.

[mbuechse]

Thanks for keeping us informed. The final version is to be found at https://opendev.org/openinfra/interop/src/commit/2a71585700b4141910dbd4139805e2c0e9c49a8e/guidelines/2022.11.json

[mbuechse]

This is one more reason for this issue BTW, because then we can explain this situation, where to find the file, how to proceed with the file, and how we intend to handle the situation going forward.

[toothstone]

I discussed the issue at length with @depressiveRobot during last weeks SCS focus session, and we agreed that everything the interop tooling offered for the certification process can be replaced by vanilla Tempest with a SCS-supplied/defined list of tests to run and some basic parsing of the resulting Tempest logs. My understanding was that we upcycle this issue here for the creation of a new standard that puts that into writing.

I suggest we rename this issue to "Create standard document to replace OpenStack Powered Compute".

[mbuechse]

Thanks @toothstone and @depressiveRobot for your commitment here. That is more or less what I meant, only better :)

[toothstone]

Something to include in the implementation notes: What combination of SCS mandated flavors and images can be used for the Tempest nova config section. I don't fully understand it but I was not able to make it work with diskless flavors. Ideally, we follow up on the standard once it's finalized and make Tempest work OOTB with SCS flavor names and SCS image metadata, lowering the barrier for CSPs to assemble a working Tempest config and showcasing the added value of SCS standardization.