openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
759 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
5790634ff4
Go to file
Martin Kopec 5790634ff4 Update documentation, add playbook for developers 
The patch updates the user-faced documentation and adds a playbook
together with a doc meant mainly for RefStack developers which
helps with running the server instance locally.

Change-Id: I268fdf717c8f0e2cd0c130c560306bf54e48f348
2021-06-25 10:11:36 +02:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc Update documentation, add playbook for developers 2021-06-25 10:11:36 +02:00
docker Migrating from bower to yarn 2018-06-13 16:19:14 -07:00
etc Update refstack.conf.sample 2021-06-23 12:31:19 +00:00
playbooks Update documentation, add playbook for developers 2021-06-25 10:11:36 +02:00
refstack Update the guidelines location, try #2 2021-06-22 22:43:10 +00:00
refstack-ui Add shared-file-system guideline 2021-03-08 12:21:44 +00:00
specs Fix broken links and redirects 2021-01-08 21:17:29 +00:00
tools Fix broken links and redirects 2021-01-08 21:17:29 +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 Update .gitreview after repo rename 2020-06-13 09:40:16 +02:00
.stestr.conf Fix CI, Drop python2 and 3.5, update jobs to python3 2020-12-18 20:59:21 +00:00
.zuul.yaml Clean requirements, add pip check job 2021-06-23 12:50:15 +00: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 Replace freenode by OFTC 2021-06-14 08:23:23 +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 Clean requirements, add pip check job 2021-06-23 12:50:15 +00: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 vendors - Vendors can use RefStack to demonstrate that their distros, and/or their customers' installed clouds remain with OpenStack after their software has been incorporated into the distro or cloud.

RefStack consists of two parts:

Get involved!