|6 years ago|
|bin||6 years ago|
|defcore||6 years ago|
|doc||6 years ago|
|etc||6 years ago|
|refstack||6 years ago|
|refstack-ui||6 years ago|
|specs||6 years ago|
|.gitignore||6 years ago|
|.gitreview||7 years ago|
|.testr.conf||6 years ago|
|LICENSE||7 years ago|
|README.rst||6 years ago|
|__init__.py||7 years ago|
|requirements.txt||6 years ago|
|setup-mysql-tests.sh||6 years ago|
|setup.cfg||6 years ago|
|setup.py||7 years ago|
|test-requirements.txt||6 years ago|
|tox.ini||6 years ago|
What is refstack?
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:
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.
refstack-client contains the tools you will need to run the DefCore tests.