openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
468 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
1d3d96e07b
Go to file
hayderimran7 1d3d96e07b Fix docs instructions for test upload 
There are several things wrong in this doc:
- pub key and signature must be uploaded via UI otherwise
user gets `Bad Request Request doesnt correspond to schema`
- upload can be done with --insecure when a user
has cert issue of https://refstack.openstack.org/api
- add explicit mention of where the test json file is
produced so its easy to find when running vanilla refstack.

Change-Id: I85ac6c4dc4589d7e4c54f162723d432c40875a9f
closes-bug: 1525458
2016-02-02 23:25:13 -08:00
bin Add oslo.log library 2015-02-12 15:25:50 +04:00
doc Fix docs instructions for test upload 2016-02-02 23:25:13 -08:00
docker Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
etc Improve logout 2015-10-20 15:23:57 -07:00
refstack Merge "RefStack should allow associating specific guideline/target." 2015-12-11 23:14:33 +00:00
refstack-ui Merge "RefStack should allow associating specific guideline/target." 2015-12-11 23:14:33 +00:00
specs Re-organize the RefStack specs directory. 2015-12-08 11:16:47 -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 Update eslint and update angular style to match 2015-09-30 13:47:20 -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
bower.json Add confirmation dialogs 2015-08-27 16:50:55 -07:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
package.json Update eslint and update angular style to match 2015-09-30 13:47:20 -07:00
README.rst Update for hosting RefStack server at OpenStack Infrastructure. 2015-10-15 11:31:31 -07:00
requirements.txt Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
run-in-docker Rename "Refstack" to "RefStack" 2015-08-31 16:07:37 -07:00
setup-mysql-tests.sh Fix functional tests 2015-09-28 14:30:24 -07: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 Add filter for signed test results and related UI 2015-08-17 17:06:02 +03:00
tox.ini Added PEP 0257 check 2015-07-02 13:45:58 +00: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!