OpenStack Dashboard (Horizon)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Gabriel Hurley 90f51fc78b Merge pull request #170 from rackerjoe/fix-syspanel-image-list 7 years ago
django-openstack container_format and project_id are flipped 7 years ago
openstack-dashboard Bumped version 7 years ago
.bzrignore Corrected bugs introduced in internationalization 7 years ago
.gitignore fixing run_tests - typo, missing requires 7 years ago
.pylintrc updating to mimic other openstack projects, pep8, pylint, coverage 7 years ago
LICENSE Initial commit 8 years ago
README updating README to explain project/repo structure 7 years ago fix typo in runtests 7 years ago


OpenStack Dashboard

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

It is based on django-openstack, which is designed to be a generic Django
module that can be re-used in other sites.

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 django-openstack, see the
README file in the django-openstack 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: django-openstack, and

django-openstack holds the generic libraries and components that can be
used in any Django project. In testing, this component is set up with
buildout (see, and any dependencies that get added need to
be added to the django-openstack/buildout.cfg file.

openstack-dashboard is a reference django project that uses django-openstack
and is built with a virtualenv and tested through that environment. If
depdendencies are added that the reference django project needs, they
should be added to openstack-dashboard/tools/pip-requires.

The script invokes tests and analysis on both of these
components in it's process, and is what Jenkins uses to verify the
stability of the project.