openstack
/
horizon
Code Issues Proposed changes

Adding missing release notes around upgrades 

A few things were moved out of tree in the Mitaka release. These
need to be reflected in the release notes in the upgrade section.

Partial-Bug: #1558825
Change-Id: I0ef25c85561f63db75223e5c5334d1ea2f1ff72d
This commit is contained in:
David Lyle 2016-03-17 17:22:46 -06:00 committed by David Lyle
parent e4c468f3eb
commit baaa454ba7
3 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
releasenotes/notes/excise-sahara-7eff95feb416ce4b.yaml Normal file
View File

@ -0,0 +1,6 @@
---
upgrade:
- The Sahara based content has been removed from the Horizon source tree
and is now a separate plugin. To continue managing Sahara in Horizon,
installing the sahara-dashboard plugin on the Horizon server is required.

6
releasenotes/notes/excise-trove-ce576b50fbcd15ad.yaml Normal file
View File

@ -0,0 +1,6 @@
---
upgrade:
- The Trove based content has been removed from the Horizon source tree
and is now a separate plugin. To continue managing Trove in Horizon,
installing the trove-dashboard plugin on the Horizon server is required.

9
releasenotes/notes/move-policy-engine-b19e434a62912e5f.yaml Normal file
View File

@ -0,0 +1,9 @@
---
upgrade:
- The main engine managing integration with oslo.policy has been moved
to django_openstack_auth. The configuration is still managed in
Horizon, but the setting for ``POLICY_CHECK_FUNCTION`` now uses
``openstack_auth.policy.check`` rather than
``openstack_dashboard.policy.check``. Current behavior will
remain consistent.