zaqar - en to en_GB translation catalogue (24 entries)

en: Currently Zaqar can support more built-in/reserved attributes in queue. For now there are two important attributes 'max_messages_post_size' and 'max_message_ttl'. With this feature, when user query queues Zaqar will show those two attributes (read from config file if there is no customized value from user) in queue metadata so that user can know what value it is.
en_GB: Currently Zaqar can support more built-in/reserved attributes in queue. For now there are two important attributes 'max_messages_post_size' and 'max_message_ttl'. With this feature, when user query queues Zaqar will show those two attributes (read from config file if there is no customised value from user) in queue metadata so that user can know what value it is.

en: Currently the email subscription in Zaqar relay on the third part tools, such as "sendmail". It means that deployer should install it out of Zaqar. If he forgets, Zaqar will raise internal error. This work let Zaqar support email subscription by itself using the ``smtp`` python library.
en_GB: Currently the email subscriptions in Zaqar rely on the third part tools, such as "sendmail". It means that deployer should install it out of Zaqar. If he forgets, Zaqar will raise internal error. This work let Zaqar support email subscription by itself using the ``smtp`` python library.

en: In Queens, we support the old way to use pool_group and the new way without it in Flavor both. In Stein, we will remove the pool_group totally and only keep the new way in Flavor and Pool.
en_GB: In Queens, we support the old way to use pool_group and the new way without it in Flavour both. In Stein, we will remove the pool_group totally and only keep the new way in Flavour and Pool.

en: Introduce a new request header called "EXTRA-SPEC" and driver mechanism with stevedore to let developers to implement the task about how to deal with this informtaion. In Wallaby, there's just an empty handler by default.
en_GB: Introduce a new request header called "EXTRA-SPEC" and driver mechanism with stevedore to let developers implement the task about how to deal with this information. In Wallaby, there's just an empty handler by default.

en: Introduce a new resource called Topic into Zaqar. Topic is a concept from AWS Simple Notification Service (SNS), it will has relevance with subscriptions. User can send message to a topic, and then the subscribers will get the message according to different protocols, like http, email, sms, etc. This feature will help Zaqar to split Messaging Queue Service and Notification Service clearly.
en_GB: Introduce a new resource called Topic into Zaqar. Topic is a concept from AWS Simple Notification Service (SNS), it will has relevance with subscriptions. User can send message to a topic, and then the subscribers will get the message according to different protocols, like http, email, SMS, etc. This feature will help Zaqar to split Messaging Queue Service and Notification Service clearly.

en: Now before users send messages to subscribers through a queue, the subscribers should be confirmed first. Zaqar only sends messages to the confirmed subscribers. This feature supports "webhook" and "mailto" subscribers with mongoDB or redis backend. The "mailto" part will be done in O cycle. Set "require_confirmation = True" to enable this feature. The default value is "False" now and we will enable it by default after one or two cycles.
en_GB: Now before users send messages to subscribers through a queue, the subscribers should be confirmed first. Zaqar only sends messages to the confirmed subscribers. This feature supports "webhook" and "mailto" subscribers with MongoDB or Redis backend. The "mailto" part will be done in O cycle. Set "require_confirmation = True" to enable this feature. The default value is "False" now and we will enable it by default after one or two cycles.

en: Redis connection doesn't support password configure in zaqar, so redis-server can not set a password. If redis service doesn't set a password, it will suffer a large number of attacks. The patch will support password configure for redis connection in zaqar.
en_GB: Redis connection doesn't support password configuration in Zaqar, so Redis-server can not set a password. If Redis service doesn't set a password, it will suffer a large number of attacks. The patch will support password configuration for a Redis connection in Zaqar.

en: Since some clients use different format of client id not only uuid, like user id of ldap, so Zaqar will remove the format contrain of client id. Add one option 'client_id_uuid_safe' to allow user to control the validation of client id. Add two options 'min_length_client_id' and 'max_length_client_id' to allow user to control the length of client id if not using uuid. This also requires user to ensure the client id is immutable.
en_GB: Since some clients use different format of client id not only UUID, like user id of LDAP, so Zaqar will remove the format contraint of the client id. Add one option 'client_id_uuid_safe' to allow user to control the validation of client id. Add two options 'min_length_client_id' and 'max_length_client_id' to allow user to control the length of client id if not using UUID. This also requires user to ensure the client id is immutable.

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

en: Support 'post_data' and 'post_headers' options on subscribers, allowing customization of the payload when having a webhook subscriber. The 'post_data' option supports the '$zaqar_message$' string template, which will be replaced by the serialized JSON message if specified.
en_GB: Support 'post_data' and 'post_headers' options on subscribers, allowing customisation of the payload when having a webhook subscriber. The 'post_data' option supports the '$zaqar_message$' string template, which will be replaced by the serialised JSON message if specified.

en: Support Redis as management storage backend to improve the performance and ease of deployment. For the management driver, user needs to enable the redis storage options in redis.conf to persistent data.
en_GB: Support Redis as the management storage backend to improve the performance and ease of deployment. For the management driver, user needs to enable the Redis storage options in redis.conf to persist data.

en: Support for dead letter queue is added for MongoDB, Redis and Swift. With this feature, message will be moved to the specified dead letter queue if it's claimed many times but still can't successfully processed by a client. New reseved metadata keys of queue are added: _max_claim_count, _dead_letter_queue and _dead_letter_queue_messages_ttl.
en_GB: Support for dead letter queue is added for MongoDB, Redis and Swift. With this feature, message will be moved to the specified dead letter queue if it's claimed many times but still can't successfully processed by a client. New reserved metadata keys of queue are added: _max_claim_count, _dead_letter_queue and _dead_letter_queue_messages_ttl.

en: Support for delayed queues is added for MongoDB, Redis and Swift. With this feature, if the queue is a delayed queue, its message will be delayed some time to be claimed. New reseved metadata key of queue is added: _default_message_delay.
en_GB: Support for delayed queues is added for MongoDB, Redis and Swift. With this feature, if the queue is a delayed queue, its message will be delayed some time to be claimed. New reserved metadata key of queue is added: _default_message_delay.

en: Support more retry backoff function in webhook type. It will work when Zaqar failed to send the notification to the subscriber. Users can define the retry backoff function in metadata of queue. There are four retry backoff functions including  'linear', 'arithmetic', 'geometric' and 'exponential'.
en_GB: Support more retry back-off function in webhook type. It will work when Zaqar failed to send the notification to the subscriber. Users can define the retry back-off function in metadata of queue. There are four retry back-off functions including  'linear', 'arithmetic', 'geometric' and 'exponential'.

en: Support notificaiton delivery policy in webhook type. It will work when the notification is sent from Zaqar to the subscriber failed. User can define the retry policy in the options of subscription or metadata of queue.
en_GB: Support notification delivery policy in webhook type. It will work when the notification is sent from Zaqar to the subscriber failed. User can define the retry policy in the options of subscription or metadata of queue.

en: The OSprofiler is integrated to Zaqar in Ocata. It is a library from oslo. It aims to analyse the performance bottleneck issue by making possible to generate one trace per request affecting all involved services and build a tree of calls.
en_GB: The OSprofiler is integrated to Zaqar in Ocata. It is a library from Oslo. It aims to analyse the performance bottleneck issue by making possible to generate one trace per request affecting all involved services and build a tree of calls.

en: The code structure for configuration files are changed. This is insensitvie for end users, but the persons who work for downstream changes should pay attention. Please refactor your private configurations to ``zaqar/conf/`` folder as well.
en_GB: The code structure for configuration files are changed. This is transparent for end users, but the persons who work for downstream changes should pay attention. Please refactor your private configurations to ``zaqar/conf/`` folder as well.

en: The default value of ``[oslo_policy] policy_file`` config option has been changed from ``policy.json`` to ``policy.yaml``. Operators who are utilizing customized or previously generated static policy JSON files (which are not needed by default), should generate new policy files or convert them in YAML format. Use the `oslopolicy-convert-json-to-yaml <https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html>`_ tool to convert a JSON to YAML formatted policy file in backward compatible way.
en_GB: The default value of ``[oslo_policy] policy_file`` config option has been changed from ``policy.json`` to ``policy.yaml``. Operators utilising customised or previously generated static policy JSON files (which are not needed by default), should generate new policy files or convert them into YAML format. Use the `oslopolicy-convert-json-to-yaml <https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html>`_ tool to convert a JSON to YAML formatted policy file in a backward compatible way.

en: This feature is the third part of subscription confirmation feature. Support to send email to subscriber if confirmation is needed. To use this feature, user need to set the config option "external_confirmation_url", "subscription_confirmation_email_template" and "unsubscribe_confirmation_email_template". The confirmation page url that will be used in email subscription confirmation before notification, this page is not hosted in Zaqar server, user should build their own web service to provide this web page. The subscription_confirmation_email_template let user to customize the subscription confimation email content, including topic, body and sender. The unsubscribe_confirmation_email_template let user to customize the unsubscribe confimation email content, including topic, body and sender too.
en_GB: This feature is the third part of subscription confirmation feature. Support to send email to subscriber if confirmation is needed. To use this feature, user need to set the config option "external_confirmation_url", "subscription_confirmation_email_template" and "unsubscribe_confirmation_email_template". The confirmation page URL that will be used in email subscription confirmation before notification, this page is not hosted in Zaqar server, user should build their own web service to provide this web page. The subscription_confirmation_email_template let user to customize the subscription confirmation email content, including topic, body and sender. The unsubscribe_confirmation_email_template let user to customise the unsubscribe confirmation email content, including topic, body and sender too.

en: Upgrade one of storage drivers, mongo driver with new version of pymongo. Pymongo has been updated to 4.0.0, there are some changes which are not supported in new version: 1. Collection.count and Cursor.count is removed. 2. Collection.ensure_index is removed. 3. Collection.__bool__ raises NotImplementedError. 4. Should use Binary.from_uuid to handle the UUID object. Those changes need to upgrade the mongo driver's code to work well.
en_GB: Upgrade one of the storage drivers, the Mongo driver with new version of PyMongo. PyMongo has been updated to 4.0.0, there are some changes which are not supported in the new version: 1. Collection.count and Cursor.count is removed. 2. Collection.ensure_index is removed. 3. Collection.__bool__ raises NotImplementedError. 4. Should use Binary.from_uuid to handle the UUID object. Those changes need to upgrade the mongo driver's code to work well.

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 JSON policy files were 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: Welcome to the Victoria release of the OpenStack Message  service (zaqar). In this cycle, the Zaqar team would like to bring the following points to your attention.  Details may be found below.
en_GB: Welcome to the Victoria release of the OpenStack Message  service (Zaqar). In this cycle, the Zaqar team would like to bring the following points to your attention.  Details may be found below.

en: Zaqar API v2 has been released for several cycles and it is integrated as the default API version by most of the OpenStack services. So it is time to deprecated v1.1 in favor of v2. Now in Newton cycle, Zaqar API v1.1 is officially deprecated.
en_GB: Zaqar API v2 has been released for several cycles and it is integrated as the default API version by most of the OpenStack services. So it is time to deprecated v1.1 in favour of v2. Now in Newton cycle, Zaqar API v1.1 is officially deprecated.

en: Zaqar supports a new way to directly use pool resource without pool_group when creating Flavor. The old way will be kept in Queens and be marked useless. Zaqar will remove the pool_group totally in Rocky.
en_GB: Zaqar supports a new way to directly use a pool resource without pool_group when creating a Flavour. The old way will be kept in Queens and be marked deprecated. Zaqar will remove the pool_group totally in Rocky.
