openinfra/refstack
Code Issues Proposed changes
refstack/doc/source
History
Luz Cazares f1ed8079ec Added tox target which checks requirements.txt 
New tox target check that there is no missing or superfluous (unused)
requirements in requirements.txt.

Patch is copy/paste from Iff37af95269c38e4d435a53a21e5d60e2c5a3fa8
which do the same for Tempest projec.

This change also includes the fixes to requirements.txt needed
to pass the new tests.

Change-Id: Id52c5b140647268525120373ac19a63f72b12462
2017-02-14 21:58:43 +00:00
..
conf.py
Adding mechanism to build documentation via sphinx
2016-08-15 15:11:10 +00:00
index.rst
Add document describing the newly added vendor and product features
2016-12-08 13:31:36 -08:00
README.rst
Adding mechanism to build documentation via sphinx
2016-08-15 15:11:10 +00:00
refstack.rst
Added tox target which checks requirements.txt
2017-02-14 21:58:43 +00:00
run_in_docker.rst
Fix two typos
2016-08-23 19:38:39 +09:00
specs
Adding mechanism to build documentation via sphinx
2016-08-15 15:11:10 +00:00
test_result_management.rst
Add document describing the newly added vendor and product features
2016-12-08 13:31:36 -08:00
uploading_private_results.rst
Fix two typos
2016-08-23 19:38:39 +09:00
vendor_product.rst
Add document describing the newly added vendor and product features
2016-12-08 13:31:36 -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 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!