Liberty Series Release Notes¶
8.0.1¶
Prelude¶
Volume migration is now supported.
Image metadata editor upgraded.
Heat topology improvements.
Improved WebSSO support.
New network topology panel. Added support for subnet allocation.
Enhanced plugin support for javasciprt, SCSS and Django template.
Instance shelving and un-shelving now supported.
Added support for shell job types and multiple Sahara improvements.
Added new Trove features.
Django 1.8 is now supported, and Django 1.7 is our minimum supported version.
New Features¶
Enabled support for migrating volumes. See this for more details.
Volume types can be now edited, and include description fields. See this for more details.
The metadata editor has been updated with AngularJS. See this for more details.
Compute images metadata can now be edited from the Project dashboard, using the new metadata editor. See this for more details.
Improvements to the heat topology, making more resources identifiable where previously they had no icons and were displayed as unknown resources. See this for more details.
Added mapping for Identity Provider and Protocol specific WebSSO.
Configurable token hashing, to disable Horizon from hashing the token passed to the OpenStack services.
Added support for subnet allocation via subnet pools. See this for more details.
Added actions to easily associate LBaaS VIP with a floating IP. See this for more details.
The network topology diagram has been replaced with an interactive graph containing collapsible networks, and scales far better in large deployments. See this for more details.
Plugin improvements, Horizon auto discovers JavaScript files for inclusion, and now has mechanisms for pluggable SCSS and Django template overrides.
Full support for translation in AngularJS, along with simpler tooling. See this for more details.
Added Karma for JavaScript testing. See this for more details.
Added ESLint for JavaScript linting, using the eslint-config-openstack rules. See this for more details.
Horizon now supports overriding of existing Django templates. See this for more details.
JavaScript files are now automatically included. See this for more details.
Support for shelving and unshelving of instances. See this for more details.
Support for v2 block device mapping, falling back to v1 when unavailable. See this. for more details.
Unified job interface map. This is a human readable method for passing in configuration data that a job may require or accept. See this for more details.
Added editing capabilities for job binaries. See this for more details.
Added editing capabilities for data sources. See this for more details.
Added editing capabilities for job templates. See this for more details.
Exposed event log for clusters. See this for more details.
Added support for shell job types. See this for more details.
Added initial support for database cluster creation and management. Vertica and MongoDB are currently supported. See this for more details.
Upgrade Notes¶
Django 1.8 is now supported, and Django 1.7 is our minimum supported version. See this for more details.
Database-backed sessions will likely not persist across upgrades due to a change in their structure. See this for more details.
Horizon no longer uses QUnit in testing, and it has been removed from our requirements. See this for more details.
Horizon now has multiple configuration options for the default web URL (
WEBROOT
), static file location (STATIC_ROOT
) and static file URL (STATIC_URL
) in its settings files.
Themes have moved location from
openstack_dashboard/static/themes
, toopenstack_dashboard/themes
. Paths may need to be updated accordingly. Furthermore, Horizon is aligning closer with Bootstrap markup, and themes should be built around this ideology; see the top bar and side navigation for details.
The deprecated
OPENSTACK_QUANTUM_NETWORK
configuration option has been removed. If you still use it, you need to replace it withOPENSTACK_NEUTRON_NETWORK
.
There is now an
OPENSTACK_NOVA_EXTENSIONS_BLACKLIST
option in the settings, to disable selected extensions for performance reasons. See this for more details.
Trove and Sahara panels now reside in
openstack_dashboard/contrib
. This is to provide separation for reviews provided mostly by the service teams. In the future, these panels may become plugins rather than being kept in Horizon. See this for more details.
Horizon requires both a
volume
andvolumev2
endpoint for Cinder, even if only using v2.
Many JavaScript files and most notably the base page template (
horizon/templates/base.html
) have moved from the framework portion of the repo (horizon
) to the application side (openstack_dashboard
) to better separate the framework from the application.