openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
712 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
0f55b39a6b
Go to file
Megan Guiney 0f55b39a6b allow for the addition of new capability sources 
This change will modify a number of things about the way
we manage guideline sources
  - it allows the api to pull guidelines from a list of
    additional guideline sources, as specified in conf
  - changes the object returned by the guidelines api
    from a list to a dictionary of lists pertaining to
    a specific guideline type

Change-Id: Ic42197b32d4c9030a35e613cae8cc64dca794c85
2018-05-08 06:16:05 -07:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc Add support for new doc PTI jobs 2017-12-18 15:46:17 -08:00
docker Fix the apt upgrade command in the Docker file 2018-04-03 14:58:39 -07:00
etc allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
refstack allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
refstack-ui allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
specs Merge "Specification for subunit data API" 2017-11-21 18:30:00 +00:00
tools add token checking and creating into result update script 2017-11-10 18:05:58 -08: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 Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitreview Update .gitreview for project rename 2015-09-11 20:58:25 +00:00
.testr.conf Repair tests coverage utility 2015-03-19 10:58:51 +03:00
.zuul.yaml Zuul: Remove project name 2018-02-01 17:02:37 -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 Update node packages and styling 2017-12-18 16:15:43 -08:00
README.rst Change doc references from DefCore to Interop Working Group 2017-04-25 21:45:34 +00:00
requirements.txt Merge "Add docs to about page" 2017-05-23 17:55:28 +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 Make functional gate job work on Xenial 2016-09-06 16:55:42 -07:00
setup.cfg Merge "Adding Python 3.5 to setup metadata" 2017-03-24 07:59:47 +00:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Add support for new doc PTI jobs 2017-12-18 15:46:17 -08:00
tox.ini Disable anonymous result upload 2018-01-11 01:26:34 -08: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!