oslo.messaging - en to en_GB translation catalogue (17 entries)

en: Add a new option `enable_cancel_on_failover` for rabbitmq driver which when enabled, will cancel consumers when queue appears to be down.
en_GB: Add a new option `enable_cancel_on_failover` for RabbitMQ driver which when enabled, will cancel consumers when the queue appears to be down.

en: As a fix for `bug 1917645 <https://launchpad.net/bugs/1917645>`_ the rabbit backend is changed to use the ``[oslo_messaging_notifications]retry`` parameter when driver tries to connect to the message bus during notification sending. Before this fix the rabbit backend retried the connection forever blocking the caller thread.
en_GB: As a fix for `bug 1917645 <https://launchpad.net/bugs/1917645>`_ the rabbit backend is changed to use the ``[oslo_messaging_notifications]retry`` parameter when the driver tries to connect to the message bus during notification sending. Before this fix the rabbit backend retried the connection forever blocking the caller thread.

en: Default ttl is 1200s. Next configuration params was added
en_GB: Default TTL is 1200s. Next configuration params was added

en: Force creating non durable control exchange when a precondition failed related to config that differ occuring.
en_GB: Force creating non-durable control exchange when a precondition failed related to config that differs occurring.

en: Increased ACK_REQUEUE_EVERY_SECONDS_MAX to resolve issues with rabbitmq HA failover.
en_GB: Increased ACK_REQUEUE_EVERY_SECONDS_MAX to resolve issues with RabbitMQ HA failover.

en: Instantiating the RPCClient class directly is deprecated in favor of using the new ``get_rpc_client`` function to expose a more common API similar to existing functions such as ``get_rpc_server`` and ``get_rpc_transport``
en_GB: Instantiating the RPCClient class directly is deprecated in favour of using the new ``get_rpc_client`` function to expose a more common API similar to existing functions such as ``get_rpc_server`` and ``get_rpc_transport``

en: Introduce support for sending rpc client metrics to oslo.metrics.
en_GB: Introduce support for sending RPC client metrics to oslo.metrics.

en: NoSuchMethod exception will not be logged for special non-existing methods which names end with '_ignore_errors'. Such methods might be used as health probes for openstack services.
en_GB: NoSuchMethod exception will not be logged for special non-existing methods which names end with '_ignore_errors'. Such methods might be used as health probes for OpenStack services.

en: On rabbitmq, in the past, acknownlegement of messages was done within the application callback thread/greenlet. This thread was blocked until the message was ack. In newton, we rewrote the message acknownlegement to ensure we haven't two threads writting the the socket at the same times. Now all pendings ack are done by the main thread. They are no more reason to block the application callback thread until the message is ack. Other driver already release the application callback threads before the message is acknownleged. This is also the case for rabbitmq, now.
en_GB: On RabbitMQ, in the past, acknowledgement of messages was done within the application callback thread/greenlet. This thread was blocked until the message was acknowledged. In Newton, we rewrote the message acknowledgement to ensure we haven't two threads writing to the socket at the same time. Now all pending acknowledgements are done by the main thread. They are no more reason to block the application callback thread until the message is acknowledged. Other drivers already release the application callback threads before the message is acknowledged. This is also the case for RabbitMQ now.

en: SSL support for oslo_messaging's kafka driver
en_GB: SSL support for oslo_messaging's Kafka driver

en: The AMQP1 driver is now deprecated. Its related functional tests are also disabled. Neither debian nor ubuntu in the latest releases have any binary built for qpid server, not even 3rd party. Only qpid proton, the client lib, is available.
en_GB: The AMQP1 driver is now deprecated. Its related functional tests are also disabled. Neither Debian nor Ubuntu in the latest releases have any binary built for qpid server, not even 3rd party. Only qpid proton, the client lib, is available.

en: The Kafa driver has removed the configuration options of kafka_default_host and kafka_default_port from the [oslo_messaging_kafka] section.
en_GB: The Kafka driver has removed the configuration options of kafka_default_host and kafka_default_port from the [oslo_messaging_kafka] section.

en: The driver support for the ZeroMQ messaging library is removed. Users of the oslo.messaging RPC services must use the supported rabbit ("rabbit://...") or amqp1 ("amqp://..." )drivers.
en_GB: The driver support for the ZeroMQ messaging library is removed. Users of the oslo.messaging RPC services must use the supported Rabbit ("rabbit://...") or amqp1 ("amqp://..." )drivers.

en: The pika driver has been deprecated for removal in Rocky.  This driver was developed as a replacement for the default rabbit driver. However testing has not shown any appreciable improvement over the default rabbit driver in terms of performance and stability.
en_GB: The Pika driver has been deprecated for removal in Rocky.  This driver was developed as a replacement for the default rabbit driver. However testing has not shown any appreciable improvement over the default rabbit driver in terms of performance and stability.

en: The purpose of this new endpoint is to help operators do a RPC call (a ping) toward a specific RPC callback (e.g. a nova-compute, or a neutron-agent). This is helping a lot for monitoring agents (for example, if agents are deployed in a kubernetes pod).
en_GB: The purpose of this new endpoint is to help operators do a RPC call (a ping) toward a specific RPC callback (e.g. a nova-compute, or a neutron agent). This is helping a lot with monitoring agents (for example, if agents are deployed in a Kubernetes pod).

en: The rabbitmq driver option ``DEFAULT/max_retries`` has been deprecated for removal (at a later point in the future) as it did not make logical sense for notifications and for RPC.
en_GB: The RabbitMQ driver option ``DEFAULT/max_retries`` has been deprecated for removal (at a later point in the future) as it did not make logical sense for notifications and for RPC.

en: We undeprecated the ``heartbeat_in_pthread`` option. This option will remain available to allow customers to run the rabbitmq heartbeat in python thread or not.
en_GB: We un-deprecated the ``heartbeat_in_pthread`` option. This option will remain available to allow customers to run the RabbitMQ heartbeat in Python thread or not.
