You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by mi...@apache.org on 2018/09/26 13:51:59 UTC
[trafficcontrol] 42/46: Formatting changes
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/trafficcontrol.git
commit 083202e8a2e31c46fff69c0caaaad711cb919a17
Author: ocket8888 <oc...@gmail.com>
AuthorDate: Mon Sep 17 10:06:05 2018 -0600
Formatting changes
---
docs/source/admin/quick_howto/multi_site.rst | 124 +++++++++++++--------------
1 file changed, 60 insertions(+), 64 deletions(-)
diff --git a/docs/source/admin/quick_howto/multi_site.rst b/docs/source/admin/quick_howto/multi_site.rst
index 3989d2d..54d0bc9 100644
--- a/docs/source/admin/quick_howto/multi_site.rst
+++ b/docs/source/admin/quick_howto/multi_site.rst
@@ -16,90 +16,86 @@
.. _multi-site-origin-qht:
***************************
-Configure Multi Site Origin
+Configure Multi-Site Origin
***************************
+The following steps will take you through the procedure of setting up a Multi-Site Origin (MSO).
-1) Create cachegroups for the origin locations, and assign the appropriate parent-child relationship between the mid and org cachegroups (click the image to see full size). Each mid cachegroup can be assigned a primary and secondary origin parent cachegroup. When the mid cache parent configuration is generated, origins in the primary cachegroups will be listed first, followed by origins in the secondary cachegroup. Origin servers assigned to the delivery service that are assigned to ne [...]
+#. Create Cache Groups for the origin locations, and assign the appropriate parent-child relationship between the mid and origin Cache Groups. Each mid Cache Group can be assigned a primary and secondary origin parent Cache Group. When the mid cache parent configuration is generated, origins in the primary Cache Groups will be listed first, followed by origins in the secondary Cache Group. Origin servers assigned to the Delivery Service that are assigned to neither the primary nor second [...]
-.. image:: multi_site/00.png
- :scale: 100%
- :align: center
+ .. figure:: multi_site/00.png
+ :scale: 100%
+ :align: center
-2) Create a profile to assign to each of the origins:
+#. Create a profile to assign to each of the origins:
-.. image:: multi_site/01.png
- :scale: 100%
- :align: center
+ .. figure:: multi_site/01.png
+ :scale: 100%
+ :align: center
-3) Create server entries for the origination vips:
+#. Create server entries for the origination vips:
-.. image:: multi_site/02.png
- :scale: 100%
- :align: center
+ .. figure:: multi_site/02.png
+ :scale: 100%
+ :align: center
-4) Check the multi-site check box in the delivery service screen:
+#. Check the multi-site check box in the delivery service screen:
-.. image:: multi_site/mso-enable.png
- :scale: 100%
- :align: center
+ .. figure:: multi_site/mso-enable.png
+ :scale: 100%
+ :align: center
-5) Assign the org servers to the delivery service that will have the multi site feature. Org servers assigned to a delivery service with multi-site checked will be assigned to be the origin servers for this DS.
+#. Assign the org servers to the delivery service that will have the multi site feature. Org servers assigned to a delivery service with multi-site checked will be assigned to be the origin servers for this DS.
-.. image:: multi_site/03.png
- :scale: 100%
- :align: center
+ .. figure:: multi_site/03.png
+ :scale: 100%
+ :align: center
-.. Note:: “Origin Server Base URL” uniqueness: In order to enable MID caches to distinguish delivery services by different MSO algorithms while performing parent failover, it requires that “Origin Server Base URL” (OFQDN) for each MSO enabled delivery service is unique unless the exceptions listed afterwards. This means that the OFQDN of a MSO enabled delivery service should be different with the OFQDNs of any other delivery service, regardless of whether they are MSO enabled or not. The [...]
+ .. Note:: “Origin Server Base URL” uniqueness: In order to enable MID caches to distinguish delivery services by different MSO algorithms while performing parent fail-over, it requires that “Origin Server Base URL” (OSBU) for each MSO-enabled Delivery Service is unique. This means that the OSBU of a MSO-enabled Delivery Service should be different with the OSBUs of any other Delivery Service, regardless of whether they are MSO-enabled or not. The exceptions to this rule are:
- 1. If there are multiple CDNs created on the same Traffic Ops, delivery services across different CDNs may have the same OFQDN configured.
- 2. If several delivery services in the same CDN have the same MSO algorithm configured, they may share the same OFQDN.
- 3. If delivery services are assigned with different MID cache groups respectively, they can share the same OFQDN.
- 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.
+ - If there are multiple CDNs created on the same Traffic Ops, delivery services across different CDNs may have the same OSBU configured.
+ - If several delivery services in the same CDN have the same MSO algorithm configured, they may share the same OSBU.
+ - If delivery services are assigned with different MID cache groups respectively, they can share the same OSBU.
+ - This OSBU must be valid - ATS will perform a DNS lookup on this FQDN even if IPs, not DNS, are used in the parent.config.
+ - The OSBU 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.
+#. 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.
-6) For ATS 5.x, configure the mid hdr_rewrite on the delivery service, example: ::
+ a) Create a profile of the type DS_PROFILE for the delivery service in question.
- 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 [...]
+ .. figure:: multi_site/ds_profile.png
+ :scale: 50%
+ :align: center
-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.
+ #) Click "Show profile parameters" to bring up the parameters screen for the profile. Create parameters for the following:
- a) Create a profile of the type DS_PROFILE for the delivery service in question.
+ +----------------------------------------+------------------+--------------------------+-------------------------+
+ | Parameter Name | Config File Name | Value | ATS parent.config value |
+ +========================================+==================+==========================+=========================+
+ | mso.algorithm | parent.config | true, false, strict, | round_robin |
+ | | | consistent_hash | |
+ +----------------------------------------+------------------+--------------------------+-------------------------+
+ | mso.parent_retry | parent.config | simple_retry, both, | parent_retry |
+ | | | unavailable_server_retry | |
+ +----------------------------------------+------------------+--------------------------+-------------------------+
+ | 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. |
+ +----------------------------------------+------------------+--------------------------+-------------------------+
- .. image:: multi_site/ds_profile.png
- :scale: 50%
- :align: center
- b) Click "Show profile parameters" to bring up the parameters screen for the profile. Create parameters for the following:
+ .. figure:: multi_site/ds_profile_parameters.png
+ :scale: 100%
+ :align: center
- +----------------------------------------+------------------+--------------------------+-------------------------+
- | Parameter Name | Config File Name | Value | ATS parent.config value |
- +========================================+==================+==========================+=========================+
- | mso.algorithm | parent.config | true, false, strict, | round_robin |
- | | | consistent_hash | |
- +----------------------------------------+------------------+--------------------------+-------------------------+
- | mso.parent_retry | parent.config | simple_retry, both, | parent_retry |
- | | | unavailable_server_retry | |
- +----------------------------------------+------------------+--------------------------+-------------------------+
- | 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. |
- +----------------------------------------+------------------+--------------------------+-------------------------+
+ #) In the delivery service page, select the newly created DS_PROFILE and save the delivery service.
-
- .. image:: multi_site/ds_profile_parameters.png
- :scale: 100%
- :align: center
-
- c) In the delivery service page, select the newly created DS_PROFILE and save the delivery service.
-
-8) Turn on parent_proxy_routing in the MID profile.
+#. Turn on parent_proxy_routing in the MID profile.