Vendor-facing API for registration of interop-compliance
3f56fde9c1
It will be replaced with API v1 written on Pecan https://storyboard.openstack.org/#!/story/132 Change-Id: I69a27b640544c22790e768be440a8396c9c3b7b8 |
||
---|---|---|
alembic | ||
defcore | ||
doc | ||
refstack | ||
scripts | ||
specs | ||
__init__.py | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
alembic.ini | ||
LICENSE | ||
README.rst | ||
refstack.cfg | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
RefStack/TCUP and Driver Test
This project support collection and publication of Community Test results for OpenStack. There are multiple components of this effort:
- RefStack: Community-facing API for registration of interop-compliance endpoints for on-demand testing.
- Driver Test
Participate
General
- Mailing List: fits@openstack.org
- IRC: #refstack on Freenode
- 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
- Launchpad: https://launchpad.net/refstack
- Blueprints: https://blueprints.launchpad.net/refstack
- Bugs: https://bugs.launchpad.net/refstack
- Code Reviews: https://review.openstack.org/#q,status:open+refstack,n,z
Collecting the Results > Running RefStack
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.