f77d86cc68
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
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:
- refstack-api
-
Our API isn't just for us to collect data from private and public cloud vendors. It can be used by vendors in house to compare interoperability data over time.
- API server install docs: doc/refstack.md
- UI server install docs: refstack-ui/README.rst
- repository: http://git.openstack.org/cgit/stackforge/refstack
- storyboard: https://storyboard.openstack.org/#!/project/700
- reviews: https://review.OpenStack.org/#q,status:open+refstack,n,z
- refstack-client
-
refstack-client contains the tools you will need to run the DefCore tests.
Get involved!
- Mailing List: fits@OpenStack.org
- IRC: #refstack on Freenode
- Dev Meetings: Mondays @ 19:00 UTC in #openstack-meeting-alt on Freenode
- Web-site: http://refstack.net
- Wiki: https://wiki.OpenStack.org/wiki/RefStack