octavia - en to en_GB translation catalogue (65 entries)

en: A new amphora image is required to resolve the amphora memory issues when a load balancer has multiple listeners and the amphora image uses haproxy 1.8 or newer.
en_GB: A new amphora image is required to resolve the amphora memory issues when a load balancer has multiple listeners and the amphora image uses HAProxy 1.8 or newer.

en: Add an API for allowing administrators to manage Octavia Availability Zones and Availability Zone Profiles, which behave nearly identically to Flavors and Flavor Profiles.
en_GB: Add an API for allowing administrators to manage Octavia Availability Zones and Availability Zone Profiles, which behave nearly identically to Flavours and Flavour Profiles.

en: Add l7policy and l7rule to octavia quota.
en_GB: Add l7policy and l7rule to Octavia quota.

en: Add missing cloud-utils-growpart RPM to Red Hat based amphora images.
en_GB: Add missing cloud-utils-growpart RPM to Red Hat-based amphora images.

en: Add missing cronie RPM to Red Hat based amphora images.
en_GB: Add missing cronie RPM to Red Hat-based amphora images.

en: Add support PROXY protocol for lbaas pool in octavia
en_GB: Add support PROXY protocol for LBaaS pool in Octavia

en: Add support for Ubuntu Xenial amphora images.
en_GB: Add support for Ubuntu Xenial Amphora images.

en: Added a new PROMETHEUS listener that exposes a prometheus exporter endpoint.
en_GB: Added a new PROMETHEUS listener that exposes a Prometheus exporter endpoint.

en: Added aarch64/arm64 amphora image support to the disk image create tool and to the devstack plugin.
en_GB: Added aarch64/arm64 amphora image support to the disk image creation tool and to the devstack plugin.

en: Added ability for Octavia to automatically set Barbican ACLs on behalf of the user. Such enables users to create TLS-terminated listeners without having to add the Octavia keystone user id to the ACL list. Octavia will also automatically revoke access to secrets whenever load balancing resources no longer require access to them.
en_GB: Added ability for Octavia to automatically set Barbican ACLs on behalf of the user. Such enables users to create TLS-terminated listeners without having to add the Octavia Keystone user id to the ACL list. Octavia will also automatically revoke access to secrets whenever load balancing resources no longer require access to them.

en: Added option 'sync_provisioning_status' to enable synchronizing provisioning status of loadbalancers with the neutron-lbaas database. Enabling this option will queue one additional message per amphora every heartbeat interval.
en_GB: Added option 'sync_provisioning_status' to enable synchronising provisioning status of load balancers with the neutron-lbaas database. Enabling this option will queue one additional message per amphora every heartbeat interval.

en: Added support for keystone default roles and system token scopes.
en_GB: Added support for Keystone default roles and system token scopes.

en: Adds a configuration option, "reserved_ips" that allows the operator to block addresses from being used in load balancer members. The default setting blocks the nova metadata service address.
en_GB: Adds a configuration option, "reserved_ips" that allows the operator to block addresses from being used in load balancer members. The default setting blocks the Nova metadata service address.

en: Adds support for amphora images that use systemd.
en_GB: Adds support for Amphora images that use systemd.

en: After this upgrade, users will no longer be able use network resources they cannot see or "show" on load balancers. Operators can revert this behavior by setting the "allow_invisible_reourece_usage" configuration file setting to ``True``.
en_GB: After this upgrade, users will no longer be able use network resources they cannot see or "show" on load balancers. Operators can revert this behaviour by setting the "allow_invisible_reourece_usage" configuration file setting to ``True``.

en: After this upgrade, users will no longer be able use network resources they cannot see or "show" on load balancers. Operators can revert this behavior by setting the "allow_invisible_resource_usage" configuration file setting to ``True``.
en_GB: After this upgrade, users will no longer be able use network resources they cannot see or "show" on load balancers. Operators can revert this behaviour by setting the "allow_invisible_resource_usage" configuration file setting to ``True``.

en: All pools configured under OVN provider driver are automatically migrated to SOURCE_IP_PORT algorithm. Previously algorithm was named as ROUND_ROBIN, but in fact it was not working like ROUND_ROBIN. After investigating, it was observed that core OVN actually utilizes a 5 Tuple Hash/RSS Hash in DPDK/Kernel as a Load Balancing algorithm. The 5 Tuple Hash has Source IP, Destination IP, Protocol, Source Port, Destination Port. To reflect this the name was changed to SOURCE_IP_PORT.
en_GB: All pools configured under OVN provider driver are automatically migrated to SOURCE_IP_PORT algorithm. Previously algorithm was named as ROUND_ROBIN, but in fact it was not working like ROUND_ROBIN. After investigating, it was observed that core OVN actually utilises a 5 Tuple Hash/RSS Hash in DPDK/Kernel as a Load Balancing algorithm. The 5 Tuple Hash has Source IP, Destination IP, Protocol, Source Port, Destination Port. To reflect this the name was changed to SOURCE_IP_PORT.

en: Allow the loadbalancer's VIP to be created on the same network as the management interface.
en_GB: Allow the load balancer's VIP to be created on the same network as the management interface.

en: Amphora API now can return the field `compute_flavor` which is the ID of the compute instance flavor used to boot the amphora.
en_GB: Amphora API now can return the field `compute_flavor` which is the ID of the compute instance flavour used to boot the amphora.

en: Amphora failover is supported when active/standby is enabled.  Should the master or backup amphora fail, the health manager will rebuild it.
en_GB: Amphora failover is supported when active/standby is enabled.  Should the master or backup Amphora fail, the health manager will rebuild it.

en: Amphora image support for RH Linux flavors.
en_GB: Amphora image support for RH Linux flavours.

en: Amphora will need to be updated to a new image with this version of the agent and ping-wrapper.sh script prior to updating the Octavia controllers. If a load balancer is using a health monitor of type PING with an amphora image that has not been updated, the next configuration change to the load balancer will cause it to go into an ERROR state until it is failed over to an updated image.
en_GB: Amphora will need to be updated to a new image with this version of the agent and ping-wrapper.sh script prior to updating the Octavia controllers. If a load balancer is using a health monitor of type PING with an Amphora image that has not been updated, the next configuration change to the load balancer will cause it to go into an ERROR state until it is failed over to an updated image.

en: Amphora with a terminated HTTPS load balancer can no longer be rebooted.  If they reboot, they will trigger a failover of the amphora.
en_GB: Amphora with a terminated HTTPS load balancer can no longer be rebooted.  If they reboot, they will trigger a failover of the Amphora.

en: An operator documentation page has been added to list known Octavia provider drivers and provide links to those drivers. Non-reference drivers, drivers other than the "amphora" driver, will be outside of the octavia code repository but are dynamically loadable via a well defined interface described in the provider driver developers guide.
en_GB: An operator documentation page has been added to list known Octavia provider drivers and provide links to those drivers. Non-reference drivers, drivers other than the "amphora" driver, will be outside of the Octavia code repository but are dynamically loadable via a well defined interface described in the provider driver developers guide.

en: As a followup to the fix that resolved CVE-2018-16856, Octavia will now encrypt certificates and keys used for secure communication with amphorae, in its internal workflows. Octavia used to exclude debug-level log prints for specific tasks and flows that were explicitly specified by name, a method that is susceptive to code changes.
en_GB: As a followup to the fix that resolved CVE-2018-16856, Octavia will now encrypt certificates and keys used for secure communication with amphorae, in its internal workflows. Octavia used to exclude debug-level log prints for specific tasks and flows that were explicitly specified by name, a method that is susceptible to code changes.

en: Certificate and key storage for terminated HTTPS load balancers is now in an encrypted ramfs path inside the amphora.
en_GB: Certificate and key storage for terminated HTTPS load balancers is now in an encrypted ramfs path inside the Amphora.

en: Disabling connection logging might make it more difficult to audit systems for unauthorized access, from which IPs it originated, and which assets were compromised.
en_GB: Disabling connection logging might make it more difficult to audit systems for unauthorised access, from which IPs it originated, and which assets were compromised.

en: Fixed an issue that caused failover to unsuccessful if the vip network was not DHCP enabled.
en_GB: Fixed an issue that caused failover to unsuccessful if the VIP network was not DHCP enabled.

en: Fixed an issue where the amphora would fail to bring up the VIP if the VIP network did not have a gateway specified in neutron.
en_GB: Fixed an issue where the amphora would fail to bring up the VIP if the VIP network did not have a gateway specified in Neutron.

en: Fixes a bug where unspecified or unlimited listener connection limit settings would lead to a 2000 connection limit when using the amphora/octavia driver. This was the compiled in connection limit in some HAproxy packages.
en_GB: Fixes a bug where unspecified or unlimited listener connection limit settings would lead to a 2000 connection limit when using the Amphora/Octavia driver. This was the compiled in connection limit in some HAproxy packages.

en: Fixes admin-state-up=False action for loadbalancer and listener.
en_GB: Fixes admin-state-up=False action for load balancer and listener.

en: Fixes an issue where if more than one amphora fails at the same time, failover might not fully complete, leaving the load balancer in ERROR.
en_GB: Fixes an issue where if more than one Amphora fails at the same time, failover might not fully complete, leaving the load balancer in ERROR.

en: Improvements to the keepalived system used in active/standby topologies. keepalived is now monitored for health by the amphora agent (previously just by the init system) and a systemd race condition between keepalived and haproxy have been resolved.
en_GB: Improvements to the keepalived system used in active/standby topologies. keepalived is now monitored for health by the amphora agent (previously just by the init system) and a systemd race condition between keepalived and HAProxy have been resolved.

en: In some enviornments (e.g. OSA) Neutron and Octavia use different queues (at least different vhosts) and so if Octavia posts to the Octavia queue and Neutron listens on the Neutron queue the events will never make it over.
en_GB: In some environments (e.g. OSA) Neutron and Octavia use different queues (at least different vhosts) and so if Octavia posts to the Octavia queue and Neutron listens on the Neutron queue the events will never make it over.

en: It is now possible to completely remove sshd from the amphora image, to further lock down access and increase security. If this is set, providing an `amp_ssh_key_name` in config will install the key, but ssh access will not be possible as sshd will not be running.
en_GB: It is now possible to completely remove SSHd from the Amphora image, to further lock down access and increase security. If this is set, providing an `amp_ssh_key_name` in config will install the key, but ssh access will not be possible as SSHd will not be running.

en: Members that are disabled via `admin_state_up=False` are now rendered in the HAProxy configuration on the amphora as `disabled`. Previously they were not rendered at all. This means that disabled members will now appear in health messages, and will properly change status to OFFLINE.
en_GB: Members that are disabled via `admin_state_up=False` are now rendered in the HAProxy configuration on the Amphora as `disabled`. Previously they were not rendered at all. This means that disabled members will now appear in health messages, and will properly change status to OFFLINE.

en: Neutron LBaaS was assigning the VIP port it created the user's project-id, thus allowing the user to attach Floating-IPs to the VIP port. Octavia, on the other hand, was assigning the Octavia project-id to the port, making it impossible for the user to attach a Floating IP. This patch brings Octavia's behavior in line with Neutron LBaaS and assigns the user's project-id to the VIP port created by Octavia.
en_GB: Neutron LBaaS was assigning the VIP port it created the user's project-id, thus allowing the user to attach Floating-IPs to the VIP port. Octavia, on the other hand, was assigning the Octavia project-id to the port, making it impossible for the user to attach a Floating IP. This patch brings Octavia's behaviour in line with Neutron LBaaS and assigns the user's project-id to the VIP port created by Octavia.

en: New option in diskimage-create.sh `-n` to completely disable sshd on the amphora.
en_GB: New option in diskimage-create.sh `-n` to completely disable SSHd on the Amphora image.

en: Note that while the Octavia v2 API now supports Role Bassed Access Control (RBAC), the Octavia v1.0 API does not.  The Octavia v1.0 API should not be exposed publicly and should only be used internally such as for the neutron-lbaas octavia driver.  Publicly accessible instances of the Octavia API should have the v1.0 API disabled via the Octavia configuration file.
en_GB: Note that while the Octavia v2 API now supports Role Based Access Control (RBAC), the Octavia v1.0 API does not.  The Octavia v1.0 API should not be exposed publicly and should only be used internally such as for the neutron-lbaas Octavia driver.  Publicly accessible instances of the Octavia API should have the v1.0 API disabled via the Octavia configuration file.

en: Octavia API now supports WSGI deplyment.
en_GB: Octavia API now supports WSGI deployment.

en: Octavia now has options to limit the amphora concurrent build rate. This may be useful for deployments where nova can get overloaded. Amphora builds will be prioritized in the following order: failover, normal, spares pool builds. See the configuration guide for more information: https://docs.openstack.org/octavia/latest/configuration/configref.html#haproxy_amphora.build_rate_limit
en_GB: Octavia now has options to limit the Amphora concurrent build rate. This may be useful for deployments where Nova can get overloaded. Amphora builds will be prioritised in the following order: failover, normal, spares pool builds. See the configuration guide for more information: https://docs.openstack.org/octavia/latest/configuration/configref.html#haproxy_amphora.build_rate_limit

en: Provider of "octavia" has been deprecated in favor of "amphora" to clarify the provider driver supporting the load balancer.
en_GB: Provider of "octavia" has been deprecated in favour of "amphora" to clarify the provider driver supporting the load balancer.

en: Resolved an issue that could cause provisioning status to become out of sync between neutron-lbaas and octavia during high load.
en_GB: Resolved an issue that could cause provisioning status to become out of sync between neutron-lbaas and Octavia during high load.

en: Some versions of HAProxy incorrectly reported nodes in DRAIN status as being UP, and Octavia code was written around this incorrect reporting. This has been fixed in some versions of HAProxy and is now handled properly in Octavia as well. Now it is possible for members to be in the status DRAINING. Note that this is masked when statuses are forwarded to neutron-lbaas in the eventstream, so no compatibility change is necessary.
en_GB: Some versions of HAProxy incorrectly reported nodes in DRAIN status as being UP, and Octavia code was written around this incorrect reporting. This has been fixed in some versions of HAProxy and is now handled properly in Octavia as well. Now it is possible for members to be in the status DRAINING. Note that this is masked when statuses are forwarded to neutron-lbaas in the event stream, so no compatibility change is necessary.

en: Start using reno to manage release notes.
en_GB: Start using Reno to manage release notes.

en: The "use_upstart" configuration option is now deprecated because the amphora agent can now automatically discover the init system in use in the amphora image.
en_GB: The "use_upstart" configuration option is now deprecated because the amphora agent can now automatically discover the init system in use in the Amphora image.

en: The Octavia project documentation has been reorganized as part of the OpenStack documentation migration project. The Octavia project documentation is now located at: https://docs.openstack.org/octavia/latest/
en_GB: The Octavia project documentation has been reorganised as part of the OpenStack documentation migration project. The Octavia project documentation is now located at: https://docs.openstack.org/octavia/latest/

en: The Octavia v2 API now supports Role Based Access Control (RBAC). The default rules require users to have a load-balancer_* role to be able to access the Octavia v2 API.  This can be overriden with the admin_or_owner-policy.json sample file provided. See the `Octavia Policies <https://docs.openstack.org/octavia/latest/configuration/policy.html>`_ document for more information.
en_GB: The Octavia v2 API now supports Role Based Access Control (RBAC). The default rules require users to have a load-balancer_* role to be able to access the Octavia v2 API.  This can be overridden with the admin_or_owner-policy.json sample file provided. See the `Octavia Policies <https://docs.openstack.org/octavia/latest/configuration/policy.html>`_ document for more information.

en: The amphora haproxy user_group setting is now automatically detected for Ubuntu, CentOS, Fedora, or RHEL based amphora.
en_GB: The Amphora HAProxy user_group setting is now automatically detected for Ubuntu, CentOS, Fedora, or RHEL based Amphora.

en: The amphora-agent is now able to distinguish between operating systems and choose the right course of action to manage files and networking on each Linux flavor.
en_GB: The Amphora-agent is now able to distinguish between operating systems and choose the right course of action to manage files and networking on each Linux flavour.

en: The compute zone (if applicable) is now cached in the database and returned in the Amphora API as `cached_zone`. Please note that this is only set at the original time of provisioning, and could be stale for various reasons (for example, if live-migrations have taken place due to maintenances). We recommend it be used for reference only, unless you are absolutey certain it is current in your environment. The source of truth is still the system you use for compute.
en_GB: The compute zone (if applicable) is now cached in the database and returned in the Amphora API as `cached_zone`. Please note that this is only set at the original time of provisioning, and could be stale for various reasons (for example, if live-migrations have taken place due to maintenances). We recommend it be used for reference only, unless you are absolutely certain it is current in your environment. The source of truth is still the system you use for compute.

en: The configuration setting auth_strategy is now set to keystone by default.
en_GB: The configuration setting auth_strategy is now set to Keystone by default.

en: The diskimage-create script supports different operating system flavors such as Ubuntu (the default option), CentOS, Fedora and RHEL. Adaptations were made to several elements to ensure all images are operational.
en_GB: The diskimage-create script supports different operating system flavours such as Ubuntu (the default option), CentOS, Fedora and RHEL. Adaptations were made to several elements to ensure all images are operational.

en: The option ``[controller_worker]/amp_image_id`` has been deprecated since Mitaka release and is now removed. This option was superseded by ``[controller_worker]/amp_image_tag`` option.
en_GB: The option ``[controller_worker]/amp_image_id`` has been deprecated since the Mitaka release and is now removed. This option was superseded by ``[controller_worker]/amp_image_tag`` option.

en: To fix the admin-state-up bug you must upgrade your amphora image.
en_GB: To fix the admin-state-up bug you must upgrade your Amphora image.

en: To support IPv6 a databse migration and amphora image update are required.
en_GB: To support IPv6 a database migration and Amphora image update are required.

en: To support multi-VIP loadbalancers, a new amphora image must be built. It is safe to upload the new image before the upgrade, as it is fully backwards compatible.
en_GB: To support multi-VIP load balancers, a new amphora image must be built. It is safe to upload the new image before the upgrade, as it is fully backwards compatible.

en: To support networks without DHCP you must upgrade your amphora image.
en_GB: To support networks without DHCP you must upgrade your Amphora image.

en: Update Python base version from 3.6 to 3.8. As per Openstack Python runtime versions policy Python 3.8 will be the the minimum Python version in the Zed release cycle.
en_GB: Update Python base version from 3.6 to 3.8. As per the OpenStack Python runtime versions policy Python 3.8 will be the minimum Python version in the Zed release cycle.

en: Updates load balancer, listener, and amphora tables.
en_GB: Updates load balancer, listener, and Amphora tables.

en: Use of JSON policy files was deprecated by the ``oslo.policy`` library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby cycle with an anticipated future removal of support by ``oslo.policy``. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on migration of any custom policy files.
en_GB: The use of JSON policy files was deprecated by the ``oslo.policy`` library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby cycle with an anticipated future removal of support by ``oslo.policy``. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on the migration of any custom policy files.

en: Validate that the creation of L7 policies is compatible with the protocol of the listener in the Amphora driver. L7 policies are allowed for Terminated HTTPS or HTTP protocol listeners, but not for HTTPS, TCP or UDP protocols listeners.
en_GB: Validate that the creation of L7 policies is compatible with the protocol of the listener in the Amphora driver. L7 policies are allowed for Terminated HTTPS or HTTP protocol listeners, but not for HTTPS, TCP or UDP protocol listeners.

en: When enabled in the configuration file, Octavia will boot an active and standby amphora for each load balancer.
en_GB: When enabled in the configuration file, Octavia will boot an active and standby Amphora for each load balancer.

en: amp_image_id option is deprecated and will be removed in one of the next releases. Operators are adviced to migrate to the new amp_image_tag option.
en_GB: amp_image_id option is deprecated and will be removed in one of the next releases. Operators are advised to migrate to the new amp_image_tag option.

en: haproxy user_group is no longer being used. it is now auto-detected for Ubuntu, CentOS, Fedora and RHEL based amphora images.
en_GB: HAProxy user_group is no longer being used. it is now auto-detected for Ubuntu, CentOS, Fedora and RHEL based Amphora images.
