Clark Boylan e6fd078a8b Update deps so that refstack builds and deploys
In bindep we specify we need GCC to compile deps and set tags to compile
and test as appropriate as none of these packages are needed as runtime
dependencies. In requirements.txt we unpin alembic and beaker and add
PyMySQL. Alembic and beaker need to be unpinned to work with modern
python3 and PyMySQL is a python only runtime dep if using MySQL.

This makes building docker images much simpler.

Change-Id: I18a296de190324c545feda3b1b87e0a9424d0f96
2020-01-31 09:43:02 -08:00
2016-11-17 10:46:31 +07:00
2018-06-13 16:19:14 -07:00
2020-01-31 09:41:21 -08: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
2019-04-19 19:35:58 +00:00
2015-03-19 10:58:51 +03:00
2016-02-25 16:00:40 -08:00
2014-05-13 16:37:37 +02:00
2018-06-13 16:19:14 -07:00
2014-03-01 17:36:44 -08:00
2018-06-13 16:19:14 -07:00

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!

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%