Vendor-facing API for registration of interop-compliance
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Zuul 94b1fa594f Merge "Use unittest.mock instead of mock" 18 hours ago
bin Remove logging import unused 4 years ago
doc Fix broken links and redirects 2 weeks ago
docker Migrating from bower to yarn 2 years ago
etc allow for the addition of new capability sources 2 years ago
refstack Merge "Use unittest.mock instead of mock" 18 hours ago
refstack-ui Fix broken links and redirects 2 weeks ago
specs Fix broken links and redirects 2 weeks ago
tools Fix broken links and redirects 2 weeks ago
.bowerrc Consolidated project files. 5 years ago
.dockerignore Local Refstack in Docker 5 years ago
.eslintignore Consolidated project files. 5 years ago
.eslintrc allow for the addition of new capability sources 2 years ago
.gitignore Fix CI, Drop python2 and 3.5, update jobs to python3 1 month ago
.gitreview Update .gitreview after repo rename 7 months ago
.stestr.conf Fix CI, Drop python2 and 3.5, update jobs to python3 1 month ago
.zuul.yaml Fix CI, Drop python2 and 3.5, update jobs to python3 1 month ago
LICENSE Add a LICENSE 6 years ago
README.rst Fix broken links and redirects 2 weeks ago
bindep.txt Update deps so that refstack builds and deploys 1 year ago
bower.json Update angular bootstrap components 4 years ago
package.json Migrating from bower to yarn 2 years ago
requirements.txt Comply with the newest release of PyJWT 2 weeks ago
run-in-docker run-in-docker starts refstack over https, fix docs 3 years ago
setup-mysql-tests.sh Add line in mysql setup to ensure that sbin is in path 2 years ago
setup.cfg Replace six by python3 code style 2 weeks ago
setup.py added tox.ini 7 years ago
test-requirements.txt Use unittest.mock instead of mock 19 hours ago
tox.ini Replace six by python3 code style 2 weeks ago
yarn.lock Migrating from bower to yarn 2 years ago

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!