openinfra/refstack
Code Issues Proposed changes

Update readme to current information.

Browse Source 
Change-Id: If801581b140e153418c5dc8182b37249640d5d06
This commit is contained in:
David Lenwell 2015-02-15 19:25:55 -08:00
parent 5c09a4a57e
commit baced31e2a
1 changed files with 51 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

73
README.rst
View File

@ -1,32 +1,61 @@
RefStack/TCUP and Driver Test refstack
============================= ========
This project support collection and publication of Community Test results for OpenStack. There are multiple components of this effort: **What is refstack?**
* `RefStack <doc/refstack.md>`_: Community-facing API for registration of interop-compliance endpoints for on-demand testing. - Toolset for testing interoperability between OpenStack clouds.
* Driver Test - Database backed website supporting collection and publication of
Community Test results for OpenStack.
- User interface to display individual test run results.
Participate **Overview**
-----------------------------------------
* General
* Mailing List: fits@openstack.org refstack intends on being THE source of tools for interoperability testing
* IRC: #refstack on Freenode of OpenStack clouds.
* Dev Meetings: https://wiki.openstack.org/wiki/Meetings#DefCore_.2F_RefStack_Development_Meeting
* Web-site: http://refstack.org
* Wiki: https://wiki.openstack.org/wiki/RefStack
* Development 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.
* Launchpad: https://launchpad.net/refstack **refstack and DefCore** - The prototypical use case for refstack provides
* Blueprints: https://blueprints.launchpad.net/refstack the DefCore Committee the tools for vendors and other users to run API
* Bugs: https://bugs.launchpad.net/refstack tests against their clouds to provide the DefCore committee with a reliable
* Code Reviews: https://review.openstack.org/#q,status:open+refstack,n,z 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.
Collecting the Results > Running RefStack **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 is a Web UI and API used to collect and display test results. This information is used by the DefCore committee to help select must-pass capabilities. **refstack consists of two parts:**
`RefStack docs <doc/refstack.md>`_ * **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.
* install docs: `doc/refstack.md <doc/refstack.md>`_
* 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.
* repository: http://git.openstack.org/cgit/stackforge/refstack-client
* storyboard: https://storyboard.openstack.org/#!/project/703
* reviews: https://review.openstack.org/#q,status:open+refstack-client,n,z
**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