openinfra
/
refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
390 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
sslypushenko f77d86cc68 Local Refstack in Docker 
Main purpose of this path is providing a way how to easily create local env of
Refstack API with from your latest code in Docker container. I should be helpful for
testing new features and newcomers developers.

run-in-docker [OPTIONS] [COMMAND]  - run refstack container (if it is not running), upload
    latest project code into container and run Refstack API in it (default COMMAND is 'api-up').
    Just run ./drun-in-docker, wait untill it finish and then check it on https://127.0.0.1
    It is important to set env[REFSTACK_HOST] with public host for your local API.
    By default 127.0.0.1 is used,  should work fine if you access to your local Refstack
    only from your localhost. You can customize Refstack API config with editing
    docker/templates/refstack.conf.tmpl. It is a bash template.
    You can use ${SOME_ENV_VARIABLE} in it.

Available options:
  -r    Force delete '${CONTAINER}' container and run it again
  -i    Run container with isolated MySQL data.
        By default MySQL data stores in refstack_data_DATA-BASE-REVISON container
        It reuses if such container exists. If you want to drop DB data, just execute
        sudo docker rm refstack_data_DATA-BASE-REVISON
  -b    Force delete '${IMAGE}' image and built it ag
  -d    Turn on debug information
  -h    Print usage message

In-container commands:
    api-up - sync project and run Refstack API
    api-init-db - initialize Refstack database
    api-db-version - get current migration version of Refstack database
    api-sync - sync project files in contaner with project on host
    activate - activate python virtual env
    mysql - open mysql console

Requirements:
Docker 1.6 (How to update on Ubuntu http://www.ubuntuupdates.org/ppa/docker)

Change-Id: I26422aecaf68af6c340ebcc2a8a36d2a4907d84c
 		2015-06-15 22:56:24 +03:00
bin Add oslo.log library 2015-02-12 15:25:50 +04:00
defcore Remove files that are now mastered in openstack/defcore 2015-04-20 17:55:40 -05:00
doc Update to use pip install instead of python setup.py install. 2015-06-08 19:54:12 +00:00
docker Local Refstack in Docker 2015-06-15 22:56:24 +03:00
etc Add API endpoint for retrieving capabilities 2015-05-01 11:56:27 -07:00
refstack Local Refstack in Docker 2015-06-15 22:56:24 +03:00
refstack-ui Merge "Added Chromium Tests" 2015-06-12 16:19:29 +00:00
specs Add Test Records Retrieval API to Refstack v1 API. 2015-03-24 16:03:39 -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 Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitreview Add a gitreview setup 2014-05-18 19:02:40 +02:00
.testr.conf Repair tests coverage utility 2015-03-19 10:58:51 +03:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
README.rst Updated the README.rst to fix the link to the wiki page. 2015-05-27 11:12:09 -05:00
bower.json Consolidated project files. 2015-06-05 08:12:19 -07:00
package.json Merge "Added PhantomJS test execution" 2015-06-12 16:18:59 +00:00
requirements.txt Local Refstack in Docker 2015-06-15 22:56:24 +03:00
run-in-docker Local Refstack in Docker 2015-06-15 22:56:24 +03:00
setup-mysql-tests.sh Improve database creation for testing 2015-03-06 10:14:04 +03:00
setup.cfg Add config auto generator 2015-02-09 11:31:06 +04:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Add API endpoint for retrieving capabilities 2015-05-01 11:56:27 -07:00
tox.ini Add unit tests for untested code 2015-03-19 10:58:51 +03:00

README.rst

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!