[trafficserver] 07/12: Update the admin-guide hierachical caching and remap.config documentation to include the NextHop strategies feature.

[zw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zwoop pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git

commit f58f65432574deb1b1a56f7c11c404d956ecbd7f
Author: John Rushford <jr...@apache.org>
AuthorDate: Thu Dec 19 21:19:52 2019 +0000

    Update the admin-guide hierachical caching and remap.config
    documentation to include the NextHop strategies feature.
    
    (cherry picked from commit 429ec3b04da7aaf3d7ee9bf552a63ac7813d7b2f)
---
 doc/admin-guide/configuration/hierarchical-caching.en.rst | 11 ++++++++++-
 doc/admin-guide/files/remap.config.en.rst                 |  7 +++++++
 2 files changed, 17 insertions(+), 1 deletion(-)

diff --git a/doc/admin-guide/configuration/hierarchical-caching.en.rst b/doc/admin-guide/configuration/hierarchical-caching.en.rst
index 81faf2f..03fc674 100644
--- a/doc/admin-guide/configuration/hierarchical-caching.en.rst
+++ b/doc/admin-guide/configuration/hierarchical-caching.en.rst
@@ -106,6 +106,11 @@ host name. This is true regardless of pristine host headers
 (:ts:cv:`proxy.config.url_remap.pristine_host_hdr`) being enabled or not. The parent node
 will receive the translated request (and thus needs to be configured to accept it).
 
+:file:`remap.config` now also allows an alternative configuration that supports all the
+**Parent Selection** policies and failover mentioned here using a new :file:`remap.config` tag,
+**@strategy**. This eliminates the need for a second lookup against the remapped host name
+required when using :file:`parent.config`.  See using NextHop strategies with :file:`remap.config`,
+:doc:`../../admin-guide/files/strategies.yaml.en`
 
 Example
 ~~~~~~~
@@ -165,7 +170,11 @@ the configuration adjustments detailed below.
    cache.
 
 #. Edit :file:`parent.config` to set parent proxy rules which will specify the
-   parent cache to which you want missed requests to be forwarded.
+   parent cache to which you want missed requests to be forwarded.  Or as an
+   alternative to :file:`parent.config`, edit :file:`strategies.yaml` to
+   specify next hop parent proxy rules and hosts.  Then in :file:`remap.config`
+   use the **@strategy** tag to select the next hop parent proxy rules. See
+   :doc:`../../admin-guide/files/strategies.yaml.en`
 
 The following example configures Traffic Server to route all requests
 containing the regular expression ``politics`` and the path
diff --git a/doc/admin-guide/files/remap.config.en.rst b/doc/admin-guide/files/remap.config.en.rst
index a4b2f83..5abcdf7 100644
--- a/doc/admin-guide/files/remap.config.en.rst
+++ b/doc/admin-guide/files/remap.config.en.rst
@@ -480,6 +480,13 @@ mapping rules. (It is activated before any mappings and is never
 deactivated.) The filter `local_only` will only be applied to the
 second mapping.
 
+NextHop Selection Strategies
+============================
+
+You may configure Nexthop or Parent hierarchical caching rules by remap using the
+**@strategy** tag.  See :doc:`../configuration/hierarchical-caching.en` and :doc:`strategies.yaml.en`
+for configuration details and examples.
+
 Including Additional Remap Files
 ================================