openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
689 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
d2130f6cb5
Go to file
Duong Ha-Quang d2130f6cb5 Convert legacy tox jobs in-tree 
This implements all step in zuulv3 migration guide [1]:

It moves the legacy tox jobs in-tree and converts them directly into
Zuul v3 native jobs.

Note that other jobs stay in project-config as common jobs.

[1] https://docs.openstack.org/infra/manual/zuulv3.html#legacy-job-migration-details

Co-Authored-By: Andreas Jaeger <aj@suse.com>
Needed-By: I210b7823bb5720d3a06cf4ac5681904c8a9c50a5
Change-Id: I3fa5ccbaf8c18c6a07bd170c3b75724be246e721
2017-11-16 19:06:15 +00:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc/source Update Refstack docs for documentation migration 2017-07-10 19:26:08 +00:00
docker Remove IPython from RefStack container 2017-04-26 10:20:37 +03:00
etc fix refstack.conf.sample typo 2017-09-15 20:01:09 -07:00
refstack Add name scheme update script for alembic version table 2017-10-16 21:11:49 +00:00
refstack-ui Add UI support for interop schema 2.0 2017-08-07 12:44:59 -07:00
specs Merge "[Trivialfix]Fix typos" 2017-09-19 19:12:45 +00:00
tools Merge "Add name scheme update script for alembic version table" 2017-10-17 17:22:54 +00: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
.zuul.yaml Convert legacy tox jobs in-tree 2017-11-16 19:06:15 +00:00
bower.json Update angular bootstrap components 2016-02-25 16:00:40 -08:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
package.json Fix gate jobs 2016-08-03 17:36:39 -07:00
README.rst Change doc references from DefCore to Interop Working Group 2017-04-25 21:45:34 +00:00
requirements.txt Merge "Add docs to about page" 2017-05-23 17:55:28 +00:00
run-in-docker run-in-docker starts refstack over https, fix docs 2017-09-12 14:46:28 -06:00
setup-mysql-tests.sh Make functional gate job work on Xenial 2016-09-06 16:55:42 -07:00
setup.cfg Merge "Adding Python 3.5 to setup metadata" 2017-03-24 07:59:47 +00:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Update Refstack docs for documentation migration 2017-07-10 19:26:08 +00:00
tox.ini Add name scheme update script for alembic version table 2017-10-16 21:11:49 +00: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 Interop Working Group - The prototypical use case for RefStack provides the Interop Working Group - formerly known as DefCore committee - the tools for vendors and other users to run API tests against their clouds to provide the WG with a reliable overview of what APIs and capabilities are being used in the marketplace. This will help to guide the Interop Working Group defined capabilities and help ensure interoperability across the entire OpenStack ecosystem. It can also be used to validate clouds against existing 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!