057d891f31
As cinder already supports volume types, it's time
to be added in Horizon. The types are added in admin panel.
A volume can either have a *valid* type, or None.
There are two minor issues:
1. When a type is deleted, if there is a volume with
this type, the type is returned as the id,
instead of the name. Which is good as consistency,
but maybe a type should not be deleted if used by a volume?
2. If no vol type is passed(None) value, the type is being
assigned as 'None', and returned as a string('None')
3. In the create volume type form, the 'Description' is
empty at the moment, I couldn't find any help info
to add for volume types...
Implements blueprint volume-types
Tested with n-cinder and n-vol services. Since Folsom both
support volume-types. I'm not sure if it is possible a grizzly
Dashboard to work with essex nova, which could be a problem.
Dashboard doesn't seem to provide permissions based on tables,
so if it needs to check if a service is available to show/hide
volume types, this will need some more effors to implement
permissions on table/action level. Or maybe this needs to be
added as a standalone panel?
Patch set 2: implemented suggestions, added one more thing:
When creating a volume from a snapshot, set the volume type
initial as the type of the original volume from which
the snapshot is being created.
Patch Set 3: Updated the description of volume types,
based on the notes from:
https://etherpad.openstack.org/grizzly-cinder-volumetypes
https://etherpad.openstack.org/cinder-usecases
Any feedback on the description is welcome.
Change-Id: Ib0c136c5c8cd9fbd34ce1dd346260f404c96f667
|
||
|---|---|---|
| .tx | ||
| bin | ||
| doc | ||
| horizon | ||
| openstack_dashboard | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .pep8 | ||
| .pylintrc | ||
| LICENSE | ||
| Makefile | ||
| manage.py | ||
| MANIFEST.in | ||
| openstack-common.conf | ||
| README.rst | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
Horizon (OpenStack Dashboard)
Horizon is a Django-based project aimed at providing a complete
OpenStack Dashboard along with an extensible framework for building new
dashboards from reusable components. The
openstack_dashboard module is a reference implementation of
a Django site that uses the horizon app to provide
web-based interactions with the various OpenStack projects.
For release management:
For blueprints and feature specifications:
For issue tracking:
Dependencies
To get started you will need to install Node.js (http://nodejs.org/) on your machine. Node.js is used with Horizon in order to use LESS (http://lesscss.org/) for our CSS needs. Horizon is currently using Node.js v0.6.12.
For Ubuntu use apt to install Node.js:
$ sudo apt-get install nodejsFor other versions of Linux, please see here:: http://nodejs.org/#download for how to install Node.js on your system.
Getting Started
For local development, first create a virtualenv for the project. In
the tools directory there is a script to create one for
you:
$ python tools/install_venv.py
Alternatively, the run_tests.sh script will also install
the environment for you and then run the full test suite to verify
everything is installed and functioning correctly.
Now that the virtualenv is created, you need to configure your local
environment. To do this, create a local_settings.py file in
the openstack_dashboard/local/ directory. There is a
local_settings.py.example file there that may be used as a
template.
If all is well you should able to run the development server locally:
$ tools/with_venv.sh manage.py runserver
or, as a shortcut:
$ ./run_tests.sh --runserverSettings Up OpenStack
The recommended tool for installing and configuring the core OpenStack components is Devstack. Refer to their documentation for getting Nova, Keystone, Glance, etc. up and running.
Note
The minimum required set of OpenStack services running includes the following:
- Nova (compute, api, scheduler, network, and volume services)
- Glance
- Keystone
Optional support is provided for Swift.
Development
For development, start with the getting started instructions above. Once you have a working virtualenv and all the necessary packages, read on.
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 it 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 unit tests:
$ ./run_tests.shBuilding Contributor Documentation
This documentation is written by contributors, for contributors.
The source is maintained in the doc/source folder using
reStructuredText
and built by Sphinx
Building Automatically:
$ ./run_tests.sh --docsBuilding 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