openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
395 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
7b48c99fcb
Go to file
Vladislav Kuzmin 7b48c99fcb Add authentication through openstackid.org 
In Refstack's database store only fullname, email and openid.
After sign in refstack backend create session and write it id in cookie.
When UI is opened in browser, Angular try to get info from
/v1/profile. If data about user received then user is authenticated.

Change-Id: Ib2cabc0c6b4de4b2ca1f02cc9e062a6e3550daa0
2015-07-02 16:20:55 +03:00
bin Add oslo.log library 2015-02-12 15:25:50 +04:00
defcore Remove files that are now mastered in openstack/defcore 2015-04-20 17:55:40 -05:00
doc Update to use pip install instead of python setup.py install. 2015-06-08 19:54:12 +00:00
docker Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
etc Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
refstack Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
refstack-ui Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
specs Add Test Records Retrieval API to Refstack v1 API. 2015-03-24 16:03:39 -07: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 Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitignore Consolidated project files. 2015-06-05 08:12:19 -07: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
bower.json Consolidated project files. 2015-06-05 08:12:19 -07:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
package.json Merge "Added test-auto-watch target" 2015-06-22 19:58:27 +00:00
README.rst Updated the README.rst to fix the link to the wiki page. 2015-05-27 11:12:09 -05:00
requirements.txt Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
run-in-docker Local Refstack in Docker 2015-06-15 22:56:24 +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 Add API endpoint for retrieving capabilities 2015-05-01 11:56:27 -07: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!