aa3966ea7a
The persistence of the openstackid session causes issues where when people log out, then click "Sign-In" again, they aren't prompted for their password. Instead they are logged in automatically with the users they just logged out from because the openstackid endpoint still has them as logged in. With this patch, the user will be logged out of refstack as well as openstackid when signing out of RefStack. This way a user can sign into refstack with another openstackid without having to delete cookies or navigate to the openstackid site to manually log out. Change-Id: I23936ba6b64b58e4f6a3f4d62ba89439c4ddee21
RefStack
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 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:
- 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: doc/refstack.md
- 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 DefCore tests.
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: https://refstack.openstack.org
- Wiki: https://wiki.OpenStack.org/wiki/RefStack