91c56ed9a1
As it was announced [1] global bindep-fallback.txt was removed and now projects need to have a local bindep.txt to be able to install binary dependencies for testing. In test jobs the script tools/test-setup.sh is called which requires mysql and postgres servers and clients to be installed. To eliminate 'ERROR: InterpreterNotFound: python3.5' of the zuul job refstack-tox-py35-func-mysql, simply replace the tox environment py35-func-mysql to py36-func-mysql with a base python of 3.6 instead of 3.5 and rename the zuul job to contain py36 in the name. Update the Zuul template to use nodejs6 jobs, this makes the single jobs obsolete, remove them. Without this change, the gate will use nodejs4 and fail. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007272.html Change-Id: I90cb912befb9d09fed330bd8d27a491caffbf7b9
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