d61a41b07c
The board approved the rename for DefCore Committee to Interop Working Group, as a part of this change, we will be renaming the references on RefStack project. Depends-On: I949e17351ce5f9ea5f12120c2599d725eda6dcc1 Change-Id: I90c0457cb20fe78ebc2334743a45557ca13039b7
70 lines
2.7 KiB
ReStructuredText
70 lines
2.7 KiB
ReStructuredText
========
|
|
RefStack
|
|
========
|
|
|
|
RefStack team and repository tags
|
|
#################################
|
|
.. image:: https://governance.openstack.org/badges/refstack.svg
|
|
:target: https://governance.openstack.org/reference/tags/index.html
|
|
|
|
|
|
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.
|
|
|
|
* repository: http://git.openstack.org/cgit/openstack/refstack-client
|
|
* reviews: https://review.openstack.org/#q,status:open+refstack-client,n,z
|
|
|
|
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
|