openinfra
/
refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
356 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
Go to file
Paul Van Eck c094c27eff Add results and test report page 
This is the groundwork for the community results listing page
and the test run report page. The report page is fairly basic, primarily
showing how results stack up against defcore capabilities. Design is subject
to change, but this gets the ball rolling. A config.json.sample was also added.
The UI now expects a config.json in the root which will contain the
Refstack API URL.

Change-Id: Id7a376d0bccda5cbb5daf05e52a2c174ad40b497
 		2015-04-27 09:50:27 -07:00
bin Add oslo.log library 2015-02-12 15:25:50 +04:00
defcore Adjust html and js to use new capabilities format 2015-04-06 20:19:22 +00:00
doc Create endpoint for listing of all uploads id without auth 2015-04-03 17:27:12 +03:00
etc Create endpoint for listing of all uploads id without auth 2015-04-03 17:27:12 +03:00
refstack Add support for uploading signed test results 2015-04-07 13:37:08 +03:00
refstack-ui Add results and test report page 2015-04-27 09:50:27 -07:00
specs Add Test Records Retrieval API to Refstack v1 API. 2015-03-24 16:03:39 -07:00
.gitignore Repair tests coverage utility 2015-03-19 10:58:51 +03:00
.gitreview Add a gitreview setup 2014-05-18 19:02:40 +02:00
.testr.conf Repair tests coverage utility 2015-03-19 10:58:51 +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
__init__.py py33 tests fixed 2014-07-22 09:37:21 +00:00
requirements.txt Add support for uploading signed test results 2015-04-07 13:37:08 +03: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 Repair tests coverage utility 2015-03-19 10:58:51 +03:00
tox.ini Add unit tests for untested code 2015-03-19 10:58:51 +03:00

README.rst

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!