[all][ops][qa] Decommissioning RefStack and retiring related software
The RefStack service at refstack.openstack.org has been unused for purposes of qualifying OpenStack trademark licenses[*] since March of last year, after a 2023 board resolution[**] relaxed the former requirement for it. Effective immediately, the service is being decommissioned along with any associated resources, and the related Git repositories in OpenDev (interop, refstack, refstack-client) will be officially retired in the near future as well. Let me know if you have any questions or concerns. [*] https://openinfra.org/legal/trademark-policy [**] https://board.openinfra.org/meetings/minutes/05122023BoardMinutes -- Jeremy Stanley on behalf of the OpenInfra Foundation
On Wed, 30 Jul 2025 at 21:11, Jeremy Stanley <jeremy@openinfra.dev> wrote:
The RefStack service at refstack.openstack.org has been unused for purposes of qualifying OpenStack trademark licenses[*] since March of last year, after a 2023 board resolution[**] relaxed the former requirement for it. Effective immediately, the service is being decommissioned along with any associated resources, and the related Git repositories in OpenDev (interop, refstack, refstack-client) will be officially retired in the near future as well.
Let me know if you have any questions or concerns.
[*] https://openinfra.org/legal/trademark-policy [**] https://board.openinfra.org/meetings/minutes/05122023BoardMinutes -- Jeremy Stanley on behalf of the OpenInfra Foundation
Are the test lists formally available from RefStack, such as version 2022.11, still available somewhere? It was useful to be able to run a focused Tempest test suite to quickly validate core functionality of an OpenStack deployment.
On 2025-08-04 16:51:31 +0200 (+0200), Pierre Riteau wrote: [...]
Are the test lists formally available from RefStack, such as version 2022.11, still available somewhere? It was useful to be able to run a focused Tempest test suite to quickly validate core functionality of an OpenStack deployment.
If you're talking about the interop guidelines, the repository hasn't been retired yet but even once it is the files will still be available from its history forever, e.g.: https://opendev.org/openinfra/interop/src/commit/2a71585/guidelines/2022.11.... I see the RefStack API has some sort of filtering mechanism for retrieving a list of tempest tests with refstack-client, and no that won't be reachable any longer with the service itself offline. That said, I haven't actually turned the service off yet but I see that it's unresponsive... the last entry in its API log is from 2025-07-08 so I think it took itself offline a month ago and nobody even mentioned it anywhere I saw, so it's probably not being used that often these days? Longer term, if this is a popular use case for Tempest then it's probably worth approaching the Tempest maintainers about getting something integrated there, or anyone who's interested can run their own RefStack server based on the last pre-retirement version of its source code (looks like it just needs a SQL server and WSGI). -- Jeremy Stanley
---- On Mon, 04 Aug 2025 08:51:42 -0700 Jeremy Stanley <fungi@yuggoth.org> wrote ---
On 2025-08-04 16:51:31 +0200 (+0200), Pierre Riteau wrote: [...]
Are the test lists formally available from RefStack, such as version 2022.11, still available somewhere? It was useful to be able to run a focused Tempest test suite to quickly validate core functionality of an OpenStack deployment.
If you're talking about the interop guidelines, the repository hasn't been retired yet but even once it is the files will still be available from its history forever, e.g.:
https://opendev.org/openinfra/interop/src/commit/2a71585/guidelines/2022.11....
I see the RefStack API has some sort of filtering mechanism for retrieving a list of tempest tests with refstack-client, and no that won't be reachable any longer with the service itself offline. That said, I haven't actually turned the service off yet but I see that it's unresponsive... the last entry in its API log is from 2025-07-08 so I think it took itself offline a month ago and nobody even mentioned it anywhere I saw, so it's probably not being used that often these days?
Longer term, if this is a popular use case for Tempest then it's probably worth approaching the Tempest maintainers about getting something integrated there, or anyone who's interested can run their own RefStack server based on the last pre-retirement version of its source code (looks like it just needs a SQL server and WSGI).
You can run or filter out a specific set of tests via multiple ways. Tempest provides the admin and non-admin (the one interop testing need) tests in a separate directory so they are easy to run via regex. Also, every test has a unique idempotent_id, which is easy to filter when you run tempest, or you can filter based on the service directory, or the type of tests. Some examples of such a list per service testing can be found in - https://github.com/openstack/tempest/tree/5f89e3cc46ba446569497c200c181c0bf6... Most of the product team running Tempest maintains the list of tests they run on their env, which can vary a lot depending on their use case. I do not think it will be easy/make sense for Tempest to define/maintain such a list at the upstream. -gmaan
-- Jeremy Stanley
participants (4)
-
Ghanshyam Maan
-
Jeremy Stanley
-
Jeremy Stanley
-
Pierre Riteau