openstack/designate
Code Issues Proposed changes

Imported Translations from Zanata

Browse Source 
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: I8017b41b72a5b789e1e0a3b8a0dd744007f8d9a2
This commit is contained in:
OpenStack Proposal Bot 2024-07-10 02:16:25 +00:00
parent d6cb801282
commit 1ac55388dc
1 changed files with 126 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

130
releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po
View File

@ -10,11 +10,11 @@ msgid ""
msgstr ""
"Project-Id-Version: Designate Release Notes\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-06-30 17:42+0000\n"
"POT-Creation-Date: 2024-07-04 01:32+0000\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"PO-Revision-Date: 2024-07-01 11:17+0000\n"
"PO-Revision-Date: 2024-07-10 12:08+0000\n"
"Last-Translator: Andi Chandler <andi@gowling.com>\n"
"Language-Team: English (United Kingdom)\n"
"Language: en_GB\n"
@ -93,8 +93,8 @@ msgstr "17.0.0"
msgid "18.0.0"
msgstr "18.0.0"
msgid "18.0.0-18"
msgstr "18.0.0-18"
msgid "18.0.0-20"
msgstr "18.0.0-20"
msgid "2.0.0"
msgstr "2.0.0"
@ -221,6 +221,23 @@ msgstr ""
"Added new state ``INACTIVE`` to the Floating IP status to indicate that it "
"is not currently associated with a DNS record."
msgid ""
"Added zone pool move command which allows admin user to move zone from pool "
"A to specified pool B. This command overcome the issues observed in zone "
"export-import thereby reducing hours of time of large zone imports (e.g. "
"20-30k records). Please note, if you have moved a zone to a different pool, "
"the pool must be configured with a proper tsig key for mini-DNS query "
"operations. Without this, you cannot have overlapping zones in different "
"pools."
msgstr ""
"Added zone pool move command which allows admin user to move zone from pool "
"A to specified pool B. This command overcome the issues observed in zone "
"export-import thereby reducing hours of time of large zone imports (e.g. "
"20-30k records). Please note, if you have moved a zone to a different pool, "
"the pool must be configured with a proper tsig key for mini-DNS query "
"operations. Without this, you cannot have overlapping zones in different "
"pools."
msgid "Added zone_name in zone trasfer request response. Closed bug#1580014"
msgstr "Added zone_name in zone transfer request response. Closed bug#1580014"
@ -395,6 +412,15 @@ msgstr ""
"updated, as we no longer support the creation of unmanaged records using the "
"sink."
msgid ""
"Database tables are now explicitly created with charset=utf8. This resolves "
"an issue running ``designate-manage database sync`` when the designate "
"database was not created with the default charset set to utf8."
msgstr ""
"Database tables are now explicitly created with charset=utf8. This resolves "
"an issue running ``designate-manage database sync`` when the Designate "
"database was not created with the default charset set to utf8."
msgid ""
"Default `policy.json` file is now removed as Designate now generate the "
"default policies from code. Please be aware that when using that file in "
@ -410,6 +436,23 @@ msgstr "Deprecation Notes"
msgid "Designate Release Notes"
msgstr "Designate Release Notes"
msgid ""
"Designate can now optionally provide catalog zones for pools. Defined in "
"`RFC 9432 <https://datatracker.ietf.org/doc/rfc9432/>`_, catalog zones allow "
"for provisioning of DNS zones on secondary nameservers through the sole "
"means of DNS. A special zone, the catalog zone, serves as a list of all "
"zones the secondary nameservers should serve and for which they will set "
"themselves up automatically. The synchronization of zones via a catalog zone "
"happens via known and proven AXFR, just like for a zone's DNS records."
msgstr ""
"Designate can now optionally provide catalogue zones for pools. Defined in "
"`RFC 9432 <https://datatracker.ietf.org/doc/rfc9432/>`_, catalogue zones "
"allow for provisioning of DNS zones on secondary nameservers through the "
"sole means of DNS. A special zone, the catalogue zone, serves as a list of "
"all zones the secondary nameservers should serve and for which they will set "
"themselves up automatically. The synchronization of zones via a catalogue "
"zone happens via known and proven AXFR, just like for a zone's DNS records."
msgid ""
"Designate can verify validity of the project id when setting quotas for it. "
"This feature is enabled by setting a new configuration option ``[service:"
@ -649,6 +692,15 @@ msgstr ""
"Import of release notes from https://wiki.openstack.org/wiki/ReleaseNotes/"
"Liberty#OpenStack_DNS_.28Designate.29"
msgid ""
"In addition, the ``infoblox-client`` library is now a dependency for the "
"Infoblox driver and should be installed additionally if the Infoblox Backend "
"is used."
msgstr ""
"In addition, the ``infoblox-client`` library is now a dependency for the "
"Infoblox driver and should be installed additionally if the Infoblox Backend "
"is used."
msgid ""
"In addition, the server will return a 400 BadRequest response to an invalid "
"pattern."
@ -823,6 +875,19 @@ msgstr ""
"used either as a regex or as a zone name, for example: patterns = ['', "
"``'#(*&^%$%$#@$']``"
msgid ""
"Provisioning via catalog zones is already supported by popular DNS "
"implementations, such as BIND9, Knot and PowerDNS (and likely others). Apart "
"from being a standardized provisioning model, the main advantage of catalog "
"zones is the scalability and robustness of keeping secondary nameservers in "
"sync."
msgstr ""
"Provisioning via catalogue zones is already supported by popular DNS "
"implementations, such as BIND9, Knot and PowerDNS (and likely others). Apart "
"from being a standardized provisioning model, the main advantage of "
"catalogue zones is the scalability and robustness of keeping secondary "
"nameservers in sync."
msgid "Purging deleted domains"
msgstr "Purging deleted domains"
@ -861,6 +926,16 @@ msgstr ""
"Removed previously deprecated ``[service:mdns]`` option ``notify``. All DNS "
"notifications now happen using the worker service."
msgid ""
"Removed previously deprecated ``service:mdns`` configuration options. These "
"are now configured under ``service:worker`` instead."
msgstr ""
"Removed previously deprecated ``service:mdns`` configuration options. These "
"are now configured under ``service:worker`` instead."
msgid "Removed previously deprecated ``storage_driver`` configuration option."
msgstr "Removed previously deprecated ``storage_driver`` configuration option."
msgid ""
"Removed the ``monascastatsd`` based metrics solution as all calls using it "
"has been changed or removed and designate is no longer tracking any metrics "
@ -912,6 +987,15 @@ msgstr "See `bug 1958533`_ for more information."
msgid "See `designate/notification_handler/base.py` for more details."
msgstr "See `designate/notification_handler/base.py` for more details."
msgid ""
"So far, the yaml Adapter made every designate-manage pool command fail if "
"the pools.yaml file was missing any of the pool attributes. This patch makes "
"the adapter to continue without raising any error."
msgstr ""
"So far, the yaml Adapter made every designate-manage pool command fail if "
"the pools.yaml file was missing any of the pool attributes. This patch makes "
"the adapter to continue without raising any error."
msgid "Start using reno to manage release notes."
msgstr "Start using Reno to manage release notes."
@ -999,6 +1083,13 @@ msgstr ""
"The ``[service:api]`` option ``enable_host_header`` is now enabled by "
"default."
msgid ""
"The ``edgegrid-python`` library is now an optional dependency and should be "
"installed additionally if the Akamai v2 Backend is used."
msgstr ""
"The ``edgegrid-python`` library is now an optional dependency and should be "
"installed additionally if the Akamai v2 Backend is used."
msgid ""
"The ``v1`` API is now off by default. To re-enable the V1 API please set "
"``enable_api_v1 = True`` in the ``[service:api]`` section of your designate "
@ -1032,6 +1123,11 @@ msgstr ""
"The above config which you need to put or uncomment them into/in designate "
"config file."
msgid ""
"The agent and all agent backends has been removed and can no longer be used."
msgstr ""
"The agent and all agent backends has been removed and can no longer be used."
msgid ""
"The backend agent framework and agent based drivers are deprecated for "
"removal in the \"C\" release. The following backend agent drivers are now "
@ -1087,6 +1183,32 @@ msgstr ""
"oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html>`_ tool to "
"convert a JSON to YAML formatted policy file in backward compatible way."
msgid ""
"The deprecated Infoblox configuration options in ``desginate.conf`` has now "
"been removed. All Infoblox configuration should now be in the ``pools.yaml`` "
"configuration file."
msgstr ""
"The deprecated Infoblox configuration options in ``desginate.conf`` has now "
"been removed. All Infoblox configuration should now be in the ``pools.yaml`` "
"configuration file."
msgid ""
"The example \"api-paste.ini\" file for Designate has been updated to enable "
"the oslo middleware sizelimit filter by default. If you update your \"api-"
"paste.ini\" to the version with sizelimit in it, you will need to adjust the "
"[oslo_middleware] max_request_body_size setting in the Designate "
"configuration file to be large enough to accommodate the expected maximum "
"zone import size in your deployment. The oslo middleware "
"max_request_body_size default is 114688 bytes."
msgstr ""
"The example \"api-paste.ini\" file for Designate has been updated to enable "
"the oslo middleware sizelimit filter by default. If you update your \"api-"
"paste.ini\" to the version with sizelimit in it, you will need to adjust the "
"[oslo_middleware] max_request_body_size setting in the Designate "
"configuration file to be large enough to accommodate the expected maximum "
"zone import size in your deployment. The oslo middleware "
"max_request_body_size default is 114688 bytes."
msgid ""
"The existing Infoblox driver has been updated and is now based on the "
"official Infoblox client."