Vendor-facing API for registration of interop-compliance
Go to file
Vladislav Kuzmin bc1c92505b Cleanup .gitignore and remove refstack.cfg
Cleanup .gitignore file and sort it in alfabetical order.
Remove unused refstack.cfg file.

Change-Id: I3aebb5c58a8fdf4fa4da5f68763ba8db9883d336
2015-03-19 10:57:41 +03:00
bin Add oslo.log library 2015-02-12 15:25:50 +04:00
defcore Remove XML tests in the havancore.json file. 2015-02-13 10:49:41 -08:00
doc Remove unused README file in the doc directory. 2015-03-06 16:09:27 -08:00
etc Add oslo.log library 2015-02-12 15:25:50 +04:00
refstack Add unit tests for validators and database 2015-03-19 10:55:48 +03:00
specs Merge "Workflow documentation is now in infra-manual" 2015-03-04 21:44:27 +00:00
__init__.py py33 tests fixed 2014-07-22 09:37:21 +00:00
.gitignore Cleanup .gitignore and remove refstack.cfg 2015-03-19 10:57:41 +03:00
.gitreview Add a gitreview setup 2014-05-18 19:02:40 +02:00
.testr.conf Improve database creation for testing 2015-03-06 10:14:04 +03:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
README.rst Update readme to current information. 2015-02-16 05:47:11 -08:00
requirements.txt Add oslo.log library 2015-02-12 15:25:50 +04:00
setup-mysql-tests.sh Improve database creation for testing 2015-03-06 10:14:04 +03:00
setup.cfg Add config auto generator 2015-02-09 11:31:06 +04:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Increase test coverage for database migration 2015-03-17 11:38:48 +03:00
tox.ini Increase test coverage for database migration 2015-03-17 11:38:48 +03:00

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 DefCore - The prototypical use case for refstack provides the DefCore Committee the tools for vendors and other users to run API tests against their clouds to provide the DefCore committee with a reliable overview of what APIs and capabilities are being used in the marketplace. This will help to guide the DefCore-defined capabilities and help ensure interoperability across the entire OpenStack ecosystem. It can also be used to validate clouds against existing DefCore 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!