d23adad7f6
With an updated eslint version and the addition of eslint-config-openstack and eslint-plugin-angular, there are several more stylistic guidelines to follow. However, this is what other OpenStack angular projects follow such as Horizon. Some notable changes are: * Wrapped javascript content in anonymous functions. This is a safeguard to keep the code from conflicting with other variables with the same name in other scripts on the same page. * Explicitly inject dependencies and have controllers, factories, etc as explicitly declared functions. * Use angular "controller as" syntax instead of assigning variables to $scope. * Added eslint rule that requires JSDoc for every function declaration. Note these are mainly stylistic changes and all the functionality of RefStack should remain the same. Change-Id: I044b1f473d589681a2ae9d2704700dd85687cbb6
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: http://refstack.net
- Wiki: https://wiki.OpenStack.org/wiki/RefStack