openinfra
/
refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
738 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
Go to file
Martin Kopec 69c4d81773 Comply with the newest release of PyJWT 
A new version of PyJWT==2.0.0 got released a few days back which
changes a few significant things such as return types and option
names, see:
03610f0103/CHANGELOG.md (v200)
This commit edits the code of refstack in order to comply with the newest
changes of PyJWT.

Change-Id: I153384cd39ebadb8ee9eb3d99cd21aa02b8c0673
 		2021-01-08 20:15:27 +00:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc Force PEM filetype with ssh-keygen 2020-05-06 14:42:23 -07:00
docker Migrating from bower to yarn 2018-06-13 16:19:14 -07:00
etc allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
refstack Comply with the newest release of PyJWT 2021-01-08 20:15:27 +00:00
refstack-ui allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
specs Rename review.openstack.org to review.opendev.org 2019-07-25 07:41:39 +08:00
tools Merge "fix a typo" 2021-01-06 14:38:16 +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 Fix CI, Drop python2 and 3.5, update jobs to python3 2020-12-18 20:59:21 +00:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
README.rst Change openstack-dev to openstack-discuss 2019-11-06 11:28:44 +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
package.json Migrating from bower to yarn 2018-06-13 16:19:14 -07:00
requirements.txt Comply with the newest release of PyJWT 2021-01-08 20:15:27 +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 Fix CI, Drop python2 and 3.5, update jobs to python3 2020-12-18 20:59:21 +00:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Fix CI, Drop python2 and 3.5, update jobs to python3 2020-12-18 20:59:21 +00:00
tox.ini Fix CI, Drop python2 and 3.5, update jobs to python3 2020-12-18 20:59:21 +00:00
yarn.lock Migrating from bower to yarn 2018-06-13 16:19:14 -07:00

README.rst

RefStack

RefStack team and repository tags

image

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!