openinfra/refstack
Code Issues Proposed changes
Vendor-facing API for registration of interop-compliance
438 Commits 2 Branches 19 Tags 8.4 MiB
Python 57.9%
JavaScript 29%
HTML 10.4%
Shell 2.1%
CSS 0.5%
d23adad7f6
Go to file
Paul Van Eck d23adad7f6 Update eslint and update angular style to match 
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
2015-09-30 13:47:20 -07:00
bin Add oslo.log library 2015-02-12 15:25:50 +04:00
doc Update to reflect project movement from stackforge to openstack. 2015-09-13 17:01:02 -07:00
docker Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
etc Update installation documentation 2015-08-14 14:18:00 -07:00
refstack Merge "Delete legacy files and folders" 2015-09-04 16:56:57 +00:00
refstack-ui Update eslint and update angular style to match 2015-09-30 13:47:20 -07:00
specs Add Test Records Retrieval API to Refstack v1 API. 2015-03-24 16:03:39 -07:00
.bowerrc Consolidated project files. 2015-06-05 08:12:19 -07:00
.dockerignore Local Refstack in Docker 2015-06-15 22:56:24 +03:00
.eslintignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.eslintrc Update eslint and update angular style to match 2015-09-30 13:47:20 -07:00
.gitignore Consolidated project files. 2015-06-05 08:12:19 -07:00
.gitreview Update .gitreview for project rename 2015-09-11 20:58:25 +00:00
.testr.conf Repair tests coverage utility 2015-03-19 10:58:51 +03:00
bower.json Add confirmation dialogs 2015-08-27 16:50:55 -07:00
LICENSE Add a LICENSE 2014-05-13 16:37:37 +02:00
package.json Update eslint and update angular style to match 2015-09-30 13:47:20 -07:00
README.rst Update to reflect project movement from stackforge to openstack. 2015-09-13 17:01:02 -07:00
requirements.txt Add authentication through openstackid.org 2015-07-02 16:20:55 +03:00
run-in-docker Rename "Refstack" to "RefStack" 2015-08-31 16:07:37 -07:00
setup-mysql-tests.sh Improve database creation for testing 2015-03-06 10:14:04 +03:00
setup.cfg Add config auto generator 2015-02-09 11:31:06 +04:00
setup.py added tox.ini 2014-03-01 17:36:44 -08:00
test-requirements.txt Add filter for signed test results and related UI 2015-08-17 17:06:02 +03:00
tox.ini Added PEP 0257 check 2015-07-02 13:45:58 +00:00

README.rst

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:

Get involved!