horizon 23.4.0.dev3 - en to en_GB translation catalogue (94 entries)

en: A custom theme directory can be organized differently, depending on the level of customization that is desired, as it can include static files as well as Django templates.  It can include special subdirectories that will be used differently: ``static``, ``templates`` and ``img``.
en_GB: A custom theme directory can be organised differently, depending on the level of customisation that is desired, as it can include static files as well as Django templates.  It can include special subdirectories that will be used differently: ``static``, ``templates`` and ``img``.

en: A dictionary containing classes of exceptions which Horizon's centralized exception handling should be aware of. Based on these exception categories, Horizon will handle the exception and display a message to the user.
en_GB: A dictionary containing classes of exceptions which Horizon's centralised exception handling should be aware of. Based on these exception categories, Horizon will handle the exception and display a message to the user.

en: A list of javascript source files to be included in the compressed set of files that are loaded on every page. This is needed for AngularJS modules that are referenced in ``angular_modules`` and therefore need to be include in every page.
en_GB: A list of JavaScript source files to be included in the compressed set of files that are loaded on every page. This is needed for AngularJS modules that are referenced in ``angular_modules`` and therefore need to be include in every page.

en: A list of javascript spec files to include for integration with the Jasmine spec runner. Jasmine is a behavior-driven development framework for testing JavaScript code.
en_GB: A list of JavaScript spec files to include for integration with the Jasmine spec runner. Jasmine is a behaviour-driven development framework for testing JavaScript code.

en: A list of names of services for which the system scope token should be used. If empty, system scope will be removed from the context switching menu. If not empty, the context switching menu will show a "system scope" option, and the admin panels for the services listed will be moved to that context, no longer showing up in the project context.
en_GB: A list of names of services for which the system scope token should be used. If empty, the system scope will be removed from the context switching menu. If not empty, the context switching menu will show a "system scope" option, and the admin panels for the services listed will be moved to that context, no longer showing up in the project context.

en: A list of xstatic modules containing javascript and scss files to be included in the compressed set of files that are loaded on every page. Related files specified in ``ADD_XSTATIC_MODULES`` do not need to be included in ``ADD_JS_FILES``. This option expects a list of tuples, each consists of a xstatic module and a list of javascript files to be loaded if any. For more details, please check the comment of ``BASE_XSTATIC_MODULES`` in openstack_dashboard/utils/settings.py.
en_GB: A list of xstatic modules containing JavaScript and scss files to be included in the compressed set of files that are loaded on every page. Related files specified in ``ADD_XSTATIC_MODULES`` do not need to be included in ``ADD_JS_FILES``. This option expects a list of tuples, each consists of a xstatic module and a list of JavaScript files to be loaded if any. For more details, please check the comment of ``BASE_XSTATIC_MODULES`` in openstack_dashboard/utils/settings.py.

en: A string which specifies the endpoint type to use for the Keystone (identity) endpoint when looking it up in the service catalog. This overrides the ``OPENSTACK_ENDPOINT_TYPE`` parameter. If set to ``None``, ``OPENSTACK_ENDPOINT_TYPE`` is used for the identity endpoint.
en_GB: A string which specifies the endpoint type to use for the Keystone (identity) endpoint when looking it up in the service catalogue. This overrides the ``OPENSTACK_ENDPOINT_TYPE`` parameter. If set to ``None``, ``OPENSTACK_ENDPOINT_TYPE`` is used for the identity endpoint.

en: A string which specifies the endpoint type to use for the endpoints in the Keystone service catalog.
en_GB: A string which specifies the endpoint type to use for the endpoints in the Keystone service catalogue.

en: A time margin in seconds to subtract from the real token's validity. An example use case is that the token can be valid once the middleware passed, and invalid (timed-out) during a view rendering and this generates authorization errors during the view rendering. By setting this value to a few seconds, you can avoid token expiration during a view rendering.
en_GB: A time margin in seconds to subtract from the real token's validity. An example use case is that the token can be valid once the middleware passed, and invalid (timed-out) during a view rendering and this generates authorisation errors during the view rendering. By setting this value to a few seconds, you can avoid token expiration during a view rendering.

en: A value of the dict is a list of full name of an extra step classes (where a module name and a class name must be delimiteed by a period). Steps specified via ``EXTRA_STEPS`` will be displayed in the order of being registered.
en_GB: A value of the dict is a list of full name of an extra step classes (where a module name and a class name must be delimited by a full stop). Steps specified via ``EXTRA_STEPS`` will be displayed in the order of being registered.

en: A value of the dict is a list of full name of an extra tab classes (where a module name and a class name must be delimiteed by a period). Tabs specified via ``EXTRA_TABS`` will be displayed in the order of being registered.
en_GB: A value of the dict is a list of full name of an extra tab classes (where a module name and a class name must be delimited by a full stop). Tabs specified via ``EXTRA_TABS`` will be displayed in the order of being registered.

en: Additional settings may be required in the config files of your webserver of choice. For example to make ``"/dashboard/"`` the web root in Apache, the ``"sites-available/horizon.conf"`` requires a couple of additional aliases set::
en_GB: Additional settings may be required in the config files of your web-server of choice. For example to make ``"/dashboard/"`` the web root in Apache, the ``"sites-available/horizon.conf"`` requires a couple of additional aliases set::

en: Alerts use the basic Bootstrap brand colors.  See **Colors** section of your variables file for specifics.
en_GB: Alerts use the basic Bootstrap brand colours.  See **Colours** section of your variables file for specifics.

en: All Horizon's javascript files are listed in the ``openstack_dashboard/templates/horizon/_scripts.html`` partial template, which is included in Horizon's base template in ``block js``.
en_GB: All Horizon's JavaScript files are listed in the ``openstack_dashboard/templates/horizon/_scripts.html`` partial template, which is included in Horizon's base template in ``block js``.

en: Allows to specify a callback to the IdP to cleanup the SSO resources. Once the user logs out it will redirect to the IdP log out method.
en_GB: Allows to specify a callback to the IdP to clean-up the SSO resources. Once the user logs out it will redirect to the IdP log out method.

en: An administrator can specify a default user data (e.g. comments or instructions for cloudinit) via this settings. It can be a string or template string that accepts a request object.
en_GB: An administrator can specify default user data (e.g. comments or instructions for cloud-init) via these settings. It can be a string or template string that accepts a request object.

en: As of the Kilo release, styling for the OpenStack Dashboard can be altered through the use of a theme. A theme is a directory containing a ``_variables.scss`` file to override the color codes used throughout the SCSS and a ``_styles.scss`` file with additional styles to load after dashboard styles have loaded.
en_GB: As of the Kilo release, styling for the OpenStack Dashboard can be altered through the use of a theme. A theme is a directory containing a ``_variables.scss`` file to override the colour codes used throughout the SCSS and a ``_styles.scss`` file with additional styles to load after dashboard styles have loaded.

en: Bootswatch provides a number of other themes, that once Horizon is fully theme compliant, will allow easy toggling and customizations for darker or accessibility driven experiences.
en_GB: Bootswatch provides a number of other themes, that once Horizon is fully theme compliant, will allow easy toggling and customisations for darker or accessibility driven experiences.

en: Controls whether clouds.yaml is accesible from the user menu and the api access panel.
en_GB: Controls whether clouds.yaml is accessible from the user menu and the API access panel.

en: Controls whether the keystone openrc file is accesible from the user menu and the api access panel.
en_GB: Controls whether the Keystone openrc file is accessible from the user menu and the API access panel.

en: Custom Javascript
en_GB: Custom JavaScript

en: Customize Angular dashboards
en_GB: Customise Angular dashboards

en: Customize the project and user table columns
en_GB: Customise the project and user table columns

en: Customizing Horizon
en_GB: Customising Horizon

en: Customizing Meta Attributes
en_GB: Customising Meta Attributes

en: Customizing the Footer
en_GB: Customising the Footer

en: Customizing the Logo
en_GB: Customising the Logo

en: Default DNS servers you would like to use when a subnet is created. This is only a default. Users can still choose a different list of dns servers.
en_GB: Default DNS servers you would like to use when a subnet is created. This is only a default. Users can still choose a different list of DNS servers.

en: Either the reversible Django url name or an absolute url
en_GB: Either the reversible Django URL name or an absolute URL

en: Enable or disable Nova and Neutron 'get-me-a-network' feature. This 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. Horizon checks if both nova and neutron support the feature and enable it only when supported. However, whether the feature works properly depends on deployments, so this setting is disabled by default. (The detail on the required preparation is described in `the Networking Guide <https://docs.openstack.org/neutron/latest/admin/config-auto-allocation.html>`__.)
en_GB: Enable or disable Nova and Neutron 'get-me-a-network' feature. This 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. Horizon checks if both Nova and Neutron support the feature and enable it only when supported. However, whether the feature works properly depends on deployments, so this setting is disabled by default. (The detail on the required preparation is described in `the Networking Guide <https://docs.openstack.org/neutron/latest/admin/config-auto-allocation.html>`__.)

en: Extra tabs can be added to a tab group implemented in horizon or other horizon plugins by using this setting. Extra tabs will be shown after default tabs defined in a corresponding tab group.
en_GB: Extra tabs can be added to a tab group implemented in Horizon or other Horizon plugins by using this setting. Extra tabs will be shown after default tabs defined in a corresponding tab group.

en: For example, if you wish to customize the sidebar, Horizon expects the template to live at ``horizon/_sidebar.html``.  You would need to duplicate that directory structure under your templates directory, such that your override would live at ``{ theme_path }/templates/horizon/_sidebar.html``.
en_GB: For example, if you wish to customise the sidebar, Horizon expects the template to live at ``horizon/_sidebar.html``.  You would need to duplicate that directory structure under your templates directory, such that your override would live at ``{ theme_path }/templates/horizon/_sidebar.html``.

en: For use in cases of web single-sign-on authentication when the control plane has no outbound connectivity to the external service endpoints. By default the HTTP_REFERER is used to derive the Keystone endpoint to pass requests to. As previous requests to an external IdP will be using Keystone's external endpoint, this HTTP_REFERER will be Keystone's external endpoint. When Horizon is unable to connect to Keystone's external endpoint in this setup this leads to a time out. ``WEBSSO_USE_HTTP_REFERER`` can be set to False to use the ``OPENSTACK_KEYSTONE_URL`` instead, which should be set to an internal Keystone endpoint, so that this request will succeed.
en_GB: For use in cases of web single-sign-on authentication when the control plane has no outbound connectivity to the external service endpoints. By default, the HTTP_REFERER is used to derive the Keystone endpoint to pass requests to. As previous requests to an external IdP will be using Keystone's external endpoint, this HTTP_REFERER will be Keystone's external endpoint. When Horizon is unable to connect to Keystone's external endpoint in this setup this leads to a time out. ``WEBSSO_USE_HTTP_REFERER`` can be set to False to use the ``OPENSTACK_KEYSTONE_URL`` instead, which should be set to an internal Keystone endpoint, so that this request will succeed.

en: For use with the provider network extension. This is a dictionary to define extra provider network definitions. Network types supported by Neutron depend on the configured plugin. Horizon has predefined provider network types but horizon cannot cover all of them. If you are using a provider network type not defined in advance, you can add a definition through this setting.
en_GB: For use with the provider network extension. This is a dictionary to define extra provider network definitions. Network types supported by Neutron depend on the configured plugin. Horizon has predefined provider network types but Horizon cannot cover all of them. If you are using a provider network type not defined in advance, you can add a definition through this setting.

en: For use with the provider network extension. This is a dictionary where each key is a provider network type and each value is a list containing two numbers. The first number is the minimum segmentation ID that is valid. The second number is the maximum segmentation ID. Pertains only to the vlan, gre, and vxlan network types. By default this option is not provided and each minimum and maximum value will be the default for the provider network type.
en_GB: For use with the provider network extension. This is a dictionary where each key is a provider network type and each value is a list containing two numbers. The first number is the minimum segmentation ID that is valid. The second number is the maximum segmentation ID. Pertains only to the VLAN, GRE, and VXLAN network types. By default this option is not provided and each minimum and maximum value will be the default for the provider network type.

en: General Pluggbale Settings
en_GB: General Pluggable Settings

en: Horizon allows dashboards, panels and panel groups to be added without modifying the default settings. Pluggable settings are a mechanism to allow settings to be stored in separate files.  Those files are read at startup and used to modify the default settings.
en_GB: Horizon allows dashboards, panels and panel groups to be added without modifying the default settings. Pluggable settings are a mechanism to allow settings to be stored in separate files.  Those files are read at start-up and used to modify the default settings.

en: Horizon customization module (overrides)
en_GB: Horizon customisation module (overrides)

en: Horizon has a global overrides mechanism available to perform customizations that are not yet customizable via configuration settings. This file can perform monkey patching and other forms of customization which are not possible via the enabled folder's customization method.
en_GB: Horizon has a global overrides mechanism available to perform customisations that are not yet customisable via configuration settings. This file can perform monkey patching and other forms of customisation which are not possible via the enabled folder's customisation method.

en: Horizon uses icon fonts to represent checkboxes.  In order to customize this, you simply need to override the standard scss.  For an example of this, see themes/material/static/horizon/components/_checkboxes.scss
en_GB: Horizon uses icon fonts to represent checkboxes.  In order to customise this, you simply need to override the standard scss.  For an example of this, see themes/material/static/horizon/components/_checkboxes.scss

en: If horizon is behind a proxy server and the proxy is configured, the IP address from request is passed using header variables inside the request. The header name depends on a proxy or a load-balancer. This setting specifies the name of the header with remote IP address. The main use is for authentication log (success or fail) displaing the IP address of the user. The commom value for this setting is ``HTTP_X_REAL_IP`` or ``HTTP_X_FORWARDED_FOR``. If not present, then ``REMOTE_ADDR`` header is used. (``REMOTE_ADDR`` is the field of Django HttpRequest object which contains IP address of the client.)
en_GB: If Horizon is behind a proxy server and the proxy is configured, the IP address from request is passed using header variables inside the request. The header name depends on a proxy or a load-balancer. This setting specifies the name of the header with remote IP address. The main use is for authentication log (success or fail) displaying the IP address of the user. The common value for this setting is ``HTTP_X_REAL_IP`` or ``HTTP_X_FORWARDED_FOR``. If not present, then ``REMOTE_ADDR`` header is used. (``REMOTE_ADDR`` is the field of Django HttpRequest object which contains IP address of the client.)

en: If set to ``True``, this setting allows users to specify an image location (URL) as the image source when creating or updating images. Depending on the Glance version, the ability to set an image location is controlled by policies and/or the Glance configuration. Therefore IMAGES_ALLOW_LOCATION should only be set to ``True`` if Glance is configured to allow specifying a location. This setting has no effect when the Keystone catalog doesn't contain a Glance v2 endpoint.
en_GB: If set to ``True``, this setting allows users to specify an image location (URL) as the image source when creating or updating images. Depending on the Glance version, the ability to set an image location is controlled by policies and/or the Glance configuration. Therefore IMAGES_ALLOW_LOCATION should only be set to ``True`` if Glance is configured to allow specifying a location. This setting has no effect when the Keystone catalogue doesn't contain a Glance v2 endpoint.

en: If the default template is not suitable for your deployment, for example, if your deployment uses saml2, openid and so on for authentication, the default ``openrc`` would not be sufficient. You can provide your own clouds.yaml by specifying this setting.
en_GB: If the default template is not suitable for your deployment, for example, if your deployment uses SAML2, OpenID and so on for authentication, the default ``openrc`` would not be sufficient. You can provide your own clouds.yaml by specifying this setting.

en: If the theme folder contains a sub-folder ``templates``, then the path to that sub-folder will be prepended to the ``TEMPLATE_DIRS`` tuple to allow for theme specific template customizations.
en_GB: If the theme folder contains a sub-folder ``templates``, then the path to that sub-folder will be prepended to the ``TEMPLATE_DIRS`` tuple to allow for theme specific template customisations.

en: If you need to do more to customize the logo than simply replacing the existing SVG, then you can also override the _brand.html through a custom theme.  To use this technique, simply add a ``templates/header/_brand.html`` to the root of your custom theme, and add markup directly to the file.  For an example of how to do this, see ``openstack_dashboard/themes/material/templates/header/_brand.html``.
en_GB: If you need to do more to customise the logo than simply replacing the existing SVG, then you can also override the _brand.html through a custom theme.  To use this technique, simply add a ``templates/header/_brand.html`` to the root of your custom theme, and add markup directly to the file.  For an example of how to do this, see ``openstack_dashboard/themes/material/templates/header/_brand.html``.

en: If you wish to alter dashboards or panels which are not part of your codebase, you can specify a custom python module which will be loaded after the entire Horizon site has been initialized, but prior to the URLconf construction. This allows for common site-customization requirements such as:
en_GB: If you wish to alter dashboards or panels which are not part of your codebase, you can specify a custom python module which will be loaded after the entire Horizon site has been initialised, but prior to the URLconf construction. This allows for common site-customisation requirements such as:

en: If you wish to override the ``logo.svg`` using the previous method, and if the image used is larger than the height of the top navigation, then the image will be constrained to fit within the height of nav.  You can customize the height of the top navigation bar by customizing the SCSS variable: ``$navbar-height``. If the image's height is smaller than the navbar height, then the image will retain its original resolution and size, and simply be centered vertically in the available space.
en_GB: If you wish to override the ``logo.svg`` using the previous method, and if the image used is larger than the height of the top navigation, then the image will be constrained to fit within the height of nav.  You can customise the height of the top navigation bar by customizing the SCSS variable: ``$navbar-height``. If the image's height is smaller than the navbar height, then the image will retain its original resolution and size, and simply be centred vertically in the available space.

en: It is important to also note that the navbar now uses native Bootstrap dropdowns, which are customizable with variables.  Please see the **Dropdowns** section of your variables file.
en_GB: It is important to also note that the navbar now uses native Bootstrap dropdowns, which are customisable with variables.  Please see the **Dropdowns** section of your variables file.

en: It is possible to customize the global and login footers by using Django's recursive inheritance to extend the ``base.html``, ``auth/login.html``, and ``auth/_login_form.html`` templates. You do this by naming your template the same name as the template you wish to extend and only overriding the blocks you wish to change.
en_GB: It is possible to customise the global and login footers by using Django's recursive inheritance to extend the ``base.html``, ``auth/login.html``, and ``auth/_login_form.html`` templates. You do this by naming your template the same name as the template you wish to extend and only overriding the blocks you wish to change.

en: Nova has a mechanism to cache network info but it is not fast enough in some cases. For example, when a user associates a floating IP or updates an IP address of an server port, it is not reflected to the nova network info cache immediately. This means an action which a user makes from the horizon instance table is not reflected into the table content just after the action. To avoid this, horizon retrieves IP address info from neutron when retrieving a list of servers from nova.
en_GB: Nova has a mechanism to cache network info but it is not fast enough in some cases. For example, when a user associates a Floating IP or updates an IP address of an server port, it is not reflected to the Nova Network info cache immediately. This means an action which a user makes from the horizon instance table is not reflected into the table content just after the action. To avoid this, horizon retrieves IP address info from Neutron when retrieving a list of servers from Nova.

en: On the other hand, this operation requires a full list of neutron ports and can potentially lead to a performance issue in large deployments (:launchpad:`bug 1722417<horizon/+bug/1722417>`). This issue can be avoided by skipping querying IP addresses to neutron and setting this to ``False`` achieves this. Note that when disabling the query to neutron it takes some time until associated floating IPs are visible in the project instance table and users may reload the table to check them.
en_GB: On the other hand, this operation requires a full list of neutron ports and can potentially lead to a performance issue in large deployments (:launchpad:`bug 1722417<horizon/+bug/1722417>`). This issue can be avoided by skipping querying IP addresses to Neutron and setting this to ``False`` achieves this. Note that when disabling the query to Neutron it takes some time until associated floating IPs are visible in the project instance table and users may reload the table to check them.

en: Organizing Your Theme Directory
en_GB: Organising Your Theme Directory

en: Password will have an expiration date when using keystone v3 and enabling the feature. This setting allows you to set the number of days that the user will be alerted prior to the password expiration. Once the password expires keystone will deny the access and users must contact an admin to change their password. Setting this value to ``N`` days means the user will be alerted when the password expires in less than ``N+1`` days. ``-1`` disables the feature.
en_GB: Password will have an expiration date when using Keystone v3 and enabling the feature. This setting allows you to set the number of days that the user will be alerted prior to the password expiration. Once the password expires keystone will deny the access and users must contact an admin to change their password. Setting this value to ``N`` days means the user will be alerted when the password expires in less than ``N+1`` days. ``-1`` disables the feature.

en: Pie Charts are SVG elements.  SVG elements allow CSS customizations for only a basic element's look and feel (i.e. colors, size).
en_GB: Pie Charts are SVG elements.  SVG elements allow CSS customisations for only a basic element's look and feel (i.e. colours, size).

en: Please see ``_bar_charts.scss`` for specifics on what can be customized for SVGs.  See the **Progress bars** section of your variables file for specific variables to customize.
en_GB: Please see ``_bar_charts.scss`` for specifics on what can be customised for SVGs.  See the **Progress bars** section of your variables file for specific variables to customise.

en: See **Tabs** section of your variables file for variables to customize.
en_GB: See **Tabs** section of your variables file for variables to customise.

en: Similarly to adding custom styling (see above), it is possible to include custom javascript files.
en_GB: Similarly to adding custom styling (see above), it is possible to include custom JavaScript files.

en: The SVG implementation will not make use of the customized Progress Bar height though, so it is recommended that Bootstrap Progress Bars are used whenever possible.
en_GB: The SVG implementation will not make use of the customised Progress Bar height though, so it is recommended that Bootstrap Progress Bars are used whenever possible.

en: The default service region is set on a per-endpoint basis, meaning that once the user logs into some Keystone endpoint, if a default service region is defined for it in this setting and exists within Keystone catalog, it will be set as the initial service region in this endpoint. By default it is an empty dictionary because upstream can neither predict service region names in a specific deployment, nor tell whether this behavior is desired. The key of the dictionary is a full url of a Keystone endpoint with version suffix, the value is a region name.
en_GB: The default service region is set on a per-endpoint basis, meaning that once the user logs into some Keystone endpoint, if a default service region is defined for it in this setting and exists within Keystone catalogue, it will be set as the initial service region in this endpoint. By default it is an empty dictionary because upstream can neither predict service region names in a specific deployment, nor tell whether this behaviour is desired. The key of the dictionary is a full URL of a Keystone endpoint with version suffix, the value is a region name.

en: The following settings inform the OpenStack Dashboard of information about the other OpenStack projects which are part of this cloud and control the behavior of specific dashboards, panels, API calls, etc.
en_GB: The following settings inform the OpenStack Dashboard of information about the other OpenStack projects which are part of this cloud and control the behaviour of specific dashboards, panels, API calls, etc.

en: The full URL for the Keystone endpoint used for authentication. Unless you are using HTTPS, running your Keystone server on a nonstandard port, or using a nonstandard URL scheme you shouldn't need to touch this setting.
en_GB: The full URL for the Keystone endpoint used for authentication. Unless you are using HTTPS, running your Keystone server on a non-standard port, or using a non-standard URL scheme you shouldn't need to touch this setting.

en: The list of roles that have administrator privileges in this OpenStack installation. This check is very basic and essentially only works with keystone v3 with the default policy file. The setting assumes there is a common ``admin`` like role(s) across services. Example uses of this setting are:
en_GB: The list of roles that have administrator privileges in this OpenStack installation. This check is very basic and essentially only works with Keystone v3 with the default policy file. The setting assumes there is a common ``admin`` like role(s) across services. Example uses of this setting are:

en: The login splash page now uses a standard Bootstrap panel in its implementation. See the **Panels** section in your variables file to variables to easily customize.
en_GB: The login splash page now uses a standard Bootstrap panel in its implementation. See the **Panels** section in your variables file to variables to easily customise.

en: The logo also acts as a hyperlink. The default behavior is to redirect to ``horizon:user_home``. By adding the attribute ``SITE_BRANDING_LINK`` with the desired url target e.g., ``http://sample-company.com`` in ``local_settings.py``, the target of the hyperlink can be changed.
en_GB: The logo also acts as a hyperlink. The default behaviour is to redirect to ``horizon:user_home``. By adding the attribute ``SITE_BRANDING_LINK`` with the desired URL target e.g., ``http://sample-company.com`` in ``local_settings.py``, the target of the hyperlink can be changed.

en: The modal login experience, as used when switching regions, uses a standard Bootstrap dialog.  See the **Modals** section of your variables file for specific variables to customize.
en_GB: The modal login experience, as used when switching regions, uses a standard Bootstrap dialogue.  See the **Modals** section of your variables file for specific variables to customise.

en: The standard Django tables now make use of the native Bootstrap table markup. See **Tables** section of your variables file for variables to customize.
en_GB: The standard Django tables now make use of the native Bootstrap table markup. See **Tables** section of your variables file for variables to customise.

en: The static root of the theme folder must always contain a _variables.scss file and a _styles.scss file.  These must contain or import all the bootstrap and horizon specific variables and styles which are used to style the GUI. For example themes, see: /horizon/openstack_dashboard/themes/
en_GB: The static root of the theme folder must always contain a _variables.scss file and a _styles.scss file.  These must contain or import all the bootstrap and Horizon specific variables and styles which are used to style the GUI. For example themes, see: /horizon/openstack_dashboard/themes/

en: The top navbar in Horizon now uses a native Bootstrap ``navbar``.  There are a number of variables that can be used to customize this element.  Please see the **Navbar** section of your variables file for specifics on what can be set: any variables that use ``navbar-default``.
en_GB: The top navbar in Horizon now uses a native Bootstrap ``navbar``.  There are a number of variables that can be used to customise this element.  Please see the **Navbar** section of your variables file for specifics on what can be set: any variables that use ``navbar-default``.

en: The value ``allow`` enables more than one simultaneous sessions for a user. The Value ``disconnect`` disables more than one simultaneous sessions for a user. Only one active session is allowed. The newer session will be considered as the valid one and any existing session will be disconnected after a subsequent successful login.
en_GB: The value ``allow`` enables more than one simultaneous session for a user. The Value ``disconnect`` disables more than one simultaneous session for a user. Only one active session is allowed. The newer session will be considered the valid one and any existing session will be disconnected after a subsequent successful login.

en: This SESSION_TIMEOUT is a method to supercede the token timeout with a shorter horizon session timeout (in seconds). If SESSION_REFRESH is True (the default) SESSION_TIMEOUT acts like an idle timeout rather than being a hard limit, but will never exceed the token expiry. If your token expires in 60 minutes, a value of 1800 will log users out after 30 minutes of inactivity, or 60 minutes with activity. Setting SESSION_REFRESH to False will make SESSION_TIMEOUT act like a hard limit on session times.
en_GB: This SESSION_TIMEOUT is a method to supersede the token timeout with a shorter Horizon session timeout (in seconds). If SESSION_REFRESH is True (the default) SESSION_TIMEOUT acts like an idle timeout rather than being a hard limit, but will never exceed the token expiry. If your token expires in 60 minutes, a value of 1800 will log users out after 30 minutes of inactivity, or 60 minutes with activity. Setting SESSION_REFRESH to False will make SESSION_TIMEOUT act like a hard limit on session times.

en: This example sorts flavors by vcpus in descending order:
en_GB: This example sorts flavours by vCPUs in descending order:

en: This is a sample module file to demonstrate how to make some customizations to the Images Panel.::
en_GB: This is a sample module file to demonstrate how to make some customisations to the Images Panel.::

en: This method of customization is meant to be available for deployers of Horizon, and use of this should be avoided by Horizon plugins at all cost. Plugins needing this level of monkey patching and flexibility should instead look for changing their __init__.py file and performing customizations through other means.
en_GB: This method of customisation is meant to be available for deployers of Horizon, and use of this should be avoided by Horizon plugins at all cost. Plugins needing this level of monkey patching and flexibility should instead look for changing their __init__.py file and performing customisations through other means.

en: This setting allows an administrator to specify a default availability zone for a new server creation. The valid value is ``Any`` or availability zone list. If ``Any`` is specified, the default availability zone is decided by the nova scheduler. If one of availability zones is specified, the specified availability zone is used as the default availability zone. If a value specified in this setting is not found in the availability zone list, the setting will be ignored and the behavior will be same as when ``Any`` is specified.
en_GB: This setting allows an administrator to specify a default availability zone for a new server creation. The valid value is ``Any`` or availability zone list. If ``Any`` is specified, the default availability zone is decided by the nova scheduler. If one of availability zones is specified, the specified availability zone is used as the default availability zone. If a value specified in this setting is not found in the availability zone list, the setting will be ignored and the behaviour will be same as when ``Any`` is specified.

en: This setting allows you to expose configuration values over Horizons internal REST API, so that the AngularJS panels can access them. Please be cautious about which values are listed here (and thus exposed on the frontend). For security purpose, this exposure of settings should be recognized explicitly by operator. So ``REST_API_REQUIRED_SETTINGS`` is not set by default. Please refer ``local_settings.py.example`` and confirm your ``local_settings.py``.
en_GB: This setting allows you to expose configuration values over Horizons internal REST API, so that the AngularJS panels can access them. Please be cautious about which values are listed here (and thus exposed on the frontend). For security purpose, this exposure of settings should be recognised explicitly by operator. So ``REST_API_REQUIRED_SETTINGS`` is not set by default. Please refer ``local_settings.py.example`` and confirm your ``local_settings.py``.

en: This setting allows you to set rules for passwords if your organization requires them.
en_GB: This setting allows you to set rules for passwords if your organisation requires them.

en: This setting controls the behavior of the operation log.
en_GB: This setting controls the behaviour of the operation log.

en: This setting controls whether ``SimpleTenantUsage`` nova API is used in the usage overview. According to feedbacks to the horizon team, the usage of ``SimpleTenantUsage`` can cause performance issues in the nova API in larger deployments. Try to set this to ``False`` for such cases.
en_GB: This setting controls whether ``SimpleTenantUsage`` nova API is used in the usage overview. According to feedbacks to the Horizon team, the usage of ``SimpleTenantUsage`` can cause performance issues in the Nova API in larger deployments. Try to set this to ``False`` for such cases.

en: This setting disables Volumes as a valid boot source for launching instances. Volumes sources won't show up in the Launch Instance modal.
en_GB: This setting disables Volumes as a valid boot source for launching instances. Volume sources won't show up in the Launch Instance modal.

en: To add custom javascript files, create an ``_scripts.html`` partial template in your dashboard ``openstack_dashboard/dashboards/my_custom_dashboard/templates/my_custom_dashboard/_scripts.html`` which extends ``horizon/_scripts.html``. In this template override the ``block custom_js_files`` including your custom javascript files::
en_GB: To add custom JavaScript files, create an ``_scripts.html`` partial template in your dashboard ``openstack_dashboard/dashboards/my_custom_dashboard/templates/my_custom_dashboard/_scripts.html`` which extends ``horizon/_scripts.html``. In this template override the ``block custom_js_files`` including your custom javascript files::

en: To specify the python module containing your modifications, add the key ``customization_module`` to your ``HORIZON_CONFIG`` dictionary in ``local_settings.py``. The value should be a string containing the path to your module in dotted python path notation. Example::
en_GB: To specify the Python module containing your modifications, add the key ``customization_module`` to your ``HORIZON_CONFIG`` dictionary in ``local_settings.py``. The value should be a string containing the path to your module in dotted Python path notation. Example::

en: True for absolute URLs, False for django urls.
en_GB: True for absolute URLs, False for django URLs.

en: Used to customize features related to the image service, such as the list of supported image formats.
en_GB: Used to customise features related to the image service, such as the list of supported image formats.

en: Used to customize the titles for image custom property attributes that appear on image detail pages.
en_GB: Used to customise the titles for image custom property attributes that appear on image detail pages.

en: When launching a new instance the default flavor is sorted by RAM usage in ascending order. You can customize the sort order by: id, name, ram, disk and vcpus. Additionally, you can insert any custom callback function. You can also provide a flag for reverse sort. See the description in local_settings.py.example for more information.
en_GB: When launching a new instance the default flavour is sorted by RAM usage in ascending order. You can customise the sort order by: id, name, ram, disk and vCPUs. Additionally, you can insert any custom callback function. You can also provide a flag for reverse sort. See the description in local_settings.py.example for more information.

en: When set to an integer N (as by default), the start date in the Overview panel meters will be today minus N days. This setting is used to limit the amount of data fetched by default when rendering the Overview panel. If set to ``None`` (which corresponds to the behavior in past Horizon versions), the start date will be from the beginning of the current month until the current date. The legacy behaviour is not recommended for large deployments as Horizon suffers significant lag in this case.
en_GB: When set to an integer N (as by default), the start date in the Overview panel meters will be today minus N days. This setting is used to limit the amount of data fetched by default when rendering the Overview panel. If set to ``None`` (which corresponds to the behaviour in past Horizon versions), the start date will be from the beginning of the current month until the current date. The legacy behaviour is not recommended for large deployments as Horizon suffers significant lag in this case.

en: When the user logins to horizon, the message files collected are processed and displayed to the user. Each message file should contain a JSON formatted data and must have a .json file extension. For example:
en_GB: When the user logins to Horizon, the message files collected are processed and displayed to the user. Each message file should contain a JSON formatted data and must have a .json file extension. For example:

en: You can do essentially anything you like in the customization module. For example, you could change the name of a panel::
en_GB: You can do essentially anything you like in the customisation module. For example, you could change the name of a panel::

en: You could also customize what columns are displayed in an existing table, by redefining the ``columns`` attribute of its ``Meta`` class. This can be achieved in 3 steps:
en_GB: You could also customise what columns are displayed in an existing table, by redefining the ``columns`` attribute of its ``Meta`` class. This can be achieved in 3 steps:

en: `General Settings`_: this includes visual settings like the modal backdrop style, bug url and theme configuration, as well as settings that affect every service, such as page sizes on API requests.
en_GB: `General Settings`_: this includes visual settings like the modal backdrop style, bug URL and theme configuration, as well as settings that affect every service, such as page sizes on API requests.

en: ``"receiver_connection_string"`` is a url from which traces are retrieved by Horizon, needed because Horizon is not only the traces producer, but also a consumer. Having 2 settings which usually contain the same value is legacy feature from older versions of osprofiler when OpenStack components could use oslo.messaging for notifications and the trace client used ceilometer as a receiver backend. By default Horizon uses the same URL pointing to a MongoDB cluster for both purposes. Example: ``"receiver_connection_string": "mongodb://%s" % OPENSTACK_HOST``.
en_GB: ``"receiver_connection_string"`` is a URL from which traces are retrieved by Horizon. It is needed because Horizon is not only the traces producer, but also a consumer. Having two settings which usually contain the same value is legacy feature from older versions of osprofiler when OpenStack components could use oslo.messaging for notifications and the trace client used Ceilometer as a receiver backend. By default Horizon uses the same URL pointing to a MongoDB cluster for both purposes. Example: ``"receiver_connection_string": "mongodb://%s" % OPENSTACK_HOST``.

en: ``cinder_policy.d`` and ``nova_policy.d`` are registered by default to maintain policies which have ben dropped from nova and cinder but horizon still uses. We recommend not to drop them.
en_GB: ``cinder_policy.d`` and ``nova_policy.d`` are registered by default to maintain policies which have ben dropped from Nova and Cinder but Horizon still uses. We recommend not to drop them.

en: ``my_project.overrides`` needs to be importable by the python process running Horizon. If your module is not installed as a system-wide python package, you can either make it installable (e.g., with a setup.py) or you can adjust the python path used by your WSGI server to include its location.
en_GB: ``my_project.overrides`` needs to be importable by the Python process running Horizon. If your module is not installed as a system-wide python package, you can either make it installable (e.g., with a setup.py) or you can adjust the python path used by your WSGI server to include its location.

en: url
en_GB: URL
