53a5164d82
enable_firewall and enable_vpn settings have been deprecated
since Juno release, but they have not been dropped yet just because
we need a lot of changes in unit tests if dropped.
The situation is resolved by the parent commit and we can now drop these
settings safely. We can control whether a specific panel should be
enabled or disabled via the pluggable panel mechanism ("enabled" dir).
Also clean up enable_lb which has gone several releases ago.
Closes-Bug: #1687185
Change-Id: I83fa48c5d9568a00294be7cd5f43ef181bc1f28d
13 lines
642 B
YAML
13 lines
642 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The settings ``enable_firewall`` and ``enable_vpn`` which have been
|
|
deprecated since Juno release are now actually dropped.
|
|
If you are using these settings to disable FWaaS v1 and VPNaaS dashboards,
|
|
use ``REMOVE_PANEL`` of `the Pluggable Panel mechanism
|
|
<https://docs.openstack.org/developer/horizon/topics/settings.html#pluggable-settings-for-panels>`
|
|
to disable these panels. Note that Horizon checks the availability of
|
|
FWaaS v1 and/or VPNaaS in your Neutron deploymennt and disables corresponding
|
|
panels if not available, so in most cases you do not need to take care of
|
|
the change.
|