openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
765 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
5eb0e719fc
Go to file
Martin Kopec 5eb0e719fc Reflect osf/ to openinfra/ namespace rename 
Lately osf/ namespace got renamed to openinfra/ [1], this commit
reflects this change within refstack's repo.

[1] https://review.opendev.org/c/openstack/project-config/+/808479

Change-Id: Id8ff246faf19ac67ed6c9dc5ab2514c4655a0610
2021-10-21 22:35:42 +00:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +00:00
docker Migrating from bower to yarn 2018-06-13 16:19:14 -07: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 Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +00:00
refstack-ui Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +00:00
specs Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +00:00
tools Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +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 Fix uploading of documentation to opendev.org 2021-10-19 16:26:09 +02:00
bindep.txt Update deps so that refstack builds and deploys 2020-01-31 09:43:02 -08:00
bower.json Update angular bootstrap components 2016-02-25 16:00:40 -08:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
package.json Migrating from bower to yarn 2018-06-13 16:19:14 -07:00
README.rst Reflect osf/ to openinfra/ namespace rename 2021-10-21 22:35:42 +00:00
requirements.txt Clean requirements, add pip check job 2021-06-23 12:50:15 +00: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 Add line in mysql setup to ensure that sbin is in path 2018-07-03 22:15:25 -07:00
setup.cfg Replace six by python3 code style 2021-01-11 20:33:56 +00:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Use unittest.mock instead of mock 2021-01-25 19:38:53 +00:00
tox.ini Fix documentation structure 2021-10-18 11:27:11 +02: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.

Overview

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 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!