openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
588 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
77b1d14173
Go to file
Flavio Percoco 77b1d14173 Show team and repo badges on README 
This patch adds the team's and repository's badges to the README file.
The motivation behind this is to communicate the project status and
features at first glance.

For more information about this effort, please read this email threads[1][2]

To see an example of how this would look like check[3]

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-October/105562.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-December/108710.html
[3] https://gist.github.com/f862e9d7fa0ba34d8b676496a302085f

Co-Authored-By: Luz Cazares <luz.cazares@intel.com>

Change-Id: Iadfc72ff96c4de66bb8a4a379d5566fac7445c83
2016-12-14 17:25:37 +00:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc/source Fix invalid and duplicate links 2016-10-12 23:30:51 -07:00
docker Minor fix in docker scripts 2016-11-10 16:36:57 +02:00
etc Improve logout 2015-10-20 15:23:57 -07:00
refstack Merge "Rename key name from 'reason' to 'registration_decline_reason'" 2016-11-22 19:27:32 +00:00
refstack-ui Rename key name from 'reason' to 'registration_decline_reason' 2016-11-21 15:44:51 -08:00
specs Specification to mark a test result as "used for verification". 2016-09-28 11:47:12 -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 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 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 Show team and repo badges on README 2016-12-14 17:25:37 +00:00
requirements.txt Fix gate jobs 2016-08-03 17:36:39 -07:00
run-in-docker Rename "Refstack" to "RefStack" 2015-08-31 16:07:37 -07:00
setup-mysql-tests.sh Make functional gate job work on Xenial 2016-09-06 16:55:42 -07:00
setup.cfg Set up a correct home page for the project 2016-09-07 06:30:55 -07:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Show team and repo badges on README 2016-12-14 17:25:37 +00:00
tox.ini Deprecated tox -downloadcache option removed 2015-12-11 23:32:58 +01: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!