Vendor-facing API for registration of interop-compliance
Go to file
Martin Kopec fa704ce067 Include openstack-tox-py311 job
Getting rid of the antelope template and replacing it with the list
of the jobs instead - it's gonna be easier to add newer python
jobs as we won't have to check which ones are a part of a template
and which need to be added directly.
mysql-server and mysql-client seem to be changed for mariadb-server
and mariadb-client:
https://github.com/geerlingguy/ansible-role-mysql/issues/336

Change-Id: Id37a96f32e58c5a91f25d731c89c7a565614d99f
2023-09-20 10:28:04 +02:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc Update Refstack Docs 2023-06-05 11:50:39 -04:00
etc Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +00:00
playbooks Update documentation, add playbook for developers 2021-06-25 10:11:36 +02:00
refstack Merge "Fix security vulnerabilities using Bandit" 2023-02-08 13:25:41 +00:00
refstack-ui Adding 2 missing programs to menu on home page 2023-05-10 21:15:19 +02:00
specs Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +00:00
tools Update jobs for Bobcat development cycle 2023-05-18 08:53:36 +00:00
.bowerrc Consolidated project files. 2015-06-05 08:12:19 -07:00
.dockerignore Local Refstack in Docker 2015-06-15 22:56:24 +03:00
.eslintignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.eslintrc allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
.gitignore Fix CI, Drop python2 and 3.5, update jobs to python3 2020-12-18 20:59:21 +00:00
.gitreview [project-rename] Update .gitreview 2021-10-16 18:07:56 +00:00
.stestr.conf Fix CI, Drop python2 and 3.5, update jobs to python3 2020-12-18 20:59:21 +00:00
.zuul.yaml Include openstack-tox-py311 job 2023-09-20 10:28:04 +02:00
CONTRIBUTING.rst Add contributing page and some updates 2021-11-15 14:36:25 +00:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
README.rst Add contributing page and some updates 2021-11-15 14:36:25 +00:00
bindep.txt Include openstack-tox-py311 job 2023-09-20 10:28:04 +02:00
bower.json Update angular bootstrap components 2016-02-25 16:00:40 -08:00
package.json Migrating from bower to yarn 2018-06-13 16:19:14 -07:00
requirements.txt Fix compatibility issues 2022-08-11 15:52:14 +02:00
run-in-docker run-in-docker starts refstack over https, fix docs 2017-09-12 14:46:28 -06:00
setup-mysql-tests.sh Fix compatibility issues 2022-08-11 15:52:14 +02:00
setup.cfg Include openstack-tox-py311 job 2023-09-20 10:28:04 +02:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Make refstack jobs work again 2023-02-01 15:29:36 +01:00
tox.ini Make refstack jobs work again 2023-02-01 15:29:36 +01:00
yarn.lock Migrating from bower to yarn 2018-06-13 16:19:14 -07:00

README.rst

RefStack

What is RefStack?

  • Toolset for testing interoperability between OpenStack clouds.
  • Database backed website supporting collection and publication of Community Test results for OpenStack.
  • User interface to display individual test run results.

RefStack intends on being THE source of tools for interoperability testing of OpenStack clouds.

RefStack provides users in the OpenStack community with a Tempest wrapper, refstack-client, that helps to verify interoperability of their cloud with other OpenStack clouds. It does so by validating any cloud implementation against the OpenStack Tempest API tests.

Refstack's Use Case

RefStack and Interop Working Group - The prototypical use case for RefStack provides the Interop Working Group - formerly known as DefCore committee - the tools for vendors and other users to run API tests against their clouds to provide the WG with a reliable overview of what APIs and capabilities are being used in the marketplace. This will help to guide the Interop Working Group defined capabilities and help ensure interoperability across the entire OpenStack ecosystem. It can also be used to validate clouds against existing capability lists, giving you assurance that your cloud faithfully implements OpenStack standards.

Value add for openstack distro or solution vendors - Vendors can use RefStack to demonstrate that their distros, and/or their customers' installed clouds remain OpenStack compliant after their software has been incorporated into the distro or cloud.

RefStack consists of two parts:

Get Involved!

See the CONTRIBUTING guide on how to get involved.