openinfra
/
refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
733 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
Go to file
Clark Boylan 093d0211ac Rework the docker image and bootstrap tooling 
The old docker image installed nginx, mysql, and refstack in an all in
one container. This is not the preferred way to do containers as each
container should run a single process instead. Additionally the old
builds relied on PYTHONPATH munging rather than properly installing the
refstack project.

We can fix that by splitting up the services into per process
containers. Refstack now runs in a dedicated container based on
opendev's python-builder and python-base staged builds. We then run a
MariaDB along side refstack using docker-compose. A later addition can
add in a webserver and SSL termination.

Note that the end goal here is to have something we can deploy in
OpenDev using ansible and docker-compose to manage the refstack service.
This needs a lot of cleanup, but this records a working point in time.

Change-Id: I9d1c0a1b78a826266ffa67b0f58381a39a8ea89a
 		2020-01-31 09:45:19 -08:00
bin Remove logging import unused 2016-11-17 10:46:31 +07:00
doc Change testrepository for stestr in doc 2018-10-18 20:43:49 +00:00
docker Rework the docker image and bootstrap tooling 2020-01-31 09:45:19 -08:00
etc allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
refstack Remove extraneous print statement from unit test 2018-07-20 21:08:33 -07:00
refstack-ui allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
specs Rename review.openstack.org to review.opendev.org 2019-07-25 07:41:39 +08:00
tools Add utility to install js tools 2020-01-31 09:41:21 -08:00
.bowerrc Consolidated project files. 2015-06-05 08:12:19 -07:00
.eslintignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.eslintrc allow for the addition of new capability sources 2018-05-08 06:16:05 -07:00
.gitignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:35:58 +00:00
.testr.conf Repair tests coverage utility 2015-03-19 10:58:51 +03:00
.zuul.yaml Add local bindep.txt and py36-func-mysql job 2019-09-14 20:35:16 +02:00
Dockerfile Rework the docker image and bootstrap tooling 2020-01-31 09:45:19 -08:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
README.rst Change openstack-dev to openstack-discuss 2019-11-06 11:28:44 +00:00
bindep.txt Update deps so that refstack builds and deploys 2020-01-31 09:43:02 -08:00
bower.json Update angular bootstrap components 2016-02-25 16:00:40 -08:00
docker-compose.yaml Rework the docker image and bootstrap tooling 2020-01-31 09:45:19 -08:00
package.json Migrating from bower to yarn 2018-06-13 16:19:14 -07:00
requirements.txt Update deps so that refstack builds and deploys 2020-01-31 09:43:02 -08:00
setup-mysql-tests.sh Add line in mysql setup to ensure that sbin is in path 2018-07-03 22:15:25 -07:00
setup.cfg Change openstack-dev to openstack-discuss 2019-11-06 11:28:44 +00:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Add support for new doc PTI jobs 2017-12-18 15:46:17 -08:00
tox.ini Add local bindep.txt and py36-func-mysql job 2019-09-14 20:35:16 +02:00
yarn.lock Migrating from bower to yarn 2018-06-13 16:19:14 -07: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!