You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by da...@apache.org on 2017/06/07 23:55:01 UTC
[51/51] [partial] incubator-trafficcontrol-website git commit: 1.8.0
is latest release
1.8.0 is latest release
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/commit/0ba7314b
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/tree/0ba7314b
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/diff/0ba7314b
Branch: refs/heads/master
Commit: 0ba7314b172d8441867e7af1e257e8c3b5ed65dd
Parents: 9c7fc09
Author: Dan Kirkwood <da...@gmail.com>
Authored: Wed Jun 7 17:53:41 2017 -0600
Committer: Dan Kirkwood <da...@gmail.com>
Committed: Wed Jun 7 17:53:41 2017 -0600
----------------------------------------------------------------------
docs/latest/.buildinfo | 4 -
docs/latest/_sources/admin/index.rst.txt | 48 -
docs/latest/_sources/admin/index.txt | 48 +
.../_sources/admin/quick_howto/dnssec.rst.txt | 72 -
.../_sources/admin/quick_howto/dnssec.txt | 72 +
.../admin/quick_howto/federations.rst.txt | 135 -
.../_sources/admin/quick_howto/federations.txt | 135 +
.../_sources/admin/quick_howto/index.rst.txt | 28 -
.../latest/_sources/admin/quick_howto/index.txt | 28 +
.../admin/quick_howto/multi_site.rst.txt | 95 -
.../_sources/admin/quick_howto/multi_site.txt | 95 +
.../admin/quick_howto/regionalgeo.rst.txt | 109 -
.../_sources/admin/quick_howto/regionalgeo.txt | 109 +
.../_sources/admin/quick_howto/steering.rst.txt | 95 -
.../_sources/admin/quick_howto/steering.txt | 95 +
.../_sources/admin/traffic_monitor.rst.txt | 142 -
docs/latest/_sources/admin/traffic_monitor.txt | 142 +
.../_sources/admin/traffic_ops_config.rst.txt | 186 -
.../_sources/admin/traffic_ops_config.txt | 186 +
.../admin/traffic_ops_extensions.rst.txt | 88 -
.../_sources/admin/traffic_ops_extensions.txt | 88 +
.../_sources/admin/traffic_ops_install.rst.txt | 381 -
.../_sources/admin/traffic_ops_install.txt | 381 +
.../_sources/admin/traffic_ops_using.rst.txt | 1060 --
.../latest/_sources/admin/traffic_ops_using.txt | 1060 ++
.../_sources/admin/traffic_portal.rst.txt | 53 -
docs/latest/_sources/admin/traffic_portal.txt | 53 +
.../_sources/admin/traffic_router.rst.txt | 494 -
docs/latest/_sources/admin/traffic_router.txt | 494 +
.../_sources/admin/traffic_server.rst.txt | 71 -
docs/latest/_sources/admin/traffic_server.txt | 71 +
.../latest/_sources/admin/traffic_stats.rst.txt | 187 -
docs/latest/_sources/admin/traffic_stats.txt | 187 +
.../latest/_sources/admin/traffic_vault.rst.txt | 195 -
docs/latest/_sources/admin/traffic_vault.txt | 195 +
.../_sources/basics/cache_revalidation.rst.txt | 71 -
.../_sources/basics/cache_revalidation.txt | 71 +
.../_sources/basics/caching_proxies.rst.txt | 238 -
docs/latest/_sources/basics/caching_proxies.txt | 238 +
.../basics/content_delivery_networks.rst.txt | 40 -
.../basics/content_delivery_networks.txt | 40 +
docs/latest/_sources/basics/http_11.rst.txt | 48 -
docs/latest/_sources/basics/http_11.txt | 48 +
docs/latest/_sources/basics/index.rst.txt | 29 -
docs/latest/_sources/basics/index.txt | 29 +
docs/latest/_sources/development/index.rst.txt | 29 -
docs/latest/_sources/development/index.txt | 29 +
.../development/traffic_monitor.rst.txt | 112 -
.../_sources/development/traffic_monitor.txt | 112 +
.../traffic_monitor/traffic_monitor_api.rst.txt | 178 -
.../traffic_monitor/traffic_monitor_api.txt | 178 +
.../_sources/development/traffic_ops.rst.txt | 630 -
.../latest/_sources/development/traffic_ops.txt | 630 +
.../development/traffic_ops_api/routes.rst.txt | 116 -
.../development/traffic_ops_api/routes.txt | 116 +
.../development/traffic_ops_api/v11/asn.rst.txt | 69 -
.../development/traffic_ops_api/v11/asn.txt | 69 +
.../traffic_ops_api/v11/cachegroup.rst.txt | 317 -
.../traffic_ops_api/v11/cachegroup.txt | 317 +
.../development/traffic_ops_api/v11/cdn.rst.txt | 1086 --
.../development/traffic_ops_api/v11/cdn.txt | 1086 ++
.../traffic_ops_api/v11/changelog.rst.txt | 154 -
.../traffic_ops_api/v11/changelog.txt | 154 +
.../traffic_ops_api/v11/deliveryservice.rst.txt | 1276 --
.../traffic_ops_api/v11/deliveryservice.txt | 1276 ++
.../traffic_ops_api/v11/hwinfo.rst.txt | 67 -
.../development/traffic_ops_api/v11/hwinfo.txt | 67 +
.../traffic_ops_api/v11/parameter.rst.txt | 136 -
.../traffic_ops_api/v11/parameter.txt | 136 +
.../traffic_ops_api/v11/phys_location.rst.txt | 449 -
.../traffic_ops_api/v11/phys_location.txt | 449 +
.../traffic_ops_api/v11/profile.rst.txt | 129 -
.../development/traffic_ops_api/v11/profile.txt | 129 +
.../traffic_ops_api/v11/region.rst.txt | 235 -
.../development/traffic_ops_api/v11/region.txt | 235 +
.../traffic_ops_api/v11/role.rst.txt | 58 -
.../development/traffic_ops_api/v11/role.txt | 58 +
.../traffic_ops_api/v11/server.rst.txt | 630 -
.../development/traffic_ops_api/v11/server.txt | 630 +
.../traffic_ops_api/v11/static_dns.rst.txt | 63 -
.../traffic_ops_api/v11/static_dns.txt | 63 +
.../traffic_ops_api/v11/status.rst.txt | 127 -
.../development/traffic_ops_api/v11/status.txt | 127 +
.../traffic_ops_api/v11/system.rst.txt | 79 -
.../development/traffic_ops_api/v11/system.txt | 79 +
.../traffic_ops_api/v11/to_extension.rst.txt | 210 -
.../traffic_ops_api/v11/to_extension.txt | 210 +
.../traffic_ops_api/v11/type.rst.txt | 151 -
.../development/traffic_ops_api/v11/type.txt | 151 +
.../traffic_ops_api/v11/user.rst.txt | 778 --
.../development/traffic_ops_api/v11/user.txt | 778 ++
.../development/traffic_ops_api/v12/asn.rst.txt | 192 -
.../development/traffic_ops_api/v12/asn.txt | 192 +
.../traffic_ops_api/v12/cache_stats.rst.txt | 134 -
.../traffic_ops_api/v12/cache_stats.txt | 134 +
.../traffic_ops_api/v12/cachegroup.rst.txt | 696 --
.../traffic_ops_api/v12/cachegroup.txt | 696 ++
.../development/traffic_ops_api/v12/cdn.rst.txt | 1334 ---
.../development/traffic_ops_api/v12/cdn.txt | 1334 +++
.../traffic_ops_api/v12/changelog.rst.txt | 154 -
.../traffic_ops_api/v12/changelog.txt | 154 +
.../traffic_ops_api/v12/deliveryservice.rst.txt | 1756 ---
.../traffic_ops_api/v12/deliveryservice.txt | 1756 +++
.../v12/deliveryservice_stats.rst.txt | 155 -
.../v12/deliveryservice_stats.txt | 155 +
.../traffic_ops_api/v12/division.rst.txt | 202 -
.../traffic_ops_api/v12/division.txt | 202 +
.../traffic_ops_api/v12/federation.rst.txt | 151 -
.../traffic_ops_api/v12/federation.txt | 151 +
.../traffic_ops_api/v12/hwinfo.rst.txt | 68 -
.../development/traffic_ops_api/v12/hwinfo.txt | 68 +
.../traffic_ops_api/v12/influxdb.rst.txt | 65 -
.../traffic_ops_api/v12/influxdb.txt | 65 +
.../traffic_ops_api/v12/parameter.rst.txt | 516 -
.../traffic_ops_api/v12/parameter.txt | 516 +
.../traffic_ops_api/v12/phys_location.rst.txt | 448 -
.../traffic_ops_api/v12/phys_location.txt | 448 +
.../traffic_ops_api/v12/profile.rst.txt | 357 -
.../development/traffic_ops_api/v12/profile.txt | 357 +
.../v12/profile_parameter.rst.txt | 457 -
.../traffic_ops_api/v12/profile_parameter.txt | 457 +
.../traffic_ops_api/v12/region.rst.txt | 235 -
.../development/traffic_ops_api/v12/region.txt | 235 +
.../traffic_ops_api/v12/role.rst.txt | 59 -
.../development/traffic_ops_api/v12/role.txt | 59 +
.../traffic_ops_api/v12/server.rst.txt | 1125 --
.../development/traffic_ops_api/v12/server.txt | 1125 ++
.../traffic_ops_api/v12/static_dns.rst.txt | 66 -
.../traffic_ops_api/v12/static_dns.txt | 66 +
.../traffic_ops_api/v12/status.rst.txt | 127 -
.../development/traffic_ops_api/v12/status.txt | 127 +
.../traffic_ops_api/v12/system.rst.txt | 80 -
.../development/traffic_ops_api/v12/system.txt | 80 +
.../traffic_ops_api/v12/to_extension.rst.txt | 206 -
.../traffic_ops_api/v12/to_extension.txt | 206 +
.../traffic_ops_api/v12/topology.rst.txt | 54 -
.../traffic_ops_api/v12/topology.txt | 54 +
.../traffic_ops_api/v12/type.rst.txt | 151 -
.../development/traffic_ops_api/v12/type.txt | 151 +
.../traffic_ops_api/v12/user.rst.txt | 784 --
.../development/traffic_ops_api/v12/user.txt | 784 ++
.../_sources/development/traffic_portal.rst.txt | 54 -
.../_sources/development/traffic_portal.txt | 54 +
.../_sources/development/traffic_router.rst.txt | 143 -
.../_sources/development/traffic_router.txt | 143 +
.../traffic_router/traffic_router_api.rst.txt | 48 -
.../traffic_router/traffic_router_api.txt | 48 +
.../_sources/development/traffic_server.rst.txt | 19 -
.../_sources/development/traffic_server.txt | 19 +
.../_sources/development/traffic_stats.rst.txt | 58 -
.../_sources/development/traffic_stats.txt | 58 +
docs/latest/_sources/faq/administration.rst.txt | 66 -
docs/latest/_sources/faq/administration.txt | 66 +
docs/latest/_sources/faq/development.rst.txt | 21 -
docs/latest/_sources/faq/development.txt | 21 +
docs/latest/_sources/faq/general.rst.txt | 52 -
docs/latest/_sources/faq/general.txt | 52 +
docs/latest/_sources/faq/index.rst.txt | 26 -
docs/latest/_sources/faq/index.txt | 26 +
docs/latest/_sources/glossary.rst.txt | 81 -
docs/latest/_sources/glossary.txt | 66 +
docs/latest/_sources/index.rst.txt | 80 -
docs/latest/_sources/index.txt | 80 +
docs/latest/_sources/overview/index.rst.txt | 30 -
docs/latest/_sources/overview/index.txt | 30 +
.../_sources/overview/introduction.rst.txt | 28 -
docs/latest/_sources/overview/introduction.txt | 28 +
.../_sources/overview/traffic_monitor.rst.txt | 66 -
.../_sources/overview/traffic_monitor.txt | 66 +
.../_sources/overview/traffic_ops.rst.txt | 39 -
docs/latest/_sources/overview/traffic_ops.txt | 39 +
.../_sources/overview/traffic_portal.rst.txt | 43 -
.../latest/_sources/overview/traffic_portal.txt | 43 +
.../_sources/overview/traffic_router.rst.txt | 108 -
.../latest/_sources/overview/traffic_router.txt | 108 +
.../_sources/overview/traffic_server.rst.txt | 49 -
.../latest/_sources/overview/traffic_server.txt | 49 +
.../_sources/overview/traffic_stats.rst.txt | 35 -
docs/latest/_sources/overview/traffic_stats.txt | 35 +
.../_sources/overview/traffic_vault.rst.txt | 36 -
docs/latest/_sources/overview/traffic_vault.txt | 36 +
docs/latest/_static/basic.css | 79 +-
docs/latest/_static/comment-bright.png | Bin 756 -> 3500 bytes
docs/latest/_static/comment-close.png | Bin 829 -> 3578 bytes
docs/latest/_static/comment.png | Bin 641 -> 3445 bytes
docs/latest/_static/doctools.js | 28 +-
docs/latest/_static/down-pressed.png | Bin 222 -> 347 bytes
docs/latest/_static/down.png | Bin 202 -> 347 bytes
docs/latest/_static/file.png | Bin 286 -> 358 bytes
.../_static/fonts/fontawesome-webfont.svg | 414 +
docs/latest/_static/jquery-1.11.1.js | 10308 +++++++++++++++++
docs/latest/_static/jquery-3.1.0.js | 10074 ----------------
docs/latest/_static/jquery.js | 8 +-
docs/latest/_static/minus.png | Bin 90 -> 173 bytes
docs/latest/_static/plus.png | Bin 90 -> 173 bytes
docs/latest/_static/pygments.css | 2 -
docs/latest/_static/searchtools.js | 166 +-
docs/latest/_static/up-pressed.png | Bin 214 -> 345 bytes
docs/latest/_static/up.png | Bin 203 -> 345 bytes
docs/latest/_static/websupport.js | 4 +-
docs/latest/admin/index.html | 15 +-
docs/latest/admin/quick_howto/dnssec.html | 21 +-
docs/latest/admin/quick_howto/federations.html | 27 +-
docs/latest/admin/quick_howto/index.html | 15 +-
docs/latest/admin/quick_howto/multi_site.html | 29 +-
docs/latest/admin/quick_howto/regionalgeo.html | 63 +-
docs/latest/admin/quick_howto/steering.html | 51 +-
docs/latest/admin/traffic_monitor.html | 31 +-
docs/latest/admin/traffic_ops_config.html | 33 +-
docs/latest/admin/traffic_ops_extensions.html | 81 +-
docs/latest/admin/traffic_ops_install.html | 191 +-
docs/latest/admin/traffic_ops_using.html | 139 +-
docs/latest/admin/traffic_portal.html | 15 +-
docs/latest/admin/traffic_router.html | 31 +-
docs/latest/admin/traffic_server.html | 21 +-
docs/latest/admin/traffic_stats.html | 38 +-
docs/latest/admin/traffic_vault.html | 51 +-
docs/latest/basics/cache_revalidation.html | 83 +-
docs/latest/basics/caching_proxies.html | 185 +-
.../basics/content_delivery_networks.html | 32 +-
docs/latest/basics/http_11.html | 27 +-
docs/latest/basics/index.html | 15 +-
docs/latest/development/index.html | 15 +-
docs/latest/development/traffic_monitor.html | 17 +-
.../traffic_monitor/traffic_monitor_api.html | 13 +-
docs/latest/development/traffic_ops.html | 51 +-
.../development/traffic_ops_api/routes.html | 105 +-
.../development/traffic_ops_api/v11/asn.html | 35 +-
.../traffic_ops_api/v11/cachegroup.html | 163 +-
.../development/traffic_ops_api/v11/cdn.html | 323 +-
.../traffic_ops_api/v11/changelog.html | 75 +-
.../traffic_ops_api/v11/deliveryservice.html | 579 +-
.../development/traffic_ops_api/v11/hwinfo.html | 33 +-
.../traffic_ops_api/v11/parameter.html | 81 +-
.../traffic_ops_api/v11/phys_location.html | 225 +-
.../traffic_ops_api/v11/profile.html | 43 +-
.../development/traffic_ops_api/v11/region.html | 87 +-
.../development/traffic_ops_api/v11/role.html | 25 +-
.../development/traffic_ops_api/v11/server.html | 483 +-
.../traffic_ops_api/v11/static_dns.html | 37 +-
.../development/traffic_ops_api/v11/status.html | 101 +-
.../development/traffic_ops_api/v11/system.html | 37 +-
.../traffic_ops_api/v11/to_extension.html | 107 +-
.../development/traffic_ops_api/v11/type.html | 53 +-
.../development/traffic_ops_api/v11/user.html | 293 +-
.../development/traffic_ops_api/v12/asn.html | 77 +-
.../traffic_ops_api/v12/cache_stats.html | 61 +-
.../traffic_ops_api/v12/cachegroup.html | 317 +-
.../development/traffic_ops_api/v12/cdn.html | 427 +-
.../traffic_ops_api/v12/changelog.html | 75 +-
.../traffic_ops_api/v12/deliveryservice.html | 947 +-
.../v12/deliveryservice_stats.html | 73 +-
.../traffic_ops_api/v12/division.html | 91 +-
.../traffic_ops_api/v12/federation.html | 67 +-
.../development/traffic_ops_api/v12/hwinfo.html | 33 +-
.../traffic_ops_api/v12/influxdb.html | 49 +-
.../traffic_ops_api/v12/parameter.html | 225 +-
.../traffic_ops_api/v12/phys_location.html | 225 +-
.../traffic_ops_api/v12/profile.html | 109 +-
.../traffic_ops_api/v12/profile_parameter.html | 263 +-
.../development/traffic_ops_api/v12/region.html | 87 +-
.../development/traffic_ops_api/v12/role.html | 25 +-
.../development/traffic_ops_api/v12/server.html | 687 +-
.../traffic_ops_api/v12/static_dns.html | 37 +-
.../development/traffic_ops_api/v12/status.html | 101 +-
.../development/traffic_ops_api/v12/system.html | 37 +-
.../traffic_ops_api/v12/to_extension.html | 107 +-
.../traffic_ops_api/v12/topology.html | 17 +-
.../development/traffic_ops_api/v12/type.html | 53 +-
.../development/traffic_ops_api/v12/user.html | 293 +-
docs/latest/development/traffic_portal.html | 15 +-
docs/latest/development/traffic_router.html | 17 +-
.../traffic_router/traffic_router_api.html | 13 +-
docs/latest/development/traffic_server.html | 15 +-
docs/latest/development/traffic_stats.html | 15 +-
docs/latest/faq/administration.html | 56 +-
docs/latest/faq/development.html | 15 +-
docs/latest/faq/general.html | 15 +-
docs/latest/faq/index.html | 15 +-
docs/latest/genindex.html | 483 +-
docs/latest/glossary.html | 53 +-
docs/latest/index.html | 13 +-
docs/latest/objects.inv | Bin 3713 -> 2636 bytes
docs/latest/overview/index.html | 15 +-
docs/latest/overview/introduction.html | 15 +-
docs/latest/overview/traffic_monitor.html | 15 +-
docs/latest/overview/traffic_ops.html | 15 +-
docs/latest/overview/traffic_portal.html | 15 +-
docs/latest/overview/traffic_router.html | 29 +-
docs/latest/overview/traffic_server.html | 17 +-
docs/latest/overview/traffic_stats.html | 15 +-
docs/latest/overview/traffic_vault.html | 26 +-
docs/latest/search.html | 11 +-
docs/latest/searchindex.js | 2 +-
294 files changed, 37063 insertions(+), 36763 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/.buildinfo
----------------------------------------------------------------------
diff --git a/docs/latest/.buildinfo b/docs/latest/.buildinfo
deleted file mode 100644
index d80d85a..0000000
--- a/docs/latest/.buildinfo
+++ /dev/null
@@ -1,4 +0,0 @@
-# Sphinx build info version 1
-# This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: ca8576454f95ff0477038bbbe38dc7fb
-tags: 645f666f9bcd5a90fca523b33c5a78b7
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/index.rst.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/index.rst.txt b/docs/latest/_sources/admin/index.rst.txt
deleted file mode 100644
index e92f5e2..0000000
--- a/docs/latest/_sources/admin/index.rst.txt
+++ /dev/null
@@ -1,48 +0,0 @@
-..
-..
-.. Licensed under the Apache License, Version 2.0 (the "License");
-.. you may not use this file except in compliance with the License.
-.. You may obtain a copy of the License at
-..
-.. http://www.apache.org/licenses/LICENSE-2.0
-..
-.. Unless required by applicable law or agreed to in writing, software
-.. distributed under the License is distributed on an "AS IS" BASIS,
-.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-.. See the License for the specific language governing permissions and
-.. limitations under the License.
-..
-
-Administrator's Guide
-*********************
-
-Traffic Control is distributed in source form for the developer, but also as a binary package. This guide details how to install and configure a Traffic Control CDN using the binary packages, as well as how to perform common operations running a CDN.
-
-When installing a complete CDN from scratch, a sample recommended order is:
-
-1. Traffic Ops
-2. Traffic Vault (Riak)
-3. Apache Traffic Server Mid-Tier Caches
-4. Apache Traffic Server Edge Caches
-5. Traffic Monitor
-6. Traffic Router
-7. Traffic Stats
-8. Traffic Portal
-
-Once everything is installed, you will need to configure the servers to talk to each other. You will also need Origin server(s), which the Mid-Tier Cache(s) get content from. An Origin server is simply an HTTP(S) server which serves the content you wish to cache on the CDN.
-
-.. toctree::
- :maxdepth: 3
-
- traffic_ops_install.rst
- traffic_ops_config.rst
- traffic_ops_using.rst
- traffic_ops_extensions.rst
- traffic_portal.rst
- traffic_monitor.rst
- traffic_router.rst
- traffic_stats.rst
- traffic_server.rst
- traffic_vault.rst
- quick_howto/index.rst
-
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/index.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/index.txt b/docs/latest/_sources/admin/index.txt
new file mode 100644
index 0000000..e92f5e2
--- /dev/null
+++ b/docs/latest/_sources/admin/index.txt
@@ -0,0 +1,48 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+Administrator's Guide
+*********************
+
+Traffic Control is distributed in source form for the developer, but also as a binary package. This guide details how to install and configure a Traffic Control CDN using the binary packages, as well as how to perform common operations running a CDN.
+
+When installing a complete CDN from scratch, a sample recommended order is:
+
+1. Traffic Ops
+2. Traffic Vault (Riak)
+3. Apache Traffic Server Mid-Tier Caches
+4. Apache Traffic Server Edge Caches
+5. Traffic Monitor
+6. Traffic Router
+7. Traffic Stats
+8. Traffic Portal
+
+Once everything is installed, you will need to configure the servers to talk to each other. You will also need Origin server(s), which the Mid-Tier Cache(s) get content from. An Origin server is simply an HTTP(S) server which serves the content you wish to cache on the CDN.
+
+.. toctree::
+ :maxdepth: 3
+
+ traffic_ops_install.rst
+ traffic_ops_config.rst
+ traffic_ops_using.rst
+ traffic_ops_extensions.rst
+ traffic_portal.rst
+ traffic_monitor.rst
+ traffic_router.rst
+ traffic_stats.rst
+ traffic_server.rst
+ traffic_vault.rst
+ quick_howto/index.rst
+
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt b/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt
deleted file mode 100644
index d336057..0000000
--- a/docs/latest/_sources/admin/quick_howto/dnssec.rst.txt
+++ /dev/null
@@ -1,72 +0,0 @@
-..
-..
-.. Licensed under the Apache License, Version 2.0 (the "License");
-.. you may not use this file except in compliance with the License.
-.. You may obtain a copy of the License at
-..
-.. http://www.apache.org/licenses/LICENSE-2.0
-..
-.. Unless required by applicable law or agreed to in writing, software
-.. distributed under the License is distributed on an "AS IS" BASIS,
-.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-.. See the License for the specific language governing permissions and
-.. limitations under the License.
-..
-
-.. _rl-dnssec-qht:
-
-****************
-Configure DNSSEC
-****************
-
-.. Note:: In order for Traffic Ops to successfully store keys in Traffic Vault, at least one Riak Server needs to be configured in Traffic Ops. See the `Traffic Vault admin page <../traffic_vault.html>`_ for more information.
-
-.. Note:: Currently DNSSEC is only supported for DNS delivery services.
-
-1) Go to Tools->Manage DNSSEC Keys choose a CDN and click Manage DNSSEC Keys
-
-.. image:: dnssec01.png
- :scale: 100%
- :align: center
-
-2) Generate keys for a CDN by clicking Generate Keys then entering the following information:
-
- - Expiration in days for the Zone Signing Key (ZSK)
- - Expiration in days for the Key Signing Key (KSK)
- - Effective Date
-
- Once the required information has been entered click on the 'Generate Keys' button.
-
- Depending upon the number of Delivery Services in the CDN, generating DNSSEC keys may take serveral seconds.
-
-.. image:: dnssec02.png
- :scale: 100%
- :align: center
-
-3) In order for DNSSEC to work properly, the DS Record information needs to be added to the parent zone of the CDN's domain (e.g. If the CDN's domain is 'cdn.kabletown.net' the parent zone is 'kabletown.net').
-
- If you control your parent zone you can enter this information yourself, otherwise you will need to work with your DNS team to get the DS Record added to the parent zone.
-
-.. image:: dnssec03.png
- :scale: 70%
- :align: center
-
-4) Once DS Record information has been added to the parent zone, DNSSEC needs to be activated for the CDN so that Traffic Router will sign responses.
-
- Click on Tools -> Manage DNSSEC Keys -> Choose your CDN -> On the Manage DNSSEC Keys page click the activate DNSSEC Keys button.
-
- This will add a 'dnssec.enabled = "true"' entry to CRConfig for the chosen CDN.
-
-.. image:: dnssec04.png
- :scale: 70%
- :align: center
-
-5) DNSSEC should now be active on your CDN and Traffic Router should be signing responses.
-
- A dig command with +dnssec added should show you the signed responses.
-
- ``dig edge.cdn.kabletown.net. +dnssec``
-
-6) When KSK expiration is approaching (default 365 days), it is necessary to manually generate a new KSK for the TLD (Top Level Domain) and add the DS Record to the parent zone. In order to avoid signing errors, it is suggested that an effective date is chosen which allows time for the DS Record to be added to the parent zone before the new KSK becomes active.
-
- A new KSK can be generated by clicking the 'Regenerate KSK' button on the Manage DNSSEC Keys screen (see screenshot above).
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/dnssec.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/dnssec.txt b/docs/latest/_sources/admin/quick_howto/dnssec.txt
new file mode 100644
index 0000000..d336057
--- /dev/null
+++ b/docs/latest/_sources/admin/quick_howto/dnssec.txt
@@ -0,0 +1,72 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+.. _rl-dnssec-qht:
+
+****************
+Configure DNSSEC
+****************
+
+.. Note:: In order for Traffic Ops to successfully store keys in Traffic Vault, at least one Riak Server needs to be configured in Traffic Ops. See the `Traffic Vault admin page <../traffic_vault.html>`_ for more information.
+
+.. Note:: Currently DNSSEC is only supported for DNS delivery services.
+
+1) Go to Tools->Manage DNSSEC Keys choose a CDN and click Manage DNSSEC Keys
+
+.. image:: dnssec01.png
+ :scale: 100%
+ :align: center
+
+2) Generate keys for a CDN by clicking Generate Keys then entering the following information:
+
+ - Expiration in days for the Zone Signing Key (ZSK)
+ - Expiration in days for the Key Signing Key (KSK)
+ - Effective Date
+
+ Once the required information has been entered click on the 'Generate Keys' button.
+
+ Depending upon the number of Delivery Services in the CDN, generating DNSSEC keys may take serveral seconds.
+
+.. image:: dnssec02.png
+ :scale: 100%
+ :align: center
+
+3) In order for DNSSEC to work properly, the DS Record information needs to be added to the parent zone of the CDN's domain (e.g. If the CDN's domain is 'cdn.kabletown.net' the parent zone is 'kabletown.net').
+
+ If you control your parent zone you can enter this information yourself, otherwise you will need to work with your DNS team to get the DS Record added to the parent zone.
+
+.. image:: dnssec03.png
+ :scale: 70%
+ :align: center
+
+4) Once DS Record information has been added to the parent zone, DNSSEC needs to be activated for the CDN so that Traffic Router will sign responses.
+
+ Click on Tools -> Manage DNSSEC Keys -> Choose your CDN -> On the Manage DNSSEC Keys page click the activate DNSSEC Keys button.
+
+ This will add a 'dnssec.enabled = "true"' entry to CRConfig for the chosen CDN.
+
+.. image:: dnssec04.png
+ :scale: 70%
+ :align: center
+
+5) DNSSEC should now be active on your CDN and Traffic Router should be signing responses.
+
+ A dig command with +dnssec added should show you the signed responses.
+
+ ``dig edge.cdn.kabletown.net. +dnssec``
+
+6) When KSK expiration is approaching (default 365 days), it is necessary to manually generate a new KSK for the TLD (Top Level Domain) and add the DS Record to the parent zone. In order to avoid signing errors, it is suggested that an effective date is chosen which allows time for the DS Record to be added to the parent zone before the new KSK becomes active.
+
+ A new KSK can be generated by clicking the 'Regenerate KSK' button on the Manage DNSSEC Keys screen (see screenshot above).
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/federations.rst.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/federations.rst.txt b/docs/latest/_sources/admin/quick_howto/federations.rst.txt
deleted file mode 100644
index a17122c..0000000
--- a/docs/latest/_sources/admin/quick_howto/federations.rst.txt
+++ /dev/null
@@ -1,135 +0,0 @@
-..
-..
-.. Licensed under the Apache License, Version 2.0 (the "License");
-.. you may not use this file except in compliance with the License.
-.. You may obtain a copy of the License at
-..
-.. http://www.apache.org/licenses/LICENSE-2.0
-..
-.. Unless required by applicable law or agreed to in writing, software
-.. distributed under the License is distributed on an "AS IS" BASIS,
-.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-.. See the License for the specific language governing permissions and
-.. limitations under the License.
-..
-
-.. _rl-federations-qht:
-
-*********************
-Configure Federations
-*********************
-
-1) Create a user with a federations role (Misc -> Users -> Add User). This user will have the ability to perform the following actions:
-
- - Edit the federation
- - Delete the federation
- - Add IPV4 resolvers
- - Add IPV6 resolvers
-
-.. image:: federation01.png
- :scale: 100%
- :align: center
-
-2) As a user with admin priveleges, create a Federation Mapping by going to Delivery Services -> Federations and then clicking 'Add Federation Mapping'
-
-3) Choose the Delivery Service for the federation to be mapped to and assign it to the Federation User; click Add.
-
-.. image:: federation02.png
- :scale: 100%
- :align: center
-
-4) After the Federation is added, Traffic Ops will display the Federation.
-
- Changes can be made at this time or the Federation can be deleted. Notice that no resolvers have been added to the fedeation yet. This can only be done by the federation user created in step 1.
-
- If no further action is necessary, the Close button will close the window and display the list of all Federations.
-
-.. image:: federation03.png
- :scale: 100%
- :align: center
-
-
-**The Federation user can now add resolvers to the Federation Mapping in Traffic Ops.**
-
-5) The federation user logs to traffic ops and stores the mojolicious cookie. The mojolicious cookie can be obtained manually using the debug tools on a web browser or via curl.
-
- Example::
-
- $ curl -i -XPOST "http://localhost:3000/api/1.1/user/login" -H "Content-Type: application/json" -d '{ "u": "federation_user1", "p": "password" }'
-
- HTTP/1.1 200 OK
- Date: Wed, 02 Dec 2015 21:12:06 GMT
- Content-Length: 65
- Access-Control-Allow-Credentials: true
- Content-Type: application/json
- Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
- Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0; expires=Thu, 03 Dec 2015 01:12:06 GMT; path=/; HttpOnly
- Server: Mojolicious (Perl)
- Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
- Cache-Control: no-cache, no-store, max-age=0, must-revalidate
- Connection: keep-alive
- Access-Control-Allow-Origin: http://localhost:8080
-
- {"alerts":[{"level":"success","text":"Successfully logged in."}]}
-
-6) The federation user sends a request to Traffic Ops to add IPV4 and/or IPV6 resolvers
-
-
- Example::
-
- $ curl -ki -H "Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0;" -XPUT 'http://localhost:3000/api/1.2/federations' -d '
- {"federations": [
- { "deliveryService": "images-c1",
- "mappings":
- { "resolve4": [ "8.8.8.8/32", "8.8.4.4/32" ],
- "resolve6": ["2001:4860:4860::8888/128", "2001:4860:4860::8844"]
- }
- }
- ]
- }'
-
- HTTP/1.1 200 OK
- Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1OTQyLCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---b42be0749415cefd1d14e1a91bb214845b4de556; expires=Thu, 03 Dec 2015 01:25:42 GMT; path=/; HttpOnly
- Server: Mojolicious (Perl)
- Date: Wed, 02 Dec 2015 21:25:42 GMT
- Content-Length: 74
- Access-Control-Allow-Credentials: true
- Content-Type: application/json
- Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
- Cache-Control: no-cache, no-store, max-age=0, must-revalidate
- Access-Control-Allow-Origin: http://localhost:8080
- Connection: keep-alive
- Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
-
- {"response":"federation_user1 successfully created federation resolvers."}
-
-7) The resolvers added by the federation user will now visible in Traffic Ops.
-
-.. image:: federation04.png
- :scale: 100%
- :align: center
-
-8) Any requests made from a client that resolves to one of the federation resolvers will now be given a CNAME from Traffic Router.
-
- Example::
-
- $ dig @tr.kabletown.net edge.images-c1.kabletown.net
-
- ; <<>> DiG 9.7.3-RedHat-9.7.3-2.el6 <<>> @tr.kabletown.net edge.images-c1.kabletown.net
- ; (1 server found)
- ;; global options: +cmd
- ;; Got answer:
- ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45110
- ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
- ;; WARNING: recursion requested but not available
-
- ;; QUESTION SECTION:
- ;edge.images-c1.kabletown.net. IN A
-
- ;; ANSWER SECTION:
- edge.images-c1.kabletown.net. 30 IN CNAME img.mega-cdn.net.
-
- ;; Query time: 9 msec
- ;; SERVER: 10.10.10.10#53(10.10.10.10)
- ;; WHEN: Wed Dec 2 22:05:26 2015
- ;; MSG SIZE rcvd: 84
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/federations.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/federations.txt b/docs/latest/_sources/admin/quick_howto/federations.txt
new file mode 100644
index 0000000..a17122c
--- /dev/null
+++ b/docs/latest/_sources/admin/quick_howto/federations.txt
@@ -0,0 +1,135 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+.. _rl-federations-qht:
+
+*********************
+Configure Federations
+*********************
+
+1) Create a user with a federations role (Misc -> Users -> Add User). This user will have the ability to perform the following actions:
+
+ - Edit the federation
+ - Delete the federation
+ - Add IPV4 resolvers
+ - Add IPV6 resolvers
+
+.. image:: federation01.png
+ :scale: 100%
+ :align: center
+
+2) As a user with admin priveleges, create a Federation Mapping by going to Delivery Services -> Federations and then clicking 'Add Federation Mapping'
+
+3) Choose the Delivery Service for the federation to be mapped to and assign it to the Federation User; click Add.
+
+.. image:: federation02.png
+ :scale: 100%
+ :align: center
+
+4) After the Federation is added, Traffic Ops will display the Federation.
+
+ Changes can be made at this time or the Federation can be deleted. Notice that no resolvers have been added to the fedeation yet. This can only be done by the federation user created in step 1.
+
+ If no further action is necessary, the Close button will close the window and display the list of all Federations.
+
+.. image:: federation03.png
+ :scale: 100%
+ :align: center
+
+
+**The Federation user can now add resolvers to the Federation Mapping in Traffic Ops.**
+
+5) The federation user logs to traffic ops and stores the mojolicious cookie. The mojolicious cookie can be obtained manually using the debug tools on a web browser or via curl.
+
+ Example::
+
+ $ curl -i -XPOST "http://localhost:3000/api/1.1/user/login" -H "Content-Type: application/json" -d '{ "u": "federation_user1", "p": "password" }'
+
+ HTTP/1.1 200 OK
+ Date: Wed, 02 Dec 2015 21:12:06 GMT
+ Content-Length: 65
+ Access-Control-Allow-Credentials: true
+ Content-Type: application/json
+ Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+ Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0; expires=Thu, 03 Dec 2015 01:12:06 GMT; path=/; HttpOnly
+ Server: Mojolicious (Perl)
+ Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+ Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+ Connection: keep-alive
+ Access-Control-Allow-Origin: http://localhost:8080
+
+ {"alerts":[{"level":"success","text":"Successfully logged in."}]}
+
+6) The federation user sends a request to Traffic Ops to add IPV4 and/or IPV6 resolvers
+
+
+ Example::
+
+ $ curl -ki -H "Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1MTI2LCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---06b4f870d809d82a91433e92eae8320875c3e8b0;" -XPUT 'http://localhost:3000/api/1.2/federations' -d '
+ {"federations": [
+ { "deliveryService": "images-c1",
+ "mappings":
+ { "resolve4": [ "8.8.8.8/32", "8.8.4.4/32" ],
+ "resolve6": ["2001:4860:4860::8888/128", "2001:4860:4860::8844"]
+ }
+ }
+ ]
+ }'
+
+ HTTP/1.1 200 OK
+ Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDQ5MTA1OTQyLCJhdXRoX2RhdGEiOiJmZWRlcmF0aW9uX3VzZXIxIn0---b42be0749415cefd1d14e1a91bb214845b4de556; expires=Thu, 03 Dec 2015 01:25:42 GMT; path=/; HttpOnly
+ Server: Mojolicious (Perl)
+ Date: Wed, 02 Dec 2015 21:25:42 GMT
+ Content-Length: 74
+ Access-Control-Allow-Credentials: true
+ Content-Type: application/json
+ Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
+ Cache-Control: no-cache, no-store, max-age=0, must-revalidate
+ Access-Control-Allow-Origin: http://localhost:8080
+ Connection: keep-alive
+ Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
+
+ {"response":"federation_user1 successfully created federation resolvers."}
+
+7) The resolvers added by the federation user will now visible in Traffic Ops.
+
+.. image:: federation04.png
+ :scale: 100%
+ :align: center
+
+8) Any requests made from a client that resolves to one of the federation resolvers will now be given a CNAME from Traffic Router.
+
+ Example::
+
+ $ dig @tr.kabletown.net edge.images-c1.kabletown.net
+
+ ; <<>> DiG 9.7.3-RedHat-9.7.3-2.el6 <<>> @tr.kabletown.net edge.images-c1.kabletown.net
+ ; (1 server found)
+ ;; global options: +cmd
+ ;; Got answer:
+ ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45110
+ ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
+ ;; WARNING: recursion requested but not available
+
+ ;; QUESTION SECTION:
+ ;edge.images-c1.kabletown.net. IN A
+
+ ;; ANSWER SECTION:
+ edge.images-c1.kabletown.net. 30 IN CNAME img.mega-cdn.net.
+
+ ;; Query time: 9 msec
+ ;; SERVER: 10.10.10.10#53(10.10.10.10)
+ ;; WHEN: Wed Dec 2 22:05:26 2015
+ ;; MSG SIZE rcvd: 84
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/index.rst.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/index.rst.txt b/docs/latest/_sources/admin/quick_howto/index.rst.txt
deleted file mode 100644
index 96f098f..0000000
--- a/docs/latest/_sources/admin/quick_howto/index.rst.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-..
-..
-.. Licensed under the Apache License, Version 2.0 (the "License");
-.. you may not use this file except in compliance with the License.
-.. You may obtain a copy of the License at
-..
-.. http://www.apache.org/licenses/LICENSE-2.0
-..
-.. Unless required by applicable law or agreed to in writing, software
-.. distributed under the License is distributed on an "AS IS" BASIS,
-.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-.. See the License for the specific language governing permissions and
-.. limitations under the License.
-..
-
-Quick How To Guides
-*******************
-
-Traffic Control is a complicated system, and documenting it is not trivial. Sometimes a picture says more than a thousand words, so here are some screen shot based tutorials on how to use some of the more involved features.
-
-.. toctree::
- :maxdepth: 3
-
- multi_site.rst
- dnssec.rst
- federations.rst
- regionalgeo.rst
- steering.rst
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/index.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/index.txt b/docs/latest/_sources/admin/quick_howto/index.txt
new file mode 100644
index 0000000..96f098f
--- /dev/null
+++ b/docs/latest/_sources/admin/quick_howto/index.txt
@@ -0,0 +1,28 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+Quick How To Guides
+*******************
+
+Traffic Control is a complicated system, and documenting it is not trivial. Sometimes a picture says more than a thousand words, so here are some screen shot based tutorials on how to use some of the more involved features.
+
+.. toctree::
+ :maxdepth: 3
+
+ multi_site.rst
+ dnssec.rst
+ federations.rst
+ regionalgeo.rst
+ steering.rst
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt b/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt
deleted file mode 100644
index 32b5436..0000000
--- a/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt
+++ /dev/null
@@ -1,95 +0,0 @@
-..
-..
-.. Licensed under the Apache License, Version 2.0 (the "License");
-.. you may not use this file except in compliance with the License.
-.. You may obtain a copy of the License at
-..
-.. http://www.apache.org/licenses/LICENSE-2.0
-..
-.. Unless required by applicable law or agreed to in writing, software
-.. distributed under the License is distributed on an "AS IS" BASIS,
-.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-.. See the License for the specific language governing permissions and
-.. limitations under the License.
-..
-
-.. _rl-multi-site-origin-qht:
-
-***************************
-Configure Multi Site Origin
-***************************
-
-1) Create "cachegroups" for the origin locations, and assign the appropriate parent-child relationship between the mid cg's and org cgs (click the image to see full size):
-
-.. image:: C5C4CD22-949A-48FD-8976-C673083E2177.png
- :scale: 100%
- :align: center
-
-2) Create a profile to assign to each of the origins:
-
-.. image:: 19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png
- :scale: 100%
- :align: center
-
-3) Create server entries for the origination vips:
-
-.. image:: D28614AA-9758-45ED-9EFD-3A284FC4218E.png
- :scale: 100%
- :align: center
-
-4) Check the multi-site check box in the delivery service screen and make sure that Content Routing Type is set to HTTP_LIVE_NATL:
-
-.. image:: mso-enable.png
- :scale: 100%
- :align: center
-
-5) Assign the org servers to the delivery service that will have the multi site feature:
-
-.. image:: 066CEF4F-C1A3-4A89-8B52-4F72B0531367.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 exceptions 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.
-
-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 server profile. Origin servers with lower values of rank have higher ranking in the origin server list on MID caches, e.g. OS with rank of "2" precedes OS with the rank of "5". For any OS, if rank value is not defined in its profile, its rank value will default to “1”. In the event that both location based cachegroups are used alongside rank, sorting will be by cachegroup first and rank second. In this way it is possible to have specific backup servers for use at specific locations.
-
-.. 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) 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.connect_attempts_max_retries 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries_dead_server 1 __RETURN__ set-config proxy.config.http.transaction_active_timeout_in 5 [L] __RETURN__
-
-10) Turn on parent_proxy_routing in the MID profile.
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/multi_site.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/multi_site.txt b/docs/latest/_sources/admin/quick_howto/multi_site.txt
new file mode 100644
index 0000000..32b5436
--- /dev/null
+++ b/docs/latest/_sources/admin/quick_howto/multi_site.txt
@@ -0,0 +1,95 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+.. _rl-multi-site-origin-qht:
+
+***************************
+Configure Multi Site Origin
+***************************
+
+1) Create "cachegroups" for the origin locations, and assign the appropriate parent-child relationship between the mid cg's and org cgs (click the image to see full size):
+
+.. image:: C5C4CD22-949A-48FD-8976-C673083E2177.png
+ :scale: 100%
+ :align: center
+
+2) Create a profile to assign to each of the origins:
+
+.. image:: 19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png
+ :scale: 100%
+ :align: center
+
+3) Create server entries for the origination vips:
+
+.. image:: D28614AA-9758-45ED-9EFD-3A284FC4218E.png
+ :scale: 100%
+ :align: center
+
+4) Check the multi-site check box in the delivery service screen and make sure that Content Routing Type is set to HTTP_LIVE_NATL:
+
+.. image:: mso-enable.png
+ :scale: 100%
+ :align: center
+
+5) Assign the org servers to the delivery service that will have the multi site feature:
+
+.. image:: 066CEF4F-C1A3-4A89-8B52-4F72B0531367.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 exceptions 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.
+
+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 server profile. Origin servers with lower values of rank have higher ranking in the origin server list on MID caches, e.g. OS with rank of "2" precedes OS with the rank of "5". For any OS, if rank value is not defined in its profile, its rank value will default to “1”. In the event that both location based cachegroups are used alongside rank, sorting will be by cachegroup first and rank second. In this way it is possible to have specific backup servers for use at specific locations.
+
+.. 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) 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.connect_attempts_max_retries 2 __RETURN__ set-config proxy.config.http.connect_attempts_max_retries_dead_server 1 __RETURN__ set-config proxy.config.http.transaction_active_timeout_in 5 [L] __RETURN__
+
+10) Turn on parent_proxy_routing in the MID profile.
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt b/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt
deleted file mode 100644
index a903c8a..0000000
--- a/docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt
+++ /dev/null
@@ -1,109 +0,0 @@
-..
-..
-.. Licensed under the Apache License, Version 2.0 (the "License");
-.. you may not use this file except in compliance with the License.
-.. You may obtain a copy of the License at
-..
-.. http://www.apache.org/licenses/LICENSE-2.0
-..
-.. Unless required by applicable law or agreed to in writing, software
-.. distributed under the License is distributed on an "AS IS" BASIS,
-.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-.. See the License for the specific language governing permissions and
-.. limitations under the License.
-..
-
-.. _rl-regionalgeo-qht:
-
-**************************************
-Configure Regional Geo-blocking (RGB)
-**************************************
-
-.. Note:: RGB is only supported for HTTP delivery services.
-
-1) Prepare RGB configuration file
-
-RGB uses a configuration file in JSON format to define regional geo-blocking rules for delivery services. The file needs to be put on an HTTP server accessible to Traffic Router. An example of the JSON is as follows::
-
- {
- "deliveryServices":
- [
- {
- "deliveryServiceId": "hls-live",
- "urlRegex": ".*live4\\.m3u8",
- "geoLocation": {"includePostalCode":["N0H", "L9V", "L9W"]},
- "redirectUrl": "http://third-party.com/blacked_out.html"
- },
- {
- "deliveryServiceId": "hls-live",
- "urlRegex": ".*live5\\.m3u8",
- "ipWhiteList": [185.68.71.9/22","142.232.0.79/24"],
- "geoLocation": {"excludePostalCode":["N0H", "L9V"]},
- "redirectUrl": "/live5_low_bitrate.m3u8"
- }
- ]
- }
-
-* The value of "deliveryServiceId" shall be equal to the “XML ID” field of the intended delivery service defined on Traffic Ops.
-
-* “urlRegex” is to match request URLs. The URLs matching the regex are applicable to the rule.
-
-* “geoLocation” currently supports “includePostalCode” and “excludePostalCode” attribute. When “includePostalCode” attribute is used, only the clients whose FSAs are in the “includePostalCode” list are able to view the content represented by “urlRegex”. When “excludePostalCode” is used, any client whose FSA are not in the “excludePostalCode” list are allowed to view the content. “includePostalCode” and “excludePostalCode” are mutually exclusive in one rule. (FSA: Forward Sortation Area, first three postal characters of Canadian postal codes)
-
-* “redirectUrl” is the URL that will be responded to the blocked clients. Without a domain name in the URL, the URL will still be served in the same delivery service. Thus Traffic Router will redirect the client to a chosen cache server assigned to the delivery service. If the URL includes a domain name, Traffic Router simply redirects the client to the defined URL. In the later case, the redirect URL must not match the “urlRegex” part to avoid HTTP 302 loop on Traffic Router.
-
-* “ipWhiteList” is an optional element. It includes a list of CIDR (Classless Inter-Domain Routing) blocks indicating the IPv4 subnets that are allowed by the rule. If this list exists and the value is not empty, client IP will be matched against the CIDR list, and if there is any match, the request will be allowed and no postal code matching logic is needed. If there is no match in the white list, postal code matching logic will be processed further.
-
-
-2) Add RGB parameters on Traffic Ops
-
-The two new parameters in following table are required to be added into CRConfig.json:
-
-* "regional_geoblocking.polling.url": the HTTP URL of RGB configuration file. Traffic Router will fetch the file from this URL.
-* "regional_geoblocking.polling.interval": the interval that Traffic Router polls the RGB configuration file.
-
-.. image:: regionalgeo01.png
- :scale: 100%
- :align: center
-
-3) Enable RGB for a delivery service
-
-.. image:: regionalgeo02.png
- :scale: 100%
- :align: center
-
-4) Make configuration effective
-
-Go to Tools->Snapshot CRConfig, perform “Diff CRConfig” and click "Write CRConfig".
-
-.. image:: regionalgeo03.png
- :scale: 70%
- :align: center
-
-5) Traffic Router access log with RGB
-
-RGB extends the field of "rtype" and adds a new field "rgb" in Traffic Router access.log to help to monitor the working of this feature.
-
-For "rtype", RGALT indicates that a request is redirected to an alternate URL by RGB; RGDENY indicates that a request is denied by RGB because there is no matching rule in JSON for this request.
-
-For "rgb", when RGB is enabled, it will be non-empty with following format::
-
- {FSA}:{allowed/disallowed}:{include/exclude postal}:{fallback config/current config}:{allowed by whitelist/otherwise}
-
-
-* {FSA}: It is the client’s FSA part of its postal code, which is retrieved from geo-location database. If FSA is empty, dash (“-“) is filled in.
-* {allowed/disallowed}: This flag shows if a request is allowed or disallowed by RGB (1 for yes, and 0 for no).
-* {include/exclude postal}: It shows that when a rule in JSON is matched for a request, it is an include or exclude list of postal codes (i.e. FSAs). “I” for include, and “X” for exclude. If no rule matches, dash (“-“) is filled in.
-* {fallback config/current config}: when TR fails to parse an RGB JSON, TR will handle requests with latest valid JSON configuration, but will set {fallback config} flag to 1. If the new JSON is valid, then the flag is set to 0.
-* {allowed by whitelist/otherwise}: If a request is allowed by whitelist, this flag is set to 1; for all other cases, it is 0.
-
-
-Example::
-
- 1446442214.685 qtype=HTTP chi=129.100.254.79 url="http://ccr.geo2.cdn.com/live5.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=GEO rloc="-" rdtl=- rerr="-" rgb="N6G:1:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/live5.m3u8 rh="-"
-
- 1446442219.181 qtype=HTTP chi=184.68.71.9 url="http://ccr.geo2.cdn.com/live5.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=RGALT rloc="-" rdtl=- rerr="-" rgb="-:0:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/low_bitrate.m3u8 rh="-"
-
- 1446445521.677 qtype=HTTP chi=24.114.29.79 url="http://ccr.geo2.cdn.com/live51.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=RGDENY rloc="-" rdtl=- rerr="-" rgb="L4S:0:-:0:0" pssc=520 ttms=3 rurl="-" rh="-"
-
-
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/regionalgeo.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/regionalgeo.txt b/docs/latest/_sources/admin/quick_howto/regionalgeo.txt
new file mode 100644
index 0000000..a903c8a
--- /dev/null
+++ b/docs/latest/_sources/admin/quick_howto/regionalgeo.txt
@@ -0,0 +1,109 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+.. _rl-regionalgeo-qht:
+
+**************************************
+Configure Regional Geo-blocking (RGB)
+**************************************
+
+.. Note:: RGB is only supported for HTTP delivery services.
+
+1) Prepare RGB configuration file
+
+RGB uses a configuration file in JSON format to define regional geo-blocking rules for delivery services. The file needs to be put on an HTTP server accessible to Traffic Router. An example of the JSON is as follows::
+
+ {
+ "deliveryServices":
+ [
+ {
+ "deliveryServiceId": "hls-live",
+ "urlRegex": ".*live4\\.m3u8",
+ "geoLocation": {"includePostalCode":["N0H", "L9V", "L9W"]},
+ "redirectUrl": "http://third-party.com/blacked_out.html"
+ },
+ {
+ "deliveryServiceId": "hls-live",
+ "urlRegex": ".*live5\\.m3u8",
+ "ipWhiteList": [185.68.71.9/22","142.232.0.79/24"],
+ "geoLocation": {"excludePostalCode":["N0H", "L9V"]},
+ "redirectUrl": "/live5_low_bitrate.m3u8"
+ }
+ ]
+ }
+
+* The value of "deliveryServiceId" shall be equal to the “XML ID” field of the intended delivery service defined on Traffic Ops.
+
+* “urlRegex” is to match request URLs. The URLs matching the regex are applicable to the rule.
+
+* “geoLocation” currently supports “includePostalCode” and “excludePostalCode” attribute. When “includePostalCode” attribute is used, only the clients whose FSAs are in the “includePostalCode” list are able to view the content represented by “urlRegex”. When “excludePostalCode” is used, any client whose FSA are not in the “excludePostalCode” list are allowed to view the content. “includePostalCode” and “excludePostalCode” are mutually exclusive in one rule. (FSA: Forward Sortation Area, first three postal characters of Canadian postal codes)
+
+* “redirectUrl” is the URL that will be responded to the blocked clients. Without a domain name in the URL, the URL will still be served in the same delivery service. Thus Traffic Router will redirect the client to a chosen cache server assigned to the delivery service. If the URL includes a domain name, Traffic Router simply redirects the client to the defined URL. In the later case, the redirect URL must not match the “urlRegex” part to avoid HTTP 302 loop on Traffic Router.
+
+* “ipWhiteList” is an optional element. It includes a list of CIDR (Classless Inter-Domain Routing) blocks indicating the IPv4 subnets that are allowed by the rule. If this list exists and the value is not empty, client IP will be matched against the CIDR list, and if there is any match, the request will be allowed and no postal code matching logic is needed. If there is no match in the white list, postal code matching logic will be processed further.
+
+
+2) Add RGB parameters on Traffic Ops
+
+The two new parameters in following table are required to be added into CRConfig.json:
+
+* "regional_geoblocking.polling.url": the HTTP URL of RGB configuration file. Traffic Router will fetch the file from this URL.
+* "regional_geoblocking.polling.interval": the interval that Traffic Router polls the RGB configuration file.
+
+.. image:: regionalgeo01.png
+ :scale: 100%
+ :align: center
+
+3) Enable RGB for a delivery service
+
+.. image:: regionalgeo02.png
+ :scale: 100%
+ :align: center
+
+4) Make configuration effective
+
+Go to Tools->Snapshot CRConfig, perform “Diff CRConfig” and click "Write CRConfig".
+
+.. image:: regionalgeo03.png
+ :scale: 70%
+ :align: center
+
+5) Traffic Router access log with RGB
+
+RGB extends the field of "rtype" and adds a new field "rgb" in Traffic Router access.log to help to monitor the working of this feature.
+
+For "rtype", RGALT indicates that a request is redirected to an alternate URL by RGB; RGDENY indicates that a request is denied by RGB because there is no matching rule in JSON for this request.
+
+For "rgb", when RGB is enabled, it will be non-empty with following format::
+
+ {FSA}:{allowed/disallowed}:{include/exclude postal}:{fallback config/current config}:{allowed by whitelist/otherwise}
+
+
+* {FSA}: It is the client’s FSA part of its postal code, which is retrieved from geo-location database. If FSA is empty, dash (“-“) is filled in.
+* {allowed/disallowed}: This flag shows if a request is allowed or disallowed by RGB (1 for yes, and 0 for no).
+* {include/exclude postal}: It shows that when a rule in JSON is matched for a request, it is an include or exclude list of postal codes (i.e. FSAs). “I” for include, and “X” for exclude. If no rule matches, dash (“-“) is filled in.
+* {fallback config/current config}: when TR fails to parse an RGB JSON, TR will handle requests with latest valid JSON configuration, but will set {fallback config} flag to 1. If the new JSON is valid, then the flag is set to 0.
+* {allowed by whitelist/otherwise}: If a request is allowed by whitelist, this flag is set to 1; for all other cases, it is 0.
+
+
+Example::
+
+ 1446442214.685 qtype=HTTP chi=129.100.254.79 url="http://ccr.geo2.cdn.com/live5.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=GEO rloc="-" rdtl=- rerr="-" rgb="N6G:1:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/live5.m3u8 rh="-"
+
+ 1446442219.181 qtype=HTTP chi=184.68.71.9 url="http://ccr.geo2.cdn.com/live5.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=RGALT rloc="-" rdtl=- rerr="-" rgb="-:0:X:0:0" pssc=302 ttms=3 rurl=http://cent6-44.geo2.cdn.com/low_bitrate.m3u8 rh="-"
+
+ 1446445521.677 qtype=HTTP chi=24.114.29.79 url="http://ccr.geo2.cdn.com/live51.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=RGDENY rloc="-" rdtl=- rerr="-" rgb="L4S:0:-:0:0" pssc=520 ttms=3 rurl="-" rh="-"
+
+
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/steering.rst.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/steering.rst.txt b/docs/latest/_sources/admin/quick_howto/steering.rst.txt
deleted file mode 100644
index 1060f29..0000000
--- a/docs/latest/_sources/admin/quick_howto/steering.rst.txt
+++ /dev/null
@@ -1,95 +0,0 @@
-..
-..
-.. Licensed under the Apache License, Version 2.0 (the "License");
-.. you may not use this file except in compliance with the License.
-.. You may obtain a copy of the License at
-..
-.. http://www.apache.org/licenses/LICENSE-2.0
-..
-.. Unless required by applicable law or agreed to in writing, software
-.. distributed under the License is distributed on an "AS IS" BASIS,
-.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-.. See the License for the specific language governing permissions and
-.. limitations under the License.
-..
-
-.. _rl-steering-qht:
-
-***********************************
-Configure Delivery Service Steering
-***********************************
-
-1) Create two target delivery services in Traffic Ops. They must both be HTTP delivery services that are part of the same CDN.
-
-.. image:: steering01.png
- :scale: 100%
- :align: center
-
-2) Create a delivery service with type STEERING in Traffic Ops.
-
-.. image:: steering02.png
- :scale: 100%
- :align: center
-
-3) Click the 'Manage Steering Assignments' button on the delivery service screen to assign targets.
-
-.. image:: steering03.png
- :scale: 100%
- :align: center
-
-4) Create a user with the role of Steering.
-
-.. image:: steering04.png
- :scale: 100%
- :align: center
-
-5) As the steering user, assign weights to target delivery services. This will require logging in to Traffic Ops first via ``http://to.kabletown.net/api/1.2/user/login`` and storing the mojolicious cookie.
-
- Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds" -d @/tmp/steering.json``
-
- Sample JSON body:
-
-::
-
- {
- "targets": [
- {
- "weight": "1000",
- "deliveryService": "target-deliveryservice-1"
- },
- {
- "weight": "9000",
- "deliveryService": "target-deliveryservice-2"
- }
- ]
- }
-
-6) If desired, the steering user can create filters for the target delivery services.
-
- Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds" -d @/tmp/steering.json``
-
- Sample JSON body:
-
-::
-
- {
- "filters": [
- {
- "pattern": ".*\\gototarget1\\..*",
- "deliveryService": "target-deliveryservice-1"
- }
- ],
- "targets": [
- {
- "weight": "1000",
- "deliveryService": "target-deliveryservice-1"
- },
- {
- "weight": "9000",
- "deliveryService": "target-deliveryservice-2"
- }
- ]
- }
-
-7) Any requests to Traffic Router for the steering delivery service should now be routed to target delivery services based on configured weight. Example: ``curl -Lvs http://tr.steering-ds.cdn.kabletown.net/foo``
-
http://git-wip-us.apache.org/repos/asf/incubator-trafficcontrol-website/blob/0ba7314b/docs/latest/_sources/admin/quick_howto/steering.txt
----------------------------------------------------------------------
diff --git a/docs/latest/_sources/admin/quick_howto/steering.txt b/docs/latest/_sources/admin/quick_howto/steering.txt
new file mode 100644
index 0000000..1060f29
--- /dev/null
+++ b/docs/latest/_sources/admin/quick_howto/steering.txt
@@ -0,0 +1,95 @@
+..
+..
+.. Licensed under the Apache License, Version 2.0 (the "License");
+.. you may not use this file except in compliance with the License.
+.. You may obtain a copy of the License at
+..
+.. http://www.apache.org/licenses/LICENSE-2.0
+..
+.. Unless required by applicable law or agreed to in writing, software
+.. distributed under the License is distributed on an "AS IS" BASIS,
+.. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+.. See the License for the specific language governing permissions and
+.. limitations under the License.
+..
+
+.. _rl-steering-qht:
+
+***********************************
+Configure Delivery Service Steering
+***********************************
+
+1) Create two target delivery services in Traffic Ops. They must both be HTTP delivery services that are part of the same CDN.
+
+.. image:: steering01.png
+ :scale: 100%
+ :align: center
+
+2) Create a delivery service with type STEERING in Traffic Ops.
+
+.. image:: steering02.png
+ :scale: 100%
+ :align: center
+
+3) Click the 'Manage Steering Assignments' button on the delivery service screen to assign targets.
+
+.. image:: steering03.png
+ :scale: 100%
+ :align: center
+
+4) Create a user with the role of Steering.
+
+.. image:: steering04.png
+ :scale: 100%
+ :align: center
+
+5) As the steering user, assign weights to target delivery services. This will require logging in to Traffic Ops first via ``http://to.kabletown.net/api/1.2/user/login`` and storing the mojolicious cookie.
+
+ Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds" -d @/tmp/steering.json``
+
+ Sample JSON body:
+
+::
+
+ {
+ "targets": [
+ {
+ "weight": "1000",
+ "deliveryService": "target-deliveryservice-1"
+ },
+ {
+ "weight": "9000",
+ "deliveryService": "target-deliveryservice-2"
+ }
+ ]
+ }
+
+6) If desired, the steering user can create filters for the target delivery services.
+
+ Sample cURL: ``curl -H "Cookie: mojolicious=xxxyyy" -XPUT "https://to.kabletown.net/internal/api/1.2/steering/steering-ds" -d @/tmp/steering.json``
+
+ Sample JSON body:
+
+::
+
+ {
+ "filters": [
+ {
+ "pattern": ".*\\gototarget1\\..*",
+ "deliveryService": "target-deliveryservice-1"
+ }
+ ],
+ "targets": [
+ {
+ "weight": "1000",
+ "deliveryService": "target-deliveryservice-1"
+ },
+ {
+ "weight": "9000",
+ "deliveryService": "target-deliveryservice-2"
+ }
+ ]
+ }
+
+7) Any requests to Traffic Router for the steering delivery service should now be routed to target delivery services based on configured weight. Example: ``curl -Lvs http://tr.steering-ds.cdn.kabletown.net/foo``
+