This is an automated email from the ASF dual-hosted git repository. mitchell852 pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/incubator-trafficcontrol.git
The following commit(s) were added to refs/heads/master by this push: new 37133ca Remove old references to mso algorithm 37133ca is described below commit 37133ca2a21a8476958a8f52ddd609fac5aefbb7 Author: Derek Gelinas <mrdgeli...@gmail.com> AuthorDate: Fri Feb 9 10:49:28 2018 -0500 Remove old references to mso algorithm --- .../D22DCAA3-18CC-48F4-965B-5312993F9820.png | Bin 99921 -> 0 bytes docs/source/admin/quick_howto/mso-enable.png | Bin 107805 -> 124819 bytes docs/source/admin/quick_howto/mso-rank.png | Bin 140070 -> 0 bytes docs/source/admin/quick_howto/multi_site.rst | 50 ++++++--------------- 4 files changed, 13 insertions(+), 37 deletions(-) diff --git a/docs/source/admin/quick_howto/D22DCAA3-18CC-48F4-965B-5312993F9820.png b/docs/source/admin/quick_howto/D22DCAA3-18CC-48F4-965B-5312993F9820.png deleted file mode 100644 index 59d5b8e..0000000 Binary files a/docs/source/admin/quick_howto/D22DCAA3-18CC-48F4-965B-5312993F9820.png and /dev/null differ diff --git a/docs/source/admin/quick_howto/mso-enable.png b/docs/source/admin/quick_howto/mso-enable.png index 9932de1..70207ba 100644 Binary files a/docs/source/admin/quick_howto/mso-enable.png and b/docs/source/admin/quick_howto/mso-enable.png differ diff --git a/docs/source/admin/quick_howto/mso-rank.png b/docs/source/admin/quick_howto/mso-rank.png deleted file mode 100644 index de80ac5..0000000 Binary files a/docs/source/admin/quick_howto/mso-rank.png and /dev/null differ diff --git a/docs/source/admin/quick_howto/multi_site.rst b/docs/source/admin/quick_howto/multi_site.rst index bd4807d..270efc2 100644 --- a/docs/source/admin/quick_howto/multi_site.rst +++ b/docs/source/admin/quick_howto/multi_site.rst @@ -57,45 +57,12 @@ Configure Multi Site Origin 4) This OFQDN must be valid - ATS will perform a DNS lookup on this FQDN even if IPs, not DNS, are used in the parent.config. 5) The OFQDN entered as the "Origin Server Base URL" will be sent to the origins as a host header. All origins must be configured to respond to this host. -6) Select an option from the "Multi Site Origin Algorithm" drop-down list. Four MSO algorithms are supported: - -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| Option | Description | -+==================+====================================================================================================================+ -| Consistent hash | Origin server selection is based on the consistent hash of requested URLs. | -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| Primary/back | Round robin selection does not occur. The first origin server is selected unless it fails. | -| | If the first fails, the second and other following origin servers will be tried by order. | -| | Order is defined by 2 factors - if the origin server's cachegroup is configured as the | -| | parent cachegroup for the mid, then this server will be used as the primary. The same rules | -| | apply for secondary parents, in order. Within the cachegroups, the rank parameter will sort | -| | order further. If no parents are defined at the mid, then only rank is considered. | -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| Strict | MID caches serve requests strictly in turn. For example: origin server 1 serves the first request, | -| round-robin | origin server 2 serves the second request, and so on. | -+------------------+--------------------------------------------------------------------------------------------------------------------+ -| IP based | MID cache goes through the origin server list in a round robin-based on the IP address of EDGE cache. | -| round-robin | | -+------------------+--------------------------------------------------------------------------------------------------------------------+ - -7) Optionally, there are two configuration options that can set the order of the origins used if "Primary/backup" is selected for "Multi Site Origin Algorithm". By creating location-based cachegroups and assigning the origin servers accordingly and defining these cachegroups as parents for specific mids, location-based primary/secondary selection can be made. If primary/secondary selection should be the same for all mids, then a new parameter “rank” should be configured for each origin [...] - -.. image:: mso-rank.png - :scale: 60% - :align: center - -8) Assign the parent.config location parameter to the MID profile: - -.. image:: D22DCAA3-18CC-48F4-965B-5312993F9820.png - :scale: 100% - :align: center - -9) For ATS 5.x, configure the mid hdr_rewrite on the delivery service, example: :: +6) For ATS 5.x, configure the mid hdr_rewrite on the delivery service, example: :: cond %{REMAP_PSEUDO_HOOK} __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_enabled 1 __RETURN__ set-config proxy.config.http.parent_origin.simple_retry_response_codes "400,404,412" __RETURN__ set-config proxy.config.http.parent_origin.dead_server_retry_response_codes "502,503" __RETURN__ set-config proxy.config.http.connect_attempts_timeout 2 __RETURN__ set-config proxy.config.http.connec [...] -10) As of ATS 6.x, multi-site options must be set as parameters within the parent.config. Header rewrite parameters will be ignored. See `ATS parent.config <https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/files/parent.config.en.html>` for more details. These parameters are now handled by the creation of a delivery service profile. +7) Create a delivery service profile. This must be done to set the MSO algorithm. Also, as of ATS 6.x, multi-site options must be set as parameters within the parent.config. Header rewrite parameters will be ignored. See `ATS parent.config <https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/files/parent.config.en.html>` for more details. These parameters are now handled by the creation of a delivery service profile. a) Create a profile of the type DS_PROFILE for the delivery service in question. @@ -114,8 +81,17 @@ b) Click "Show profile parameters" to bring up the parameters screen for the pro | mso.parent_retry | parent.config | simple_retry, both, | parent_retry | | | | unavailable_server_retry | | +----------------------------------------+------------------+--------------------------+-------------------------+ -| mso.unavailable_server_retry_responses | parent.config | list of server response | | -| | | codes, eg "500,502,503" | | +| mso.unavailable_server_retry_responses | parent.config | list of server response | defaults to the value | +| | | codes, eg "500,502,503" | in records.config | +| | | | when unused. | ++----------------------------------------+------------------+--------------------------+-------------------------+ +| mso.max_simple_retries | parent.config | Nubmer of retries made | defaults to the value | +| | | after a 4xx error | in records.config | +| | | | when unused. | ++----------------------------------------+------------------+--------------------------+-------------------------+ +| mso.max_unavailable_server_retries | parent.config | Nubmer of retries made | defaults to the value | +| | | after a 5xx error | in records.config | +| | | | when unused. | +----------------------------------------+------------------+--------------------------+-------------------------+ -- To stop receiving notification emails like this one, please contact mitchell...@apache.org.