| 2017-07-24 11:27:39 |
Rob Cresswell |
description |
The horizon plugin framework does not allow to override default panel settings by same filename. This leads to make operators difficult to change the order of panels from the default.
The horizon document says that "The settings are applied in alphabetical order of the filenames. If the same dashboard has configuration files in enabled and local/enabled, the local name will be used." [1] but actually both files are processed in the order of 'enabled' and then 'local/enabled'. This means the default dashboard is once registered in all cases.
This sometimes makes things difficult.
For example, if we move the floating IP panel just after the Router panel, we need to disable the default enabled file _1490_project_floating_ips_panel.py by adding a file with the same filename which contains DISABLED =True and then add locale/enabled/_1450_project_floating_ips_panel.py (for example).
[1] https://docs.openstack.org/developer/horizon/install/settings.html#pluggable-settings |
The horizon plugin framework does not allow to override default panel settings by same filename. This leads to make operators difficult to change the order of panels from the default.
The horizon document says that "The settings are applied in alphabetical order of the filenames. If the same dashboard has configuration files in enabled and local/enabled, the local name will be used." [1] but actually both files are processed in the order of 'enabled' and then 'local/enabled'. This means the default dashboard is once registered in all cases.
This sometimes makes things difficult.
For example, if we move the floating IP panel just after the Router panel, we need to disable the default enabled file _1490_project_floating_ips_panel.py by adding a file with the same filename which contains DISABLED =True and then add locale/enabled/_1450_project_floating_ips_panel.py (for example).
[1] https://docs.openstack.org/horizon/latest/configuration/pluggable_panels.html#introduction |
|
