Designate Release Notes - en to en_GB translation catalogue (37 entries)

en: A new recordset api ``/v2/recordsets`` is exposed with GET method allowed only. The api can be used for retrieving recordsets across all the zones under a tenant. Filtering on certain fields is supported as well.
en_GB: A new recordset API ``/v2/recordsets`` is exposed with GET method allowed only. The API can be used for retrieving recordsets across all the zones under a tenant. Filtering on certain fields is supported as well.

en: Added new state ``INACTIVE`` to the Floating IP status to indicate that it is not currently associated to a DNS record.
en_GB: Added new state ``INACTIVE`` to the Floating IP status to indicate that it is not currently associated with a DNS record.

en: Added zone_name in zone trasfer request response. Closed bug#1580014
en_GB: Added zone_name in zone transfer request response. Closed bug#1580014

en: All designate services will now report to designate-central when they are running. This is implmented as a heartbeat reporting system. There is also a new API endpoint in the v2 API - $API_BASE/v2/service_status. This will show the list of services running, and when they last reported as running. Currently the "stats" and "capabilities" values will be blank, but will be updated in the future as services implement them.
en_GB: All designate services will now report to designate-central when they are running. This is implemented as a heartbeat reporting system. There is also a new API endpoint in the v2 API - $API_BASE/v2/service_status. This will show the list of services running, and when they last reported as running. Currently the "stats" and "capabilities" values will be blank, but will be updated in the future as services implement them.

en: CAA records now allow the use of `+` prefixed subadresses like `security+caa@example.net` within mail urls. (https://www.rfc-editor.org/rfc/rfc5233.html#section-1)
en_GB: CAA records now allow the use of `+` prefixed subadresses like `security+caa@example.net` within mail URLs. (https://www.rfc-editor.org/rfc/rfc5233.html#section-1)

en: CERT recordset type have been added. All users should be able to use this type from the API and openstack client. This can be disabled (like other record types) by setting the `[DEFAULT].supported-record-type` config variable in all designate services.
en_GB: CERT recordset types have been added. All users should be able to use this type from the API and OpenStack client. This can be disabled (like other record types) by setting the `[DEFAULT].supported-record-type` config variable in all Designate services.

en: Check for multi level tlds
en_GB: Check for multi level TLDs

en: Create / Update / Delete API methods on /v2/pools/ Using these messages **will** cause unforseen issues with pools. We highly recommend that the policy file be updated to restrict create / update / delete from all users
en_GB: Create / Update / Delete API methods on /v2/pools/ Using these messages **will** cause unforeseen issues with pools. We highly recommend that the policy file be updated to restrict create / update / delete from all users

en: Currently designate does not provide zone specific option to delete the zone resources (such as files) on the back-end (e.g. bind9) when the zone is deleted. To fix this add a header ``x-designate-hard-delete`` which will be used in the zone delete API to delete zone files on the back-end. This is in addition to the existing per-pool configration option that will override this new header option. This option is restricted for admin.
en_GB: Currently, Designate does not provide zone-specific option to delete the zone resources (such as files) on the back-end (e.g. bind9) when the zone is deleted. To fix this add a header ``x-designate-hard-delete`` which will be used in the zone delete API to delete zone files on the back-end. This is in addition to the existing per-pool configuration option that will override this new header option. This option is restricted for admin.

en: 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 your environment.
en_GB: Default `policy.json` file is now removed as Designate now generates the default policies from code. Please be aware of that when using that file in your environment.

en: Designate has increased the minimum version of dnspython to 2.2.1 for the antelope (2023.1) release to reflect support for python 3.10.
en_GB: Designate has increased the minimum version of dnspython to 2.2.1 for the Antelope (2023.1) release to reflect support for Python 3.10.

en: Designate now support policy in code, which means if users don't want to modify any of policy rules, they can remove or comment all of rules in policy file or even not deploy it at all. Because from now, Designate keeps all default policies under `designate/common/policies` module. Users can modify/generate `policy.yaml` file which will override policy rules in code if those rules show in `policy.yaml` file. Users also still use `policy.json` file but oslo team recommend that we should use the newer YAML format instead.
en_GB: Designate now support policy in code, which means if users don't want to modify any of policy rules, they can remove or comment all of rules in policy file or even not deploy it at all. Because from now, Designate keeps all default policies under `designate/common/policies` module. Users can modify/generate `policy.yaml` file which will override policy rules in code if those rules show in `policy.yaml` file. Users also still use `policy.json` file but Oslo team recommend that we should use the newer YAML format instead.

en: Designate will now use the openstacksdk to access neutron instead of the deprecated neutronclient. The python-neutronclient module requirement has been replaced by the openstacksdk module.
en_GB: Designate will now use the openstacksdk to access Neutron instead of the deprecated neutronclient. The python-neutronclient module requirement has been replaced by the openstacksdk module.

en: Fixed an issue with the API reference using the wrong path for list service statuses. In addition a compatibility workaround was added for the incorrect /v2/service_status path.
en_GB: Fixed an issue with the API reference using the wrong path for listing service statuses. In addition, a compatibility workaround was added for the incorrect /v2/service_status path.

en: Fixes `bug 1934252`_ which ignored invalid denylist patterns. The fix entailed checking the pattern string via regular expression compiler and testing for zero length.
en_GB: Fixes `bug 1934252`_ which ignored invalid denylist patterns. The fix entailed checking the pattern string via a regular expression compiler and testing for zero length.

en: Fixes bug where requests to powerDNS fail if the dns is configured for TLS traffic.
en_GB: Fixes bug where requests to powerDNS fail if the DNS is configured for TLS traffic.

en: Fixes support for keystone default roles and scoped tokens.
en_GB: Fixes support for Keystone default roles and scoped tokens.

en: It does so by adding a configuration variable, `api_ca_cert`, users can use to declare the location of the CA cert needed to verify TLS traffic.
en_GB: It does so by adding a configuration variable, `api_ca_cert`, which users can use to declare the location of the CA cert needed to verify TLS traffic.

en: Previous versions of eventlet changed the behaviour of socket.send() to match socket.sendall(). in eventlet 0.18.0 this changed and it reverted to the traditional behaviour. MiniDNS has been updated to allow minidns to push large zone transfers over long range network connections
en_GB: Previous versions of eventlet changed the behaviour of socket.send() to match socket.sendall(). in eventlet 0.18.0 this changed and it reverted to the traditional behaviour. MiniDNS has been updated to allow MiniDNS to push large zone transfers over long range network connections

en: Python 2.7 support has been dropped. Last release of Designate to support python 2.7 is OpenStack Train. The minimum version of Python now supported by Designate is Python 3.6.
en_GB: Python 2.7 support has been dropped. Last release of Designate to support Python 2.7 is OpenStack Train. The minimum version of Python now supported by Designate is Python 3.6.

en: Removed previously deprecated ``[service:mdns]`` option ``notify``. All DNS notifications now happens using the worker service.
en_GB: Removed previously deprecated ``[service:mdns]`` option ``notify``. All DNS notifications now happen using the worker service.

en: Removed the ``monascastatsd`` based metrics solution as all calls using it has been changed or removed and designate is no longer tracking any metrics using the metrics endpoint.
en_GB: Removed the ``monascastatsd`` based metrics solution as all calls using it has been changed or removed and Designate is no longer tracking any metrics using the metrics endpoint.

en: Removed the following unused central rpc calls. This should not impact normal installations, but if these are used in any custom written backends or plugins that you are using, you will need to update your code before upgrading.
en_GB: Removed the following unused central RPC calls. This should not impact normal installations, but if these are used in any custom written backends or plugins that you are using, you will need to update your code before upgrading.

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

en: The Akamai eDNS backend has reached it's end of life and has been removed. Please upgrade to the Akamai v2 backend.
en_GB: The Akamai eDNS backend has reached its end of life and has been removed. Please upgrade to the Akamai v2 backend.

en: The ``SECONDARY zone`` RPC calls were moved from the ``mdns`` service to ``worker`` service. When upgrading multi-controller deployments we recommend that you restart the ``central`` and ``worker`` services first to move the ``SECONDARY zone`` calls to the ``worker``, and once both services has been upgraded go ahead and restart the ``mdns`` service.
en_GB: The ``SECONDARY zone`` RPC calls were moved from the ``mdns`` service to ``worker`` service. When upgrading multi-controller deployments we recommend that you restart the ``central`` and ``worker`` services first to move the ``SECONDARY zone`` calls to the ``worker``, and once both services have been upgraded go ahead and restart the ``mdns`` service.

en: The ``[service:api] max_header_line`` parameter has been deprecated. This parameter has hd no effect since the Train release. Use the ``[DEFAULT] max_header_line`` parameter of the ``oslo.service`` library instead.
en_GB: The ``[service:api] max_header_line`` parameter has been deprecated. This parameter has had no effect since the Train release. Use the ``[DEFAULT] max_header_line`` parameter of the ``oslo.service`` library instead.

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 who are utilising customised 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: The fix for minidns's issues TCP can cause minidns to fail to send some messages. This manifests itself with eventlet not being able to send all the data before socket is closed.
en_GB: The fix for MiniDNS's issues TCP can cause MiniDNS to fail to send some messages. This manifests itself with eventlet not being able to send all the data before socket is closed.

en: The following parameters have been deprecated. These parameters have had no effect since SSLMiddleware was removed during Ussuri cycle.
en_GB: The following parameters have been deprecated. These parameters have had no effect since SSLMiddleware was removed during the Ussuri cycle.

en: The netaddr python module has been removed as a Designate requirement. It has been replaced with the python standard library 'ipaddress' module.
en_GB: The netaddr python module has been removed as a Designate requirement. It has been replaced with the Python standard library 'ipaddress' module.

en: This adds the quotas api from /admin to /v2 with some changes. All users can GET /v2/quotas/<project_id> Users with "All-Projects" permission can view other projects (by setting X-Auth-All-Projects:True in the HTTP Headers) Users with "All-Projects" and "set-quotas" can set other projects quotas Moved the API rendering to Designate Object based rendering
en_GB: This adds the quotas API from /admin to /v2 with some changes. All users can GET /v2/quotas/<project_id> Users with "All-Projects" permission can view other projects (by setting X-Auth-All-Projects:True in the HTTP Headers) Users with "All-Projects" and "set-quotas" can set other projects quotas Moved the API rendering to Designate Object based rendering

en: designate-mdns, designate-agent and designate-api can now bind to multiple host:port pairs via the new "listen" configuration arguments for eacg service.
en_GB: designate-mdns, designate-agent and designate-api can now bind to multiple host:port pairs via the new "listen" configuration arguments for each service.

en: designate-pool-manager : It is recommended to use a supported tooz backend.
en_GB: designate-pool-manager : It is recommended to use a supported Tooz backend.

en: designate-zone-manager : If a tooz backend is not used, all zone-managers will assume ownership of all zones, and there will be 'n' 'exists' messages per hour, where 'n' is the number of zone-manager processes.
en_GB: designate-zone-manager : If a Tooz backend is not used, all zone-managers will assume ownership of all zones, and there will be 'n' 'exists' messages per hour, where 'n' is the number of zone-manager processes.

en: designate-zone-manager : It is recommended to use a supported tooz backend.
en_GB: designate-zone-manager : It is recommended to use a supported Tooz backend.

en: designate-zone-manager : ZooKeeper is recommended, or anything supported by tooz.
en_GB: designate-zone-manager : ZooKeeper is recommended, or anything supported by Tooz.
