x/tuskar-ui
Code Issues Proposed changes
RETIRED, The UI component for Tuskar
1,336 Commits 3 Branches 13 Tags 16 MiB
aca739445e
Go to file
Gabriel Hurley aca739445e Refactored test suite. 
* Moves all tests to use a single set of central test data and
    Adds a nifty manager for it.
    Implements blueprint unified-test-data.

  * Cleans up API code and API tests so that we're not testing
    code that has no custom logic, or wrapping objects unnecessarily.
    Implements blueprint api-simplification.

  * Adds lots of docs on testing. It's a good step towards
    blueprint improve-dev-documentation.

  * Improves API exception handling for duplicate objects and containers.
    Fixes bug 930816.

Change-Id: I5526ccf5b38708885ea2d1f06b0d3483c58c4dad
2012-02-13 15:24:06 -08:00
docs Refactored test suite. 2012-02-13 15:24:06 -08:00
horizon Refactored test suite. 2012-02-13 15:24:06 -08:00
openstack-dashboard Full support for dashboard and panel configuration via service catalog. 2012-02-12 18:03:09 -08:00
tools Updated Copyright dates to 2012. 2012-02-09 19:46:48 -06:00
.bzrignore Re-architects the OpenStack Dashboard for modularity and extensibility. 2011-11-07 12:59:21 -08:00
.gitignore Reworked all the usage implementations into one standard set. 2012-02-02 14:59:26 -08:00
.gitreview Add .gitreview and rfc.sh. 2011-10-28 09:50:35 -04:00
.pylintrc updating run_tests.sh to mimic other openstack projects, pep8, pylint, coverage 2011-08-31 14:41:36 -07:00
LICENSE Initial commit 2011-01-12 13:43:31 -08:00
README.rst Unified horizon and openstack-dashboard environments. 2012-01-05 13:57:07 -08:00
run_tests.sh Cleans up leftover coverage files after test run. 2012-02-03 12:46:44 -08:00

README.rst

OpenStack Dashboard (Horizon)

The OpenStack Dashboard is a Django based reference implementation of a web based management interface for OpenStack.

It is based on the horizon module, which is designed to be a generic Django app that can be re-used in other projects.

For more information about how to get started with the OpenStack Dashboard, view the README file in the openstack-dashboard folder.

For more information about working directly with horizon, see the README file in the horizon folder.

For release management:

For blueprints and feature specifications:

For issue tracking:

Project Structure and Testing:

This project is a bit different from other OpenStack projects in that it has two very distinct components underneath it: horizon, and openstack-dashboard.

The horizon directory holds the generic libraries and components that can be used in any Django project.

The openstack-dashboard directory contains a reference Django project that uses horizon.

For development, both pieces share an environment which (by default) is built with the tools/install_venv.py script. That script creates a virtualenv and installs all the necessary packages.

If dependencies are added to either horizon or openstack-dashboard, they should be added to tools/pip-requires.

The run_tests.sh script invokes tests and analyses on both of these components in its process, and is what Jenkins uses to verify the stability of the project. If run before an environment is set up, it will ask if you wish to install one.

To run the tests:

$ ./run_tests.sh

Building Contributor Documentation

This documentation is written by contributors, for contributors.

The source is maintained in the docs/source folder using reStructuredText and built by Sphinx

  • Building Automatically:

    $ ./run_tests.sh --docs

  • Building Manually:

    $ export DJANGO_SETTINGS_MODULE=local.local_settings
$ python doc/generate_autodoc_index.py
$ sphinx-build -b html doc/source build/sphinx/html

Results are in the build/sphinx/html directory