horizon - en to en_GB translation catalogue (177 entries)

en: (For Horizon plugin developers) The AVAIL_CHANGED event of transfer table is removed. It is superseded by event TABLES_CHANGED. The name of AVAIL_CHANGED was misleading because it implicitly and uncontrollably updated the allocated table too. The new event allows independent updates to all four tables. We believe it is safe to remove AVAIL_CHANGED without deprecation because its implementation contained a bug that must have been discovered before if anybody had used it. Anyway possible out-of-tree plugin maintainers are recommended to consume the new event even if your plugins relied on the buggy behavior of AVAIL_CHANGED.
en_GB: (For Horizon plugin developers) The AVAIL_CHANGED event of transfer table is removed. It is superseded by event TABLES_CHANGED. The name of AVAIL_CHANGED was misleading because it implicitly and uncontrollably updated the allocated table too. The new event allows independent updates to all four tables. We believe it is safe to remove AVAIL_CHANGED without deprecation because its implementation contained a bug that must have been discovered before if anybody had used it. Anyway possible out-of-tree plugin maintainers are recommended to consume the new event even if your plugins relied on the buggy behaviour of AVAIL_CHANGED.

en: (optional) Use the common Angular template as the basis of any Angular pages to minimize boilerplate code and to ensure that we use similar features/framing.
en_GB: (optional) Use the common Angular template as the basis of any Angular pages to minimise boilerplate code and to ensure that we use similar features/framing.

en: A `thorough set of documentation`_ for developers on how to go about internationalizing, localizing and translating OpenStack projects is now available.
en_GB: A `thorough set of documentation`_ for developers on how to go about internationalising, localising and translating OpenStack projects is now available.

en: A malicious user can make the exact same "unauthorized" requests via the CLI as they can via the dashboard; no special privileges are granted.
en_GB: A malicious user can make the exact same "unauthorised" requests via the CLI as they can via the dashboard; no special privileges are granted.

en: A new entry has been added to the context switcher menu, visible only when the current user has access to the system scope. This entry, labeled "system scope", allows to switch to a system-scope token, so that operations that require this kind of token can be performed.
en_GB: A new entry has been added to the context switcher menu, visible only when the current user has access to the system scope. This entry, labelled "system scope", allows switching to a system-scope token so that operations that require this kind of token can be performed.

en: A new setting ``OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES`` was introduced to control whether IP addresses of servers are retrieved from neutron in the project instance table. This setting was introduces to mitigate a performance issue in large deployments and setting this to ``False`` skips the query to neutron. Deployments without floating IP support can set this setting to ``False`` for better performance. For more detail, see [:bug:`1722417`].
en_GB: A new setting ``OPENSTACK_INSTANCE_RETRIEVE_IP_ADDRESSES`` was introduced to control whether IP addresses of servers are retrieved from Neutron in the project instance table. This setting was introduced to mitigate a performance issue in large deployments and setting this to ``False`` skips the query to Neutron. Deployments without Floating IP support can set this setting to ``False`` for better performance. For more detail, see [:bug:`1722417`].

en: A shocking number of the problems first-time deployers of OpenStack have can be summarized as "I thought I set everything up, then I tried to log into the dashboard and I was immediately logged back out." The root cause of this was that in an effort to be as secure as possible any 401 or 403 response from any service API was being treated the same as if it was an attempt to access an unauthorized portion of Horizon, and the user was summarily logged out with little to no information as to why.
en_GB: A shocking number of the problems first-time deployers of OpenStack have can be summarized as "I thought I set everything up, then I tried to log into the dashboard and I was immediately logged back out." The root cause of this was that in an effort to be as secure as possible any 401 or 403 response from any service API was being treated the same as if it was an attempt to access an unauthorised portion of Horizon, and the user was summarily logged out with little to no information as to why.

en: ANGULAR_FEATURES now allows for a key 'flavors_panel' to be specified as True or False indicating whether the Angular version of the panel is enabled.
en_GB: ANGULAR_FEATURES now allows for a key 'flavours_panel' to be specified as True or False indicating whether the Angular version of the panel is enabled.

en: API call efficiency optimizations.
en_GB: API call efficiency optimisations.

en: Add "Create Network QoS Policy" button to QoS Policy Panel. From Horizon users can now create network qos policy.
en_GB: Add "Create Network QoS Policy" button to QoS Policy Panel. From Horizon users can now create a network QoS policy.

en: Add ``OPENSTACK_KEYSTONE_BACKEND`` manually into ``REST_API_REQUIRED_SETTINGS`` on ``local_settings.py``, if your deployment uses Angularized identity panels and needs to enable ``can_edit_*`` settings in ``OPENSTACK_KEYSTONE_BACKEND``.
en_GB: Add ``OPENSTACK_KEYSTONE_BACKEND`` manually into ``REST_API_REQUIRED_SETTINGS`` on ``local_settings.py``, if your deployment uses Angularised identity panels and needs to enable ``can_edit_*`` settings in ``OPENSTACK_KEYSTONE_BACKEND``.

en: Add support for horizon offering a clouds.yaml file for download along with the openrc files. For more information on clouds.yaml, see `os-client-config documentation <https://docs.openstack.org/os-client-config/latest/user/>`__.
en_GB: Add support for Horizon offering a clouds.yaml file for download along with the openrc files. For more information on clouds.yaml, see `os-client-config documentation <https://docs.openstack.org/os-client-config/latest/user/>`__.

en: Add support to portforwardings in the Network Floating IPs dashboard.
en_GB: Add support to port forwarding in the Network Floating IPs dashboard.

en: Added an ``cleanup_angular_template_cache`` management command, that clears template cache for angularized views. The command is available as ``./manage.py cleanup_angular_template_cache``.
en_GB: Added an ``cleanup_angular_template_cache`` management command, that clears template cache for Angularised views. The command is available as ``./manage.py cleanup_angular_template_cache``.

en: Added new setting INTEGRATION_TESTS_SUPPORT, default value is `False`. This value is used when running `manage.py compress` command, so by default all static assets and html classes used by integration tests are removed from Horizon production build. Integration tests gate job sets this variable to `True` and recompresses static assets.
en_GB: Added new setting INTEGRATION_TESTS_SUPPORT, default value is `False`. This value is used when running `manage.py compress` command, so by default all static assets and html classes used by integration tests are removed from Horizon production build. Integration tests gate job sets this variable to `True` and re-compresses static assets.

en: Added settings OPENSTACK_KEYSTONE_DOMAIN_DROPDOWN (boolean) and OPENSTACK_KEYSTONE_DOMAIN_CHOICES (tuple of tuples) to support a dropdown list of keystone domains to choose from at login. This should NOT be enabled for public clouds, as advertising enabled domains to unauthenticated users irresponsibly exposes private information. This is useful for private clouds that sit behind a corprate firewall and that have a small number of domains mapped to known corporate structures, such as an LDAP directory, Active Directory domains, geopgraphical regions or business units.
en_GB: Added settings OPENSTACK_KEYSTONE_DOMAIN_DROPDOWN (boolean) and OPENSTACK_KEYSTONE_DOMAIN_CHOICES (tuple of tuples) to support a dropdown list of keystone domains to choose from at login. This should NOT be enabled for public clouds, as advertising enabled domains to unauthenticated users irresponsibly exposes private information. This is useful for private clouds that sit behind a corporate firewall and that have a small number of domains mapped to known corporate structures, such as an LDAP directory, Active Directory domains, geographical regions or business units.

en: Added the Metadata tab to the new Launch Instance workflow to allow adding key-value metadata to an instance at launch. This includes any properties from the OS::Nova::Server namespace of the glance metadata definitions.
en_GB: Added the Metadata tab to the new Launch Instance workflow to allow adding key-value metadata to an instance at launch. This includes any properties from the OS::Nova::Server namespace of the Glance metadata definitions.

en: Added the Scheduler Hints tab to the new Launch Instance workflow to allow adding scheduler hints to an instance at launch. In addition to adding custom key-value pairs, the user can also choose from properties in the glance metadata definitions catalog that have the OS::Nova::Server resource type and scheduler_hints properties target.
en_GB: Added the Scheduler Hints tab to the new Launch Instance workflow to allow adding scheduler hints to an instance at launch. In addition to adding custom key-value pairs, the user can also choose from properties in the Glance metadata definitions catalogue that have the OS::Nova::Server resource type and scheduler_hints properties target.

en: Added the angular extensible service which allows angular horizon elements such as workflows, tables, actions, and forms to be extended dynamically by adding, removing, or replacing items. The extensible service is applied to every workflow created using the horizon workflow service. This includes the angular Launch Instance workflow.
en_GB: Added the angular extensible service which allows angular Horizon elements such as workflows, tables, actions, and forms to be extended dynamically by adding, removing, or replacing items. The extensible service is applied to every workflow created using the Horizon workflow service. This includes the angular Launch Instance workflow.

en: Added two charts to show the Number of Volumes and Total Volume Storage quotas on launch instance modal when cinder is enabled.
en_GB: Added two charts to show the Number of Volumes and Total Volume Storage quotas on launch instance modal when Cinder is enabled.

en: Adds complete support for Glance v2 so that Horizon no longer depends on having a Glance v1 endpoint in the Keystone catalog. Also provides code compatibility between Glance v1 and v2.
en_GB: Adds complete support for Glance v2 so that Horizon no longer depends on having a Glance v1 endpoint in the Keystone catalogue. Also provides code compatibility between Glance v1 and v2.

en: Adds options to gui to allow user to select which storage policy container will use and displays the container's storage policy in the container information.
en_GB: Adds options to GUI to allow user to select which storage policy container will use and displays the container's storage policy in the container information.

en: Allow external plugins to contribute translations to the Javascript message catalog.
en_GB: Allow external plugins to contribute translations to the Javascript message catalogue.

en: Also debuting in Havana is the OpenStack Metering project (Ceilometer). Initial support for Ceilometer is included in Horizon so that it is possible for an administrator to query the usage of the cloud through the OpenStack Dashboard and better understand how the system is functioning and being utilized.
en_GB: Also debuting in Havana is the OpenStack Metering project (Ceilometer). Initial support for Ceilometer is included in Horizon so that it is possible for an administrator to query the usage of the cloud through the OpenStack Dashboard and better understand how the system is functioning and being utilised.

en: Another addition is support for utilizing and restoring from incremental database backups.
en_GB: Another addition is support for utilising and restoring from incremental database backups.

en: Any past use of the Django based Swift UI is no longer supported and the code is being removed. The new angularJS based version should be used instead.
en_GB: Any past use of the Django based Swift UI is no longer supported and the code is being removed. The new AngularJS based version should be used instead.

en: As a result of Admin dashboard reorganization, panel groups of many Admin panels have been changed. Operators who customize Admin panels (for example, disable some Admin panels) through ``enabled`` directory need to update panel groups in ``enabled`` files. Horizon plugin developers and deployers may also need to update panel configurations under ``enabled`` directory to adapt the new Admin menus.
en_GB: As a result of Admin dashboard reorganisation, panel groups of many Admin panels have been changed. Operators who customise Admin panels (for example, disable some Admin panels) through ``enabled`` directory need to update panel groups in ``enabled`` files. Horizon plugin developers and deployers may also need to update panel configurations under ``enabled`` directory to adapt the new Admin menus.

en: As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilized like any other python dependency in Horizon.
en_GB: As part of the Horizon team's ongoing efforts to split the repository into more logical pieces, all the 3rd party JavaScript libraries that Horizon depends on have been removed from the Horizon code base and python xstatic packages have been utilized instead. The xstatic format allows for easy consumption by the Django framework Horizon is built on. Now JavaScript libraries are utilised like any other python dependency in Horizon.

en: By far the biggest UI/UX change in the Folsom release is the introduction of programmatic workflows. These components allow developers to create concise interactions that combine discrete tasks spanning multiple services and resources in a user-friendly way and with minimal boilerplate code. Within a workflow, related objects can also be dynamically created so users don't lose their place when they realize the item they wanted isn't currently available. Look for examples of these workflows in Launch Instance, Associate Floating IP, and Create/Edit Project.
en_GB: By far the biggest UI/UX change in the Folsom release is the introduction of programmatic workflows. These components allow developers to create concise interactions that combine discrete tasks spanning multiple services and resources in a user-friendly way and with minimal boilerplate code. Within a workflow, related objects can also be dynamically created so users don't lose their place when they realise the item they wanted isn't currently available. Look for examples of these workflows in Launch Instance, Associate Floating IP, and Create/Edit Project.

en: Centralized error handling for vastly improved stability/reliability across APIs/clients.
en_GB: Centralised error handling for vastly improved stability/reliability across APIs/clients.

en: Chinese locales ``zh-cn`` and ``zh-tw`` are now changed to ``zh-hans`` and ``zh-hant`` respectively. This follows the change in Django which is a framework horizon depends on. The new locales decouples what are spoken from specific locations as they are also used outside of China/Taiwan.
en_GB: Chinese locales ``zh-cn`` and ``zh-tw`` are now changed to ``zh-hans`` and ``zh-hant`` respectively. This follows the change in Django which is a framework Horizon depends on. The new locales decouples what are spoken from specific locations as they are also used outside of China/Taiwan.

en: Cinder consistency group support in horizon has been dropped in Train release. It was deprecated in Pike release in Cinder and deprecated in Stein release in Horizon. The feature is superseded by the generic group feature and horizon provides full support of the generic group.
en_GB: Cinder consistency group support in Horizon has been dropped in Train release. It was deprecated in Pike release in Cinder and deprecated in Stein release in Horizon. The feature is superseded by the generic group feature and horizon provides full support of the generic group.

en: Cinder consistency group support in horizon will be dropped in Train release or later. It was deprecated in Pike release in Cinder and was superseded by the generic group feature. Horizon supports the generic group since Rocky release.
en_GB: Cinder consistency group support in Horizon will be dropped in the Train release or later; it was deprecated in the Pike release in Cinder and was superseded by the generic group feature. Horizon supports the generic group since Rocky release.

en: Django 1.11 support was dropped. Django 1.11 ends its extended support in April 2020 which is before Ussuri release. Considering this, horizon dropped Django 1.11 support and use Django 2.2 as default.
en_GB: Django 1.11 support was dropped. Django 1.11 ends its extended support in April 2020 which is before Ussuri release. Considering this, Horizon dropped Django 1.11 support and use Django 2.2 as default.

en: Django 3.2 support is added. As of Xena release, it is considered as experimental. Considering Django 2.2 EOL, Django 3.2 will be the default Django version in Yoga release.
en_GB: Django 3.2 support is added. As of the Xena release, it is considered experimental. Considering Django 2.2 EOL, Django 3.2 will be the default Django version in the Yoga release.

en: Due to the mechanisms by which Keystone determines "admin"-ness for a user, an admin user interacting with the "Project" dashboard may see some inconsistent behavior such as all resources being listed instead of only those belonging to that project, or only being able to return to the "Admin" dashboard while accessing certain projects.
en_GB: Due to the mechanisms by which Keystone determines "admin"-ness for a user, an admin user interacting with the "Project" dashboard may see some inconsistent behaviour such as all resources being listed instead of only those belonging to that project, or only being able to return to the "Admin" dashboard while accessing certain projects.

en: Due to the way that Nova handles flavor editing/replacement it is necessary to delete the old flavor before creating the replacement flavor. As such, if an API error occurs while creating the replacement it is possible to lose the old flavor without the new one being created.
en_GB: Due to the way that Nova handles flavour editing/replacement it is necessary to delete the old flavour before creating the replacement flavour. As such, if an API error occurs while creating the replacement it is possible to lose the old flavour without the new one being created.

en: Editable and interactive network topology visualizations.
en_GB: Editable and interactive network topology visualisations.

en: Editing a Flavor Which Results In An API Error Will Delete The Flavor
en_GB: Editing a Flavour which results in an API error will delete the Flavour

en: Editing flavors is deprecated and may be removed from the 'R' cycle onwards.
en_GB: Editing flavours is deprecated and may be removed from the 'R' cycle onwards.

en: Enabled horizon to make use of cinder's feature to backup up snapshots of block storage volumes.
en_GB: Enabled Horizon to make use of Cinder's feature to backup up snapshots of block storage volumes.

en: Exceptions during customization
en_GB: Exceptions during customisation

en: Exceptions raised while overriding built-in Horizon behavior via the "customization_module" setting may trigger a bug in the error handling which will mask the original exception.
en_GB: Exceptions raised while overriding built-in Horizon behaviour via the "customization_module" setting may trigger a bug in the error handling which will mask the original exception.

en: FWaaS dashboard is now split out into a separate project ``neutron-fwaas-dashboard``. All new features and maintenances are provided from the new project from now on. The new project provides all features available in Horizon in the past release. To continue to use FWaaS dashboard, install ``neutron-fwaas-dashboard`` and set up the horizon plugin configuration file in ``enabled`` directory. For more information, see `neutron-fwaas-dashboard documentation <https://docs.openstack.org/neutron-fwaas-dashboard/latest/>`__.
en_GB: FWaaS dashboard is now split out into a separate project ``neutron-fwaas-dashboard``. All new features and maintenances are provided from the new project from now on. The new project provides all features available in Horizon in the past release. To continue to use FWaaS dashboard, install ``neutron-fwaas-dashboard`` and set up the Horizon plugin configuration file in ``enabled`` directory. For more information, see `neutron-fwaas-dashboard documentation <https://docs.openstack.org/neutron-fwaas-dashboard/latest/>`__.

en: Fix an error on image description field when it is changed in the Angularized panel [:bug: `1779879`]
en_GB: Fix an error on image description field when it is changed in the Angularised panel [:bug: `1779879`]

en: Flavor Extra Specs Support
en_GB: Flavour Extra Specs Support

en: Flavor editing was made significantly more stable.
en_GB: Flavour editing was made significantly more stable.

en: Floating IP addresses have a description field that is now exposed in the dashboard.  It is also possible to set the description when allocating a floating IP.
en_GB: Floating IP addresses have a description field that is now exposed in the dashboard.  It is also possible to set the description when allocating a Floating IP.

en: Fullscreen Modals have been deprecated in favor of modal-xl.  Currently, it is set to 95% of the viewable screen width.
en_GB: Fullscreen Modals have been deprecated in favour of modal-xl.  Currently, it is set to 95% of the viewable screen width.

en: Get the timezone offset for the current day instead of January 1st. This bug only appears to be a cosmetic one where the TZ offset would be calculated on current_year/01/01 so would remain in daylight saving offset when displaying the timezones list in the user configuration settings.
en_GB: Get the timezone offset for the current day instead of 1st January. This bug only appears to be a cosmetic one where the TZ offset would be calculated on current_year/01/01 so would remain in daylight saving offset when displaying the timezones list in the user configuration settings.

en: Glance v1 API support is now deprecated and will be dropped in Train release at earliest. It was removed from glance in Rokcy release.
en_GB: Glance v1 API support is now deprecated and will be dropped in Train release at earliest. It was removed from glance in Rocky release.

en: Going forward the user will not be logged out, but no information will be populated on the page and they will be presented with error messages informing them that they are unauthorized for the data they attempted to access.
en_GB: Going forward the user will not be logged out, but no information will be populated on the page and they will be presented with error messages informing them that they are unauthorised for the data they attempted to access.

en: Heat dashboard is now split out into a separate project ``heat-dashboard``. All new features and maintenances are provided from the new project from now on. The new project provides all features available in Horizon in the past release. To continue to use heat dashboard, install ``heat-dashboard`` and set up the horizon plugin configuration file in ``enabled`` directory. For more information, see ``heat-dashboard`` documentation https://docs.openstack.org/heat-dashboard/latest/.
en_GB: Heat dashboard is now split out into a separate project ``heat-dashboard``. All new features and maintenance are provided from the new project from now on. The new project provides all features available in Horizon in the past release. To continue to use Heat dashboard, install ``heat-dashboard`` and set up the Horizon plugin configuration file in ``enabled`` directory. For more information, see ``heat-dashboard`` documentation https://docs.openstack.org/heat-dashboard/latest/.

en: Horizon no longer requires the keystone admin endpoint. keystone does not distinguish public and admin endpoints and there is no functional difference between public and admin endpoints. There is no need for a separate endpoint for keystone admin operations, but horizon required the keystone admin endpoint is configured previously. This requirement no longer exists. An endpoint specified by ``OPENSTACK_ENDPOINT_TYPE`` setting is used for the keystone admin operations. You can drop the admin endpoint for keystone (unless other services require it). [:bug:`1950659`]
en_GB: Horizon no longer requires the keystone admin endpoint. Keystone does not distinguish between public and admin endpoints and there is no functional difference between public and admin endpoints. There is no need for a separate endpoint for keystone admin operations, but Horizon required the Keystone admin endpoint is configured previously. This requirement no longer exists. An endpoint specified by ``OPENSTACK_ENDPOINT_TYPE`` setting is used for the Keystone admin operations. You can drop the admin endpoint for Keystone (unless other services require it). [:bug:`1950659`]

en: Horizon now provides a Wizard control to complete multi-step interdependent tasks. This is now utilized in the create network action.
en_GB: Horizon now provides a Wizard control to complete multi-step interdependent tasks. This is now utilised in the create network action.

en: Horizon supports the registered default policies and operators now only need to define policies which they would like to override in policy files in ``POLICY_FILES`` setting. (Previously the policy files need to contain all defined policies including default policies.) The registered default policies are defined in files under ``DEFAULT_POLICY_FILES`` and they are synced with registered defaults of back-end services before the horizon release.
en_GB: Horizon supports the registered default policies and operators now only need to define policies which they would like to override in policy files in ``POLICY_FILES`` setting. (Previously the policy files need to contain all defined policies including default policies.) The registered default policies are defined in files under ``DEFAULT_POLICY_FILES`` and they are synced with registered defaults of back-end services before the Horizon release.

en: Horizon's structure has been divided into logical groupings called dashboards and panels. Horizon's classes representing these concepts handle all the structural concerns associated with building a complete user interface (navigation, access control, url structure, etc.).
en_GB: Horizon's structure has been divided into logical groupings called dashboards and panels. Horizon's classes representing these concepts handle all the structural concerns associated with building a complete user interface (navigation, access control, URL structure, etc.).

en: If your deployment uses the signed-cookies as a session engine, ensure that ``SESSION_ENGINE`` is configured to ``django.contrib.sessions.backends.signed_cookies`` before upgrading horizon to Stein release. If your deployment uses the cached session engine and your cache backend depends on horizon default setting, ensure to ``CACHES`` setting to use the local-memory backend.
en_GB: If your deployment uses the signed-cookies as a session engine, ensure that ``SESSION_ENGINE`` is configured to ``django.contrib.sessions.backends.signed_cookies`` before upgrading horizon to Stein release. If your deployment uses the cached session engine and your cache backend depends on Horizon default setting, ensure to ``CACHES`` setting to use the local-memory backend.

en: Improved unicode support for the Object Storage panels.
en_GB: Improved Unicode support for the Object Storage panels.

en: In Folsom, Nova added support for "extra specs" on flavors--additional metadata which custom schedulers could use for appropriately scheduling instances. As of the Grizzly release, Horizon now supports reading and writing that data on any flavor.
en_GB: In Folsom, Nova added support for "extra specs" on flavours--additional metadata which custom schedulers could use for appropriately scheduling instances. As of the Grizzly release, Horizon now supports reading and writing that data on any flavour.

en: In Grizzly we have instead chosen to improve this by treating service API 401 and 403 errors as slightly less severe than unauthorized access attempts to restricted areas of Horizon. The reason for this is threefold:
en_GB: In Grizzly we have instead chosen to improve this by treating service API 401 and 403 errors as slightly less severe than unauthorised access attempts to restricted areas of Horizon. The reason for this is threefold:

en: In Juno, Glance introduced the ability to manage a catalog of metadata definitions where users can register the metadata definitions to be used on various resource types including images, volumes, aggregates, and flavors. Support for viewing and editing the assignment of these metadata tags is included in Horizon.
en_GB: In Juno, Glance introduced the ability to manage a catalogue of metadata definitions where users can register the metadata definitions to be used on various resource types including images, volumes, aggregates, and flavours. Support for viewing and editing the assignment of these metadata tags is included in Horizon.

en: In Juno, Horizon transitioned to utilizing Bootstrap v3. Horizon had been pinned to an older version of Bootstrap for several releases. This change now allows Horizon to pick up numerous bug fixes and overall improvements in the Bootstrap framework. The look and feel remains mainly consistent with the Icehouse release.
en_GB: In Juno, Horizon transitioned to utilising Bootstrap v3. Horizon had been pinned to an older version of Bootstrap for several releases. This change now allows Horizon to pick up numerous bug fixes and overall improvements in the Bootstrap framework. The look and feel remains mainly consistent with the Icehouse release.

en: In an effort to establish Angular conventions, use the framework's toastService rather than the legacy horizon.alert(...) in client-side code. horizon.alert is still used by the django messaging framework, so horizon.messages.js still exists.
en_GB: In an effort to establish Angular conventions, use the framework's toastService rather than the legacy horizon.alert(...) in client-side code. horizon.alert is still used by the Django messaging framework, so horizon.messages.js still exists.

en: In an effort to standarize our HTML class naming conventions, we will be updating various class names to use dashes, instead of underscore or camelcasing, to match with Bootstrap's convention.
en_GB: In an effort to standardise our HTML class naming conventions, we will be updating various class names to use dashes, instead of underscore or camel-casing, to match with Bootstrap's convention.

en: In an ongoing effort to implement Role Based Access Support throughout Horizon, access controls were added in the OpenStack Volume (Cinder) related panels. Utilization of the Cinder v2 API is now a supported option in the Icehouse release. The ability to extend volumes is now available as well.
en_GB: In an ongoing effort to implement Role Based Access Support throughout Horizon, access controls were added in the OpenStack Volume (Cinder) related panels. Utilisation of the Cinder v2 API is now a supported option in the Icehouse release. The ability to extend volumes is now available as well.

en: In conjunction with the previous item, the dashboard-specific template blocks (e.g. ``nova_main``, ``syspanel_main``, etc.) have been removed in favor of a single ``main`` template block.
en_GB: In conjunction with the previous item, the dashboard-specific template blocks (e.g. ``nova_main``, ``syspanel_main``, etc.) have been removed in favour of a single ``main`` template block.

en: Instance shelving and unshelving now supported.
en_GB: Instance shelving and un-shelving now supported.

en: Integration tests for Flavor features may also be toggled in openstack_dashboard/test/integration_tests/horizon.conf using the 'panel_type' feature in the 'flavors' setting, either set to 'legacy' or 'angular' to match the enabled panel type.
en_GB: Integration tests for Flavour features may also be toggled in openstack_dashboard/test/integration_tests/horizon.conf using the 'panel_type' feature in the 'flavours' setting, either set to 'legacy' or 'angular' to match the enabled panel type.

en: Internationalization fully enabled, with all strings marked for translation.
en_GB: Internationalisation fully enabled, with all strings marked for translation.

en: Internationalization of client-side JavaScript is now possible in addition to server-side Python code.
en_GB: Internationalisation of client-side JavaScript is now possible in addition to server-side Python code.

en: Keystone v2 API support in horizon will be dropped in Train release. It was was removed from keystone in Queens release.
en_GB: Keystone v2 API support in Horizon will be dropped in Train release. It was was removed from Keystone in Queens release.

en: Large amounts of new documentation was added during the Grizzly cycle, most notably are sections documenting: all of the available settings for Horizon and the OpenStack Dashboard; security and deployment considerations; and deeper guides on customizing the OpenStack Dashboard.
en_GB: Large amounts of new documentation was added during the Grizzly cycle, most notably are sections documenting: all of the available settings for Horizon and the OpenStack Dashboard; security and deployment considerations; and deeper guides on customising the OpenStack Dashboard.

en: Loadbalancer Feature
en_GB: Load Balancer Feature

en: Making Horizon extensible for third-party developers was one of the core goals for the Essex release cycle. Massive strides have been made to allow for the addition of new "plug-in" components and customization of OpenStack Dashboard deployments.
en_GB: Making Horizon extensible for third-party developers was one of the core goals for the Essex release cycle. Massive strides have been made to allow for the addition of new "plug-in" components and customisation of OpenStack Dashboard deployments.

en: Multiattach capable volumes can only be attached with nova API microversion 2.60 or later.
en_GB: Multiattach capable volumes can only be attached with Nova API microversion 2.60 or later.

en: Neutron network type for Geneve tunneling protocol is now supported.
en_GB: Neutron network type for Geneve tunnelling protocol is now supported.

en: Neutron provider network configuration now becomes more flexible so that operators can configure various provider network parameters including new network type, segmenatiton ID ranges and so on based on neutron network back-ends they use.
en_GB: Neutron provider network configuration now becomes more flexible so that operators can configure various provider network parameters including new network type, segmentation ID ranges and so on based on neutron network back-ends they use.

en: New visualizations for utilization and quotas.
en_GB: New visualisations for utilisation and quotas.

en: Note that only horizon is verified with Django 2.2 and most horizon plugins are not verified with Django 2.2. If you enable horizon plugins in your environment, we would suggest to use Django 1.11 or 2.0. Be careful when you enable horizon plugins with Django 2.2.
en_GB: Note that only Horizon is verified with Django 2.2 and most Horizon plugins are not verified with Django 2.2. If you enable Horizon plugins in your environment, we would suggest to use Django 1.11 or 2.0. Be careful when you enable Horizon plugins with Django 2.2.

en: Note that operators need to create at least one group type so that users can use the generic group feature. Otherwise, it might be better to disable the group and group snapshot panels by the horizon plugin ``enabled`` files.
en_GB: Note that operators need to create at least one group type so that users can use the generic group feature. Otherwise, it might be better to disable the group and group snapshot panels by the Horizon plugin ``enabled`` files.

en: Nova and Glance are no longer required in order to run Horizon. As long as keystone is present, Horizon will run correctly.
en_GB: Nova and Glance are no longer required in order to run Horizon. As long as Keystone is present, Horizon will run correctly.

en: Nova-network support will be dropped in Train release completely. Horizon dropped nova-network floating IP and security gruop supports in Queens release, but we still supports operations on server instances created with nova-network. This deprecation means such support will be dropped in the near future and horizon will assume neutron is deployed.
en_GB: Nova-network support will be dropped in Train release completely. Horizon dropped nova-network floating IP and security group supports in Queens release, but we still supports operations on server instances created with nova-network. This deprecation means such support will be dropped in the near future and Horizon will assume Neutron is deployed.

en: PKI token support has been dropped from horizon. PKI token was removed from keystone in Ocata release which was released two years ago. It is a good timing to drop its support.
en_GB: PKI token support has been dropped from Horizon. PKI token was removed from Keystone in Ocata release which was released two years ago. It is a good timing to drop its support.

en: Panel group is introduced in the Admin dashboard to organize admin panels better. Panels in "System" group of Admin dashboard are now categorized into four groups: "Compute", "Volume", "Network" and "System".
en_GB: Panel group is introduced in the Admin dashboard to organize admin panels better. Panels in "System" group of Admin dashboard are now categorised into four groups: "Compute", "Volume", "Network" and "System".

en: Password forms in horizon now does not strip leading/trailing spaces included in input passwords. Previously horizon stripped leading/trailing spaces in input passwords but on the other hand keystone accepts leading/trailing spaces and it can be an issue when such passwords are set via keystone API. To handle this situation horizon no longer strips leading/trailing spaces in passwords. See [:bug:`1861224`] and `the related mailing thread <http://lists.openstack.org/pipermail/openstack-discuss/2020-January/thread.html#12222>`__ for more detail. (Note that this change is part of horizon 18.5.0 release but we forgot to mention it.)
en_GB: Password forms in Horizon now does not strip leading/trailing spaces included in input passwords. Previously Horizon stripped leading/trailing spaces in input passwords but on the other hand keystone accepts leading/trailing spaces and it can be an issue when such passwords are set via Keystone API. To handle this situation Horizon no longer strips leading/trailing spaces in passwords. See [:bug:`1861224`] and `the related mailing thread <http://lists.openstack.org/pipermail/openstack-discuss/2020-January/thread.html#12222>`__ for more detail. (Note that this change is part of Horizon 18.5.0 release but we forgot to mention it.)

en: Per-project flavor support.
en_GB: Per-project flavour support.

en: Previously horizon assumes only ``volume`` as an endpoint for the Cinder regardless of the API version. As a result, if deployers configure Cinder v2/v3 API endpoint as ``volumev2`` or ``volumev3``, Volume related menus -- "Create Volume from instance snapshot" and "Create instance from Volume" -- were not displayed. Horizon now checks the availability of the Block Storage service by looking for all posible endpoints ``volume``, ``volumev2`` and ``volumev3``.
en_GB: Previously Horizon assumes only ``volume`` as an endpoint for the Cinder regardless of the API version. As a result, if deployers configure Cinder v2/v3 API endpoint as ``volumev2`` or ``volumev3``, Volume related menus -- "Create Volume from instance snapshot" and "Create instance from Volume" -- were not displayed. Horizon now checks the availability of the Block Storage service by looking for all possible endpoints ``volume``, ``volumev2`` and ``volumev3``.

en: Provided the ability for plugins to contribute translations to the JavaScript message catalog. Previously the horizon and openstack_dahboard applications were hardcoded.
en_GB: Provided the ability for plugins to contribute translations to the JavaScript message catalogue. Previously the Horizon and openstack_dashboard applications were hardcoded.

en: Python 2.7 support has been dropped. Last release of horizon to support python 2.7 is OpenStack Train. The minimum version of Python now supported by horizon is Python 3.6.
en_GB: Python 2.7 support has been dropped. Last release of Horizon to support Python 2.7 is OpenStack Train. The minimum version of Python now supported by Horizon is Python 3.6.

en: Remove formerly deprecated initScope() function for Angularized actions. Instead use initAction() and get scope from second parameter of perform() function.
en_GB: Remove formerly deprecated initScope() function for Angularised actions. Instead use initAction() and get scope from second parameter of perform() function.

en: Reorganizations
en_GB: Reorganisations

en: Resizing of Trove instances -- changing instance flavor
en_GB: Resizing of Trove instances -- changing instance flavour

en: Router rules is a horizon extension provided by Big Switch Networks. As part of the horizon-vendor-split work, we drop the extension from upstream horizon. It is now available as a separate plugin at https://github.com/bigswitch/horizon-bsn
en_GB: Router rules is a Horizon extension provided by Big Switch Networks. As part of the Horizon-vendor-split work, we drop the extension from upstream Horizon. It is now available as a separate plugin at https://github.com/bigswitch/horizon-bsn

en: Securtiy group "Add rule" form now allows to specify 'any' IP protocol and 'any' port number (for TCP and UDP protocols). This feature is available when neutron is used as a networking back-end. You can specify 'any' IP protocol for 'Other Protocol' and ``-1`` means 'any' IP protocol. You can also see ``All ports`` choice in 'Open Port' field in case of TCP or UDP protocol is selected.
en_GB: Security group "Add rule" form now allows to specify 'any' IP protocol and 'any' port number (for TCP and UDP protocols). This feature is available when neutron is used as a networking back-end. You can specify 'any' IP protocol for 'Other Protocol' and ``-1`` means 'any' IP protocol. You can also see ``All ports`` choice in 'Open Port' field in case of TCP or UDP protocol is selected.

en: Setting 'can_set_password' to True in OPENSTACK_HYPERVISOR_FEATURES adds the option to set admin password from AngularJS Launch Instance dialog.
en_GB: Setting 'can_set_password' to True in OPENSTACK_HYPERVISOR_FEATURES adds the option to set admin password from AngularJS Launch Instance dialogue.

en: Several new indicators have been added to inform users why they've been logged out when they land on the login screen unexpectedly. These indicators make it clear whether the user's session has expired, they timed out due to inactivity, or they are not authorized for the section of the dashboard they attempted to access.
en_GB: Several new indicators have been added to inform users why they've been logged out when they land on the login screen unexpectedly. These indicators make it clear whether the user's session has expired, they timed out due to inactivity, or they are not authorised for the section of the dashboard they attempted to access.

en: String attributes ``action_present`` and ``action_past`` were dropped from ``horizon.tables.BatchAction``. ``action_present`` and ``action_past`` *methods* are the recommended way to define action labels for BatchAction. The offical way allows us to define more complete strings for action labels and this also allows translators to translate more flexibily.
en_GB: String attributes ``action_present`` and ``action_past`` were dropped from ``horizon.tables.BatchAction``. ``action_present`` and ``action_past`` *methods* are the recommended way to define action labels for BatchAction. The official way allows us to define more complete strings for action labels and this also allows translators to translate more flexibility.

en: Support for Federated authentication via Web Single-Sign-On -- When configured in keystone, the user will be able to choose the authentication mechanism to use from those support by the deployment. This feature must be enabled by changes to local_settings.py to be utilized. The related settings to enable and configure can be found `here <https://docs.openstack.org/horizon/latest/configuration/settings.html#websso-enabled>`__.
en_GB: Support for Federated authentication via Web Single-Sign-On -- When configured in Keystone, the user will be able to choose the authentication mechanism to use from those support by the deployment. This feature must be enabled by changes to local_settings.py to be utilised. The related settings to enable and configure can be found `here <https://docs.openstack.org/horizon/latest/configuration/settings.html#websso-enabled>`__.

en: Support for easily setting flavor extra specs
en_GB: Support for easily setting flavour extra specs

en: Support security groups association per network port for operators and users. Note that the current implementation only supports to edit security groups of neutron port from the port tables in the network detail page (Further improvement is planned).
en_GB: Support security groups association per network port for operators and users. Note that the current implementation only supports to edit security groups of Neutron port from the port tables in the network detail page (Further improvement is planned).

en: The Django version of the Images, Keypairs, and Roles panels is deprecated now. Switch to the AngularJS version by setting ``images_panel``, ``key_pairs_panel`` and ``roles_panel`` keys in ``ANGULAR_FEATURES`` setting to ``True`` (or dropping these keys from ``ANGULAR_FEATURES`` setting). The horizon team believes that feature gaps between Django and AngularJS implementations have been closed for all these panels and we can drop the Django version. If you see any feature gap, please file a bug to horizon or contact the horizon team.
en_GB: The Django version of the Images, Keypairs, and Roles panels is deprecated now. Switch to the AngularJS version by setting ``images_panel``, ``key_pairs_panel`` and ``roles_panel`` keys in ``ANGULAR_FEATURES`` setting to ``True`` (or dropping these keys from ``ANGULAR_FEATURES`` setting). The horizon team believes that feature gaps between Django and AngularJS implementations have been closed for all these panels and we can drop the Django version. If you see any feature gap, please file a bug to Horizon or contact the Horizon team.

en: The Django version of the launch instance form is deprecated now. Switch to the AngularJS version of the form by setting ``LAUNCH_INSTANCE_NG_ENABLED`` to ``True`` and ``LAUNCH_INSTANCE_LEGACY_ENABLED`` to ``False``. The horizon team believes that feature gaps between Django and AngularJS implementations have been closed and we can drop the Django version. If you see any feature gap, please file a bug to horizon or contact the horizon team.
en_GB: The Django version of the launch instance form is deprecated now. Switch to the AngularJS version of the form by setting ``LAUNCH_INSTANCE_NG_ENABLED`` to ``True`` and ``LAUNCH_INSTANCE_LEGACY_ENABLED`` to ``False``. The Horizon team believes that feature gaps between Django and AngularJS implementations have been closed and we can drop the Django version. If you see any feature gap, please file a bug to horizon or contact the Horizon team.

en: The Django version of the launch instance form was dropped. It was deprecated since Wallaby release. ``LAUNCH_INSTANCE_LEGACY_ENABLED`` and ``LAUNCH_INSTANCE_NG_ENABLED`` settings were dropped as horizon always uses the Angular version of the launch instance form.
en_GB: The Django version of the launch instance form was dropped. It was deprecated since the Wallaby release. ``LAUNCH_INSTANCE_LEGACY_ENABLED`` and ``LAUNCH_INSTANCE_NG_ENABLED`` settings were dropped as Horizon always uses the Angular version of the launch instance form.

en: The Flavor panel now may be configured to use either the legacy or Angular code.
en_GB: The Flavour panel now may be configured to use either the legacy or Angular code.

en: The HA property is updateable in the UI, however, Neutron API does not allow the update operation because toggling HA support does not work.
en_GB: The HA property is updatable in the UI, however, Neutron API does not allow the update operation because toggling HA support does not work.

en: The Loadbalancer feature landed in the 11th hour for both Quantum and Horizon and, though we did our best to test it, may still contain undiscovered bugs. It is best considered a "beta" or "experimental" feature for the Grizzly release.
en_GB: The Load Balancer feature landed in the 11th hour for both Quantum and Horizon and, though we did our best to test it, may still contain undiscovered bugs. It is best considered a "beta" or "experimental" feature for the Grizzly release.

en: The OpenStack Orchestration project (Heat) debuted in Havana, and Horizon delivers full support for managing your Heat stacks. Highlights include support for dynamic form generation from supported Heat template formats, stack topology visualizations, and full stack resource inspection.
en_GB: The OpenStack Orchestration project (Heat) debuted in Havana, and Horizon delivers full support for managing your Heat stacks. Highlights include support for dynamic form generation from supported Heat template formats, stack topology visualisations, and full stack resource inspection.

en: The Queens release of horizon depends on Django 1.8 to 1.11, but Django 1.8 to 1.10 support will be dropped in the next release (Rocky).
en_GB: The Queens release of Horizon depends on Django 1.8 to 1.11, but Django 1.8 to 1.10 support will be dropped in the next release (Rocky).

en: The ability to edit flavors is disabled by default. See ``ENABLE_FLAVOR_EDIT`` in the settings documentation for more information.
en_GB: The ability to edit flavours is disabled by default. See ``ENABLE_FLAVOR_EDIT`` in the settings documentation for more information.

en: The customization override templates have been deprecated in favor of using recursive inheritance in your themes. The following templates have been deprecated and are slated for removal in the U release: * ``_footer.html'`` * ``_login_footer.html`` * ``_login_form_footer.html`` * ``horizon/_custom_head_js.html`` * ``horizon/_custom_meta.html``
en_GB: The customisation override templates have been deprecated in favour of using recursive inheritance in your themes. The following templates have been deprecated and are slated for removal in the U release: * ``_footer.html'`` * ``_login_footer.html`` * ``_login_form_footer.html`` * ``horizon/_custom_head_js.html`` * ``horizon/_custom_meta.html``

en: The dashboard-specific ``base.html`` templates (e.g. ``nova/base.html``, ``syspanel/base.html``, etc.) have been removed in favor of a single ``base.html`` template.
en_GB: The dashboard-specific ``base.html`` templates (e.g. ``nova/base.html``, ``syspanel/base.html``, etc.) have been removed in favour of a single ``base.html`` template.

en: The default keystone API vesion is switch to ``v3``. If you still use the keystone v2.0 API by default, you need to configure ``OPENSTACK_API_VERSIONS`` and ``OPENSTACK_KEYSTONE_URL`` to point to the keystone v2.0 API.
en_GB: The default Keystone API version is switch to ``v3``. If you still use the keystone v2.0 API by default, you need to configure ``OPENSTACK_API_VERSIONS`` and ``OPENSTACK_KEYSTONE_URL`` to point to the Keystone v2.0 API.

en: The default value of ``SHOW_KEYSTONE_V2_RC`` setting is changed to ``False`` in favor of the deprecation of keystone v2 API support in horizon.
en_GB: The default value of ``SHOW_KEYSTONE_V2_RC`` setting is changed to ``False`` in favour of the deprecation of Keystone v2 API support in Horizon.

en: The default values of the settings listed in ``local_settings.py.example`` in past releases have been moved to ``openstack_dashboard/defaults.py``. By doing this, horizon can now provide the definitions of the default settings more explicitly. For the available settings, see ``openstack_dashboard/defaults.py`` and the horizon setting reference found at https://docs.openstack.org/horizon/latest/configuration/settings.html.
en_GB: The default values of the settings listed in ``local_settings.py.example`` in past releases have been moved to ``openstack_dashboard/defaults.py``. By doing this, Horizon can now provide the definitions of the default settings more explicitly. For the available settings, see ``openstack_dashboard/defaults.py`` and the horizon setting reference found at https://docs.openstack.org/horizon/latest/configuration/settings.html.

en: The deprecated feature of "Edit Flavor" was deleted Historically, Horizon has provided the ability to edit Flavors by deleting and creating a new one with the same information. This is not supported in the Nova API and causes unexpected issues and breakages.
en_GB: The deprecated feature of "Edit Flavour" was deleted. Historically, Horizon has provided the ability to edit Flavours by deleting and creating a new one with the same information. This is not supported in the Nova API and causes unexpected issues and breakages.

en: The final django TEMPLATE_LOADERS configuration will now be generated from TEMPLATE_LOADERS, CACHED_TEMPLATE_LOADERS and ADD_TEMPLATE_LOADERS settings. See the settings documentation for more information.
en_GB: The final Django TEMPLATE_LOADERS configuration will now be generated from TEMPLATE_LOADERS, CACHED_TEMPLATE_LOADERS and ADD_TEMPLATE_LOADERS settings. See the settings documentation for more information.

en: The function fix_auth_url_version() should be removed from openstack_auth library as soon as Horizon no longer needs it. The replacement function is fix_auth_url_version_prefix() which returns a fixed url and a boolean flag indicating if the url was actually fixed. Having a separate flag allows to emit more precise warning messages about inconsistencies in Keystone endpoint URL.
en_GB: The function fix_auth_url_version() should be removed from openstack_auth library as soon as Horizon no longer needs it. The replacement function is fix_auth_url_version_prefix() which returns a fixed URL and a boolean flag indicating if the URL was actually fixed. Having a separate flag allows to emit more precise warning messages about inconsistencies in Keystone endpoint URL.

en: The hard-coded run_tests commands for extracting translatable strings and updating message catalogs have been ported to django management commands as extract_messages and update_catalog. These accept several parameters to make them easier to use with downstream customisations and string modifications, but the default behaviour is the same as before.
en_GB: The hard-coded run_tests commands for extracting translatable strings and updating message catalogues have been ported to Django management commands as extract_messages and update_catalog. These accept several parameters to make them easier to use with downstream customisations and string modifications, but the default behaviour is the same as before.

en: The keystone v3 API now becomes the default keystone API version.
en_GB: The Keystone v3 API now becomes the default keystone API version.

en: The legacy way to retrive neutron resource usages is deprecated. In future, horizon will require ``quota_details`` neutron extension. In the legacy way, horizon list all related resources to count resource usage. It is not efficient and ``quota_details`` neutron extension was added to address it. It was implemented in Pike release and the enough migration period has passed, so we deprecate the legacy way.
en_GB: The legacy way to retrieve Neutron resource usages is deprecated. In future, Horizon will require ``quota_details`` Neutron extension. In the legacy way, Horizon list all related resources to count resource usage. It is not efficient and ``quota_details`` neutron extension was added to address it. It was implemented in Pike release and the enough migration period has passed, so we deprecate the legacy way.

en: The legacy way to retrive neutron resource usages was dropped and horizon now assumes the ``quota_details`` neutron API extension implemented in Pike release (over three years ago), so we expect this is available in all Wallaby neutron deployments.
en_GB: The legacy way to retrieve Neutron resource usages was dropped and Horizon now assumes the ``quota_details`` Neutron API extension implemented in Pike release (over three years ago), so we expect this is available in all Wallaby Neutron deployments.

en: 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.
en_GB: 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 behaviour will remain consistent.

en: The missing nova's os-aggregates policy rules are added to the dashboard.
en_GB: The missing Nova's os-aggregates policy rules are added to the dashboard.

en: The missing nova's os-flavors policy rules are added to the dashboard.
en_GB: The missing Nova's os-flavors policy rules are added to the dashboard.

en: The new setting ``OPENSTACK_SERVER_DEFAULT_USER_DATA`` allows an administrator to specify a default user data (e.g. comments or instructions for cloudinit) for new VMs. It can be a raw string or string template that accepts the request.
en_GB: The new setting ``OPENSTACK_SERVER_DEFAULT_USER_DATA`` allows an administrator to specify default user data (e.g. comments or instructions for cloud-init) for new VMs. It can be a raw string or string template that accepts the request.

en: The oslo concurrency minimum requirement has been raised from 3.5.0 to 3.7.1
en_GB: The Oslo concurrency minimum requirement has been raised from 3.5.0 to 3.7.1

en: The policy framework in horizon now supports policy directories per service. This corresponds to ``policy_dirs`` configuration option from "oslo.policy" library. The new setting ``POLICY_DIRS`` was introduced. The setting allows to define multiple policy directories per service. For example, it is useful for a case where multiple projects provide policy files like neutron stadium projects. For detail, see `the horizon Setting Reference <https://docs.openstack.org/horizon/latest/configuration/settings.html#policy-dirs>`__.
en_GB: The policy framework in Horizon now supports policy directories per service. This corresponds to ``policy_dirs`` configuration option from "oslo.policy" library. The new setting ``POLICY_DIRS`` was introduced. The setting allows to define multiple policy directories per service. For example, it is useful for a case where multiple projects provide policy files like neutron stadium projects. For detail, see `the horizon Setting Reference <https://docs.openstack.org/horizon/latest/configuration/settings.html#policy-dirs>`__.

en: 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.
en_GB: 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 deployment and disables corresponding panels if not available, so in most cases you do not need to take care of the change.

en: The supported stylesheets in Horizon have been converted to utilize SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing python based LESS compilers.
en_GB: The supported stylesheets in Horizon have been converted to utilise SCSS rather than LESS. The change was necessary due to a prevalent lack of support for LESS compilers in Python. This change also allowed us to upgrade to Bootstrap 3, as parts of the Bootstrap 3 LESS stylesheets were not supported by existing Python based LESS compilers.

en: To aid in continued maintenance of Horizon as a themable and customizable framework, the highly customized 'default' styles are being dropped in favor of standard Bootstrap styles. The 'default' theme will only house scss variable changes going forward.
en_GB: To aid in continued maintenance of Horizon as a themable and customizable framework, the highly customized 'default' styles are being dropped in favour of standard Bootstrap styles. The 'default' theme will only house SCSS variable changes going forward.

en: To change the behavior around hypervisor management in Horizon you must add the ``OPENSTACK_HYPERVISOR_FEATURES`` setting to your ``settings.py`` or ``local_settings.py`` file.
en_GB: To change the behaviour around hypervisor management in Horizon you must add the ``OPENSTACK_HYPERVISOR_FEATURES`` setting to your ``settings.py`` or ``local_settings.py`` file.

en: Trove supports using multiple types of datastores, e.g., mysql, redis, mongodb. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.
en_GB: Trove supports using multiple types of datastores, e.g., MySQL, Redis, MongoDB. Users can now select from the list of datastores supported by the cloud operator when creating their database instances.

en: Under The Hood
en_GB: Under The Bonnet

en: Under the Hood
en_GB: Under the Bonnet

en: Unnecessary API calls to back-end services are eliminated when checking the quota and usage in individual panels. Each panel checks a resource can be created by retrieving the current quota and usage for the resource. However, the previous implementation retrieves quota and usage of unrelated resources (For example, Nova usage is retrieved when checking a network usage). It can be a performance problem in large deployments. This behavior is now fixed to load quota and usage only for resources which are really required.
en_GB: Unnecessary API calls to back-end services are eliminated when checking the quota and usage in individual panels. Each panel checks a resource can be created by retrieving the current quota and usage for the resource. However, the previous implementation retrieves quota and usage of unrelated resources (For example, Nova usage is retrieved when checking a network usage). It can be a performance problem in large deployments. This behaviour is now fixed to load quota and usage only for resources which are really required.

en: UpdateAction is deprecated in Newton and removed now. You should not use inline edit functionality in your plugins anymore.
en_GB: UpdateAction was deprecated in Newton and removed now. You should not use inline edit functionality in your plugins any more.

en: User language preference customization.
en_GB: User language preference customisation.

en: Very early in the Grizzly cycle we took the opportunity to do some longstanding cleanup and refactoring work. The "nova" dashboard was renamed to "project" and the "syspanel" dashboard was renamed to "admin" to better reflect their respective purposes.
en_GB: Very early in the Grizzly cycle we took the opportunity to do some long-standing clean-up and refactoring work. The "Nova" dashboard was renamed to "Project" and the "Syspanel" dashboard was renamed to "Admin" to better reflect their respective purposes.

en: Volume backups is now supported for admin panel. Admin is now able to view all volume backups for differenet users.
en_GB: Volume backups is now supported for admin panel. Admin is now able to view all volume backups for different users.

en: Volume v2 API support is now deprecated. The API has been marked as deprecated in cinder in favor of volume v3 API. Horizon will drop volume v2 API support in a same release where cinder drops it.
en_GB: Volume v2 API support is now deprecated. The API has been marked as deprecated in Cinder in favour of volume v3 API. Horizon will drop volume v2 API support in a same release where Cinder drops it.

en: We've now improved it so that the button to open the menu is clearly labeled and the hitbox for clicking it is significantly larger.
en_GB: We've now improved it so that the button to open the menu is clearly labelled and the hitbox for clicking it is significantly larger.

en: When multiple availability zones are available, the default behavior is to allow the scheduler to spawn a VM in any of them. The new setting ``LAUNCH_INSTANCE_DEFAULTS.default_availability_zone`` allows an administrator to specify a default static availability zone for new VM creation.
en_GB: When multiple availability zones are available, the default behaviour is to allow the scheduler to spawn a VM in any of them. The new setting ``LAUNCH_INSTANCE_DEFAULTS.default_availability_zone`` allows an administrator to specify a default static availability zone for new VM creation.

en: With the fixes in Rocky that allow using Django's recursive template inheritance we have added new blocks in our ``base.html`` template to allow a better means of customizing through your themes. For details see the ``customizing`` docs.
en_GB: With the fixes in Rocky that allow using Django's recursive template inheritance we have added new blocks in our ``base.html`` template to allow a better means of customising through your themes. For details see the ``customizing`` docs.

en: [:blueprint:`cinder-generic-volume-groups`] Cinder generic groups is now supported for admin panel. Admin is now able to view all groups and group snapshots for differenet users. Also group-type and group-type-spec support added to admin panel. Admin is able to create group-type and group-type-spec now.
en_GB: [:blueprint:`cinder-generic-volume-groups`] Cinder generic groups is now supported for admin panel. Admin is now able to view all groups and group snapshots for different users. Also group-type and group-type-spec support added to admin panel. Admin is able to create group-type and group-type-spec now.

en: [:blueprint:`drop-nova-network`] Horizon nova-network floating IP and security groups supports have been dropped in Pike release. nova-network has been marked as deprecated in Nova in Newton release and horizon support was dropped in favor of it. Neutron now becomes a requirement for floating IP and security groups. Other operations on instances which created with nova-network should work same as before.
en_GB: [:blueprint:`drop-nova-network`] Horizon nova-network floating IP and security groups supports have been dropped in Pike release. nova-network has been marked as deprecated in Nova in Newton release and Horizon support was dropped in favour of it. Neutron now becomes a requirement for floating IP and security groups. Other operations on instances which created with nova-network should work same as before.

en: [:blueprint:`handle-multiple-login-sessions-from-same-user-in-horizon`] This blueprint allows operators to control if multiple simultaneous dashboard sessions are allowed or not for a user. A new setting ``SIMULTANEOUS_SESSIONS`` controls the behavior. The default behavior allows multiple dashboard sessions for a user. The new setting allows operators to configure horizon to disallow multiple sessions per user. When multiple simultaneous sessions are disabled, the most recent authenticated session will be considered as the valid one and the previous session will be invalidated.
en_GB: [:blueprint:`handle-multiple-login-sessions-from-same-user-in-horizon`] This blueprint allows operators to control if multiple simultaneous dashboard sessions are allowed or not for a user. A new setting ``SIMULTANEOUS_SESSIONS`` controls the behaviour. The default behaviour allows multiple dashboard sessions for a user. The new setting allows operators to configure horizon to disallow multiple sessions per user. When multiple simultaneous sessions are disabled, the most recent authenticated session will be considered the valid one and the previous session will be invalidated.

en: [:blueprint:`horizon-plugin-tab-for-info-and-quotas`] (for horizon plugin developers) Django workflow step is now pluggable and horizon plugins can add extra step(s) to an existing workflow provided by horizon or other horizon plugins. Extra steps can be added via the horizon plugin “enabled” file. For more detail, see ``EXTRA_TABS`` description in `Pluggable Panels and Groups <https://docs.openstack.org/horizon/latest/configuration/pluggable_panels.html#extra-steps>`__ of the horizon documentation.
en_GB: [:blueprint:`horizon-plugin-tab-for-info-and-quotas`] (for horizon plugin developers) Django workflow step is now pluggable and Horizon plugins can add extra step(s) to an existing workflow provided by Horizon or other Horizon plugins. Extra steps can be added via the Horizon plugin “enabled” file. For more detail, see ``EXTRA_TABS`` description in `Pluggable Panels and Groups <https://docs.openstack.org/horizon/latest/configuration/pluggable_panels.html#extra-steps>`__ of the Horizon documentation.

en: [:blueprint:`merge-openstack-auth`] ``django_openstack_auth`` was merged into the main horizon repository. Ensure to uninstall ``django-openstack-auth`` python package **BEFORE** upgrading horizon to Queens.
en_GB: [:blueprint:`merge-openstack-auth`] ``django_openstack_auth`` was merged into the main Horizon repository. Ensure to uninstall ``django-openstack-auth`` python package **BEFORE** upgrading Horizon to Queens.

en: [:bug:`1337473`] The default quotas of neutron resource for a new project are no longer got from the quotas of the current project. Neutron did not provide a way to retrieve the default quotas and horizon used the quotas of the current project as the default quotas for a new project as a workaround. Neutron implemented an API to retrieve default quotas since newton and horizon now consumes it.
en_GB: [:bug:`1337473`] The default quotas of Neutron resource for a new project are no longer received from the quotas of the current project. Neutron did not provide a way to retrieve the default quotas and Horizon used the quotas of the current project as the default quotas for a new project as a workaround. Neutron implemented an API to retrieve default quotas since Newton, and Horizon now consumes it.

en: [:bug:`1690433`] "Get me a network" feature provided by nova and neutron is now exposed in the launch server form. This feature will sets up a neutron network topology for a project if there is no network in the project. It simplifies the workflow when launching a server. In the horizon support, when there is no network which can be used for a server, a dummy network named 'auto_allocated_network' is shown in the network choices. The feature is disabled by default because it requires preparations in your neutron deployment. To enable it, set ``enable_auto_allocated_network`` in ``OPENSTACK_NEUTRON_NETWORK`` to ``True``.
en_GB: [:bug:`1690433`] "Get me a network" feature provided by Nova and Neutron is now exposed in the launch server form. This feature will sets up a Neutron network topology for a project if there is no network in the project. It simplifies the workflow when launching a server. In the Horizon support, when there is no network which can be used for a server, a dummy network named 'auto_allocated_network' is shown in the network choices. The feature is disabled by default because it requires preparations in your neutron deployment. To enable it, set ``enable_auto_allocated_network`` in ``OPENSTACK_NEUTRON_NETWORK`` to ``True``.

en: [:bug:`1700325`] Horizon now allows to override an embeded default plugin enabled file by specifying an enabled plguin file with a same filename. If there are plugin enabled files with a same name both in ``enabled`` and ``local/enabled`` directories, the file in ``local/enabled`` will be used and the file in ``enabled`` will be ignored now. Previously, both files are processed in the order of ``enabled`` and then ``local/enabled`` in this case, but this made operators difficult to change the order of panels from the default order.
en_GB: [:bug:`1700325`] Horizon now allows to override an embedded default plugin enabled file by specifying an enabled plugin file with a same filename. If there are plugin enabled files with a same name both in ``enabled`` and ``local/enabled`` directories, the file in ``local/enabled`` will be used and the file in ``enabled`` will be ignored now. Previously, both files are processed in the order of ``enabled`` and then ``local/enabled`` in this case, but this made operators difficult to change the order of panels from the default order.

en: [:bug:`1744670`] Previously when a custom SSL CA is used horizon cannot retrieve volume and snapshot information from cinder. It is fixed now and a custom CA is handled properly in horizon when communicating with cinder.
en_GB: [:bug:`1744670`] Previously when a custom SSL CA is used Horizon cannot retrieve volume and snapshot information from Cinder. It is fixed now and a custom CA is handled properly in Horizon when communicating with Cinder.

en: [:bug:`1746754`] (for horizon plugin developers) Django tab is now pluggable and horizon plugins can add extra tab(s) to an existing tab provided by horizon or other horizon plugins. Extra tabs can be added via the horizon plugin "enabled" file. For more detail, see ``EXTRA_TABS`` description in `Pluggable Panels and Groups <https://docs.openstack.org/horizon/latest/configuration/pluggable_panels.html#extra-tabs>`__ of the horizon documentation.
en_GB: [:bug:`1746754`] (for horizon plugin developers) Django tab is now pluggable and Horizon plugins can add extra tab(s) to an existing tab provided by Horizon or other Horizon plugins. Extra tabs can be added via the Horizon plugin "enabled" file. For more detail, see ``EXTRA_TABS`` description in `Pluggable Panels and Groups <https://docs.openstack.org/horizon/latest/configuration/pluggable_panels.html#extra-tabs>`__ of the Horizon documentation.

en: [:bug:`1755339`] (for horizon plugin developers) A new plugin option ``ADD_XSTATIC_MODULES`` is now available and horizon plugins can add extra xstatic modules via the horizon plugin "enabled" file. For more detail, see ``ADD_XSTATIC_MODULES`` description in `Pluggable Panels and Groups <https://docs.openstack.org/horizon/latest/configuration/pluggable_panels.html#ADD_XSTATIC_MODULES>`__ in horizon documentation.
en_GB: [:bug:`1755339`] (for horizon plugin developers) A new plugin option ``ADD_XSTATIC_MODULES`` is now available and Horizon plugins can add extra xstatic modules via the Horizon plugin "enabled" file. For more detail, see ``ADD_XSTATIC_MODULES`` description in `Pluggable Panels and Groups <https://docs.openstack.org/horizon/latest/configuration/pluggable_panels.html#ADD_XSTATIC_MODULES>`__ in Horizon documentation.

en: [:bug:`1763204`] Use of this 'djano.wsgi' file has been deprecated since the Rocky release in favor of 'wsgi.py' in the 'openstack_dashboard' module. This file is a legacy naming from before Django 1.4 and an importable 'wsgi.py' is now the default. This file will be removed in the T release cycle.
en_GB: [:bug:`1763204`] Use of this 'djano.wsgi' file has been deprecated since the Rocky release in favour of 'wsgi.py' in the 'openstack_dashboard' module. This file is a legacy naming from before Django 1.4 and an importable 'wsgi.py' is now the default. This file will be removed in the T release cycle.

en: [:bug:`1772345`] ``DEFAULT_SERVICE_REGIONS`` no longer overrides the cookie value from ``services_region``. This fixes the UX where a user controlled value keeps being overridden by a setting and changes ``DEFAULT_SERVICE_REGIONS`` to act as a default (as the name implies) per endpoint if the cookie is not set rather than an override. The cookie will still be overridden when it is for a region not present in the user's current catalog, so this will still handle the original multi-keystone case that requried the introduction of ``DEFAULT_SERVICE_REGIONS``.
en_GB: [:bug:`1772345`] ``DEFAULT_SERVICE_REGIONS`` no longer overrides the cookie value from ``services_region``. This fixes the UX where a user controlled value keeps being overridden by a setting and changes ``DEFAULT_SERVICE_REGIONS`` to act as a default (as the name implies) per endpoint if the cookie is not set rather than an override. The cookie will still be overridden when it is for a region not present in the user's current catalogue, so this will still handle the original multi-keystone case that required the introduction of ``DEFAULT_SERVICE_REGIONS``.

en: [:bug:`1779268`] Supported ``can_edit_*`` settings in Angularized identity panels. To enable this settings in Angularized identity panels, add ``OPENSTACK_KEYSTONE_BACKEND`` into ``REST_API_REQUIRED_SETTINGS`` on ``local_settings.py``. For more detail, see `REST_API_REQUIRED_SETTINGS <https://docs.openstack.org/horizon/latest/configuration/settings.html#rest-api-required-settings>`__ in horizon settings documentation.
en_GB: [:bug:`1779268`] Supported ``can_edit_*`` settings in Angularised identity panels. To enable this settings in Angularised identity panels, add ``OPENSTACK_KEYSTONE_BACKEND`` into ``REST_API_REQUIRED_SETTINGS`` on ``local_settings.py``. For more detail, see `REST_API_REQUIRED_SETTINGS <https://docs.openstack.org/horizon/latest/configuration/settings.html#rest-api-required-settings>`__ in horizon settings documentation.

en: [:bug:`1795851`] Operators now can control whether the links of "Download OpenRC" and "Download clouds.yaml" are displayed or not via new settings ``SHOW_OPENRC_FILE`` and ``SHOW_OPENSTACK_CLOUDS_YAML``. ``openrc`` and ``clouds.yaml`` files provided by horizon now assume the basic simple deployment and do not cover keystone authentication like saml2, openid and so on. The default ``openrc`` and ``clouds.yaml`` from horizon do not make sense for such environments.
en_GB: [:bug:`1795851`] Operators now can control whether the links of "Download OpenRC" and "Download clouds.yaml" are displayed or not via new settings ``SHOW_OPENRC_FILE`` and ``SHOW_OPENSTACK_CLOUDS_YAML``. ``openrc`` and ``clouds.yaml`` files provided by Horizon now assume the basic simple deployment and do not cover Keystone authentication like saml2, openid and so on. The default ``openrc`` and ``clouds.yaml`` from Horizon do not make sense for such environments.

en: [:bug:`1874705`] Add a new variable WEBSSO_USE_HTTP_REFERER to facilitate WEBSSO deployments where network segmentation is used per security requirement. In this case, the controllers cannot reach other services external endpoints. Therefore, using the HTTP_REFERER to derive the Keystone endpoint in the websso view will return a timeout for requests to Keystone in cases where the external Keystone endpoint is the HTTP_REFERER. WEBSSO_USE_HTTP_REFERER defaults to True to keep inline with current functionality. When set to False the OPENSTACK_KEYSTONE_URL is used instead of the HTTP_REFERER. If OPENSTACK_KEYSTONE_URL is set to the internal Keystone endpoint the requests between Horizon and Keystone should be able to connect.
en_GB: [:bug:`1874705`] Add a new variable WEBSSO_USE_HTTP_REFERER to facilitate WEBSSO deployments where network segmentation is used per security requirement. In this case, the controllers cannot reach other services' external endpoints. Therefore, using the HTTP_REFERER to derive the Keystone endpoint in the websso view will return a timeout for requests to Keystone in cases where the external Keystone endpoint is the HTTP_REFERER. WEBSSO_USE_HTTP_REFERER defaults to True to keep inline with current functionality. When set to False the OPENSTACK_KEYSTONE_URL is used instead of the HTTP_REFERER. If OPENSTACK_KEYSTONE_URL is set to the internal Keystone endpoint the requests between Horizon and Keystone should be able to connect.

en: [`blueprint angular-table-directive <https://blueprints.launchpad.net/horizon/+spec/angular-table-directive>`_] This blueprint provides a way for developers to programatically declare an Angular table vs writing HTML markup. It reduces the boilerplate HTML code. For a basic table, you need to pass in the data and the column configuration into the `hz-dynamic-table` directive.
en_GB: [`blueprint angular-table-directive <https://blueprints.launchpad.net/horizon/+spec/angular-table-directive>`_] This blueprint provides a way for developers to programmatically declare an Angular table vs writing HTML markup. It reduces the boilerplate HTML code. For a basic table, you need to pass in the data and the column configuration into the `hz-dynamic-table` directive.

en: [`blueprint application-credentials <https://blueprints.launchpad.net/horizon/+spec/application-credentials>`_] Adds a new panel for creating, viewing, and deleting keystone application credentials.
en_GB: [`blueprint application-credentials <https://blueprints.launchpad.net/horizon/+spec/application-credentials>`_] Adds a new panel for creating, viewing, and deleting Keystone application credentials.

en: [`blueprint extensible-header <https://blueprints.launchpad.net/horizon/+spec/extensible-header>`_] Added a feature to insert custom headers into horizon's topbar.
en_GB: [`blueprint extensible-header <https://blueprints.launchpad.net/horizon/+spec/extensible-header>`_] Added a feature to insert custom headers into Horizon's topbar.

en: [`blueprint keystone-federation-mapping <https://blueprints.launchpad.net/horizon/+spec/keystone-federation-mapping>`_] Add basic support for managing keystone federation mapping.
en_GB: [`blueprint keystone-federation-mapping <https://blueprints.launchpad.net/horizon/+spec/keystone-federation-mapping>`_] Add basic support for managing Keystone federation mapping.

en: [`blueprint kubernetes-config-gen <https://blueprints.launchpad.net/horizon/+spec/kubernetes-config-gen>`_] Horizon now supports the optional automatic generation of a Kubernetes configuration file (kubeconfig) based on application credentials. Adds a new download button for this purpose in the application credentials creation dialog.
en_GB: [`blueprint kubernetes-config-gen <https://blueprints.launchpad.net/horizon/+spec/kubernetes-config-gen>`_] Horizon now supports the optional automatic generation of a Kubernetes configuration file (kubeconfig) based on application credentials. Adds a new download button for this purpose in the application credentials creation dialogue.

en: [`blueprint message-of-the-day <https://blueprints.launchpad.net/horizon/+spec/message-of-the-day>`_] Message of the day can now be configured in horizon, this will be displayed to the user whenever they login. To enable the feature set ``MESSAGES_PATH`` in the local_settting.py to the directory where message files are located. The message file must have a .json file extension.
en_GB: [`blueprint message-of-the-day <https://blueprints.launchpad.net/horizon/+spec/message-of-the-day>`_] Message of the day can now be configured in Horizon, this will be displayed to the user whenever they login. To enable the feature set ``MESSAGES_PATH`` in the local_settting.py to the directory where message files are located. The message file must have a .json file extension.

en: [`blueprint neutron-rbac-policies <https://blueprints.launchpad.net/horizon/+spec/rbac-policies>`_] This blueprint adds RBAC policies panel to the Admin Network group. This panel will be enabled by default when the RBAC extension is enabled. Remove this panel by setting "'enable_rbac_policy': False" in 'local_settings.py'. RBAC policy supports the control of two resources: networks and qos policies, because qos policies is an extension function of neutron, need to enable this extension if wants to use it.
en_GB: [`blueprint neutron-rbac-policies <https://blueprints.launchpad.net/horizon/+spec/rbac-policies>`_] This blueprint adds RBAC policies panel to the Admin Network group. This panel will be enabled by default when the RBAC extension is enabled. Remove this panel by setting "'enable_rbac_policy': False" in 'local_settings.py'. RBAC policy supports the control of two resources: networks and QoS policies, because QoS policies is an extension function of neutron, need to enable this extension if wants to use it.

en: [`blueprint ng-server-groups <https://blueprints.launchpad.net/horizon/+spec/ng-server-groups>`_] This blueprint add angular server groups panel below the Project->Compute panel group. The panel turns on if Nova API extension 'ServerGroups' is available. It displays information about server groups. The details page for each server group also shows information about instances of that server group. Supported actions: create, delete.
en_GB: [`blueprint ng-server-groups <https://blueprints.launchpad.net/horizon/+spec/ng-server-groups>`_] This blueprint add Angular server groups panel below the Project->Compute panel group. The panel turns on if Nova API extension 'ServerGroups' is available. It displays information about server groups. The details page for each server group also shows information about instances of that server group. Supported actions: create, delete.

en: [`blueprint pagination-for-flavor <https://blueprints.launchpad.net/horizon/+spec/pagination-for-flavor>`_] Added forward and backward pagination to the Flavors panel
en_GB: [`blueprint pagination-for-flavor <https://blueprints.launchpad.net/horizon/+spec/pagination-for-flavor>`_] Added forward and backward pagination to the Flavours panel

en: [`blueprint refactor-error-messages <https://blueprints.launchpad.net/horizon/+spec/refactor-error-messages>`_] User can see detailed error message on the horizon UI. This blueprint adds a hyperlink "details" in the alert box. So now when an exception occurs a user can click on this hyperlink "details" which shows original error message included in a corresponding error. This may help a user to understand what happens in detail.
en_GB: [`blueprint refactor-error-messages <https://blueprints.launchpad.net/horizon/+spec/refactor-error-messages>`_] User can see detailed error message on the Horizon UI. This blueprint adds a hyperlink "details" in the alert box. So now when an exception occurs a user can click on this hyperlink "details" which shows original error message included in a corresponding error. This may help a user to understand what happens in detail.

en: [`bug/1733271 <https://bugs.launchpad.net/horizon/1744271>`_] Users panel has Angularized, but buttons showing passwords is not implemented, i.e. for Password, Confirm Password and Admin password. Also, button adding project for selection of Primary Project is not implemented.
en_GB: [`bug/1733271 <https://bugs.launchpad.net/horizon/1744271>`_] Users panel has Angularised, but buttons showing passwords is not implemented, i.e. for Password, Confirm Password and Admin password. Also, button adding project for selection of Primary Project is not implemented.

en: ``OPENSTACK_ENDPOINT_TYPE`` setting now has a consistent default value and it defaults to ``publicURL``. If you use the default value, previously (at least Ocata release) Horizon used ``internalURL`` for keystone and ``publicURL`` for other services. The default value is now ``publicURL``, so if you want horizon to use ``internalURL`` to talk with back-end services, ensure to set ``OPENSTACK_ENDPOINT_TYPE`` to ``internalURL``.
en_GB: ``OPENSTACK_ENDPOINT_TYPE`` setting now has a consistent default value and it defaults to ``publicURL``. If you use the default value, previously (at least Ocata release) Horizon used ``internalURL`` for Keystone and ``publicURL`` for other services. The default value is now ``publicURL``, so if you want Horizon to use ``internalURL`` to talk with back-end services, ensure to set ``OPENSTACK_ENDPOINT_TYPE`` to ``internalURL``.

en: ``OPENSTACK_NOVA_EXTENSIONS_BLACKLIST`` option is deprecated. All of the nova API extensions have been mainlined several releases ago and there is no potential performance issue in the nova API. This option is used only to toggle features in horizon and there seems no performance issues controlled by the option in horizon. Considering this situation, this option is deprecated now.
en_GB: ``OPENSTACK_NOVA_EXTENSIONS_BLACKLIST`` option is deprecated. All of the nova API extensions have been mainlined several releases ago and there is no potential performance issue in the nova API. This option is used only to toggle features in Horizon and there seems no performance issues controlled by the option in Horizon. Considering this situation, this option is deprecated now.

en: ``OPENSTACK_NOVA_EXTENSIONS_BLACKLIST`` setting is now dropped. If you specify ``SimpleTenantUsage`` in this setting, consider setting ``OPENSTACK_USE_SIMPLE_TENANT_USAGE`` to ``False`` instead. For other effective values in this setting, no replacement is provided as nova provides all features in recent versions of nova API. Note that you can enable/disable table actions via policy rules.
en_GB: ``OPENSTACK_NOVA_EXTENSIONS_BLACKLIST`` setting is now dropped. If you specify ``SimpleTenantUsage`` in this setting, consider setting ``OPENSTACK_USE_SIMPLE_TENANT_USAGE`` to ``False`` instead. For other effective values in this setting, no replacement is provided as nova provides all features in recent versions of Nova API. Note that you can enable/disable table actions via policy rules.

en: ``SHOW_KEYSTONE_V2_RC`` setting is deprecated in favor of the deprecation of keystone v2 API support in horizon.
en_GB: ``SHOW_KEYSTONE_V2_RC`` setting is deprecated in favour of the deprecation of Keystone v2 API support in Horizon.

en: ``enable_quotas`` in ``OPENSTACK_NEUTRON_NETWORK`` is now enabled by default. Neutron provides the quotas API for long and most horizon deployments are expected to enable this, so the feature is enabled by default. If your deployment disables the neutron quotas support, make sure to set this value to ``False``.
en_GB: ``enable_quotas`` in ``OPENSTACK_NEUTRON_NETWORK`` is now enabled by default. Neutron provides the quotas API for long and most Horizon deployments are expected to enable this, so the feature is enabled by default. If your deployment disables the Neutron quotas support, make sure to set this value to ``False``.

en: ``simple_ip_management`` setting in ``HORIZON_CONFIG`` was dropped. This actually has no meaning after nova-network support was dropped in Pike. If you use this setting to hide ``Disassociate Floating IP`` button in the instance table, use the policy file instead.
en_GB: ``simple_ip_management`` setting in ``HORIZON_CONFIG`` was dropped. This actually has no meaning after Nova-Network support was dropped in Pike. If you use this setting to hide ``Disassociate Floating IP`` button in the instance table, use the policy file instead.
