84be8b1766
This is the update to the patch by mtreinish that allows for the setting of a custom alembic version_table name. In this patch, the name of this table is set via a new flag in conf. This is the first patch of several that will allow us to build in the ability to collect and upload subunit data to the refstack server. By default, the table is set to be named "alembic_version". Previously, this patch also included some alembic configuration. This has been removed due to the fact that renaming the alembic_version table is not as simple as previously hoped, and will, as a result, require the usage of a migration script. Because of this, I have chosen to sever the two patches, largely, due to the fact that they have separate functionalities, although the migration patch will consume the conf setting created in this patch, so this merging this patch first would be highly advisable. Change-Id: I4c82aabb727694d7cd55aaab339bbc55b1835f27
RefStack
RefStack team and repository tags
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:
- 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 and UI install docs: http://github.com/openstack/refstack/blob/master/doc/source/refstack.rst
- repository: http://git.openstack.org/cgit/openstack/refstack
- reviews: https://review.openstack.org/#q,status:open+refstack,n,z
- refstack-client
-
refstack-client contains the tools you will need to run the Interop Working Group tests.
Get involved!
- Mailing List: openstack-dev@lists.openstack.org
- IRC: #refstack on Freenode
- Dev Meetings: Tuesdays @ 19:00 UTC in #openstack-meeting-alt on Freenode
- Web-site: https://refstack.openstack.org
- Wiki: https://wiki.OpenStack.org/wiki/RefStack