Paul Van Eck 93e9462ec9 Remove version from setup.cfg
We should let pbr calculate the version number instead of
hardcoding it in setup.cfg. This is to avoid having to keep updating
it in the future as we tag more releases.

Change-Id: Id2e0daf317f312e30d8135505216c6e29960d820
2016-02-15 13:17:44 -08:00
2015-02-12 15:25:50 +04:00
2016-02-02 23:25:13 -08:00
2015-10-20 15:23:57 -07:00
2015-06-05 08:12:19 -07:00
2015-06-15 22:56:24 +03:00
2015-06-05 08:12:19 -07:00
2015-06-05 08:12:19 -07:00
2015-03-19 10:58:51 +03:00
2015-08-27 16:50:55 -07:00
2014-05-13 16:37:37 +02:00
2015-08-31 16:07:37 -07:00
2015-09-28 14:30:24 -07:00
2016-02-15 13:17:44 -08:00
2014-03-01 17:36:44 -08:00

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!

Description
Vendor-facing API for registration of interop-compliance
Readme 8.4 MiB
Languages
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%