From 7b5a69073222df26c4d88fd96e2e1df6a6a63114 Mon Sep 17 00:00:00 2001 From: Chris McFarlen Date: Thu, 15 Aug 2024 18:19:20 -0500 Subject: [PATCH 1/5] Documentation: Update release notes --- doc/release-notes/upgrading.en.rst | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/doc/release-notes/upgrading.en.rst b/doc/release-notes/upgrading.en.rst index da13e9e1d4e..05dee41b6a9 100644 --- a/doc/release-notes/upgrading.en.rst +++ b/doc/release-notes/upgrading.en.rst @@ -34,6 +34,8 @@ version of ATS. Deprecated features should be avoided, with the expectation that removed in the next major release of ATS. * Removed Features + * HostDB no longer supports persistent storage for DNS resolution + * Removed support for the MMH crypto hash function * Traffic Manager is no longer part of |TS|. Administrative tools now interact with |TS| directly by using the :ref:`jsonrpc-node`. @@ -146,10 +148,21 @@ The following :file:`records.yaml` changes have been made: files, but they did not have any effect. These have been removed from default configs files. - The default values for ``proxy.config.http.request_header_max_size``, ``proxy.config.http.response_header_max_size``, and ``proxy.config.http.header_field_max_size`` have been changed to 32KB. +- The records.yaml entry ``proxy.config.http.server_ports`` now also accepts the + ``allow-plain`` option +- The records.yaml entry ``proxy.config.http.down_server.abort_threshold`` has + been removed +- The records.yaml entry ``proxy.config.http.cache.max_open_write_retry_timeout`` has been added to specify a timeout for starting a write to cache +- The records.yaml entry ``proxy.config.net.per_client.max_connections_in`` has + been added to limit the number of connections from a client IP +- The records.yaml entry ``proxy.config.http.no_dns_just_forward_to_parent`` is + not overridable The following changes have been made to the :file:`sni.yaml` file: - ``disable_h2`` has been removed. Use ``http2`` with :code:`off` instead. +- The ``ip_allow`` key can now take a reference to a file containing the ip + allow rules Plugins ------- @@ -178,7 +191,15 @@ TS_LUA_CONFIG_HTTP_CONNECT_DEAD_POLICY has been renamed to TS_LUA_CONFIG_HTTP_CO Metrics ------- -The HTTP connection metric proxy.process.http.dead_server.no_requests has been renamed to proxy.process.http.down_server.no_requests. +- The HTTP connection metric proxy.process.http.dead_server.no_requests has been renamed to proxy.process.http.down_server.no_requests. +- The network metric ``proxy.process.net.calls_to_readfromnet_afterpoll`` has been +removed +- The network metric ``proxy.process.net.calls_to_writetonet_afterpoll`` has been +removed +- New cache metrics ``proxy.process.cache.stripes`` and + ``proxy.process.cache.volume_X.stripes`` that counts cache stripes +- All metric names that ended in ``_stat`` have had that suffix dropped and no + longer end with ``_stat`` Logging ------- From 6e7cb02e92171f8e9aaf58ce1c9b177d672aaa07 Mon Sep 17 00:00:00 2001 From: Chris McFarlen Date: Thu, 15 Aug 2024 18:37:34 -0500 Subject: [PATCH 2/5] Add links to record entries --- doc/release-notes/upgrading.en.rst | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/doc/release-notes/upgrading.en.rst b/doc/release-notes/upgrading.en.rst index 05dee41b6a9..5c47c7632f1 100644 --- a/doc/release-notes/upgrading.en.rst +++ b/doc/release-notes/upgrading.en.rst @@ -135,11 +135,11 @@ The ``records.config`` file has been renamed to :file:`records.yaml` and now it The following :file:`records.yaml` changes have been made: - The records.yaml entry ``proxy.config.http.down_server.abort_threshold`` has been removed. -- The records.yaml entry ``proxy.config.http.connect_attempts_max_retries_dead_server`` has been renamed to ``proxy.config.http.connect_attempts_max_retries_down_server``. -- The entry ``proxy.config.http.connect.dead.policy`` has been renamed to ``proxy.config.http.connect.down.policy``. +- The records.yaml entry ``proxy.config.http.connect_attempts_max_retries_dead_server`` has been renamed to :ts:cv:``proxy.config.http.connect_attempts_max_retries_down_server``. +- The entry ``proxy.config.http.connect.dead.policy`` has been renamed to :ts:cv:``proxy.config.http.connect.down.policy``. - The records.yaml entry ``proxy.config.http.parent_proxy.connect_attempts_timeout`` and ``proxy.config.http.post_connect_attempts_timeout`` have been removed. Instead use - ``proxy.config.http.connect_attempts_timeout`` to control all connection to origin timeouts. + :ts:cv:``proxy.config.http.connect_attempts_timeout`` to control all connection to origin timeouts. - The per server origin connection feature had a few configurations that were not used removed. ``proxy.config.http.per_server.connection.queue_size`` and ``proxy.config.http.per_server.connection.queue_delay`` have been removed. @@ -149,13 +149,17 @@ The following :file:`records.yaml` changes have been made: - The default values for ``proxy.config.http.request_header_max_size``, ``proxy.config.http.response_header_max_size``, and ``proxy.config.http.header_field_max_size`` have been changed to 32KB. - The records.yaml entry ``proxy.config.http.server_ports`` now also accepts the +- The default values for :ts:cv:``proxy.config.http.request_header_max_size``, :ts:cv:``proxy.config.http.response_header_max_size``, and + :ts:cv:``proxy.config.http.header_field_max_size`` have been changed to 32KB. +- The records.yaml entry :ts:cv:``proxy.config.http.server_ports`` now also accepts the ``allow-plain`` option - The records.yaml entry ``proxy.config.http.down_server.abort_threshold`` has been removed -- The records.yaml entry ``proxy.config.http.cache.max_open_write_retry_timeout`` has been added to specify a timeout for starting a write to cache -- The records.yaml entry ``proxy.config.net.per_client.max_connections_in`` has - been added to limit the number of connections from a client IP -- The records.yaml entry ``proxy.config.http.no_dns_just_forward_to_parent`` is +- The records.yaml entry :ts:cv:``proxy.config.http.cache.max_open_write_retry_timeout`` has been added to specify a timeout for starting a write to cache +- The records.yaml entry :ts:cv:``proxy.config.net.per_client.max_connections_in`` has + been added to limit the number of connections from a client IP. This works the + same as :ts:cv:``proxy.config.http.per_server.connection.max`` +- The records.yaml entry :ts:cv:``proxy.config.http.no_dns_just_forward_to_parent`` is not overridable The following changes have been made to the :file:`sni.yaml` file: From ca495e29a9df9d8c9932c5276bd85972e223f10f Mon Sep 17 00:00:00 2001 From: Chris McFarlen Date: Thu, 15 Aug 2024 18:43:56 -0500 Subject: [PATCH 3/5] fix indent --- doc/release-notes/upgrading.en.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/doc/release-notes/upgrading.en.rst b/doc/release-notes/upgrading.en.rst index 5c47c7632f1..fa65634f736 100644 --- a/doc/release-notes/upgrading.en.rst +++ b/doc/release-notes/upgrading.en.rst @@ -196,10 +196,8 @@ Metrics ------- - The HTTP connection metric proxy.process.http.dead_server.no_requests has been renamed to proxy.process.http.down_server.no_requests. -- The network metric ``proxy.process.net.calls_to_readfromnet_afterpoll`` has been -removed -- The network metric ``proxy.process.net.calls_to_writetonet_afterpoll`` has been -removed +- The network metric ``proxy.process.net.calls_to_readfromnet_afterpoll`` has been removed +- The network metric ``proxy.process.net.calls_to_writetonet_afterpoll`` has been removed - New cache metrics ``proxy.process.cache.stripes`` and ``proxy.process.cache.volume_X.stripes`` that counts cache stripes - All metric names that ended in ``_stat`` have had that suffix dropped and no From f2b3176b36215ece7fac540213e976de47e9cdcc Mon Sep 17 00:00:00 2001 From: Chris McFarlen Date: Fri, 16 Aug 2024 09:35:17 -0500 Subject: [PATCH 4/5] cleanup --- doc/release-notes/upgrading.en.rst | 5 ----- 1 file changed, 5 deletions(-) diff --git a/doc/release-notes/upgrading.en.rst b/doc/release-notes/upgrading.en.rst index fa65634f736..084e13586cd 100644 --- a/doc/release-notes/upgrading.en.rst +++ b/doc/release-notes/upgrading.en.rst @@ -146,15 +146,10 @@ The following :file:`records.yaml` changes have been made: - The records.yaml entries ``proxy.config.http.parent_proxy.connect_attempts_timeout`` and ``proxy.config.http.post_connect_attempts_timeout`` were previously referenced in default config files, but they did not have any effect. These have been removed from default configs files. -- The default values for ``proxy.config.http.request_header_max_size``, ``proxy.config.http.response_header_max_size``, and - ``proxy.config.http.header_field_max_size`` have been changed to 32KB. -- The records.yaml entry ``proxy.config.http.server_ports`` now also accepts the - The default values for :ts:cv:``proxy.config.http.request_header_max_size``, :ts:cv:``proxy.config.http.response_header_max_size``, and :ts:cv:``proxy.config.http.header_field_max_size`` have been changed to 32KB. - The records.yaml entry :ts:cv:``proxy.config.http.server_ports`` now also accepts the ``allow-plain`` option -- The records.yaml entry ``proxy.config.http.down_server.abort_threshold`` has - been removed - The records.yaml entry :ts:cv:``proxy.config.http.cache.max_open_write_retry_timeout`` has been added to specify a timeout for starting a write to cache - The records.yaml entry :ts:cv:``proxy.config.net.per_client.max_connections_in`` has been added to limit the number of connections from a client IP. This works the From 6c7233071b5b746014ef6432368db898bf904539 Mon Sep 17 00:00:00 2001 From: Chris McFarlen Date: Fri, 16 Aug 2024 10:24:24 -0500 Subject: [PATCH 5/5] fix ref quotes --- doc/release-notes/upgrading.en.rst | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/doc/release-notes/upgrading.en.rst b/doc/release-notes/upgrading.en.rst index 084e13586cd..07437c2eb60 100644 --- a/doc/release-notes/upgrading.en.rst +++ b/doc/release-notes/upgrading.en.rst @@ -135,26 +135,26 @@ The ``records.config`` file has been renamed to :file:`records.yaml` and now it The following :file:`records.yaml` changes have been made: - The records.yaml entry ``proxy.config.http.down_server.abort_threshold`` has been removed. -- The records.yaml entry ``proxy.config.http.connect_attempts_max_retries_dead_server`` has been renamed to :ts:cv:``proxy.config.http.connect_attempts_max_retries_down_server``. -- The entry ``proxy.config.http.connect.dead.policy`` has been renamed to :ts:cv:``proxy.config.http.connect.down.policy``. +- The records.yaml entry ``proxy.config.http.connect_attempts_max_retries_dead_server`` has been renamed to :ts:cv:`proxy.config.http.connect_attempts_max_retries_down_server`. +- The entry ``proxy.config.http.connect.dead.policy`` has been renamed to :ts:cv:`proxy.config.http.connect.down.policy`. - The records.yaml entry ``proxy.config.http.parent_proxy.connect_attempts_timeout`` and ``proxy.config.http.post_connect_attempts_timeout`` have been removed. Instead use - :ts:cv:``proxy.config.http.connect_attempts_timeout`` to control all connection to origin timeouts. + :ts:cv:`proxy.config.http.connect_attempts_timeout` to control all connection to origin timeouts. - The per server origin connection feature had a few configurations that were not used removed. ``proxy.config.http.per_server.connection.queue_size`` and ``proxy.config.http.per_server.connection.queue_delay`` have been removed. - The records.yaml entries ``proxy.config.http.parent_proxy.connect_attempts_timeout`` and ``proxy.config.http.post_connect_attempts_timeout`` were previously referenced in default config files, but they did not have any effect. These have been removed from default configs files. -- The default values for :ts:cv:``proxy.config.http.request_header_max_size``, :ts:cv:``proxy.config.http.response_header_max_size``, and - :ts:cv:``proxy.config.http.header_field_max_size`` have been changed to 32KB. -- The records.yaml entry :ts:cv:``proxy.config.http.server_ports`` now also accepts the +- The default values for :ts:cv:`proxy.config.http.request_header_max_size`, :ts:cv:`proxy.config.http.response_header_max_size`, and + :ts:cv:`proxy.config.http.header_field_max_size` have been changed to 32KB. +- The records.yaml entry :ts:cv:`proxy.config.http.server_ports` now also accepts the ``allow-plain`` option -- The records.yaml entry :ts:cv:``proxy.config.http.cache.max_open_write_retry_timeout`` has been added to specify a timeout for starting a write to cache -- The records.yaml entry :ts:cv:``proxy.config.net.per_client.max_connections_in`` has +- The records.yaml entry :ts:cv:`proxy.config.http.cache.max_open_write_retry_timeout` has been added to specify a timeout for starting a write to cache +- The records.yaml entry :ts:cv:`proxy.config.net.per_client.max_connections_in` has been added to limit the number of connections from a client IP. This works the - same as :ts:cv:``proxy.config.http.per_server.connection.max`` -- The records.yaml entry :ts:cv:``proxy.config.http.no_dns_just_forward_to_parent`` is + same as :ts:cv:`proxy.config.http.per_server.connection.max` +- The records.yaml entry :ts:cv:`proxy.config.http.no_dns_just_forward_to_parent` is not overridable The following changes have been made to the :file:`sni.yaml` file: