Vendor-facing API for registration of interop-compliance
Python JavaScript HTML Shell Other
Clone or download
mguiney fix documentation formatting
New documentation regarding how to install yarn needed double
newlines rather than the current single newlines. As is, it is
rendering as a single line, which is obfuscating eyesore.

Change-Id: I4a3e921342703ea00a4ab622b304c70250006063
Latest commit aee81c6 Jun 16, 2018
Failed to load latest commit information.
bin Remove logging import unused Nov 17, 2016
doc fix documentation formatting Jun 16, 2018
docker Migrating from bower to yarn Jun 13, 2018
etc allow for the addition of new capability sources May 8, 2018
refstack-ui allow for the addition of new capability sources May 8, 2018
refstack allow for the addition of new capability sources May 8, 2018
specs Merge "Specification for subunit data API" Nov 21, 2017
tools add token checking and creating into result update script Nov 11, 2017
.bowerrc Consolidated project files. Jun 5, 2015
.dockerignore Local Refstack in Docker Jun 15, 2015
.eslintignore Consolidated project files. Jun 5, 2015
.eslintrc allow for the addition of new capability sources May 8, 2018
.gitignore Consolidated project files. Jun 5, 2015
.gitreview Update .gitreview for project rename Sep 11, 2015
.testr.conf Repair tests coverage utility Mar 19, 2015
.zuul.yaml Zuul: Remove project name Feb 2, 2018
LICENSE Add a LICENSE May 13, 2014
README.rst Change doc references from DefCore to Interop Working Group Apr 25, 2017
bower.json Update angular bootstrap components Feb 26, 2016
package.json Migrating from bower to yarn Jun 13, 2018
requirements.txt Merge "Add docs to about page" May 23, 2017
run-in-docker run-in-docker starts refstack over https, fix docs Sep 12, 2017 Make functional gate job work on Xenial Sep 6, 2016
setup.cfg Merge "Adding Python 3.5 to setup metadata" Mar 24, 2017 added tox.ini Mar 2, 2014
test-requirements.txt Add support for new doc PTI jobs Dec 18, 2017
tox.ini Disable anonymous result upload Jan 11, 2018
yarn.lock Migrating from bower to yarn Jun 13, 2018



RefStack team and repository tags

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