You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by zr...@apache.org on 2020/09/28 20:22:31 UTC
[trafficcontrol-website] branch asf-site updated (c9c5aee ->
0563cad)
This is an automated email from the ASF dual-hosted git repository.
zrhoffman pushed a change to branch asf-site
in repository https://gitbox.apache.org/repos/asf/trafficcontrol-website.git.
from c9c5aee Remove "incubator" from repo name
new 8fbe0ff Do not track docs since we have the redirect to readthedocs.io already
new ba4ac97 HTTPS URLs
new 248b6be Reformat pages
new 0563cad ApacheCon @Home news item
The 4 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.htaccess | 6 +-
.../066CEF4F-C1A3-4A89-8B52-4F72B0531367.png | Bin 63381 -> 0 bytes
docs/latest/_images/12m.png | Bin 22728 -> 0 bytes
.../19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png | Bin 62806 -> 0 bytes
.../C5C4CD22-949A-48FD-8976-C673083E2177.png | Bin 55410 -> 0 bytes
.../D28614AA-9758-45ED-9EFD-3A284FC4218E.png | Bin 45381 -> 0 bytes
docs/latest/_images/anonymous_blocking01.png | Bin 109855 -> 0 bytes
docs/latest/_images/anonymous_blocking02.png | Bin 28800 -> 0 bytes
docs/latest/_images/bad.png | Bin 472 -> 0 bytes
docs/latest/_images/bad1.png | Bin 472 -> 0 bytes
docs/latest/_images/cache_groups_1.png | Bin 80623 -> 0 bytes
docs/latest/_images/clock-black.png | Bin 427 -> 0 bytes
docs/latest/_images/dnssec01.png | Bin 32216 -> 0 bytes
docs/latest/_images/dnssec02.png | Bin 61047 -> 0 bytes
docs/latest/_images/dnssec03.png | Bin 145394 -> 0 bytes
docs/latest/_images/dnssec04.png | Bin 195587 -> 0 bytes
docs/latest/_images/ds-profile.png | Bin 107817 -> 0 bytes
docs/latest/_images/ds_profile_parameters.png | Bin 99479 -> 0 bytes
docs/latest/_images/federation01.png | Bin 96843 -> 0 bytes
docs/latest/_images/federation02.png | Bin 101666 -> 0 bytes
docs/latest/_images/federation03.png | Bin 316490 -> 0 bytes
docs/latest/_images/federation04.png | Bin 269316 -> 0 bytes
docs/latest/_images/fwda.png | Bin 206 -> 0 bytes
docs/latest/_images/fwda1.png | Bin 206 -> 0 bytes
docs/latest/_images/good.png | Bin 617 -> 0 bytes
docs/latest/_images/good1.png | Bin 617 -> 0 bytes
docs/latest/_images/graph.png | Bin 483 -> 0 bytes
docs/latest/_images/info.png | Bin 3379 -> 0 bytes
docs/latest/_images/mso-enable.png | Bin 124819 -> 0 bytes
docs/latest/_images/regionalgeo01.png | Bin 75096 -> 0 bytes
docs/latest/_images/regionalgeo02.png | Bin 93191 -> 0 bytes
docs/latest/_images/regionalgeo03.png | Bin 42367 -> 0 bytes
docs/latest/_images/steering01.png | Bin 51223 -> 0 bytes
docs/latest/_images/steering02.png | Bin 116876 -> 0 bytes
docs/latest/_images/steering03.png | Bin 210908 -> 0 bytes
docs/latest/_images/steering04.png | Bin 35255 -> 0 bytes
docs/latest/_images/tp_menu.png | Bin 100018 -> 0 bytes
docs/latest/_images/tp_menu_configure.png | Bin 65142 -> 0 bytes
docs/latest/_images/tp_menu_monitor.png | Bin 57825 -> 0 bytes
docs/latest/_images/tp_menu_other.png | Bin 61114 -> 0 bytes
docs/latest/_images/tp_menu_services.png | Bin 61219 -> 0 bytes
docs/latest/_images/tp_menu_tools.png | Bin 58820 -> 0 bytes
docs/latest/_images/tp_menu_topology.png | Bin 66984 -> 0 bytes
docs/latest/_images/tp_menu_user_admin.png | Bin 59728 -> 0 bytes
docs/latest/_images/tp_table_ds_requests.png | Bin 120150 -> 0 bytes
docs/latest/_images/tp_table_ds_requests1.png | Bin 120150 -> 0 bytes
docs/latest/_images/traffic_control_overview_3.png | Bin 138671 -> 0 bytes
docs/latest/_sources/admin/index.rst.txt | 52 -
.../admin/quick_howto/anonymous_blocking.rst.txt | 87 -
.../_sources/admin/quick_howto/dnssec.rst.txt | 72 -
.../_sources/admin/quick_howto/ds_requests.rst.txt | 81 -
.../_sources/admin/quick_howto/federations.rst.txt | 135 -
.../_sources/admin/quick_howto/index.rst.txt | 43 -
.../_sources/admin/quick_howto/multi_site.rst.txt | 105 -
.../_sources/admin/quick_howto/regionalgeo.rst.txt | 109 -
.../_sources/admin/quick_howto/steering.rst.txt | 111 -
docs/latest/_sources/admin/traffic_monitor.rst.txt | 177 -
.../_sources/admin/traffic_monitor_golang.rst.txt | 65 -
.../admin/traffic_ops/configuration.rst.txt | 322 -
.../admin/traffic_ops/default_profiles.rst.txt | 53 -
.../_sources/admin/traffic_ops/extensions.rst.txt | 88 -
.../admin/traffic_ops/installation.rst.txt | 243 -
.../traffic_ops/migration_from_10_to_20.rst.txt | 88 -
.../traffic_ops/migration_from_20_to_22.rst.txt | 122 -
.../_sources/admin/traffic_ops/using.rst.txt | 1224 ---
.../admin/traffic_portal/installation.rst.txt | 51 -
.../traffic_portal/usingtrafficportal.rst.txt | 800 --
docs/latest/_sources/admin/traffic_router.rst.txt | 588 --
docs/latest/_sources/admin/traffic_server.rst.txt | 149 -
docs/latest/_sources/admin/traffic_stats.rst.txt | 188 -
docs/latest/_sources/admin/traffic_vault.rst.txt | 188 -
docs/latest/_sources/api/index.rst.txt | 28 -
docs/latest/_sources/api/routes.rst.txt | 118 -
docs/latest/_sources/api/traffic_ops_api.rst.txt | 196 -
docs/latest/_sources/api/v11/asn.rst.txt | 69 -
docs/latest/_sources/api/v11/cachegroup.rst.txt | 317 -
docs/latest/_sources/api/v11/cdn.rst.txt | 1088 --
docs/latest/_sources/api/v11/changelog.rst.txt | 154 -
.../_sources/api/v11/deliveryservice.rst.txt | 1286 ---
docs/latest/_sources/api/v11/hwinfo.rst.txt | 67 -
docs/latest/_sources/api/v11/index.rst.txt | 40 -
docs/latest/_sources/api/v11/parameter.rst.txt | 136 -
docs/latest/_sources/api/v11/phys_location.rst.txt | 449 -
docs/latest/_sources/api/v11/profile.rst.txt | 129 -
docs/latest/_sources/api/v11/region.rst.txt | 235 -
docs/latest/_sources/api/v11/role.rst.txt | 58 -
docs/latest/_sources/api/v11/server.rst.txt | 630 --
docs/latest/_sources/api/v11/static_dns.rst.txt | 63 -
docs/latest/_sources/api/v11/status.rst.txt | 127 -
docs/latest/_sources/api/v11/system.rst.txt | 79 -
docs/latest/_sources/api/v11/to_extension.rst.txt | 210 -
docs/latest/_sources/api/v11/type.rst.txt | 151 -
docs/latest/_sources/api/v11/user.rst.txt | 778 --
.../latest/_sources/api/v12/api_capability.rst.txt | 320 -
docs/latest/_sources/api/v12/asn.rst.txt | 200 -
docs/latest/_sources/api/v12/cache.rst.txt | 84 -
docs/latest/_sources/api/v12/cache_stats.rst.txt | 134 -
docs/latest/_sources/api/v12/cachegroup.rst.txt | 821 --
.../_sources/api/v12/cachegroup_fallbacks.rst.txt | 288 -
.../_sources/api/v12/cachegroup_parameter.rst.txt | 177 -
docs/latest/_sources/api/v12/capability.rst.txt | 271 -
docs/latest/_sources/api/v12/cdn.rst.txt | 1410 ---
docs/latest/_sources/api/v12/changelog.rst.txt | 164 -
.../_sources/api/v12/configfiles_ats.rst.txt | 193 -
.../_sources/api/v12/deliveryservice.rst.txt | 3486 -------
.../_sources/api/v12/deliveryservice_regex.rst.txt | 374 -
.../_sources/api/v12/deliveryservice_stats.rst.txt | 155 -
docs/latest/_sources/api/v12/division.rst.txt | 203 -
docs/latest/_sources/api/v12/federation.rst.txt | 434 -
.../api/v12/federation_deliveryservice.rst.txt | 155 -
.../api/v12/federation_federationresolver.rst.txt | 118 -
.../_sources/api/v12/federation_resolver.rst.txt | 110 -
.../_sources/api/v12/federation_user.rst.txt | 161 -
docs/latest/_sources/api/v12/hwinfo.rst.txt | 68 -
docs/latest/_sources/api/v12/index.rst.txt | 63 -
docs/latest/_sources/api/v12/influxdb.rst.txt | 65 -
docs/latest/_sources/api/v12/iso.rst.txt | 132 -
docs/latest/_sources/api/v12/job.rst.txt | 136 -
docs/latest/_sources/api/v12/parameter.rst.txt | 691 --
docs/latest/_sources/api/v12/phys_location.rst.txt | 456 -
docs/latest/_sources/api/v12/profile.rst.txt | 415 -
.../_sources/api/v12/profile_parameter.rst.txt | 573 --
docs/latest/_sources/api/v12/region.rst.txt | 244 -
docs/latest/_sources/api/v12/role.rst.txt | 59 -
docs/latest/_sources/api/v12/server.rst.txt | 1496 ---
docs/latest/_sources/api/v12/static_dns.rst.txt | 66 -
docs/latest/_sources/api/v12/status.rst.txt | 127 -
.../_sources/api/v12/steering_target.rst.txt | 333 -
docs/latest/_sources/api/v12/system.rst.txt | 80 -
docs/latest/_sources/api/v12/tenant.rst.txt | 255 -
docs/latest/_sources/api/v12/to_extension.rst.txt | 206 -
docs/latest/_sources/api/v12/topology.rst.txt | 152 -
docs/latest/_sources/api/v12/type.rst.txt | 151 -
docs/latest/_sources/api/v12/user.rst.txt | 1258 ---
docs/latest/_sources/api/v13/coordinate.rst.txt | 272 -
docs/latest/_sources/api/v13/index.rst.txt | 25 -
docs/latest/_sources/api/v13/origin.rst.txt | 474 -
.../_sources/basics/cache_revalidation.rst.txt | 71 -
.../latest/_sources/basics/caching_proxies.rst.txt | 238 -
.../basics/content_delivery_networks.rst.txt | 40 -
docs/latest/_sources/basics/http_11.rst.txt | 48 -
docs/latest/_sources/basics/index.rst.txt | 29 -
docs/latest/_sources/development/building.rst.txt | 94 -
docs/latest/_sources/development/index.rst.txt | 29 -
.../_sources/development/traffic_monitor.rst.txt | 301 -
.../traffic_monitor/traffic_monitor_api.rst.txt | 178 -
.../_sources/development/traffic_ops.rst.txt | 369 -
.../_sources/development/traffic_portal.rst.txt | 51 -
.../_sources/development/traffic_router.rst.txt | 145 -
.../traffic_router/traffic_router_api.rst.txt | 91 -
.../_sources/development/traffic_stats.rst.txt | 58 -
docs/latest/_sources/faq/administration.rst.txt | 95 -
docs/latest/_sources/faq/development.rst.txt | 21 -
docs/latest/_sources/faq/general.rst.txt | 55 -
docs/latest/_sources/faq/index.rst.txt | 26 -
docs/latest/_sources/glossary.rst.txt | 81 -
docs/latest/_sources/index.rst.txt | 88 -
docs/latest/_sources/overview/index.rst.txt | 29 -
docs/latest/_sources/overview/introduction.rst.txt | 49 -
.../_sources/overview/traffic_monitor.rst.txt | 66 -
docs/latest/_sources/overview/traffic_ops.rst.txt | 41 -
.../_sources/overview/traffic_portal.rst.txt | 33 -
.../_sources/overview/traffic_router.rst.txt | 109 -
.../latest/_sources/overview/traffic_stats.rst.txt | 35 -
.../latest/_sources/overview/traffic_vault.rst.txt | 36 -
docs/latest/_static/ajax-loader.gif | Bin 673 -> 0 bytes
docs/latest/_static/basic.css | 665 --
docs/latest/_static/comment-bright.png | Bin 756 -> 0 bytes
docs/latest/_static/comment-close.png | Bin 829 -> 0 bytes
docs/latest/_static/comment.png | Bin 641 -> 0 bytes
docs/latest/_static/css/badge_only.css | 2 -
docs/latest/_static/css/badge_only.css.map | 7 -
docs/latest/_static/css/theme.css | 5 -
docs/latest/_static/css/theme.css.map | 7 -
docs/latest/_static/doctools.js | 313 -
docs/latest/_static/documentation_options.js | 9 -
docs/latest/_static/down-pressed.png | Bin 222 -> 0 bytes
docs/latest/_static/down.png | Bin 202 -> 0 bytes
docs/latest/_static/favicon.ico | Bin 1150 -> 0 bytes
docs/latest/_static/file.png | Bin 286 -> 0 bytes
docs/latest/_static/fonts/FontAwesome.otf | Bin 62856 -> 0 bytes
docs/latest/_static/fonts/Inconsolata-Bold.ttf | Bin 47064 -> 0 bytes
docs/latest/_static/fonts/Inconsolata.ttf | Bin 63184 -> 0 bytes
docs/latest/_static/fonts/Lato-Bold.ttf | Bin 82368 -> 0 bytes
docs/latest/_static/fonts/Lato-Regular.ttf | Bin 81980 -> 0 bytes
docs/latest/_static/fonts/RobotoSlab-Bold.ttf | Bin 36596 -> 0 bytes
docs/latest/_static/fonts/RobotoSlab-Regular.ttf | Bin 36276 -> 0 bytes
docs/latest/_static/fonts/fontawesome-webfont.eot | Bin 38205 -> 0 bytes
docs/latest/_static/fonts/fontawesome-webfont.ttf | Bin 80652 -> 0 bytes
docs/latest/_static/fonts/fontawesome-webfont.woff | Bin 44432 -> 0 bytes
docs/latest/_static/jquery-3.2.1.js | 10253 -------------------
docs/latest/_static/jquery.js | 4 -
docs/latest/_static/js/modernizr.min.js | 4 -
docs/latest/_static/js/theme.js | 50 -
docs/latest/_static/minus.png | Bin 90 -> 0 bytes
docs/latest/_static/plus.png | Bin 90 -> 0 bytes
docs/latest/_static/pygments.css | 69 -
docs/latest/_static/searchtools.js | 761 --
docs/latest/_static/tc_logo_c_only.png | Bin 106800 -> 0 bytes
docs/latest/_static/theme_overrides.css | 69 -
docs/latest/_static/underscore-1.3.1.js | 999 --
docs/latest/_static/underscore.js | 31 -
docs/latest/_static/up-pressed.png | Bin 214 -> 0 bytes
docs/latest/_static/up.png | Bin 203 -> 0 bytes
docs/latest/_static/websupport.js | 808 --
docs/latest/admin/index.html | 563 -
.../admin/quick_howto/anonymous_blocking.html | 355 -
docs/latest/admin/quick_howto/dnssec.html | 348 -
docs/latest/admin/quick_howto/ds_requests.html | 343 -
docs/latest/admin/quick_howto/federations.html | 411 -
docs/latest/admin/quick_howto/index.html | 330 -
docs/latest/admin/quick_howto/multi_site.html | 403 -
docs/latest/admin/quick_howto/regionalgeo.html | 375 -
docs/latest/admin/quick_howto/steering.html | 383 -
docs/latest/admin/traffic_monitor.html | 458 -
docs/latest/admin/traffic_monitor_golang.html | 342 -
docs/latest/admin/traffic_ops/configuration.html | 722 --
.../latest/admin/traffic_ops/default_profiles.html | 322 -
docs/latest/admin/traffic_ops/extensions.html | 357 -
docs/latest/admin/traffic_ops/installation.html | 531 -
.../admin/traffic_ops/migration_from_10_to_20.html | 352 -
.../admin/traffic_ops/migration_from_20_to_22.html | 434 -
docs/latest/admin/traffic_ops/using.html | 1900 ----
docs/latest/admin/traffic_portal/installation.html | 331 -
.../admin/traffic_portal/usingtrafficportal.html | 1363 ---
docs/latest/admin/traffic_router.html | 1055 --
docs/latest/admin/traffic_server.html | 446 -
docs/latest/admin/traffic_stats.html | 528 -
docs/latest/admin/traffic_vault.html | 541 -
docs/latest/api/index.html | 375 -
docs/latest/api/routes.html | 467 -
docs/latest/api/traffic_ops_api.html | 495 -
docs/latest/api/v11/asn.html | 363 -
docs/latest/api/v11/cachegroup.html | 740 --
docs/latest/api/v11/cdn.html | 2049 ----
docs/latest/api/v11/changelog.html | 496 -
docs/latest/api/v11/deliveryservice.html | 2370 -----
docs/latest/api/v11/hwinfo.html | 361 -
docs/latest/api/v11/index.html | 319 -
docs/latest/api/v11/parameter.html | 462 -
docs/latest/api/v11/phys_location.html | 988 --
docs/latest/api/v11/profile.html | 471 -
docs/latest/api/v11/region.html | 649 --
docs/latest/api/v11/role.html | 351 -
docs/latest/api/v11/server.html | 1247 ---
docs/latest/api/v11/static_dns.html | 361 -
docs/latest/api/v11/status.html | 447 -
docs/latest/api/v11/system.html | 379 -
docs/latest/api/v11/to_extension.html | 582 --
docs/latest/api/v11/type.html | 501 -
docs/latest/api/v11/user.html | 1499 ---
docs/latest/api/v12/api_capability.html | 798 --
docs/latest/api/v12/asn.html | 586 --
docs/latest/api/v12/cache.html | 385 -
docs/latest/api/v12/cache_stats.html | 467 -
docs/latest/api/v12/cachegroup.html | 1581 ---
docs/latest/api/v12/cachegroup_fallbacks.html | 710 --
docs/latest/api/v12/cachegroup_parameter.html | 517 -
docs/latest/api/v12/capability.html | 701 --
docs/latest/api/v12/cdn.html | 2566 -----
docs/latest/api/v12/changelog.html | 520 -
docs/latest/api/v12/configfiles_ats.html | 488 -
docs/latest/api/v12/deliveryservice.html | 5990 -----------
docs/latest/api/v12/deliveryservice_regex.html | 859 --
docs/latest/api/v12/deliveryservice_stats.html | 494 -
docs/latest/api/v12/division.html | 585 --
docs/latest/api/v12/federation.html | 931 --
.../latest/api/v12/federation_deliveryservice.html | 500 -
.../api/v12/federation_federationresolver.html | 449 -
docs/latest/api/v12/federation_resolver.html | 432 -
docs/latest/api/v12/federation_user.html | 510 -
docs/latest/api/v12/hwinfo.html | 364 -
docs/latest/api/v12/index.html | 341 -
docs/latest/api/v12/influxdb.html | 353 -
docs/latest/api/v12/iso.html | 468 -
docs/latest/api/v12/job.html | 472 -
docs/latest/api/v12/parameter.html | 1382 ---
docs/latest/api/v12/phys_location.html | 1008 --
docs/latest/api/v12/profile.html | 981 --
docs/latest/api/v12/profile_parameter.html | 1105 --
docs/latest/api/v12/region.html | 672 --
docs/latest/api/v12/role.html | 354 -
docs/latest/api/v12/server.html | 2702 -----
docs/latest/api/v12/static_dns.html | 364 -
docs/latest/api/v12/status.html | 447 -
docs/latest/api/v12/steering_target.html | 800 --
docs/latest/api/v12/system.html | 382 -
docs/latest/api/v12/tenant.html | 655 --
docs/latest/api/v12/to_extension.html | 582 --
docs/latest/api/v12/topology.html | 519 -
docs/latest/api/v12/type.html | 501 -
docs/latest/api/v12/user.html | 2302 -----
docs/latest/api/v13/coordinate.html | 705 --
docs/latest/api/v13/index.html | 303 -
docs/latest/api/v13/origin.html | 1034 --
docs/latest/basics/cache_revalidation.html | 343 -
docs/latest/basics/caching_proxies.html | 517 -
docs/latest/basics/content_delivery_networks.html | 324 -
docs/latest/basics/http_11.html | 328 -
docs/latest/basics/index.html | 307 -
docs/latest/development/building.html | 362 -
docs/latest/development/index.html | 354 -
docs/latest/development/traffic_monitor.html | 549 -
.../traffic_monitor/traffic_monitor_api.html | 545 -
docs/latest/development/traffic_ops.html | 654 --
docs/latest/development/traffic_portal.html | 341 -
docs/latest/development/traffic_router.html | 488 -
.../traffic_router/traffic_router_api.html | 355 -
docs/latest/development/traffic_stats.html | 345 -
docs/latest/faq/administration.html | 395 -
docs/latest/faq/development.html | 301 -
docs/latest/faq/general.html | 342 -
docs/latest/faq/index.html | 316 -
docs/latest/genindex.html | 549 -
docs/latest/glossary.html | 328 -
docs/latest/index.html | 653 --
docs/latest/objects.inv | Bin 5040 -> 0 bytes
docs/latest/overview/index.html | 318 -
docs/latest/overview/introduction.html | 333 -
docs/latest/overview/traffic_monitor.html | 330 -
docs/latest/overview/traffic_ops.html | 315 -
docs/latest/overview/traffic_portal.html | 307 -
docs/latest/overview/traffic_router.html | 373 -
docs/latest/overview/traffic_stats.html | 307 -
docs/latest/overview/traffic_vault.html | 336 -
docs/latest/search.html | 288 -
docs/latest/searchindex.js | 1 -
index.html | 495 +-
mailing_lists/index.html | 317 +-
releases/index.html | 776 +-
security/index.html | 267 +-
331 files changed, 1066 insertions(+), 125595 deletions(-)
delete mode 100644 docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png
delete mode 100644 docs/latest/_images/12m.png
delete mode 100644 docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png
delete mode 100644 docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png
delete mode 100644 docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png
delete mode 100644 docs/latest/_images/anonymous_blocking01.png
delete mode 100644 docs/latest/_images/anonymous_blocking02.png
delete mode 100644 docs/latest/_images/bad.png
delete mode 100644 docs/latest/_images/bad1.png
delete mode 100644 docs/latest/_images/cache_groups_1.png
delete mode 100644 docs/latest/_images/clock-black.png
delete mode 100644 docs/latest/_images/dnssec01.png
delete mode 100644 docs/latest/_images/dnssec02.png
delete mode 100644 docs/latest/_images/dnssec03.png
delete mode 100644 docs/latest/_images/dnssec04.png
delete mode 100644 docs/latest/_images/ds-profile.png
delete mode 100644 docs/latest/_images/ds_profile_parameters.png
delete mode 100644 docs/latest/_images/federation01.png
delete mode 100644 docs/latest/_images/federation02.png
delete mode 100644 docs/latest/_images/federation03.png
delete mode 100644 docs/latest/_images/federation04.png
delete mode 100644 docs/latest/_images/fwda.png
delete mode 100644 docs/latest/_images/fwda1.png
delete mode 100644 docs/latest/_images/good.png
delete mode 100644 docs/latest/_images/good1.png
delete mode 100644 docs/latest/_images/graph.png
delete mode 100644 docs/latest/_images/info.png
delete mode 100644 docs/latest/_images/mso-enable.png
delete mode 100644 docs/latest/_images/regionalgeo01.png
delete mode 100644 docs/latest/_images/regionalgeo02.png
delete mode 100644 docs/latest/_images/regionalgeo03.png
delete mode 100644 docs/latest/_images/steering01.png
delete mode 100644 docs/latest/_images/steering02.png
delete mode 100644 docs/latest/_images/steering03.png
delete mode 100644 docs/latest/_images/steering04.png
delete mode 100644 docs/latest/_images/tp_menu.png
delete mode 100644 docs/latest/_images/tp_menu_configure.png
delete mode 100644 docs/latest/_images/tp_menu_monitor.png
delete mode 100644 docs/latest/_images/tp_menu_other.png
delete mode 100644 docs/latest/_images/tp_menu_services.png
delete mode 100644 docs/latest/_images/tp_menu_tools.png
delete mode 100644 docs/latest/_images/tp_menu_topology.png
delete mode 100644 docs/latest/_images/tp_menu_user_admin.png
delete mode 100644 docs/latest/_images/tp_table_ds_requests.png
delete mode 100644 docs/latest/_images/tp_table_ds_requests1.png
delete mode 100644 docs/latest/_images/traffic_control_overview_3.png
delete mode 100644 docs/latest/_sources/admin/index.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/anonymous_blocking.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/dnssec.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/ds_requests.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/federations.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/index.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/multi_site.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/regionalgeo.rst.txt
delete mode 100644 docs/latest/_sources/admin/quick_howto/steering.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_monitor.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_monitor_golang.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_ops/configuration.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_ops/default_profiles.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_ops/extensions.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_ops/installation.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_ops/migration_from_10_to_20.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_ops/migration_from_20_to_22.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_ops/using.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_portal/installation.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_portal/usingtrafficportal.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_router.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_server.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_stats.rst.txt
delete mode 100644 docs/latest/_sources/admin/traffic_vault.rst.txt
delete mode 100644 docs/latest/_sources/api/index.rst.txt
delete mode 100644 docs/latest/_sources/api/routes.rst.txt
delete mode 100644 docs/latest/_sources/api/traffic_ops_api.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/asn.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/cachegroup.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/cdn.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/changelog.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/deliveryservice.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/hwinfo.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/index.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/parameter.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/phys_location.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/profile.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/region.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/role.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/server.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/static_dns.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/status.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/system.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/to_extension.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/type.rst.txt
delete mode 100644 docs/latest/_sources/api/v11/user.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/api_capability.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/asn.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/cache.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/cache_stats.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/cachegroup.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/cachegroup_fallbacks.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/cachegroup_parameter.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/capability.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/cdn.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/changelog.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/configfiles_ats.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/deliveryservice.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/deliveryservice_regex.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/deliveryservice_stats.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/division.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/federation.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/federation_deliveryservice.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/federation_federationresolver.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/federation_resolver.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/federation_user.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/hwinfo.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/index.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/influxdb.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/iso.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/job.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/parameter.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/phys_location.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/profile.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/profile_parameter.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/region.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/role.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/server.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/static_dns.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/status.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/steering_target.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/system.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/tenant.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/to_extension.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/topology.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/type.rst.txt
delete mode 100644 docs/latest/_sources/api/v12/user.rst.txt
delete mode 100644 docs/latest/_sources/api/v13/coordinate.rst.txt
delete mode 100644 docs/latest/_sources/api/v13/index.rst.txt
delete mode 100644 docs/latest/_sources/api/v13/origin.rst.txt
delete mode 100644 docs/latest/_sources/basics/cache_revalidation.rst.txt
delete mode 100644 docs/latest/_sources/basics/caching_proxies.rst.txt
delete mode 100644 docs/latest/_sources/basics/content_delivery_networks.rst.txt
delete mode 100644 docs/latest/_sources/basics/http_11.rst.txt
delete mode 100644 docs/latest/_sources/basics/index.rst.txt
delete mode 100644 docs/latest/_sources/development/building.rst.txt
delete mode 100644 docs/latest/_sources/development/index.rst.txt
delete mode 100644 docs/latest/_sources/development/traffic_monitor.rst.txt
delete mode 100644 docs/latest/_sources/development/traffic_monitor/traffic_monitor_api.rst.txt
delete mode 100644 docs/latest/_sources/development/traffic_ops.rst.txt
delete mode 100644 docs/latest/_sources/development/traffic_portal.rst.txt
delete mode 100644 docs/latest/_sources/development/traffic_router.rst.txt
delete mode 100644 docs/latest/_sources/development/traffic_router/traffic_router_api.rst.txt
delete mode 100644 docs/latest/_sources/development/traffic_stats.rst.txt
delete mode 100644 docs/latest/_sources/faq/administration.rst.txt
delete mode 100644 docs/latest/_sources/faq/development.rst.txt
delete mode 100644 docs/latest/_sources/faq/general.rst.txt
delete mode 100644 docs/latest/_sources/faq/index.rst.txt
delete mode 100644 docs/latest/_sources/glossary.rst.txt
delete mode 100644 docs/latest/_sources/index.rst.txt
delete mode 100644 docs/latest/_sources/overview/index.rst.txt
delete mode 100644 docs/latest/_sources/overview/introduction.rst.txt
delete mode 100644 docs/latest/_sources/overview/traffic_monitor.rst.txt
delete mode 100644 docs/latest/_sources/overview/traffic_ops.rst.txt
delete mode 100644 docs/latest/_sources/overview/traffic_portal.rst.txt
delete mode 100644 docs/latest/_sources/overview/traffic_router.rst.txt
delete mode 100644 docs/latest/_sources/overview/traffic_stats.rst.txt
delete mode 100644 docs/latest/_sources/overview/traffic_vault.rst.txt
delete mode 100644 docs/latest/_static/ajax-loader.gif
delete mode 100644 docs/latest/_static/basic.css
delete mode 100644 docs/latest/_static/comment-bright.png
delete mode 100644 docs/latest/_static/comment-close.png
delete mode 100644 docs/latest/_static/comment.png
delete mode 100644 docs/latest/_static/css/badge_only.css
delete mode 100644 docs/latest/_static/css/badge_only.css.map
delete mode 100644 docs/latest/_static/css/theme.css
delete mode 100644 docs/latest/_static/css/theme.css.map
delete mode 100644 docs/latest/_static/doctools.js
delete mode 100644 docs/latest/_static/documentation_options.js
delete mode 100644 docs/latest/_static/down-pressed.png
delete mode 100644 docs/latest/_static/down.png
delete mode 100644 docs/latest/_static/favicon.ico
delete mode 100644 docs/latest/_static/file.png
delete mode 100644 docs/latest/_static/fonts/FontAwesome.otf
delete mode 100644 docs/latest/_static/fonts/Inconsolata-Bold.ttf
delete mode 100644 docs/latest/_static/fonts/Inconsolata.ttf
delete mode 100644 docs/latest/_static/fonts/Lato-Bold.ttf
delete mode 100644 docs/latest/_static/fonts/Lato-Regular.ttf
delete mode 100644 docs/latest/_static/fonts/RobotoSlab-Bold.ttf
delete mode 100644 docs/latest/_static/fonts/RobotoSlab-Regular.ttf
delete mode 100644 docs/latest/_static/fonts/fontawesome-webfont.eot
delete mode 100644 docs/latest/_static/fonts/fontawesome-webfont.ttf
delete mode 100644 docs/latest/_static/fonts/fontawesome-webfont.woff
delete mode 100644 docs/latest/_static/jquery-3.2.1.js
delete mode 100644 docs/latest/_static/jquery.js
delete mode 100644 docs/latest/_static/js/modernizr.min.js
delete mode 100644 docs/latest/_static/js/theme.js
delete mode 100644 docs/latest/_static/minus.png
delete mode 100644 docs/latest/_static/plus.png
delete mode 100644 docs/latest/_static/pygments.css
delete mode 100644 docs/latest/_static/searchtools.js
delete mode 100644 docs/latest/_static/tc_logo_c_only.png
delete mode 100644 docs/latest/_static/theme_overrides.css
delete mode 100644 docs/latest/_static/underscore-1.3.1.js
delete mode 100644 docs/latest/_static/underscore.js
delete mode 100644 docs/latest/_static/up-pressed.png
delete mode 100644 docs/latest/_static/up.png
delete mode 100644 docs/latest/_static/websupport.js
delete mode 100644 docs/latest/admin/index.html
delete mode 100644 docs/latest/admin/quick_howto/anonymous_blocking.html
delete mode 100644 docs/latest/admin/quick_howto/dnssec.html
delete mode 100644 docs/latest/admin/quick_howto/ds_requests.html
delete mode 100644 docs/latest/admin/quick_howto/federations.html
delete mode 100644 docs/latest/admin/quick_howto/index.html
delete mode 100644 docs/latest/admin/quick_howto/multi_site.html
delete mode 100644 docs/latest/admin/quick_howto/regionalgeo.html
delete mode 100644 docs/latest/admin/quick_howto/steering.html
delete mode 100644 docs/latest/admin/traffic_monitor.html
delete mode 100644 docs/latest/admin/traffic_monitor_golang.html
delete mode 100644 docs/latest/admin/traffic_ops/configuration.html
delete mode 100644 docs/latest/admin/traffic_ops/default_profiles.html
delete mode 100644 docs/latest/admin/traffic_ops/extensions.html
delete mode 100644 docs/latest/admin/traffic_ops/installation.html
delete mode 100644 docs/latest/admin/traffic_ops/migration_from_10_to_20.html
delete mode 100644 docs/latest/admin/traffic_ops/migration_from_20_to_22.html
delete mode 100644 docs/latest/admin/traffic_ops/using.html
delete mode 100644 docs/latest/admin/traffic_portal/installation.html
delete mode 100644 docs/latest/admin/traffic_portal/usingtrafficportal.html
delete mode 100644 docs/latest/admin/traffic_router.html
delete mode 100644 docs/latest/admin/traffic_server.html
delete mode 100644 docs/latest/admin/traffic_stats.html
delete mode 100644 docs/latest/admin/traffic_vault.html
delete mode 100644 docs/latest/api/index.html
delete mode 100644 docs/latest/api/routes.html
delete mode 100644 docs/latest/api/traffic_ops_api.html
delete mode 100644 docs/latest/api/v11/asn.html
delete mode 100644 docs/latest/api/v11/cachegroup.html
delete mode 100644 docs/latest/api/v11/cdn.html
delete mode 100644 docs/latest/api/v11/changelog.html
delete mode 100644 docs/latest/api/v11/deliveryservice.html
delete mode 100644 docs/latest/api/v11/hwinfo.html
delete mode 100644 docs/latest/api/v11/index.html
delete mode 100644 docs/latest/api/v11/parameter.html
delete mode 100644 docs/latest/api/v11/phys_location.html
delete mode 100644 docs/latest/api/v11/profile.html
delete mode 100644 docs/latest/api/v11/region.html
delete mode 100644 docs/latest/api/v11/role.html
delete mode 100644 docs/latest/api/v11/server.html
delete mode 100644 docs/latest/api/v11/static_dns.html
delete mode 100644 docs/latest/api/v11/status.html
delete mode 100644 docs/latest/api/v11/system.html
delete mode 100644 docs/latest/api/v11/to_extension.html
delete mode 100644 docs/latest/api/v11/type.html
delete mode 100644 docs/latest/api/v11/user.html
delete mode 100644 docs/latest/api/v12/api_capability.html
delete mode 100644 docs/latest/api/v12/asn.html
delete mode 100644 docs/latest/api/v12/cache.html
delete mode 100644 docs/latest/api/v12/cache_stats.html
delete mode 100644 docs/latest/api/v12/cachegroup.html
delete mode 100644 docs/latest/api/v12/cachegroup_fallbacks.html
delete mode 100644 docs/latest/api/v12/cachegroup_parameter.html
delete mode 100644 docs/latest/api/v12/capability.html
delete mode 100644 docs/latest/api/v12/cdn.html
delete mode 100644 docs/latest/api/v12/changelog.html
delete mode 100644 docs/latest/api/v12/configfiles_ats.html
delete mode 100644 docs/latest/api/v12/deliveryservice.html
delete mode 100644 docs/latest/api/v12/deliveryservice_regex.html
delete mode 100644 docs/latest/api/v12/deliveryservice_stats.html
delete mode 100644 docs/latest/api/v12/division.html
delete mode 100644 docs/latest/api/v12/federation.html
delete mode 100644 docs/latest/api/v12/federation_deliveryservice.html
delete mode 100644 docs/latest/api/v12/federation_federationresolver.html
delete mode 100644 docs/latest/api/v12/federation_resolver.html
delete mode 100644 docs/latest/api/v12/federation_user.html
delete mode 100644 docs/latest/api/v12/hwinfo.html
delete mode 100644 docs/latest/api/v12/index.html
delete mode 100644 docs/latest/api/v12/influxdb.html
delete mode 100644 docs/latest/api/v12/iso.html
delete mode 100644 docs/latest/api/v12/job.html
delete mode 100644 docs/latest/api/v12/parameter.html
delete mode 100644 docs/latest/api/v12/phys_location.html
delete mode 100644 docs/latest/api/v12/profile.html
delete mode 100644 docs/latest/api/v12/profile_parameter.html
delete mode 100644 docs/latest/api/v12/region.html
delete mode 100644 docs/latest/api/v12/role.html
delete mode 100644 docs/latest/api/v12/server.html
delete mode 100644 docs/latest/api/v12/static_dns.html
delete mode 100644 docs/latest/api/v12/status.html
delete mode 100644 docs/latest/api/v12/steering_target.html
delete mode 100644 docs/latest/api/v12/system.html
delete mode 100644 docs/latest/api/v12/tenant.html
delete mode 100644 docs/latest/api/v12/to_extension.html
delete mode 100644 docs/latest/api/v12/topology.html
delete mode 100644 docs/latest/api/v12/type.html
delete mode 100644 docs/latest/api/v12/user.html
delete mode 100644 docs/latest/api/v13/coordinate.html
delete mode 100644 docs/latest/api/v13/index.html
delete mode 100644 docs/latest/api/v13/origin.html
delete mode 100644 docs/latest/basics/cache_revalidation.html
delete mode 100644 docs/latest/basics/caching_proxies.html
delete mode 100644 docs/latest/basics/content_delivery_networks.html
delete mode 100644 docs/latest/basics/http_11.html
delete mode 100644 docs/latest/basics/index.html
delete mode 100644 docs/latest/development/building.html
delete mode 100644 docs/latest/development/index.html
delete mode 100644 docs/latest/development/traffic_monitor.html
delete mode 100644 docs/latest/development/traffic_monitor/traffic_monitor_api.html
delete mode 100644 docs/latest/development/traffic_ops.html
delete mode 100644 docs/latest/development/traffic_portal.html
delete mode 100644 docs/latest/development/traffic_router.html
delete mode 100644 docs/latest/development/traffic_router/traffic_router_api.html
delete mode 100644 docs/latest/development/traffic_stats.html
delete mode 100644 docs/latest/faq/administration.html
delete mode 100644 docs/latest/faq/development.html
delete mode 100644 docs/latest/faq/general.html
delete mode 100644 docs/latest/faq/index.html
delete mode 100644 docs/latest/genindex.html
delete mode 100644 docs/latest/glossary.html
delete mode 100644 docs/latest/index.html
delete mode 100644 docs/latest/objects.inv
delete mode 100644 docs/latest/overview/index.html
delete mode 100644 docs/latest/overview/introduction.html
delete mode 100644 docs/latest/overview/traffic_monitor.html
delete mode 100644 docs/latest/overview/traffic_ops.html
delete mode 100644 docs/latest/overview/traffic_portal.html
delete mode 100644 docs/latest/overview/traffic_router.html
delete mode 100644 docs/latest/overview/traffic_stats.html
delete mode 100644 docs/latest/overview/traffic_vault.html
delete mode 100644 docs/latest/search.html
delete mode 100644 docs/latest/searchindex.js
[trafficcontrol-website] 01/04: Do not track docs since we have the
redirect to readthedocs.io already
Posted by zr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
zrhoffman pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/trafficcontrol-website.git
commit 8fbe0ff06bb5e7dfdac3b8f2663fad5cc059d78e
Author: Zach Hoffman <zr...@apache.org>
AuthorDate: Mon Sep 28 13:35:42 2020 -0600
Do not track docs since we have the redirect to readthedocs.io already
---
.../066CEF4F-C1A3-4A89-8B52-4F72B0531367.png | Bin 63381 -> 0 bytes
docs/latest/_images/12m.png | Bin 22728 -> 0 bytes
.../19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png | Bin 62806 -> 0 bytes
.../C5C4CD22-949A-48FD-8976-C673083E2177.png | Bin 55410 -> 0 bytes
.../D28614AA-9758-45ED-9EFD-3A284FC4218E.png | Bin 45381 -> 0 bytes
docs/latest/_images/anonymous_blocking01.png | Bin 109855 -> 0 bytes
docs/latest/_images/anonymous_blocking02.png | Bin 28800 -> 0 bytes
docs/latest/_images/bad.png | Bin 472 -> 0 bytes
docs/latest/_images/bad1.png | Bin 472 -> 0 bytes
docs/latest/_images/cache_groups_1.png | Bin 80623 -> 0 bytes
docs/latest/_images/clock-black.png | Bin 427 -> 0 bytes
docs/latest/_images/dnssec01.png | Bin 32216 -> 0 bytes
docs/latest/_images/dnssec02.png | Bin 61047 -> 0 bytes
docs/latest/_images/dnssec03.png | Bin 145394 -> 0 bytes
docs/latest/_images/dnssec04.png | Bin 195587 -> 0 bytes
docs/latest/_images/ds-profile.png | Bin 107817 -> 0 bytes
docs/latest/_images/ds_profile_parameters.png | Bin 99479 -> 0 bytes
docs/latest/_images/federation01.png | Bin 96843 -> 0 bytes
docs/latest/_images/federation02.png | Bin 101666 -> 0 bytes
docs/latest/_images/federation03.png | Bin 316490 -> 0 bytes
docs/latest/_images/federation04.png | Bin 269316 -> 0 bytes
docs/latest/_images/fwda.png | Bin 206 -> 0 bytes
docs/latest/_images/fwda1.png | Bin 206 -> 0 bytes
docs/latest/_images/good.png | Bin 617 -> 0 bytes
docs/latest/_images/good1.png | Bin 617 -> 0 bytes
docs/latest/_images/graph.png | Bin 483 -> 0 bytes
docs/latest/_images/info.png | Bin 3379 -> 0 bytes
docs/latest/_images/mso-enable.png | Bin 124819 -> 0 bytes
docs/latest/_images/regionalgeo01.png | Bin 75096 -> 0 bytes
docs/latest/_images/regionalgeo02.png | Bin 93191 -> 0 bytes
docs/latest/_images/regionalgeo03.png | Bin 42367 -> 0 bytes
docs/latest/_images/steering01.png | Bin 51223 -> 0 bytes
docs/latest/_images/steering02.png | Bin 116876 -> 0 bytes
docs/latest/_images/steering03.png | Bin 210908 -> 0 bytes
docs/latest/_images/steering04.png | Bin 35255 -> 0 bytes
docs/latest/_images/tp_menu.png | Bin 100018 -> 0 bytes
docs/latest/_images/tp_menu_configure.png | Bin 65142 -> 0 bytes
docs/latest/_images/tp_menu_monitor.png | Bin 57825 -> 0 bytes
docs/latest/_images/tp_menu_other.png | Bin 61114 -> 0 bytes
docs/latest/_images/tp_menu_services.png | Bin 61219 -> 0 bytes
docs/latest/_images/tp_menu_tools.png | Bin 58820 -> 0 bytes
docs/latest/_images/tp_menu_topology.png | Bin 66984 -> 0 bytes
docs/latest/_images/tp_menu_user_admin.png | Bin 59728 -> 0 bytes
docs/latest/_images/tp_table_ds_requests.png | Bin 120150 -> 0 bytes
docs/latest/_images/tp_table_ds_requests1.png | Bin 120150 -> 0 bytes
docs/latest/_images/traffic_control_overview_3.png | Bin 138671 -> 0 bytes
docs/latest/_sources/admin/index.rst.txt | 52 -
.../admin/quick_howto/anonymous_blocking.rst.txt | 87 -
.../_sources/admin/quick_howto/dnssec.rst.txt | 72 -
.../_sources/admin/quick_howto/ds_requests.rst.txt | 81 -
.../_sources/admin/quick_howto/federations.rst.txt | 135 -
.../_sources/admin/quick_howto/index.rst.txt | 43 -
.../_sources/admin/quick_howto/multi_site.rst.txt | 105 -
.../_sources/admin/quick_howto/regionalgeo.rst.txt | 109 -
.../_sources/admin/quick_howto/steering.rst.txt | 111 -
docs/latest/_sources/admin/traffic_monitor.rst.txt | 177 -
.../_sources/admin/traffic_monitor_golang.rst.txt | 65 -
.../admin/traffic_ops/configuration.rst.txt | 322 -
.../admin/traffic_ops/default_profiles.rst.txt | 53 -
.../_sources/admin/traffic_ops/extensions.rst.txt | 88 -
.../admin/traffic_ops/installation.rst.txt | 243 -
.../traffic_ops/migration_from_10_to_20.rst.txt | 88 -
.../traffic_ops/migration_from_20_to_22.rst.txt | 122 -
.../_sources/admin/traffic_ops/using.rst.txt | 1224 ---
.../admin/traffic_portal/installation.rst.txt | 51 -
.../traffic_portal/usingtrafficportal.rst.txt | 800 --
docs/latest/_sources/admin/traffic_router.rst.txt | 588 --
docs/latest/_sources/admin/traffic_server.rst.txt | 149 -
docs/latest/_sources/admin/traffic_stats.rst.txt | 188 -
docs/latest/_sources/admin/traffic_vault.rst.txt | 188 -
docs/latest/_sources/api/index.rst.txt | 28 -
docs/latest/_sources/api/routes.rst.txt | 118 -
docs/latest/_sources/api/traffic_ops_api.rst.txt | 196 -
docs/latest/_sources/api/v11/asn.rst.txt | 69 -
docs/latest/_sources/api/v11/cachegroup.rst.txt | 317 -
docs/latest/_sources/api/v11/cdn.rst.txt | 1088 --
docs/latest/_sources/api/v11/changelog.rst.txt | 154 -
.../_sources/api/v11/deliveryservice.rst.txt | 1286 ---
docs/latest/_sources/api/v11/hwinfo.rst.txt | 67 -
docs/latest/_sources/api/v11/index.rst.txt | 40 -
docs/latest/_sources/api/v11/parameter.rst.txt | 136 -
docs/latest/_sources/api/v11/phys_location.rst.txt | 449 -
docs/latest/_sources/api/v11/profile.rst.txt | 129 -
docs/latest/_sources/api/v11/region.rst.txt | 235 -
docs/latest/_sources/api/v11/role.rst.txt | 58 -
docs/latest/_sources/api/v11/server.rst.txt | 630 --
docs/latest/_sources/api/v11/static_dns.rst.txt | 63 -
docs/latest/_sources/api/v11/status.rst.txt | 127 -
docs/latest/_sources/api/v11/system.rst.txt | 79 -
docs/latest/_sources/api/v11/to_extension.rst.txt | 210 -
docs/latest/_sources/api/v11/type.rst.txt | 151 -
docs/latest/_sources/api/v11/user.rst.txt | 778 --
.../latest/_sources/api/v12/api_capability.rst.txt | 320 -
docs/latest/_sources/api/v12/asn.rst.txt | 200 -
docs/latest/_sources/api/v12/cache.rst.txt | 84 -
docs/latest/_sources/api/v12/cache_stats.rst.txt | 134 -
docs/latest/_sources/api/v12/cachegroup.rst.txt | 821 --
.../_sources/api/v12/cachegroup_fallbacks.rst.txt | 288 -
.../_sources/api/v12/cachegroup_parameter.rst.txt | 177 -
docs/latest/_sources/api/v12/capability.rst.txt | 271 -
docs/latest/_sources/api/v12/cdn.rst.txt | 1410 ---
docs/latest/_sources/api/v12/changelog.rst.txt | 164 -
.../_sources/api/v12/configfiles_ats.rst.txt | 193 -
.../_sources/api/v12/deliveryservice.rst.txt | 3486 -------
.../_sources/api/v12/deliveryservice_regex.rst.txt | 374 -
.../_sources/api/v12/deliveryservice_stats.rst.txt | 155 -
docs/latest/_sources/api/v12/division.rst.txt | 203 -
docs/latest/_sources/api/v12/federation.rst.txt | 434 -
.../api/v12/federation_deliveryservice.rst.txt | 155 -
.../api/v12/federation_federationresolver.rst.txt | 118 -
.../_sources/api/v12/federation_resolver.rst.txt | 110 -
.../_sources/api/v12/federation_user.rst.txt | 161 -
docs/latest/_sources/api/v12/hwinfo.rst.txt | 68 -
docs/latest/_sources/api/v12/index.rst.txt | 63 -
docs/latest/_sources/api/v12/influxdb.rst.txt | 65 -
docs/latest/_sources/api/v12/iso.rst.txt | 132 -
docs/latest/_sources/api/v12/job.rst.txt | 136 -
docs/latest/_sources/api/v12/parameter.rst.txt | 691 --
docs/latest/_sources/api/v12/phys_location.rst.txt | 456 -
docs/latest/_sources/api/v12/profile.rst.txt | 415 -
.../_sources/api/v12/profile_parameter.rst.txt | 573 --
docs/latest/_sources/api/v12/region.rst.txt | 244 -
docs/latest/_sources/api/v12/role.rst.txt | 59 -
docs/latest/_sources/api/v12/server.rst.txt | 1496 ---
docs/latest/_sources/api/v12/static_dns.rst.txt | 66 -
docs/latest/_sources/api/v12/status.rst.txt | 127 -
.../_sources/api/v12/steering_target.rst.txt | 333 -
docs/latest/_sources/api/v12/system.rst.txt | 80 -
docs/latest/_sources/api/v12/tenant.rst.txt | 255 -
docs/latest/_sources/api/v12/to_extension.rst.txt | 206 -
docs/latest/_sources/api/v12/topology.rst.txt | 152 -
docs/latest/_sources/api/v12/type.rst.txt | 151 -
docs/latest/_sources/api/v12/user.rst.txt | 1258 ---
docs/latest/_sources/api/v13/coordinate.rst.txt | 272 -
docs/latest/_sources/api/v13/index.rst.txt | 25 -
docs/latest/_sources/api/v13/origin.rst.txt | 474 -
.../_sources/basics/cache_revalidation.rst.txt | 71 -
.../latest/_sources/basics/caching_proxies.rst.txt | 238 -
.../basics/content_delivery_networks.rst.txt | 40 -
docs/latest/_sources/basics/http_11.rst.txt | 48 -
docs/latest/_sources/basics/index.rst.txt | 29 -
docs/latest/_sources/development/building.rst.txt | 94 -
docs/latest/_sources/development/index.rst.txt | 29 -
.../_sources/development/traffic_monitor.rst.txt | 301 -
.../traffic_monitor/traffic_monitor_api.rst.txt | 178 -
.../_sources/development/traffic_ops.rst.txt | 369 -
.../_sources/development/traffic_portal.rst.txt | 51 -
.../_sources/development/traffic_router.rst.txt | 145 -
.../traffic_router/traffic_router_api.rst.txt | 91 -
.../_sources/development/traffic_stats.rst.txt | 58 -
docs/latest/_sources/faq/administration.rst.txt | 95 -
docs/latest/_sources/faq/development.rst.txt | 21 -
docs/latest/_sources/faq/general.rst.txt | 55 -
docs/latest/_sources/faq/index.rst.txt | 26 -
docs/latest/_sources/glossary.rst.txt | 81 -
docs/latest/_sources/index.rst.txt | 88 -
docs/latest/_sources/overview/index.rst.txt | 29 -
docs/latest/_sources/overview/introduction.rst.txt | 49 -
.../_sources/overview/traffic_monitor.rst.txt | 66 -
docs/latest/_sources/overview/traffic_ops.rst.txt | 41 -
.../_sources/overview/traffic_portal.rst.txt | 33 -
.../_sources/overview/traffic_router.rst.txt | 109 -
.../latest/_sources/overview/traffic_stats.rst.txt | 35 -
.../latest/_sources/overview/traffic_vault.rst.txt | 36 -
docs/latest/_static/ajax-loader.gif | Bin 673 -> 0 bytes
docs/latest/_static/basic.css | 665 --
docs/latest/_static/comment-bright.png | Bin 756 -> 0 bytes
docs/latest/_static/comment-close.png | Bin 829 -> 0 bytes
docs/latest/_static/comment.png | Bin 641 -> 0 bytes
docs/latest/_static/css/badge_only.css | 2 -
docs/latest/_static/css/badge_only.css.map | 7 -
docs/latest/_static/css/theme.css | 5 -
docs/latest/_static/css/theme.css.map | 7 -
docs/latest/_static/doctools.js | 313 -
docs/latest/_static/documentation_options.js | 9 -
docs/latest/_static/down-pressed.png | Bin 222 -> 0 bytes
docs/latest/_static/down.png | Bin 202 -> 0 bytes
docs/latest/_static/favicon.ico | Bin 1150 -> 0 bytes
docs/latest/_static/file.png | Bin 286 -> 0 bytes
docs/latest/_static/fonts/FontAwesome.otf | Bin 62856 -> 0 bytes
docs/latest/_static/fonts/Inconsolata-Bold.ttf | Bin 47064 -> 0 bytes
docs/latest/_static/fonts/Inconsolata.ttf | Bin 63184 -> 0 bytes
docs/latest/_static/fonts/Lato-Bold.ttf | Bin 82368 -> 0 bytes
docs/latest/_static/fonts/Lato-Regular.ttf | Bin 81980 -> 0 bytes
docs/latest/_static/fonts/RobotoSlab-Bold.ttf | Bin 36596 -> 0 bytes
docs/latest/_static/fonts/RobotoSlab-Regular.ttf | Bin 36276 -> 0 bytes
docs/latest/_static/fonts/fontawesome-webfont.eot | Bin 38205 -> 0 bytes
docs/latest/_static/fonts/fontawesome-webfont.ttf | Bin 80652 -> 0 bytes
docs/latest/_static/fonts/fontawesome-webfont.woff | Bin 44432 -> 0 bytes
docs/latest/_static/jquery-3.2.1.js | 10253 -------------------
docs/latest/_static/jquery.js | 4 -
docs/latest/_static/js/modernizr.min.js | 4 -
docs/latest/_static/js/theme.js | 50 -
docs/latest/_static/minus.png | Bin 90 -> 0 bytes
docs/latest/_static/plus.png | Bin 90 -> 0 bytes
docs/latest/_static/pygments.css | 69 -
docs/latest/_static/searchtools.js | 761 --
docs/latest/_static/tc_logo_c_only.png | Bin 106800 -> 0 bytes
docs/latest/_static/theme_overrides.css | 69 -
docs/latest/_static/underscore-1.3.1.js | 999 --
docs/latest/_static/underscore.js | 31 -
docs/latest/_static/up-pressed.png | Bin 214 -> 0 bytes
docs/latest/_static/up.png | Bin 203 -> 0 bytes
docs/latest/_static/websupport.js | 808 --
docs/latest/admin/index.html | 563 -
.../admin/quick_howto/anonymous_blocking.html | 355 -
docs/latest/admin/quick_howto/dnssec.html | 348 -
docs/latest/admin/quick_howto/ds_requests.html | 343 -
docs/latest/admin/quick_howto/federations.html | 411 -
docs/latest/admin/quick_howto/index.html | 330 -
docs/latest/admin/quick_howto/multi_site.html | 403 -
docs/latest/admin/quick_howto/regionalgeo.html | 375 -
docs/latest/admin/quick_howto/steering.html | 383 -
docs/latest/admin/traffic_monitor.html | 458 -
docs/latest/admin/traffic_monitor_golang.html | 342 -
docs/latest/admin/traffic_ops/configuration.html | 722 --
.../latest/admin/traffic_ops/default_profiles.html | 322 -
docs/latest/admin/traffic_ops/extensions.html | 357 -
docs/latest/admin/traffic_ops/installation.html | 531 -
.../admin/traffic_ops/migration_from_10_to_20.html | 352 -
.../admin/traffic_ops/migration_from_20_to_22.html | 434 -
docs/latest/admin/traffic_ops/using.html | 1900 ----
docs/latest/admin/traffic_portal/installation.html | 331 -
.../admin/traffic_portal/usingtrafficportal.html | 1363 ---
docs/latest/admin/traffic_router.html | 1055 --
docs/latest/admin/traffic_server.html | 446 -
docs/latest/admin/traffic_stats.html | 528 -
docs/latest/admin/traffic_vault.html | 541 -
docs/latest/api/index.html | 375 -
docs/latest/api/routes.html | 467 -
docs/latest/api/traffic_ops_api.html | 495 -
docs/latest/api/v11/asn.html | 363 -
docs/latest/api/v11/cachegroup.html | 740 --
docs/latest/api/v11/cdn.html | 2049 ----
docs/latest/api/v11/changelog.html | 496 -
docs/latest/api/v11/deliveryservice.html | 2370 -----
docs/latest/api/v11/hwinfo.html | 361 -
docs/latest/api/v11/index.html | 319 -
docs/latest/api/v11/parameter.html | 462 -
docs/latest/api/v11/phys_location.html | 988 --
docs/latest/api/v11/profile.html | 471 -
docs/latest/api/v11/region.html | 649 --
docs/latest/api/v11/role.html | 351 -
docs/latest/api/v11/server.html | 1247 ---
docs/latest/api/v11/static_dns.html | 361 -
docs/latest/api/v11/status.html | 447 -
docs/latest/api/v11/system.html | 379 -
docs/latest/api/v11/to_extension.html | 582 --
docs/latest/api/v11/type.html | 501 -
docs/latest/api/v11/user.html | 1499 ---
docs/latest/api/v12/api_capability.html | 798 --
docs/latest/api/v12/asn.html | 586 --
docs/latest/api/v12/cache.html | 385 -
docs/latest/api/v12/cache_stats.html | 467 -
docs/latest/api/v12/cachegroup.html | 1581 ---
docs/latest/api/v12/cachegroup_fallbacks.html | 710 --
docs/latest/api/v12/cachegroup_parameter.html | 517 -
docs/latest/api/v12/capability.html | 701 --
docs/latest/api/v12/cdn.html | 2566 -----
docs/latest/api/v12/changelog.html | 520 -
docs/latest/api/v12/configfiles_ats.html | 488 -
docs/latest/api/v12/deliveryservice.html | 5990 -----------
docs/latest/api/v12/deliveryservice_regex.html | 859 --
docs/latest/api/v12/deliveryservice_stats.html | 494 -
docs/latest/api/v12/division.html | 585 --
docs/latest/api/v12/federation.html | 931 --
.../latest/api/v12/federation_deliveryservice.html | 500 -
.../api/v12/federation_federationresolver.html | 449 -
docs/latest/api/v12/federation_resolver.html | 432 -
docs/latest/api/v12/federation_user.html | 510 -
docs/latest/api/v12/hwinfo.html | 364 -
docs/latest/api/v12/index.html | 341 -
docs/latest/api/v12/influxdb.html | 353 -
docs/latest/api/v12/iso.html | 468 -
docs/latest/api/v12/job.html | 472 -
docs/latest/api/v12/parameter.html | 1382 ---
docs/latest/api/v12/phys_location.html | 1008 --
docs/latest/api/v12/profile.html | 981 --
docs/latest/api/v12/profile_parameter.html | 1105 --
docs/latest/api/v12/region.html | 672 --
docs/latest/api/v12/role.html | 354 -
docs/latest/api/v12/server.html | 2702 -----
docs/latest/api/v12/static_dns.html | 364 -
docs/latest/api/v12/status.html | 447 -
docs/latest/api/v12/steering_target.html | 800 --
docs/latest/api/v12/system.html | 382 -
docs/latest/api/v12/tenant.html | 655 --
docs/latest/api/v12/to_extension.html | 582 --
docs/latest/api/v12/topology.html | 519 -
docs/latest/api/v12/type.html | 501 -
docs/latest/api/v12/user.html | 2302 -----
docs/latest/api/v13/coordinate.html | 705 --
docs/latest/api/v13/index.html | 303 -
docs/latest/api/v13/origin.html | 1034 --
docs/latest/basics/cache_revalidation.html | 343 -
docs/latest/basics/caching_proxies.html | 517 -
docs/latest/basics/content_delivery_networks.html | 324 -
docs/latest/basics/http_11.html | 328 -
docs/latest/basics/index.html | 307 -
docs/latest/development/building.html | 362 -
docs/latest/development/index.html | 354 -
docs/latest/development/traffic_monitor.html | 549 -
.../traffic_monitor/traffic_monitor_api.html | 545 -
docs/latest/development/traffic_ops.html | 654 --
docs/latest/development/traffic_portal.html | 341 -
docs/latest/development/traffic_router.html | 488 -
.../traffic_router/traffic_router_api.html | 355 -
docs/latest/development/traffic_stats.html | 345 -
docs/latest/faq/administration.html | 395 -
docs/latest/faq/development.html | 301 -
docs/latest/faq/general.html | 342 -
docs/latest/faq/index.html | 316 -
docs/latest/genindex.html | 549 -
docs/latest/glossary.html | 328 -
docs/latest/index.html | 653 --
docs/latest/objects.inv | Bin 5040 -> 0 bytes
docs/latest/overview/index.html | 318 -
docs/latest/overview/introduction.html | 333 -
docs/latest/overview/traffic_monitor.html | 330 -
docs/latest/overview/traffic_ops.html | 315 -
docs/latest/overview/traffic_portal.html | 307 -
docs/latest/overview/traffic_router.html | 373 -
docs/latest/overview/traffic_stats.html | 307 -
docs/latest/overview/traffic_vault.html | 336 -
docs/latest/search.html | 288 -
docs/latest/searchindex.js | 1 -
326 files changed, 124800 deletions(-)
diff --git a/docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png b/docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png
deleted file mode 100644
index 9998e81..0000000
Binary files a/docs/latest/_images/066CEF4F-C1A3-4A89-8B52-4F72B0531367.png and /dev/null differ
diff --git a/docs/latest/_images/12m.png b/docs/latest/_images/12m.png
deleted file mode 100644
index 36ce934..0000000
Binary files a/docs/latest/_images/12m.png and /dev/null differ
diff --git a/docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png b/docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png
deleted file mode 100644
index 1a6ad24..0000000
Binary files a/docs/latest/_images/19BB6EC1-B6E8-4D22-BFA0-B7D6A9708B42.png and /dev/null differ
diff --git a/docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png b/docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png
deleted file mode 100644
index 96fddab..0000000
Binary files a/docs/latest/_images/C5C4CD22-949A-48FD-8976-C673083E2177.png and /dev/null differ
diff --git a/docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png b/docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png
deleted file mode 100644
index 6d05b19..0000000
Binary files a/docs/latest/_images/D28614AA-9758-45ED-9EFD-3A284FC4218E.png and /dev/null differ
diff --git a/docs/latest/_images/anonymous_blocking01.png b/docs/latest/_images/anonymous_blocking01.png
deleted file mode 100644
index bda89db..0000000
Binary files a/docs/latest/_images/anonymous_blocking01.png and /dev/null differ
diff --git a/docs/latest/_images/anonymous_blocking02.png b/docs/latest/_images/anonymous_blocking02.png
deleted file mode 100644
index 0b74046..0000000
Binary files a/docs/latest/_images/anonymous_blocking02.png and /dev/null differ
diff --git a/docs/latest/_images/bad.png b/docs/latest/_images/bad.png
deleted file mode 100644
index 485e3da..0000000
Binary files a/docs/latest/_images/bad.png and /dev/null differ
diff --git a/docs/latest/_images/bad1.png b/docs/latest/_images/bad1.png
deleted file mode 100644
index 485e3da..0000000
Binary files a/docs/latest/_images/bad1.png and /dev/null differ
diff --git a/docs/latest/_images/cache_groups_1.png b/docs/latest/_images/cache_groups_1.png
deleted file mode 100644
index d03d320..0000000
Binary files a/docs/latest/_images/cache_groups_1.png and /dev/null differ
diff --git a/docs/latest/_images/clock-black.png b/docs/latest/_images/clock-black.png
deleted file mode 100644
index 4783c01..0000000
Binary files a/docs/latest/_images/clock-black.png and /dev/null differ
diff --git a/docs/latest/_images/dnssec01.png b/docs/latest/_images/dnssec01.png
deleted file mode 100644
index 044538f..0000000
Binary files a/docs/latest/_images/dnssec01.png and /dev/null differ
diff --git a/docs/latest/_images/dnssec02.png b/docs/latest/_images/dnssec02.png
deleted file mode 100644
index 82fa75a..0000000
Binary files a/docs/latest/_images/dnssec02.png and /dev/null differ
diff --git a/docs/latest/_images/dnssec03.png b/docs/latest/_images/dnssec03.png
deleted file mode 100644
index 1fc3cce..0000000
Binary files a/docs/latest/_images/dnssec03.png and /dev/null differ
diff --git a/docs/latest/_images/dnssec04.png b/docs/latest/_images/dnssec04.png
deleted file mode 100644
index f9b8d32..0000000
Binary files a/docs/latest/_images/dnssec04.png and /dev/null differ
diff --git a/docs/latest/_images/ds-profile.png b/docs/latest/_images/ds-profile.png
deleted file mode 100644
index 97ee6f8..0000000
Binary files a/docs/latest/_images/ds-profile.png and /dev/null differ
diff --git a/docs/latest/_images/ds_profile_parameters.png b/docs/latest/_images/ds_profile_parameters.png
deleted file mode 100644
index 7c8f12b..0000000
Binary files a/docs/latest/_images/ds_profile_parameters.png and /dev/null differ
diff --git a/docs/latest/_images/federation01.png b/docs/latest/_images/federation01.png
deleted file mode 100644
index bbbd924..0000000
Binary files a/docs/latest/_images/federation01.png and /dev/null differ
diff --git a/docs/latest/_images/federation02.png b/docs/latest/_images/federation02.png
deleted file mode 100644
index 9db970e..0000000
Binary files a/docs/latest/_images/federation02.png and /dev/null differ
diff --git a/docs/latest/_images/federation03.png b/docs/latest/_images/federation03.png
deleted file mode 100644
index abd52d2..0000000
Binary files a/docs/latest/_images/federation03.png and /dev/null differ
diff --git a/docs/latest/_images/federation04.png b/docs/latest/_images/federation04.png
deleted file mode 100644
index dd5a812..0000000
Binary files a/docs/latest/_images/federation04.png and /dev/null differ
diff --git a/docs/latest/_images/fwda.png b/docs/latest/_images/fwda.png
deleted file mode 100644
index ba63bee..0000000
Binary files a/docs/latest/_images/fwda.png and /dev/null differ
diff --git a/docs/latest/_images/fwda1.png b/docs/latest/_images/fwda1.png
deleted file mode 100644
index ba63bee..0000000
Binary files a/docs/latest/_images/fwda1.png and /dev/null differ
diff --git a/docs/latest/_images/good.png b/docs/latest/_images/good.png
deleted file mode 100644
index 84d96cd..0000000
Binary files a/docs/latest/_images/good.png and /dev/null differ
diff --git a/docs/latest/_images/good1.png b/docs/latest/_images/good1.png
deleted file mode 100644
index 84d96cd..0000000
Binary files a/docs/latest/_images/good1.png and /dev/null differ
diff --git a/docs/latest/_images/graph.png b/docs/latest/_images/graph.png
deleted file mode 100644
index 4502a2d..0000000
Binary files a/docs/latest/_images/graph.png and /dev/null differ
diff --git a/docs/latest/_images/info.png b/docs/latest/_images/info.png
deleted file mode 100644
index 3e1125c..0000000
Binary files a/docs/latest/_images/info.png and /dev/null differ
diff --git a/docs/latest/_images/mso-enable.png b/docs/latest/_images/mso-enable.png
deleted file mode 100644
index 70207ba..0000000
Binary files a/docs/latest/_images/mso-enable.png and /dev/null differ
diff --git a/docs/latest/_images/regionalgeo01.png b/docs/latest/_images/regionalgeo01.png
deleted file mode 100644
index 0443a17..0000000
Binary files a/docs/latest/_images/regionalgeo01.png and /dev/null differ
diff --git a/docs/latest/_images/regionalgeo02.png b/docs/latest/_images/regionalgeo02.png
deleted file mode 100644
index 5530920..0000000
Binary files a/docs/latest/_images/regionalgeo02.png and /dev/null differ
diff --git a/docs/latest/_images/regionalgeo03.png b/docs/latest/_images/regionalgeo03.png
deleted file mode 100644
index ce2676b..0000000
Binary files a/docs/latest/_images/regionalgeo03.png and /dev/null differ
diff --git a/docs/latest/_images/steering01.png b/docs/latest/_images/steering01.png
deleted file mode 100644
index 1515011..0000000
Binary files a/docs/latest/_images/steering01.png and /dev/null differ
diff --git a/docs/latest/_images/steering02.png b/docs/latest/_images/steering02.png
deleted file mode 100644
index c2fc22c..0000000
Binary files a/docs/latest/_images/steering02.png and /dev/null differ
diff --git a/docs/latest/_images/steering03.png b/docs/latest/_images/steering03.png
deleted file mode 100644
index f4b110d..0000000
Binary files a/docs/latest/_images/steering03.png and /dev/null differ
diff --git a/docs/latest/_images/steering04.png b/docs/latest/_images/steering04.png
deleted file mode 100644
index 0ab962b..0000000
Binary files a/docs/latest/_images/steering04.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu.png b/docs/latest/_images/tp_menu.png
deleted file mode 100644
index d8052c7..0000000
Binary files a/docs/latest/_images/tp_menu.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu_configure.png b/docs/latest/_images/tp_menu_configure.png
deleted file mode 100644
index 4a5d211..0000000
Binary files a/docs/latest/_images/tp_menu_configure.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu_monitor.png b/docs/latest/_images/tp_menu_monitor.png
deleted file mode 100644
index 845364e..0000000
Binary files a/docs/latest/_images/tp_menu_monitor.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu_other.png b/docs/latest/_images/tp_menu_other.png
deleted file mode 100644
index d0c29b2..0000000
Binary files a/docs/latest/_images/tp_menu_other.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu_services.png b/docs/latest/_images/tp_menu_services.png
deleted file mode 100644
index d887b16..0000000
Binary files a/docs/latest/_images/tp_menu_services.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu_tools.png b/docs/latest/_images/tp_menu_tools.png
deleted file mode 100644
index fd1db4d..0000000
Binary files a/docs/latest/_images/tp_menu_tools.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu_topology.png b/docs/latest/_images/tp_menu_topology.png
deleted file mode 100644
index f69f959..0000000
Binary files a/docs/latest/_images/tp_menu_topology.png and /dev/null differ
diff --git a/docs/latest/_images/tp_menu_user_admin.png b/docs/latest/_images/tp_menu_user_admin.png
deleted file mode 100644
index bf76e87..0000000
Binary files a/docs/latest/_images/tp_menu_user_admin.png and /dev/null differ
diff --git a/docs/latest/_images/tp_table_ds_requests.png b/docs/latest/_images/tp_table_ds_requests.png
deleted file mode 100644
index ae4ed39..0000000
Binary files a/docs/latest/_images/tp_table_ds_requests.png and /dev/null differ
diff --git a/docs/latest/_images/tp_table_ds_requests1.png b/docs/latest/_images/tp_table_ds_requests1.png
deleted file mode 100644
index ae4ed39..0000000
Binary files a/docs/latest/_images/tp_table_ds_requests1.png and /dev/null differ
diff --git a/docs/latest/_images/traffic_control_overview_3.png b/docs/latest/_images/traffic_control_overview_3.png
deleted file mode 100644
index 58f03d7..0000000
Binary files a/docs/latest/_images/traffic_control_overview_3.png and /dev/null differ
diff --git a/docs/latest/_sources/admin/index.rst.txt b/docs/latest/_sources/admin/index.rst.txt
deleted file mode 100644
index 05075cf..0000000
--- a/docs/latest/_sources/admin/index.rst.txt
+++ /dev/null
@@ -1,52 +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:
-
-#. Traffic Ops
-#. Traffic Vault (Riak)
-#. Traffic Monitor
-#. Apache Traffic Server Mid-Tier Caches
-#. Apache Traffic Server Edge Caches
-#. Traffic Router
-#. Traffic Stats
-#. 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/installation.rst
- traffic_ops/default_profiles.rst
- traffic_ops/migration_from_10_to_20.rst
- traffic_ops/migration_from_20_to_22.rst
- traffic_ops/configuration.rst
- traffic_ops/using.rst
- traffic_ops/extensions.rst
- traffic_portal/installation.rst
- traffic_portal/usingtrafficportal.rst
- traffic_monitor.rst
- traffic_monitor_golang.rst
- traffic_router.rst
- traffic_stats.rst
- traffic_server.rst
- traffic_vault.rst
- quick_howto/index.rst
diff --git a/docs/latest/_sources/admin/quick_howto/anonymous_blocking.rst.txt b/docs/latest/_sources/admin/quick_howto/anonymous_blocking.rst.txt
deleted file mode 100644
index 4ee0ad5..0000000
--- a/docs/latest/_sources/admin/quick_howto/anonymous_blocking.rst.txt
+++ /dev/null
@@ -1,87 +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-anonymous_blocking-qht:
-
-**************************************
-Configure Anonymous Blocking
-**************************************
-
-.. Note:: Anonymous Blocking is only supported for HTTP delivery services.
-
-1) Prepare the Anonymous Blocking configuration file
-
-Anonymous Blocking uses a configuration file in JSON format to define 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::
-
- {
-
- "customer": "YourCompany",
- "version": "1",
- "date" : "2017-05-23 03:28:25",
- "name": "Anonymous IP Blocking Policy",
-
- "anonymousIp": { "blockAnonymousVPN": true,
- "blockHostingProvider": true,
- "blockPublicProxy": true,
- "blockTorExitNode": true},
-
- "ip4Whitelist": ["192.168.30.0/24", "10.0.2.0/24", "10.1.1.1/32"],
-
- "ip6Whitelist": ["2001:550:90a::/48", "::1/128"],
-
- "redirectUrl": "http://youvebeenblocked.com"
- }
-
-* “anonymousIp” contains the types of IPs which can be checked against the Anonymous IP Database. There are 4 types of IPs which can be checked: VPNs, Hosting Providers, Public Proxies, and Tor Exit Nodes. Each type of IP can be enabled or disabled. If the value is true, IPs which match this type will be blocked when the feature is enabled in the delivery service. If the value is false, IPs which match this type will not be blocked. If an IP matches more than 1 type and any type is enabl [...]
-
-* “redirectUrl” is the URL that will be returned to the blocked clients. Without a redirectUrl, the clients will receive an HTTP response code 403. With a redirectUrl, the clients will be redirected with an HTTP response code 302.
-
-* “ipWhiteList” is an optional element. It includes a list of CIDR (Classless Inter-Domain Routing) blocks indicating the IPv4 and IPv6 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. If there is no match in the white list, further anonymous blocking logic will continue.
-
-
-2) Add Anonymous Blocking parameters on Traffic Ops
-
-The following three new parameters are required to be added into CRConfig.json:
-
-* "anonymousip.policy.configuration": the HTTP URL of the Anonymous Blocking configuration file. Traffic Router will fetch the file from this URL.
-* "anonymousip.polling.url": the HTTP URL of the Anonymous IP Database. Traffic Router will fetch the file from this URL.
-* "anonymousip.polling.interval": the interval that Traffic Router polls the Anonymous Blocking configuration file and Anonymous IP Database.
-
-.. image:: anonymous_blocking01.png
- :scale: 100%
- :align: center
-
-3) Enable Anonmyous Blocking for a delivery service
-
-.. image:: anonymous_blocking02.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 Anonymous Blocking
-
-Anonymous Blocking extends the field of "rtype" and adds a new field "ANON_BLOCK" in Traffic Router access.log to help to monitor the working of this feature.
-
-If rtype=ANON_BLOCK then the client's IP was found in the Anonymous IP Database and was blocked.
-
-
-
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).
diff --git a/docs/latest/_sources/admin/quick_howto/ds_requests.rst.txt b/docs/latest/_sources/admin/quick_howto/ds_requests.rst.txt
deleted file mode 100644
index 997935e..0000000
--- a/docs/latest/_sources/admin/quick_howto/ds_requests.rst.txt
+++ /dev/null
@@ -1,81 +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.
-..
-
-.. _ds_requests:
-
-Delivery Service Requests
-=========================
-
-When enabled in traffic_portal_properties.json, delivery service requests are created when ALL users attempt to create, update or delete a delivery service.
-This allows users with higher level permissions (ops or admin) to review the changes for completeness and accuracy before deploying the changes.
-In addition, most delivery service changes require cache config updates (aka queue updates) and/or a cdn snapshot. Both of these actions are reserved for users with elevated permissions.
-
-A list of the delivery service requests associated with your tenant can be found here:
-
-``https://traffic-portal.domain.com/#!/delivery-service-requests``
-
-.. image:: ../traffic_portal/images/tp_table_ds_requests.png
-
-Who Can Create a Delivery Service Request and How?
-##################################################
-
-Users with the Portal role (or above) can create delivery service requests by doing one of three things:
-
-1. Creating a new delivery service
-2. Updating an existing delivery service
-3. Deleting an exiting delivery service
-
-By performing one of these actions, a delivery service request will be created for you with a status of draft or submitted. You determine the status of your request. Only change the status of your request to submitted once the request is ready for review and deployment.
-
-Who Can Fulfill a Delivery Service Request and How?
-###################################################
-
-Users with elevated permissions (Operations or above) can fulfill (apply the changes) or reject the delivery service request. In fact, they can do all of the following:
-
-Update the contents of the delivery service request
-***************************************************
-
-Optional. This will update the "Last Edited By" field to indicate who last updated the request.
-
-Assign or unassign the delivery service request
-***********************************************
-
-Optional. Assignment is currently limited to current user. This is optional as fulfillment will auto-assign the request to the user doing the fulfillment.
-
-Reject the delivery service request
-***********************************
-
-Rejecting a delivery service request will set status to ``rejected`` and the request can no longer be modified. This will auto-assign the request to the user doing the rejection.
-
-Fulfill the delivery service request
-************************************
-
-Fulfilling a delivery service request will show the requested changes and, once committed, will apply the desired changes and set status to ``pending``. The request is pending because many types of changes will require cache config updates (aka queue updates) and/or a cdn snapshot. Once queue updates and/or cdn snapshot is complete, the request should be marked ``complete``.
-
-Complete the delivery service request
-*************************************
-
-Only after the delivery service request has been fulfilled and the changes have been applied can a delivery service request be marked as complete. Marking a delivery service as complete is currently a manual step because some changes require cache config updates (aka queue updates) and/or a cdn snapshot.
-Once that is done and the changes have been deployed, the request status should be changed from ``pending`` to ``complete``.
-
-
-Delete the delivery service request
-***********************************
-
-Delivery service requests with a status of draft or submitted can always be deleted entirely if appropriate.
-
-
-
-
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 a57473e..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 foo.images-c1.kabletown.net
-
- ; <<>> DiG 9.7.3-RedHat-9.7.3-2.el6 <<>> @tr.kabletown.net foo.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:
- ;foo.images-c1.kabletown.net. IN A
-
- ;; ANSWER SECTION:
- foo.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
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 4c6b6dc..0000000
--- a/docs/latest/_sources/admin/quick_howto/index.rst.txt
+++ /dev/null
@@ -1,43 +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.
-
-Traffic Ops
-===========
-
-.. toctree::
-
- multi_site.rst
- dnssec.rst
- federations.rst
- regionalgeo.rst
- anonymous_blocking.rst
- steering.rst
-
-Traffic Portal
-==============
-
-.. toctree::
-
- ds_requests.rst
-
-
-
-
-
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 6e0f0dd..0000000
--- a/docs/latest/_sources/admin/quick_howto/multi_site.rst.txt
+++ /dev/null
@@ -1,105 +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 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 [...]
-
-.. 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:
-
-.. image:: 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.
-
-.. 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 [...]
-
- 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.
-
-
-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 [...]
-
-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.
-
- .. image:: 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:
-
- +----------------------------------------+------------------+--------------------------+-------------------------+
- | 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:: 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.
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 36fd508..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, [...]
-
-* “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://foo.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://foo.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://foo.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="-"
-
-
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 96ae5bd..0000000
--- a/docs/latest/_sources/admin/quick_howto/steering.rst.txt
+++ /dev/null
@@ -1,111 +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 or orders to target delivery services. Assignments must either have a value for weight or order, but not both. The value of weight must be a positive integer, while the value of order can be any integer. 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"
- }
- {
- "order": -1,
- "deliveryService": "target-deliveryservice-3"
- }
- {
- "order": 3,
- "deliveryService": "target-deliveryservice-4"
- }
- ]
- }
-
-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"
- }
- {
- "order": -1,
- "deliveryService": "target-deliveryservice-3"
- }
- {
- "order": 3,
- "deliveryService": "target-deliveryservice-4"
- }
- ]
- }
-
-7) Any requests to Traffic Router for the steering delivery service should now be routed to target delivery services based on configured weight or order. Example: ``curl -Lvs http://foo.steering-ds.cdn.kabletown.net/bar``
-
diff --git a/docs/latest/_sources/admin/traffic_monitor.rst.txt b/docs/latest/_sources/admin/traffic_monitor.rst.txt
deleted file mode 100644
index 859000a..0000000
--- a/docs/latest/_sources/admin/traffic_monitor.rst.txt
+++ /dev/null
@@ -1,177 +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.
-..
-
-***************************************
-Traffic Monitor Administration (Legacy)
-***************************************
-
-.. _rl-tm-java:
-
-* These instructions are for the legacy Java Traffic Monitor, for the new Golang version, see :ref:`here <rl-tm-golang>`.
-
-Installing Traffic Monitor
-==========================
-The following are requirements to ensure an accurate set up:
-
-* CentOS 6
-* 4 vCPUs
-* 8GB RAM
-* Successful install of Traffic Ops
-* Tomcat
-* Administrative access to the Traffic Ops
-* Physical address of the site
-* perl-JSON
-* perl-WWW-Curl
-
-#. Add the Traffic Monitor server into Traffic Ops using 'Servers' -> 'Add Server'. Set the 'Type' field to 'RASCAL'.
-
-#. Make sure the FQDN of the Traffic Monitor is resolvable in DNS.
-
-#. Get the Traffic Monitor RPM.
-
- Sample command: ::
-
- wget http://traffic-control-cdn.net/downloads/1.7.0/RELEASE-1.7.0/traffic_monitor-1.7.0-3908.5b77f60f.el6.x86_64.rpm
-
-#. Install Traffic Monitor and Perl modules: ::
-
- sudo yum -y install traffic_monitor-*.rpm perl-JSON perl-WWW-Curl
-
-#. Take the config from Traffic Ops: ::
-
- sudo /opt/traffic_monitor/bin/traffic_monitor_config.pl https://<traffic-ops-URL> <traffic-ops-user>:<traffic-ops-password> prompt
-
- Sample session: ::
-
- traffic_mon # /opt/traffic_monitor/bin/traffic_monitor_config.pl https://traffic-ops.cdn.kabletown.net admin:kl0tevax prompt
- DEBUG: traffic_ops selected: https://traffic-ops.cdn.kabletown.net
- DEBUG: traffic_ops login: admin:kl0tevax
- DEBUG: Config write mode: prompt
- DEBUG: Found profile from traffic_ops: RASCAL_CDN
- DEBUG: Found CDN name from traffic_ops: kabletown_cdn
- DEBUG: Found location for rascal-config.txt from traffic_ops: /opt/traffic_monitor/conf
- WARN: Param not in traffic_ops: allow.config.edit description: Allow the running configuration to be edited through the UI Using default value of: false
- WARN: Param not in traffic_ops: default.accessControlAllowOrigin description: The value for the header: Access-Control-Allow-Origin for published jsons... should be narrowed down to TMs Using default value of: *
- WARN: Param not in traffic_ops: default.connection.timeout description: Default connection time for all queries (cache, peers, TM) Using default value of: 2000
- WARN: Param not in traffic_ops: hack.forceSystemExit description: Call System.exit on shutdown Using default value of: false
- WARN: Param not in traffic_ops: hack.peerOptimistic description: The assumption of a caches availability when unknown by peers Using default value of: true
- WARN: Param not in traffic_ops: hack.publishDsStates description: If true, the delivery service states will be included in the CrStates.json Using default value of: true
- WARN: Param not in traffic_ops: health.ds.interval description: The polling frequency for calculating the deliveryService states Using default value of: 1000
- WARN: Param not in traffic_ops: health.ds.leniency description: The amount of time before the deliveryService disregards the last update from a non-responsive cache Using default value of: 30000
- WARN: Param not in traffic_ops: health.event-count description: The number of historical events that will be kept Using default value of: 200
- WARN: Param not in traffic_ops: health.polling.interval description: The polling frequency for getting the states from caches Using default value of: 5000
- WARN: Param not in traffic_ops: health.startupMinCycles description: The number of query cycles that must be completed before this Traffic Monitor will start reporting Using default value of: 2
- WARN: Param not in traffic_ops: health.timepad description: A delay between each separate cache query Using default value of: 10
- WARN: Param not in traffic_ops: peers.polling.interval description: Polling frequency for getting states from peer monitors Using default value of: 5000
- WARN: Param not in traffic_ops: peers.polling.url description: The url for current, unfiltered states from peer monitors Using default value of: http://${hostname}/publish/CrStates?raw
- WARN: Param not in traffic_ops: peers.threadPool description: The number of threads given to the pool for querying peers Using default value of: 1
- WARN: Param not in traffic_ops: tm.auth.url description: The url for the authentication form Using default value of: https://${tmHostname}/login
- WARN: Param not in traffic_ops: tm.crConfig.json.polling.url description: Url for the cr-config (json) Using default value of: https://${tmHostname}/CRConfig-Snapshots/${cdnName}/CRConfig.json
- WARN: Param not in traffic_ops: tm.healthParams.polling.url description: The url for the heath params (json) Using default value of: https://${tmHostname}/health/${cdnName}
- WARN: Param not in traffic_ops: tm.polling.interval description: The polling frequency for getting updates from TM Using default value of: 10000
- DEBUG: allow.config.edit needed in config, but does not exist in config on disk.
- DEBUG: cdnName value on disk () does not match value needed in config (kabletown_cdn).
- DEBUG: default.accessControlAllowOrigin needed in config, but does not exist in config on disk.
- DEBUG: default.connection.timeout needed in config, but does not exist in config on disk.
- DEBUG: hack.forceSystemExit needed in config, but does not exist in config on disk.
- DEBUG: hack.peerOptimistic needed in config, but does not exist in config on disk.
- DEBUG: hack.publishDsStates needed in config, but does not exist in config on disk.
- DEBUG: health.ds.interval needed in config, but does not exist in config on disk.
- DEBUG: health.ds.leniency needed in config, but does not exist in config on disk.
- DEBUG: health.startupMinCycles needed in config, but does not exist in config on disk.
- DEBUG: health.timepad value on disk (20) does not match value needed in config (10).
- DEBUG: peers.polling.interval needed in config, but does not exist in config on disk.
- DEBUG: peers.threadPool needed in config, but does not exist in config on disk.
- DEBUG: tm.auth.password value on disk () does not match value needed in config (kl0tevax).
- DEBUG: tm.auth.username value on disk () does not match value needed in config (admin).
- DEBUG: tm.hostname value on disk () does not match value needed in config (traffic-ops.cdn.kabletown.net).
- DEBUG: Proposed traffic_monitor_config:
- {
- "traffic_monitor_config":{
- "default.accessControlAllowOrigin":"*",
- "health.startupMinCycles":"2",
- "tm.auth.password":"kl0tevax",
- "tm.auth.url":"https://${tmHostname}/login",
- "tm.healthParams.polling.url":"https://${tmHostname}/health/${cdnName}",
- "allow.config.edit":"false",
- "tm.crConfig.json.polling.url":"https://${tmHostname}/CRConfig-Snapshots/${cdnName}/CRConfig.json",
- "tm.auth.username":"admin",
- "peers.polling.url":"http://${hostname}/publish/CrStates?raw",
- "health.timepad":"10",
- "hack.publishDsStates":"true",
- "default.connection.timeout":"2000",
- "health.ds.interval":"1000",
- "peers.polling.interval":"5000",
- "hack.forceSystemExit":"false",
- "health.ds.leniency":"30000",
- "cdnName":"kabletown_cdn",
- "peers.threadPool":"1",
- "tm.polling.interval":"10000",
- "health.polling.interval":"5000",
- "health.event-count":"200",
- "hack.peerOptimistic":"true",
- "tm.hostname":"traffic-ops.cdn.kabletown.net"
- }
- }
- ----------------------------------------------
- ----OK to write this config to disk? (Y/n) [n]y
- ----------------------------------------------
- ----------------------------------------------
- ----OK to write this config to disk? (Y/n) [n]Y
- ----------------------------------------------
- DEBUG: Writing /opt/traffic_monitor/conf/traffic_monitor_config.js
- traffic_mon #
-
-#. Update the 'allow_ip' and 'allow_ip6' parameters in the profiles of all caches defined in traffic ops, both edge and mid,
- with the address of the traffic monitor being installed, so that the traffic servers will allow this Traffic Monitor
- to access the astats plugin.
- For details see :ref:`rl-param-prof` in the *Configuring Traffic Ops* section.
-
-#. Start Tomcat: ``sudo service tomcat start`` ::
-
- Using CATALINA_BASE: /opt/tomcat
- Using CATALINA_HOME: /opt/tomcat
- Using CATALINA_TMPDIR: /opt/tomcat/temp
- Using JRE_HOME: /usr
- Using CLASSPATH:/opt/tomcat/bin/bootstrap.jar
- Using CATALINA_PID:/var/run/tomcat/tomcat.pid
- Starting tomcat [ OK ]
-
-#. Configure tomcat to start automatically: ``sudo chkconfig tomcat on``
-
-#. Verify Traffic Monitor is running by pointing your browser to port 80 on the Traffic Monitor host:
-
- * The 'Cache States' tab should display all Mid and Edge caches configured in Traffic Ops.
- * The 'DeliveryService States' tab should display all delivery services configured in Traffic Ops.
-
-#. In Traffic Ops servers table, click 'Edit' for this server, then click 'Online'.
-
-
-Configuring Traffic Monitor
-===========================
-
-Configuration Overview
-----------------------
-Traffic Monitor is configured using its JSON configuration file, ``/opt/traffic_monitor/conf/traffic_monitor_config.js``.
-This file is created by ``traffic_monitor_config.pl`` script, and among other things, it contains the Traffic Ops URL and the user:password
-specified during the invocation of that script.
-
-When started, Traffic Monitor uses this basic configuration to downloads its configuration from Traffic Ops, and begins polling caches.
-Once a configurable number of polling cycles completes, health protocol state is available via RESTful JSON endpoints.
-
-
-Troubleshooting and log files
-=============================
-Traffic Monitor log files are in ``/opt/traffic_monitor/var/log/``, and tomcat log files are in ``/opt/tomcat/logs/``.
diff --git a/docs/latest/_sources/admin/traffic_monitor_golang.rst.txt b/docs/latest/_sources/admin/traffic_monitor_golang.rst.txt
deleted file mode 100644
index 649cf78..0000000
--- a/docs/latest/_sources/admin/traffic_monitor_golang.rst.txt
+++ /dev/null
@@ -1,65 +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.
-..
-
-******************************
-Traffic Monitor Administration
-******************************
-
-.. _rl-tm-golang:
-
-* These instructions are for the Golang Traffic Monitor, for the legacy Java version, see :ref:`here <rl-tm-java>`.
-
-Installing Traffic Monitor
-==========================
-
-The following are requirements to ensure an accurate set up:
-
-* CentOS 6+
-* 8 vCPUs
-* 16GB RAM
-* Successful install of Traffic Ops
-* Administrative access to the Traffic Ops
-* Physical address of the site
-
-1. Enter the Traffic Monitor server into Traffic Ops
-2. Make sure the FQDN of the Traffic Monitor is resolvable in DNS.
-3. Install Traffic Monitor: ``sudo yum -y install traffic_monitor``
-4. Configure Traffic Monitor. See :ref:`here <rl-tm-configure>`
-5. Start the service: ``sudo service traffic_monitor start`` ::
-
- Starting traffic_monitor:
-
-6. Verify Traffic Monitor is running by pointing your browser to port 80 on the Traffic Monitor host.
-
-Configuring Traffic Monitor
-===========================
-
-Configuration Overview
-----------------------
-
-.. _rl-tm-configure:
-
-Traffic Monitor is configured via two JSON configuration files, ``traffic_ops.cfg`` and ``traffic_monitor.cfg``, by default located in the ``conf`` directory in the install location.
-
-The ``traffic_ops.cfg`` config contains Traffic Ops connection information. Specify the URL, username, and password for the instance of Traffic Ops for which this Traffic Monitor is a member.
-
-The ``traffic_monitor.cfg`` config contains log file locations, as well as detailed application configuration variables, such as processing flush times and initial poll intervals.
-
-Once started with the correct configuration, Traffic Monitor downloads its configuration from Traffic Ops and begins polling caches. Once every cache has been polled, health protocol state is available via RESTful JSON endpoints.
-
-
-Troubleshooting and log files
-=============================
-Traffic Monitor log files are in ``/opt/traffic_monitor/var/log/``.
diff --git a/docs/latest/_sources/admin/traffic_ops/configuration.rst.txt b/docs/latest/_sources/admin/traffic_ops/configuration.rst.txt
deleted file mode 100644
index c63a5ec..0000000
--- a/docs/latest/_sources/admin/traffic_ops/configuration.rst.txt
+++ /dev/null
@@ -1,322 +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.
-..
-
-Traffic Ops - Configuring
-%%%%%%%%%%%%%%%%%%%%%%%%%
-
-Follow the steps below to configure the newly installed Traffic Ops Instance.
-
-Installing the SSL Cert
-=======================
-By default, Traffic Ops runs as an SSL web server, and a certificate needs to be installed.
-
-Self-signed Certificate (Development)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
- Example Procedure::
-
- $ openssl genrsa -des3 -passout pass:x -out localhost.pass.key 2048
- Generating RSA private key, 2048 bit long modulus
- ...
- $ openssl rsa -passin pass:x -in localhost.pass.key -out localhost.key
- writing RSA key
- $ rm localhost.pass.key
-
- $ openssl req -new -key localhost.key -out localhost.csr
- You are about to be asked to enter information that will be incorporated
- into your certificate request.
- What you are about to enter is what is called a Distinguished Name or a DN.
- There are quite a few fields but you can leave some blank
- For some fields there will be a default value,
- If you enter '.', the field will be left blank.
- -----
- Country Name (2 letter code) [XX]:US<enter>
- State or Province Name (full name) []:CO<enter>
- Locality Name (eg, city) [Default City]:Denver<enter>
- Organization Name (eg, company) [Default Company Ltd]: <enter>
- Organizational Unit Name (eg, section) []: <enter>
- Common Name (eg, your name or your server's hostname) []: <enter>
- Email Address []: <enter>
-
- Please enter the following 'extra' attributes
- to be sent with your certificate request
- A challenge password []: pass<enter>
- An optional company name []: <enter>
- $ openssl x509 -req -sha256 -days 365 -in localhost.csr -signkey localhost.key -out localhost.crt
- Signature ok
- subject=/C=US/ST=CO/L=Denver/O=Default Company Ltd
- Getting Private key
- $ sudo cp localhost.crt /etc/pki/tls/certs
- $ sudo cp localhost.key /etc/pki/tls/private
- $ sudo chown trafops:trafops /etc/pki/tls/certs/localhost.crt
- $ sudo chown trafops:trafops /etc/pki/tls/private/localhost.key
-
-Certificate from Certificate Authority (Production)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-.. Note:: You will need to know the appropriate answers when generating the certificate request file `trafficopss.csr` below.
-
-Example Procedure::
-
- $ openssl genrsa -des3 -passout pass:x -out trafficops.pass.key 2048
- Generating RSA private key, 2048 bit long modulus
- ...
- $ openssl rsa -passin pass:x -in trafficops.pass.key -out trafficops.key
- writing RSA key
- $ rm localhost.pass.key
-
- Generate the Certificate Signing Request (CSR) file needed for Certificate Authority (CA) request.
-
- $ openssl req -new -key trafficops.key -out trafficops.csr
- You are about to be asked to enter information that will be incorporated
- into your certificate request.
- What you are about to enter is what is called a Distinguished Name or a DN.
- There are quite a few fields but you can leave some blank
- For some fields there will be a default value,
- If you enter '.', the field will be left blank.
- -----
- Country Name (2 letter code) [XX]: <enter country code>
- State or Province Name (full name) []: <enter state or province>
- Locality Name (eg, city) [Default City]: <enter locality name>
- Organization Name (eg, company) [Default Company Ltd]: <enter organization name>
- Organizational Unit Name (eg, section) []: <enter organizational unit name>
- Common Name (eg, your name or your server's hostname) []: <enter server's hostname name>
- Email Address []: <enter e-mail address>
-
- Please enter the following 'extra' attributes
- to be sent with your certificate request
- A challenge password []: <enter challenge password>
- An optional company name []: <enter>
- $ sudo cp trafficops.key /etc/pki/tls/private
- $ sudo chown trafops:trafops /etc/pki/tls/private/trafficops.key
-
- You must then take the output file trafficops.csr and submit a request to your Certificate Authority (CA).
- Once you get approved and receive your trafficops.crt file:
-
- $ sudo cp trafficops.crt /etc/pki/tls/certs
- $ sudo chown trafops:trafops /etc/pki/tls/certs/trafficops.crt
-
- If necessary, install the CA certificates .pem and .crt in /etc/pki/tls/certs.
-
- You will need to update the file /opt/traffic_ops/app/conf/cdn.conf with the following changes:
- ...
- e.g. given trafficops.crt and trafficops.key
- 'hypnotoad' => ...
- 'listen' => 'https://[::]:443?cert=/etc/pki/tls/certs/trafficops.crt&key=/etc/pki/tls/private/trafficops.key&ca=/etc/pki/tls/certs/localhost.ca&verify=0x00&ciphers=AES128-GCM-SHA256:HIGH:!RC4:!MD5:!aNULL:!EDH:!ED'
- ...
-
-
-Content Delivery Networks
-=========================
-
-.. _rl-param-prof:
-
-Profile Parameters
-======================
-Many of the settings for the different servers in a Traffic Control CDN are controlled by parameters in the parameter view of Traffic Ops. Parameters are grouped in profiles and profiles are assigned to a server or a deliveryservice. For a typical cache there are hundreds of configuration settings to apply. The Traffic Ops parameter view contains the defined settings. To make life easier, Traffic Ops allows for duplication, comparison, import and export of Profiles. Traffic Ops also has [...]
-
-
-.. index::
- Global Profile
-
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Config file | Value |
-+==========================+===============+=======================================================================================================================================+
-| tm.url | global | The URL where this Traffic Ops instance is being served from. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| tm.rev_proxy.url | global | Not required. The URL where the Traffic Ops Config file cache instance is being served from. Requires Traffic Ops ORT 2.1 and above. |
-| | | When configured, ORT will request configuration files via this fqdn, which should be setup as a reverse proxy to the Traffic Ops host |
-| | | or hosts. Suggested cache lifetime for these files is ~3 minutes or less. This setting allows for greater scaleability of a CDN |
-| | | maintained by Traffic Ops by caching configuration files of profile and cdn scope. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| tm.toolname | global | The name of the Traffic Ops tool. Usually "Traffic Ops". Used in the About screen and in the comments headers of the files generated. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| tm.infourl | global | This is the "for more information go here" URL, which is visible in the About page. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| tm.logourl | global | This is the URL of the logo for Traffic Ops and can be relative if the logo is under traffic_ops/app/public. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| tm.instance_name | global | The name of the Traffic Ops instance. Can be used when multiple instances are active. Visible in the About page. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| tm.traffic_mon_fwd_proxy | global | When collecting stats from Traffic Monitor, Traffic Ops uses this forward proxy to pull the stats through. |
-| | | This can be any of the MID tier caches, or a forward cache specifically deployed for this purpose. Setting |
-| | | this variable can significantly lighten the load on the Traffic Monitor system and it is recommended to |
-| | | set this parameter on a production system. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| geolocation.polling.url | CRConfig.json | The location to get the GeoLiteCity database from. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| geolocation6.polling.url | CRConfig.json | The location to get the IPv6 GeoLiteCity database from. |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-| maxmind.default.override | CRConfig.json | The destination geo coordinates to use for client location when maxmind returns a default location that matches the country code. |
-| | | This parameter can be specified multiple times with different values to support default overrides for multiple countries. |
-| | | Format: <CountryCode>;<Lat>,<Long> Ex: US;37.751,-97.822 |
-+--------------------------+---------------+---------------------------------------------------------------------------------------------------------------------------------------+
-
-These parameters should be set to reflect the local environment.
-
-
-After running the postinstall script, Traffic Ops has the following profiles pre-loaded:
-
-+----------+-------------------------------------------------------------------------------------------------+
-| Name | Description |
-+==========+=================================================================================================+
-| EDGE1 | The profile to be applied to the latest supported version of ATS, when running as an EDGE cache |
-+----------+-------------------------------------------------------------------------------------------------+
-| TR1 | The profile to be applied to the latest version of Traffic Router |
-+----------+-------------------------------------------------------------------------------------------------+
-| TM1 | The profile to be applied to the latest version of Traffic Monitor |
-+----------+-------------------------------------------------------------------------------------------------+
-| MID1 | The profile to be applied to the latest supported version of ATS, when running as an MID cache |
-+----------+-------------------------------------------------------------------------------------------------+
-| RIAK_ALL | Riak profile for all CDNs to be applied to the Traffic Vault servers |
-+----------+-------------------------------------------------------------------------------------------------+
-
-.. Note:: The Traffic Server profiles contain some information that is specific to the hardware being used (most notably the disk configuration), so some parameters will have to be changed to reflect your configuration. Future releases of Traffic Control will separate the hardware and software profiles so it is easier to "mix-and-match" different hardware configurations.
-
-Below is a list of cache parameters that are likely to need changes from the default profiles shipped with Traffic Ops:
-
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| Name | Config file | Description |
-+==========================+===================+=========================================================================================================================+
-| allow_ip | astats.config | This is a comma separated list of IPv4 CIDR blocks that will have access to the astats statistics on the caches. |
-| | | The Traffic Monitor IP addresses have to be included in this, if they are using IPv4 to monitor the caches. |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| allow_ip6 | astats.config | This is a comma separated list of IPv6 CIDR blocks that will have access to the astats statistics on the caches. |
-| | | The Traffic Monitor IP addresses have to be included in this, if they are using IPv6 to monitor the caches. |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| Drive_Prefix | storage.config | The device path start of the disks. For example, if you have ``/dev/sda`` through ``/dev/sdf`` set this to ``/dev/sd`` |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| Drive_Letters | storage.config | The letter part of the disks, in the same example as above set this to ``a,b,c,d,e,f`` |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| purge_allow_ip | ip_allow.config | The IP address range that is allowed to execute the PURGE method on the caches (not related to :ref:`rl-purge`) |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_masklen_v4 | ip_allow.config | The masklen to use when coalescing v4 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_number_v4 | ip_allow.config | The number to use when coalescing v4 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_masklen_v6 | ip_allow.config | The masklen to use when coalescing v6 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| coalesce_masklen_v6 | ip_allow.config | The masklen to use when coalescing v6 networks into one line using http://search.cpan.org/~miker/NetAddr-IP-4.078/IP.pm |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| health.threshold.loadavg | rascal.properties | The Unix load average at which Traffic Router will stop sending traffic to this cache |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| health.threshold.\\ | rascal.properties | The amount of bandwidth that Traffic Router will try to keep available on the cache. |
-| availableBandwidthInKbps | | For example: "">1500000" means stop sending new traffic to this cache when traffic is at 8.5Gbps on a 10Gbps interface. |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-
-Below is a list of Traffic Server plugins that need to be configured in the parameter table:
-
-+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
-| Name | Config file | Description | Details |
-+==================+===============+======================================================+============================================================================================================+
-| astats_over_http | package | The package version for the astats_over_http plugin. | `astats_over_http <http://trafficcontrol.apache.org/downloads/index.html>`_ |
-+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
-| trafficserver | package | The package version for the trafficserver plugin. | `trafficserver <http://trafficcontrol.apache.org/downloads/index.html>`_ |
-+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
-| regex_revalidate | plugin.config | The config to be used for regex_revalidate. | `regex_revalidate <https://docs.trafficserver.apache.org/en/5.3.x/reference/plugins/regex_remap.en.html>`_ |
-| | | For example: --config regex_revalidate.config | |
-+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
-| remap_stats | plugin.config | The config to be used for remap_stats. | `remap_stats <https://github.com/apache/trafficserver/tree/master/plugins/experimental/remap_stats>`_ |
-| | | Value is left blank. | |
-+------------------+---------------+------------------------------------------------------+------------------------------------------------------------------------------------------------------------+
-
-Below is a list of cache parameters for special configuration, which are unlikely to need changes, but may be useful in particular circumstances:
-
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-| Name | Config file | Description |
-+==========================+===================+=========================================================================================================================+
-| not_a_parent | parent.config | This is a boolean flag and is considered true if it exists and has any value except 'false'. |
-| | | This prevents servers with this parameter in their profile from being inserted into the parent.config generated for |
-| | | servers with this server's cachegroup as a parent of their cachegroup. This is primarily useful for when edge caches |
-| | | are configured to have a cachegroup of other edge caches as parents (a highly unusual configuration), and it is |
-| | | necessary to exclude some, but not all, edges in the parent cachegroup from the parent.config (for example, because they|
-| | | lack necessary capabilities), but still have all edges in the same cachegroup in order to take traffic from ordinary |
-| | | delivery services at that cachegroup's geo location. Once again, this is a highly unusual scenario, and under ordinary |
-| | | circumstances this parameter should not exist. |
-+--------------------------+-------------------+-------------------------------------------------------------------------------------------------------------------------+
-
-
-Regions, Locations and Cache Groups
-===================================
-All servers have to have a `location`, which is their physical location. Each location is part of a `region`, and each region is part of a `division`. For Example, ``Denver`` could be a location in the ``Mile High`` region and that region could be part of the ``West`` division. Enter your divisions first in `Misc->Divisions`, then enter the regions in `Misc->Regions`, referencing the divisions entered, and finally, enter the physical locations in `Misc->Locations`, referencing the regio [...]
-
-All servers also have to be part of a `cache group`. A cache group is a logical grouping of caches, that don't have to be in the same physical location (in fact, usually a cache group is spread across minimally 2 physical Locations for redundancy purposes), but share geo coordinates for content routing purposes. JvD to add more.
-
-
-
-Configuring Content Purge
-=========================
-Content purge using ATS is not simple; there is no file system to delete files/directories from, and in large caches it can be hard to delete a simple regular expression from the cache. This is why Traffic Control uses the `Regex Revalidate Plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_revalidate.en.html>`_ to purge content from the system. We don't actually remove the content, we have a check that gets run before each request on each cache to see if t [...]
-
-Content Purge is controlled by the following parameters in the profile of the cache:
-
-+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Config file | Description | Details |
-+======================+=========================+==================================================+=========================================================================================================================================================+
-| location | regex_revalidate.config | What location the file should be in on the cache | The presence of this parameter tells ort to distribute this file; delete this parameter from the profile if this file is distributed using other means. |
-+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
-| maxRevalDurationDays | regex_revalidate.config | The maximum time a purge can be active | To prevent a build up of many checks before each request, this is longest time the system will allow |
-+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
-| regex_revalidate | plugin.config | The config to be used for regex_revalidate. | `regex_revalidate <https://docs.trafficserver.apache.org/en/5.3.x/reference/plugins/regex_remap.en.html>`_ |
-| | | For example: --config regex_revalidate.config | |
-+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
-| use_reval_pending | global | Configures Traffic Ops to use separate | When this flag is in use ORT will check for a new regex_revalidate.config every 60 seconds in syncds mode during the dispersal timer. This will |
-| | | reval_pending flag for each cache. | also allow ORT to be run in revalidate mode, which will check for and clear the reval_pending flag. This can be set to run via cron task. |
-| | | | Enable with a value of 1. Use of this feature requires Traffic Ops 2.1 and above. Parameter should be assigned to the GLOBAL profile. |
-+----------------------+-------------------------+--------------------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-
-Note that the TTL the adminstrator enters in the purge request should be longer than the TTL of the content to ensure the bad content will not be used. If the CDN is serving content of unknown, or unlimited TTL, the administrator should consider using `proxy-config-http-cache-guaranteed-min-lifetime <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-config-http-cache-guaranteed-min-lifetime>`_ to limit the maximum time an object can be in the [...]
-
-
-
-.. _Creating-CentOS-Kickstart:
-
-Creating the CentOS Kickstart File
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-The kickstart file is a text file, containing a list of items, each identified by a keyword. You can create it by using the Kickstart Configurator application, or writing it from scratch. The Red Hat Enterprise Linux installation program also creates a sample kickstart file based on the options that you selected during installation. It is written to the file ``/root/anaconda-ks.cfg``. This file is editable using most text editors that can save files as ASCII text.
-
-To generate ISO, the CentOS Kickstart is necessary:
-
-1. Create a kickstart file.
-2. Create a boot media with the kickstart file or make the kickstart file available on the network.
-3. Make the installation tree available.
-4. Start the kickstart installation.
-
-Create a ks.src file in the root of the selection location. See the example below:
-
-::
-
-
- mkdir newdir
- cd newdir/
- cp -r ../centos65/* .
- vim ks.src
- vim isolinux/isolinux.cfg
- cd vim osversions.cfg
- vim osversions.cfg
-
-
-This is a standard kickstart formatted file that the generate ISO process uses to create the kickstart (ks.cfg) file for the install. The generate ISO process uses the ks.src, overwriting any information set in the Generate ISO tab in Traffic Ops, creating ks.cfg.
-
-.. Note:: Streamline your install folder for under 1GB, which assists in creating a CD.
-
-.. seealso:: For in-depth instructions, please see `Kickstart Installation <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-howuse.html>`_
-
-
-Configuring the Go Application
-==============================
-Traffic Ops is in the process of migrating from Perl to Go, and currently runs as two applications. The Go application serves all endpoints which have been rewritten in the Go language, and transparently proxies all other requests to the old Perl application. Both applications are installed by the RPM, and both run as a single service. When the project has fully migrated to Go, the Perl application will be removed, and the RPM and service will consist solely of the Go application.
-
-By default, the postinstall script configures the Go application to behave and transparently serve as the old Perl Traffic Ops did in previous versions. This includes reading the old ``cdn.conf`` and ``database.conf`` config files, and logging to the old ``access.log`` location. However, if you wish to customize the Go Traffic Ops application, you can do so by running it with the ``-oldcfg=false`` argument. By default, it will then look for a config file in ``/opt/traffic_ops/conf/traffi [...]
diff --git a/docs/latest/_sources/admin/traffic_ops/default_profiles.rst.txt b/docs/latest/_sources/admin/traffic_ops/default_profiles.rst.txt
deleted file mode 100644
index 9b629be..0000000
--- a/docs/latest/_sources/admin/traffic_ops/default_profiles.rst.txt
+++ /dev/null
@@ -1,53 +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.
-..
-
-.. index::
- Traffic Ops - Default Profiles
-
-.. _rl-to-default-profiles:
-
-Traffic Ops - Default Profiles
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-Traffic Ops has the concept of :ref:`rl-working-with-profiles`, which are an integral function within Traffic Ops. To get started, a set of default Traffic Ops profiles need to be imported into Traffic Ops
-to get started to support Traffic Control components Traffic Router, Traffic Monitor, and Apache Traffic Server.
-
-`Download Default Profiles from here <http://trafficcontrol.incubator.apache.org/downloads/profiles/>`_
-
-.. _rl-to-profiles-min-needed:
-
-Minimum Traffic Ops Profiles needed
------------------------------------
- * EDGE_ATS_<version>_<platform>_PROFILE.traffic_ops
- * MID_ATS_<version>_<platform>_PROFILE.traffic_ops
- * TRAFFIC_MONITOR_PROFILE.traffic_ops
- * TRAFFIC_ROUTER_PROFILE.traffic_ops
- * TRAFFIC_STATS_PROFILE.traffic_ops
-
-
-
-Steps to Import a Profile
--------------------------
-1. Sign into Traffic Ops
-
-2. Navigate to 'Parameters->Select Profile'
-
-3. Click the "Import Profile" button at the bottom
-
-4. Choose the specific profile you want to import from your download directory
-
-5. Click 'Submit'
-
-6. Continue these steps for each :ref:`rl-to-profiles-min-needed` above
diff --git a/docs/latest/_sources/admin/traffic_ops/extensions.rst.txt b/docs/latest/_sources/admin/traffic_ops/extensions.rst.txt
deleted file mode 100644
index 4aceebb..0000000
--- a/docs/latest/_sources/admin/traffic_ops/extensions.rst.txt
+++ /dev/null
@@ -1,88 +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.
-..
-
-.. _admin-to-ext-script:
-
-Managing Traffic Ops Extensions
-*******************************
-
-Each script is a separate bash script located in ``$TO_HOME/bin/checks/``.
-
-The extensions must be registered with Traffic Ops in order to display a column on the Server Check page. The list of currently registered extensions can be listed by running ``/opt/traffic_ops/app/bin/extensions -a``.
-
-The below extensions are automatically registered with the Traffic Ops database (``to_extension`` table) at install time (see ``traffic_ops/app/db/seeds.sql``). However, cron must still be configured to run these checks periodically.
-
-The scripts are called as follows: ::
-
-
- $TO_HOME/bin/checks/To<name>Check.pl -c "{\"base_url\": \",https://\"<traffic_ops_ip>\", \"check_name\": \"<check_name>\"}" -l <log level>
- where:
-
- <name> is the type of check script
- <traffic_ops_ip> is the IP address of the Traffic Ops Server
- <check_name> is the name of the check. For example: CDU, CHR, DSCP, MTU, etc...
- <log_level> is between 1 and 4, with 4 being the most verbose. This field is optional
-
-
-Example Cron File
-=================
-Edit with ``crontab -e``. You may need to adjust the path to your $TO_HOME to match your system.
-
-::
-
-
- PERL5LIB=/opt/traffic_ops/app/local/lib/perl5:/opt/traffic_ops/app/lib
-
- # IPv4 ping examples - The 'select: ["hostName","domainName"]' works but, if you want to check DNS resolution use FQDN.
- */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"10G\", \"select\": [\"hostName\",\"domainName\"]}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"10G\", \"select\": \"ipAddress\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"10G\", \"name\": \"IPv4 Ping\", \"select\": \"ipAddress\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1
-
- # IPv6 ping examples
- */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"10G6\", \"name\": \"IPv6 Ping\", \"select\": \"ip6Address\", \"syslog_facility\": \"local0\"}" >/dev/null 2>&1
- */15 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"10G6\", \"select\": \"ip6Address\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
-
- # iLO ping
- 18 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"ILO\", \"select\": \"iloIpAddress\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- 18 * * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"ILO\", \"name\": \"ILO ping\", \"select\": \"iloIpAddress\", \"syslog_facility\": \"local0\"}" >/dev/null 2>&1
-
- # MTU ping
- 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"MTU\", \"select\": \"ipAddress\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"MTU\", \"select\": \"ip6Address\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"MTU\", \"name\": \"Max Trans Unit\", \"select\": \"ipAddress\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1
- 45 0 * * * root /opt/traffic_ops/app/bin/checks/ToPingCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"MTU\", \"name\": \"Max Trans Unit\", \"select\": \"ip6Address\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1
-
- # FQDN
- 27 * * * * root /opt/traffic_ops/app/bin/checks/ToFQDNCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"FQDN\"" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- 27 * * * * root /opt/traffic_ops/app/bin/checks/ToFQDNCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"FQDN\", \"name\": \"DNS Lookup\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1
-
- # DSCP
- 36 * * * * root /opt/traffic_ops/app/bin/checks/ToDSCPCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"DSCP\", \"cms_interface\": \"eth0\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- 36 * * * * root /opt/traffic_ops/app/bin/checks/ToDSCPCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"DSCP\", \"name\": \"Delivery Service\", \"cms_interface\": \"eth0\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1
-
- # RTR
- 10 * * * * root /opt/traffic_ops/app/bin/checks/ToRTRCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"RTR\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- 10 * * * * root /opt/traffic_ops/app/bin/checks/ToRTRCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"RTR\", \"name\": \"Content Router Check\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1
-
- # CHR
- */15 * * * * root /opt/traffic_ops/app/bin/checks/ToCHRCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"CHR\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
-
- # CDU
- 20 * * * * root /opt/traffic_ops/app/bin/checks/ToCDUCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"CDU\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
-
- # ORT
- 40 * * * * ssh_key_edge_user /opt/traffic_ops/app/bin/checks/ToORTCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"ORT\"}" >> /var/log/traffic_ops/extensionCheck.log 2>&1
- 40 * * * * ssh_key_edge_user /opt/traffic_ops/app/bin/checks/ToORTCheck.pl -c "{\"base_url\": \"https://localhost\", \"check_name\": \"ORT\", \"name\": \"Operational Readiness Test\", \"syslog_facility\": \"local0\"}" > /dev/null 2>&1
-
diff --git a/docs/latest/_sources/admin/traffic_ops/installation.rst.txt b/docs/latest/_sources/admin/traffic_ops/installation.rst.txt
deleted file mode 100644
index d2eaec1..0000000
--- a/docs/latest/_sources/admin/traffic_ops/installation.rst.txt
+++ /dev/null
@@ -1,243 +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.
-..
-
-.. index::
- Traffic Ops - Installing
-
-.. _rl-to-install:
-
-Traffic Ops - Installing
-%%%%%%%%%%%%%%%%%%%%%%%%
-
-System Requirements
--------------------
-The user must have the following for a successful minimal install:
-
-* CentOS 7
-* 2 VMs with at least 2 vCPUs, 4GB RAM, 20 GB disk space each
-* Access to Centos Base and epel repositories
-* Access to `The Comprehensive Perl Archive Network (CPAN) <http://www.cpan.org/>`_
-
-As of version 2.0 only Postgres is supported as the database. This documentation assumes CentOS 7.2 and Postgresql 9.6.3 for a production install.
-
-.. highlight:: none
-
-Navigating the Install
------------------------
-To begin the install:
-
-1. Install Postgres
-
- For a production install it is best to install postgres on it's own server/VM. To install postgres, on the postgres host (pg) ::
-
- pg-$ sudo su -
- pg-# yum -y update
- pg-# yum -y install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm
- pg-# yum -y install postgresql96-server
- pg-$ su - postgres
- pg-$ /usr/pgsql-9.6/bin/initdb -A md5 -W #-W forces the user to provide a superuser (postgres) password
-
-
- Edit ``/var/lib/pgsql/9.6/data/pg_hba.conf`` to allow your traffic ops app server access. For example if you are going to install traffic ops on ``99.33.99.1`` add::
-
- host all all 99.33.99.1/32 md5
-
- to the appropriate section of this file. Edit the ``/var/lib/pgsql/9.6/data/postgresql.conf`` file to add the approriate listen_addresses or ``listen_addresses = '*'``, set ``timezone = 'UTC'``, and start the database: ::
-
- pg-$ exit
- pg-# systemctl enable postgresql-9.6
- pg-# systemctl start postgresql-9.6
- pg-# systemctl status postgresql-9.6
-
-
-2. Build Traffic Ops
-
- Build a Traffic Ops rpm using the instructions under the :ref:`dev-building` page.
-
-
-3. Install Postgresql
-
- Install the postgresql 9.6 yum repository access. ::
-
- to-$ sudo su -
- to-# yum -y install https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-centos96-9.6-3.noarch.rpm
-
-4. Install the rpm built in step 2. ::
-
- to-# yum -y install ./dist/traffic_ops-2.0.0-xxxx.yyyyyyy.el7.x86_64.rpm
-
-
- Install some additional packages that it depends on that were not installed as dependecies in the previous step (these are for the 2.0.0 install, this may change, but the pre-installs won't hurt): ::
-
- to-# yum -y install git
- to-# wget -q https://storage.googleapis.com/golang/go1.8.3.linux-amd64.tar.gz
- to-# tar -C /usr/local -xzf go1.8.3.linux-amd64.tar.gz
- to-# PATH=$PATH:/usr/local/go/bin # go bins are needed in the path for postinstall
- to-# go get bitbucket.org/liamstask/goose/cmd/goose
-
- At this point you should be able to login to the database from the ``to`` host to the ``pg`` host like: ::
-
- to-# psql -h 99.33.99.1 -U postgres
- Password for user postgres:
- psql (9.6.3)
- Type "help" for help.
-
- postgres=#
-
- Use this connectivity to create the user and database. In this example, we use user: ``traffic_ops``, password: ``tcr0cks``, database: ``traffic_ops``: ::
-
- to-# psql -U postgres -h 99.33.99.1 -c "CREATE USER traffic_ops WITH ENCRYPTED PASSWORD 'tcr0cks';"
- Password for user postgres:
- CREATE ROLE
- to-# createdb traffic_ops --owner traffic_ops -U postgres -h 99.33.99.1
- Password:
- to-#
-
-
- Now, run the following command as root: ``/opt/traffic_ops/install/bin/postinstall``
-
- The postinstall will first get all packages needed from CPAN. This may take a while, expect up to 30 minutes on the first install.
- If there are any prompts in this phase, please just answer with the defaults (some CPAN installs can prompt for install questions).
-
- When this phase is complete, you will see::
-
- Complete! Modules were installed into /opt/traffic_ops/app/local
-
- Some additional files will be installed, and then it will proceed with the next phase of the install, where it will ask you about the local environment for your CDN. Please make sure you remember all your answers and the database answers match the database information previously used to create the database.
-
-
- Example output::
-
- ===========/opt/traffic_ops/app/conf/production/database.conf===========
- Database type [Pg]:
- Database type: Pg
- Database name [traffic_ops]:
- Database name: traffic_ops
- Database server hostname IP or FQDN [localhost]: 99.33.99.1
- Database server hostname IP or FQDN: 99.33.99.1
- Database port number [5432]:
- Database port number: 5432
- Traffic Ops database user [traffic_ops]:
- Traffic Ops database user: traffic_ops
- Password for Traffic Ops database user:
- Re-Enter Password for Traffic Ops database user:
- Writing json to /opt/traffic_ops/app/conf/production/database.conf
- Database configuration has been saved
- ===========/opt/traffic_ops/app/db/dbconf.yml===========
- Database server root (admin) user [postgres]:
- Database server root (admin) user: postgres
- Password for database server admin:
- Re-Enter Password for database server admin:
- Download Maxmind Database? [yes]:
- Download Maxmind Database?: yes
- ===========/opt/traffic_ops/app/conf/cdn.conf===========
- Generate a new secret? [yes]:
- Generate a new secret?: yes
- Number of secrets to keep? [10]:
- Number of secrets to keep?: 10
- Not setting up ldap
- ===========/opt/traffic_ops/install/data/json/users.json===========
- Administration username for Traffic Ops [admin]:
- Administration username for Traffic Ops: admin
- Password for the admin user:
- Re-Enter Password for the admin user:
- Writing json to /opt/traffic_ops/install/data/json/users.json
- ===========/opt/traffic_ops/install/data/json/openssl_configuration.json===========
- Do you want to generate a certificate? [yes]:
- Country Name (2 letter code): US
- State or Province Name (full name): CO
- Locality Name (eg, city): Denver
- Organization Name (eg, company): Super CDN, Inc
- Organizational Unit Name (eg, section):
- Common Name (eg, your name or your server's hostname):
- RSA Passphrase:
- Re-Enter RSA Passphrase:
- ===========/opt/traffic_ops/install/data/json/profiles.json===========
- Traffic Ops url [https://localhost]:
- Traffic Ops url: https://localhost
- Human-readable CDN Name. (No whitespace, please) [kabletown_cdn]: blue_cdn
- Human-readable CDN Name. (No whitespace, please): blue_cdn
- DNS sub-domain for which your CDN is authoritative [cdn1.kabletown.net]: blue-cdn.supercdn.net
- DNS sub-domain for which your CDN is authoritative: blue-cdn.supercdn.net
- Writing json to /opt/traffic_ops/install/data/json/profiles.json
- Downloading Maxmind data
- --2017-06-11 15:32:41-- http://geolite.maxmind.com/download/geoip/database/GeoLite2-City.mmdb.gz
- Resolving geolite.maxmind.com (geolite.maxmind.com)... 2400:cb00:2048:1::6810:262f, 2400:cb00:2048:1::6810:252f, 104.16.38.47, ...
- Connecting to geolite.maxmind.com (geolite.maxmind.com)|2400:cb00:2048:1::6810:262f|:80... connected.
-
- ... much SQL output skipped
-
- Starting Traffic Ops
- Restarting traffic_ops (via systemctl): [ OK ]
- Waiting for Traffic Ops to restart
- Success! Postinstall complete.
-
- to-# ifconfig
-
-
- Explanation of the information that needs to be provided:
-
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Field | Description |
- +====================================================+==============================================================================================+
- | Database type | Pg |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Database name | The name of the database Traffic Ops uses to store the configuration information |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Database server hostname IP or FQDN | The hostname of the database server |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Database port number | The database port number |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Traffic Ops database user | The username Traffic Ops will use to read/write from the database |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Password for traffic ops | The password for the above database user |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Database server root (admin) user name | Privileged database user that has permission to create the database and user for Traffic Ops |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Database server root (admin) user password | The password for the above privileged database user |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Traffic Ops url | The URL to connect to this instance of Traffic Ops, usually https://<traffic ops host FQDN>/ |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Human-readable CDN Name | The name of the first CDN traffic Ops will be managing |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | DNS sub-domain for which your CDN is authoritative | The DNS domain that will be delegated to this Traffic Control CDN |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Administration username for Traffic Ops | The Administration (highest privilege) Traffic Ops user to create; |
- | | use this user to login for the first time and create other users |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
- | Password for the admin user | The password for the above user |
- +----------------------------------------------------+----------------------------------------------------------------------------------------------+
-
-
-Traffic Ops is now installed!
-
-
-**To complete the Traffic Ops Setup See:** :ref:`rl-to-default-profiles`
-
-
-Upgrading Traffic Ops
-=====================
-To upgrade:
-
-#. Enter the following command:``service traffic_ops stop``
-#. Enter the following command:``yum upgrade traffic_ops``
-#. Enter the following command from the /opt/traffic_ops/app directory:
- ``PERL5LIB=/opt/traffic_ops/app/lib:/opt/traffic_ops/app/local/lib/perl5 ./db/admin.pl --env production upgrade``
-#. See :ref:`rl-to-install` to run postinstall.
-#. Enter the following command:``service traffic_ops start``
-
-
-
-
diff --git a/docs/latest/_sources/admin/traffic_ops/migration_from_10_to_20.rst.txt b/docs/latest/_sources/admin/traffic_ops/migration_from_10_to_20.rst.txt
deleted file mode 100644
index 4133fee..0000000
--- a/docs/latest/_sources/admin/traffic_ops/migration_from_10_to_20.rst.txt
+++ /dev/null
@@ -1,88 +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.
-..
-
-.. index::
- Traffic Ops - Migrating from Traffic Ops 1.x to Traffic Ops 2.x
-
-.. _rl-ps:
-
-Traffic Ops - Migrating from 1.x to 2.x
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-In Traffic Ops 2.x MySQL was removed and Postgres was replaced as the database of choice for the unforeseen future. A Docker-based migration tool was developed to
-help with that conversion using an open source Postgres tool called `pgloader <http://pgloader.io/>`_. The following instructions will help configuring the Migration tool
-
-System Requirements
--------------------
-The user must have the following for a successful minimal install:
-
-* CentOS 7.2+
-* Docker installed (this migration was tested against version **docker-engine-selinux-17.05.0.ce-1.el7.centos.noarch.rpm**)
-* Postgres has been installed according to :ref:`rl-to-install`
-
-Setup the traffic_ops_db directory
-----------------------------------
-
- Modify /opt dir permission to make it writable and owned by postgres:postgres
-
- ::
-
- $ sudo chmod 755 /opt
-
- Download the Traffic Control tarball for 2.0.0
-
- ::
-
- $ cd /opt
- $ wget https://dist.apache.org/repos/dist/release/incubator/trafficcontrol/<tarball_version>
-
- Extract the **traffic_ops_db** dir to **/opt/traffic_ops_db**
-
- ::
-
- $ tar -zxvf trafficcontrol-incubating-<version>.tar.gz --strip=1 trafficcontrol-incubating-<version>/traffic_ops_db
- $ sudo chown -R postgres:postgres /opt/traffic_ops_db
-
-.. highlight:: none
-
-Migration Preparation
----------------------
-Be sure there is connectivity between your MySQL server's IP address/port and your Postgres server's IP address/port.
-
-Navigating the Database Migration
----------------------------------
-Begin the database migration after settings up the **/opt/traffic_ops_db** directory
-
- Switch to the postgres user so permissions stay intact.
- ::
-
- $ su - postgres
- $ cd /opt/traffic_ops_db/
-
-1. Configure the **/opt/traffic_ops_db/pg-migration/mysql-to-postgres.env** migration for your source MySQL and target Postgres settings
-
-
-2. Run the migration, watch the console output for any errors (it may take some time)
- ::
-
- $ ./migrate.sh
-
-
- Your MySQL data should now be ported into your new instance of Postgres!
-
-
-
-
-
diff --git a/docs/latest/_sources/admin/traffic_ops/migration_from_20_to_22.rst.txt b/docs/latest/_sources/admin/traffic_ops/migration_from_20_to_22.rst.txt
deleted file mode 100644
index d27fed4..0000000
--- a/docs/latest/_sources/admin/traffic_ops/migration_from_20_to_22.rst.txt
+++ /dev/null
@@ -1,122 +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.
-..
-
-Traffic Ops - Migrating from 2.0 to 2.2
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
-Per-DeliveryService Routing Names
----------------------------------
-Before this release, DNS Delivery Services were hardcoded to use the name "edge", i.e. "edge.myds.mycdn.com", and HTTP Delivery Services use the name "tr" (or previously "ccr"), i.e. "tr.myds.mycdn.com". As of 2.2, Routing Names will default to "cdn" if left unspecified and can be set to any arbitrary non-dotted hostname.
-
-Pre-2.2 the HTTP Routing Name is configurable via the http.routing.name option in in the Traffic Router http.properties config file. If your CDN uses that option to change the name from "tr" to something else, then you will need to perform the following steps for each CDN affected:
-
-1. In Traffic Ops, create the following profile parameter (double-check for typos, trailing spaces, etc):
-
- * **name**: upgrade_http_routing_name
- * **config file**: temp
- * **value**: whatever value is used for the affected CDN's http.routing.name
-
-2. Add this parameter to a single profile in the affected CDN
-
-With those profile parameters in place Traffic Ops can be safely upgraded to 2.2. Before taking a post-upgrade snapshot, make sure to check your Delivery Service example URLs for unexpected Routing Name changes. Once Traffic Ops has been upgraded to 2.2 and a post-upgrade snapshot has been taken, your Traffic Routers can be upgraded to 2.2 (Traffic Routers must be upgraded after Traffic Ops so that they can work with custom per-DeliveryService Routing Names).
-
-Apache Traffic Server 7.x (Cachekey Plugin)
--------------------------------------------
-In Traffic Ops 2.2 we have added support for Apache Traffic Server 7.x. With 7.x comes support for the new cachekey plugin which replaces the cacheurl plugin which is now deprecated.
-While not needed immediately it is recommended to start replacing cacheurl usages with cachekey as soon as possible because ATS 6.x already supports the new cachekey plugin.
-
-It is also recommended to thoroughly vet your cachekey replacement by comparing with an existing key value. There are inconsistencies in the 6.x version of cachekey which have been
-fixed in 7.x (or require this patch(`cachekeypatch`_) on 6.x to match 7.x). So to ensure you have a matching key value you should use the xdebug plugin before fully implementing your cachekey replacement.
-
-.. _cachekeypatch: https://github.com/apache/trafficserver/commit/244288fab01bdad823f9de19dcece62a7e2a0c11
-
-First if you are currently using a regex for your delivery service you will have to remove that existing value. Then you will need to make a new DS profile and assign parameters in
-it to the cachekey.config file.
-
-Some common parameters are
-
-.. highlight:: none
-
-::
-
- static-prefix - This is used for a simple domain replacement
- separator - Used by cachekey and in general is always a single space
- remove-path - Removes path information from the URL
- remove-all-params - Removes parameters from the URL
- capture-prefix-uri - This is usually used in combination with remove-path and remove-all-params.
- Capture-prefix-uri will let you use your own full regex value for non simple cases
-
-Examples of Cacheurl to Cachekey Replacements
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-**Original regex value:**
-
-``http://test.net/(.*) http://test-cdn.net/$1``
-
-**Cachekey parameters:**
-
-+---------------+-----------------+---------------------------------+
-| Parameter | File | Value |
-+===============+=================+=================================+
-| static-prefix | cachekey.config | ``http://test-cdn.net/`` |
-+---------------+-----------------+---------------------------------+
-| separator | cachekey.config | (empty space) |
-+---------------+-----------------+---------------------------------+
-
-**Original regex value:**
-
-``http://([^?]+)(?:?|$) http://test-cdn.net/$1``
-
-**Cachekey parameters:**
-
-+-----------------------+-----------------+-----------------------------------------------------+
-| Parameter | File | Value |
-+=======================+=================+=====================================================+
-| remove-path | cachekey.config | true |
-+-----------------------+-----------------+-----------------------------------------------------+
-| remove-all-params | cachekey.config | true |
-+-----------------------+-----------------+-----------------------------------------------------+
-| separator | cachekey.config | (empty space) |
-+-----------------------+-----------------+-----------------------------------------------------+
-| capture-prefix-uri | cachekey.config | ``/https?:\/\/([^?]*)/http:\/\/test-cdn.net\/$1/`` |
-+-----------------------+-----------------+-----------------------------------------------------+
-
-Also note the ``s?`` used here so that both http and https requests will end up with the same key value
-
-**Original regex value:**
-
-``http://test.net/([^?]+)(?:\?|$) http://test-cdn.net/$1``
-
-**Cachekey parameters:**
-
-+-------------------+-----------------+---------------------------------+
-| Parameter | File | Value |
-+===================+=================+=================================+
-| static-prefix | cachekey.config | ``http://test-cdn.net/`` |
-+-------------------+-----------------+---------------------------------+
-| separator | cachekey.config | (empty space) |
-+-------------------+-----------------+---------------------------------+
-| remove-all-params | cachekey.config | true |
-+-------------------+-----------------+---------------------------------+
-
-.. _ApacheTrafficServerDocs: https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cachekey.en.html
-
-Further documentation on the cachekey plugin can be found at `ApacheTrafficServerDocs`_
-
-Apache Traffic Server 7.x (Logging)
--------------------------------------------
-Trafficserver v7 has changed the logging format. Previously this was an xml file and now it is a lua file. Traffic Control compensates for this
-automatically depending upon the filename used for the logging parameters. Previously the file used was ``logs_xml.config``, for ATS 7 it is now
-``logging.config``. The same parameters will work this new file, ``LogFormat.Format``, ``LogFormat.Name``, ``LogObject.Format`` etc.
diff --git a/docs/latest/_sources/admin/traffic_ops/using.rst.txt b/docs/latest/_sources/admin/traffic_ops/using.rst.txt
deleted file mode 100644
index c7273e5..0000000
--- a/docs/latest/_sources/admin/traffic_ops/using.rst.txt
+++ /dev/null
@@ -1,1224 +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.
-..
-
-.. |graph| image:: ../../../../traffic_ops/app/public/images/graph.png
-.. |info| image:: ../../../../traffic_ops/app/public/images/info.png
-.. |checkmark| image:: ../../../../traffic_ops/app/public/images/good.png
-.. |X| image:: ../../../../traffic_ops/app/public/images/bad.png
-.. |clock| image:: ../../../../traffic_ops/app/public/images/clock-black.png
-
-Traffic Ops - Using
-%%%%%%%%%%%%%%%%%%%
-
-
-The Traffic Ops Menu
-====================
-
-.. image:: ../12m.png
-
-The following tabs are available in the menu at the top of the Traffic Ops user interface.
-
-.. index::
- Health Tab
-
-* **Health**
-
- Information on the health of the system. Hover over this tab to get to the following options:
-
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +===============+====================================================================================================================================+
- | Table View | A real time view into the main performance indicators of the CDNs managed by Traffic Control. |
- | | This view is sourced directly by the Traffic Monitor data and is updated every 10 seconds. |
- | | This is the default screen of Traffic Ops. |
- | | See :ref:`rl-health-table` for details. |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Graph View | A real graphical time view into the main performance indicators of the CDNs managed by Traffic Control. |
- | | This view is sourced by the Traffic Monitor data and is updated every 10 seconds. |
- | | On loading, this screen will show a history of 24 hours of data from Traffic Stats |
- | | See :ref:`rl-health-graph` for details. |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Server Checks | A table showing the results of the periodic check extension scripts that are run. See :ref:`rl-server-checks` |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Daily Summary | A graph displaying the daily peaks of bandwidth, overall bytes served per day, and overall bytes served since initial installation |
- | | per CDN. |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-
-* **Delivery Services**
-
- The main Delivery Service table. This is where you Create/Read/Update/Delete Delivery Services of all types. Hover over to get the following sub option:
-
- +-------------+--------------------------------------+
- | Option | Description |
- +=============+======================================+
- | Federations | Add/Edit/Delete Federation Mappings. |
- +-------------+--------------------------------------+
-
-* **Servers**
-
- The main Servers table. This is where you Create/Read/Update/Delete servers of all types. Click the main tab to get to the main table, and hover over to get these sub options:
-
- +-------------------+------------------------------------------------------------------------------------------+
- | Option | Description |
- +===================+==========================================================================================+
- | Upload Server CSV | Bulk add of servers from a csv file. See :ref:`rl-bulkserver` |
- +-------------------+------------------------------------------------------------------------------------------+
-
-* **Parameters**
-
- Parameters and Profiles can be edited here. Hover over the tab to get the following options:
-
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +=====================+=====================================================================================================================================================================+
- | Global Profile | The table of global parameters. See :ref:`rl-param-prof`. This is where you Create/Read/Update/Delete parameters in the Global profile |
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | All Cache Groups | The table of all parameters *that are assigned to a cachegroup* - this may be slow to pull up, as there can be thousands of parameters. |
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | All Profiles | The table of all parameters *that are assigned to a profile* - this may be slow to pull up, as there can be thousands of parameters. |
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | Select Profile | Select the parameter list by profile first, then get a table of just the parameters for that profile. |
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | Export Profile | Profiles can be exported from one Traffic Ops instance to another using 'Select Profile' and under the "Profile Details" dialog for the desired profile |
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | Import Profile | Profiles can be imported from one Traffic Ops instance to another using the button "Import Profile" after using the "Export Profile" feature |
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
- | Orphaned Parameters | A table of parameters that are not associated to any profile of cache group. These parameters either should be deleted or associated with a profile of cache group. |
- +---------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-* **Tools**
-
- Tools for working with Traffic Ops and it's servers. Hover over this tab to get the following options:
-
- +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +====================+===================================================================================================================================+
- | Generate ISO | Generate a bootable image for any of the servers in the Servers table (or any server for that matter). See :ref:`rl-generate-iso` |
- +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Queue Updates | Send Updates to the caches. See :ref:`rl-queue-updates` |
- +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | DB Dump | Backup the Database to a .sql file. |
- +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Snapshot CRConfig | Send updates to the Traffic Monitor / Traffic Router servers. See :ref:`rl-queue-updates` |
- +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Invalidate Content | Invalidate or purge content from all caches in the CDN. See :ref:`rl-purge` |
- +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Manage DNSSEC keys | Manage DNSSEC Keys for a chosen CDN. |
- +--------------------+-----------------------------------------------------------------------------------------------------------------------------------+
-
-
-* **Misc**
-
- Miscellaneous editing options. Hover over this tab to get the following options:
-
- +--------------------+-------------------------------------------------------------------------------------------+
- | Option | Description |
- +====================+===========================================================================================+
- | CDNs | Create/Read/Update/Delete CDNs |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Cache Groups | Create/Read/Update/Delete cache groups |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Users | Create/Read/Update/Delete users |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Profiles | Create/Read/Update/Delete profiles. See :ref:`rl-working-with-profiles` |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Networks(ASNs) | Create/Read/Update/Delete Autonomous System Numbers See :ref:`rl-asn-czf` |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Hardware | Get detailed hardware information (note: this should be moved to a Traffic Ops Extension) |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Data Types | Create/Read/Update/Delete data types |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Divisions | Create/Read/Update/Delete divisions |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Regions | Create/Read/Update/Delete regions |
- +--------------------+-------------------------------------------------------------------------------------------+
- | Physical Locations | Create/Read/Update/Delete locations |
- +--------------------+-------------------------------------------------------------------------------------------+
-
-.. index::
- Change Log
-
-* **ChangeLog**
-
- The Changelog table displays the changes that are being made to the Traffic Ops database through the Traffic Ops user interface. This tab will show the number of changes since you last visited this tab in (brackets) since the last time you visited this tab. There are currently no sub menus for this tab.
-
-
-* **Help**
-
- Help for Traffic Ops and Traffic Control. Hover over this tab to get the following options:
-
- +---------------+---------------------------------------------------------------------+
- | Option | Description |
- +===============+=====================================================================+
- | About | Traffic Ops information, such as version, database information, etc |
- +---------------+---------------------------------------------------------------------+
- | Release Notes | Release notes for the most recent releases of Traffic Ops |
- +---------------+---------------------------------------------------------------------+
- | Logout | Logout from Traffic Ops |
- +---------------+---------------------------------------------------------------------+
-
-
-.. index::
- Edge Health
- Health
-
-Health
-======
-
-.. _rl-health-table:
-
-The Health Table
-++++++++++++++++
-The Health table is the default landing screen for Traffic Ops, it displays the status of the EDGE caches in a table form directly from Traffic Monitor (bypassing Traffic Stats), sorted by Mbps Out. The columns in this table are:
-
-
-* **Profile**: the Profile of this server or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
-* **Host Name**: the host name of the server or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
-* **Edge Cache Group**: the edge cache group short name or ALL, meaning this row shows data for multiple servers, and the row shows the sum of all values.
-* **Healthy**: indicates if this cache is healthy according to the Health Protocol. A row with ALL in any of the columns will always show a |checkmark|, this column is valid only for individual EDGE caches.
-* **Admin**: shows the administrative status of the server.
-* **Connections**: the number of connections this cache (or group of caches) has open (``ats.proxy.process.http.current_client_connections`` from ATS).
-* **Mbps Out**: the bandwidth being served out if this cache (or group of caches)
-
-Since the top line has ALL, ALL, ALL, it shows the total connections and bandwidth for all caches managed by this instance of Traffic Ops.
-
-.. _rl-health-graph:
-
-Graph View
-++++++++++
-The Graph View shows a live view of the last 24 hours of bits per seconds served and open connections at the edge in a graph. This data is sourced from Traffic Stats. If there are 2 CDNs configured, this view will show the statistis for both, and the graphs are stacked. On the left-hand side, the totals and immediate values as well as the percentage of total possible capacity are displayed. This view is update every 10 seconds.
-
-
-.. _rl-server-checks:
-
-Server Checks
-+++++++++++++
-The server checks page is intended to give an overview of the Servers managed by Traffic Control as well as their status. This data comes from `Traffic Ops extensions <traffic_ops_extensions.html>`_.
-
-+------+-----------------------------------------------------------------------+
-| Name | Description |
-+======+=======================================================================+
-| ILO | Ping the iLO interface for EDGE or MID servers |
-+------+-----------------------------------------------------------------------+
-| 10G | Ping the IPv4 address of the EDGE or MID servers |
-+------+-----------------------------------------------------------------------+
-| 10G6 | Ping the IPv6 address of the EDGE or MID servers |
-+------+-----------------------------------------------------------------------+
-| MTU | Ping the EDGE or MID using the configured MTU from Traffic Ops |
-+------+-----------------------------------------------------------------------+
-| FQDN | DNS check that matches what the DNS servers responds with compared to |
-| | what Traffic Ops has. |
-+------+-----------------------------------------------------------------------+
-| DSCP | Checks the DSCP value of packets from the edge server to the Traffic |
-| | Ops server. |
-+------+-----------------------------------------------------------------------+
-| RTR | Content Router checks. Checks the health of the Content Routers. |
-| | Checks the health of the caches using the Content Routers. |
-+------+-----------------------------------------------------------------------+
-| CHR | Cache Hit Ratio in percent. |
-+------+-----------------------------------------------------------------------+
-| CDU | Total Cache Disk Usage in percent. |
-+------+-----------------------------------------------------------------------+
-| ORT | Operational Readiness Test. Uses the ORT script on the edge and mid |
-| | servers to determine if the configuration in Traffic Ops matches the |
-| | configuration on the edge or mid. The user that this script runs as |
-| | must have an ssh key on the edge servers. |
-+------+-----------------------------------------------------------------------+
-
-Daily Summary
-+++++++++++++
-Displays daily max gbps and bytes served for all CDNs. In order for the graphs to appear, the 'daily_bw_url' and 'daily_served_url' parameters need to be be created, assigned to the global profile, and have a value of a grafana graph. For more information on configuring grafana, see the `Traffic Stats <../traffic_stats.html>`_ section.
-
-.. _rl-server:
-
-Server
-======
-This view shows a table of all the servers in Traffic Ops. The table columns show the most important details of the server. The **IPAddrr** column is clickable to launch an ``ssh://`` link to this server. The |graph| icon will link to a Traffic Stats graph of this server for caches, and the |info| will link to the server status pages for other server types.
-
-
-Server Types
-++++++++++++
-These are the types of servers that can be managed in Traffic Ops:
-
-+---------------+---------------------------------------------+
-| Name | Description |
-+===============+=============================================+
-| EDGE | Edge Cache |
-+---------------+---------------------------------------------+
-| MID | Mid Tier Cache |
-+---------------+---------------------------------------------+
-| ORG | Origin |
-+---------------+---------------------------------------------+
-| CCR | Traffic Router |
-+---------------+---------------------------------------------+
-| RASCAL | Rascal health polling & reporting |
-+---------------+---------------------------------------------+
-| TOOLS_SERVER | Ops hosts for managment |
-+---------------+---------------------------------------------+
-| RIAK | Riak keystore |
-+---------------+---------------------------------------------+
-| SPLUNK | SPLUNK indexer search head etc |
-+---------------+---------------------------------------------+
-| TRAFFIC_STATS | traffic_stats server |
-+---------------+---------------------------------------------+
-| INFLUXDB | influxDb server |
-+---------------+---------------------------------------------+
-
-
-.. index::
- Bulk Upload Server
-
-.. _rl-bulkserver:
-
-Bulk Upload Server
-++++++++++++++++++
-TBD
-
-
-Delivery Service
-================
-The fields in the Delivery Service view are:
-
-
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Name | Description [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Active | Whether or not this delivery service is active on the CDN and is capable of traffic. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Content Routing Type | DNS is the standard routing type for most CDN services. HTTP Redirect is a specialty routing service that is primarily used for video and large file downloads where localization and latency are significant concerns. [...]
-| | A "Live" routing type should be used for all live services. See :ref:`rl-ds-types`. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Key (XML ID) | This id becomes a part of the CDN service domain in the form ``http://cdn.service-key.company.com/``. Must be all lowercase, no spaces or special characters. May contain dashes. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Display Name | Name of the service that appears in the Traffic portal. No character restrictions. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Tenant | Name of company or division of company who owns account. Allows you to group your services and control access. Tenants are setup as a simple hierarchy where you may create parent / child accounts. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| CDN | The CDN in which the delivery service belongs to. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Routing Name | The routing name to use for the delivery FQDN, i.e. ``<routing-name>.<deliveryservice>.<cdn-domain>``. It must be a valid hostname without periods. [2]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Protocol | The protocol to serve this delivery service to the clients with: [...]
-| | [...]
-| | - HTTP: Delivery only HTTP traffic [...]
-| | - HTTPS: Delivery only HTTPS traffic [...]
-| | - HTTP AND HTTPS: Deliver both types of traffic. [...]
-| | - HTTP TO HTTPS: Delivery HTTP traffic as HTTPS traffic [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DSCP Tag | The Differentiated Services Code Point (DSCP) value to mark IP packets to the client with. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Signing Algorithm | Type of URL signing method to sign the URLs: [...]
-| | [...]
-| | - null: token based auth is not enabled for this delivery service. [...]
-| | - “url_sig”: URL Sign token based auth is enabled for this delivery service. [...]
-| | - “uri_signing”: URI Signing token based auth is enabled for this delivery service. [...]
-| | [...]
-| | See :ref:`rl-signed-urls`. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Deep Caching | Enables clients to be routed to the closest possible "deep" edge caches on a per Delivery Service basis. [...]
-| | See `Deep Caching <http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_router.html#deep-caching-deep-coverage-zone-topology>`_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Query String Handling | How to treat query strings: [...]
-| | [...]
-| | - 0 use in cache key and hand up to origin: Each unique query string is treated as a unique URL. [...]
-| | - 1 Do not use in cache key, but pass up to origin: 2 URLs that are the same except for the query string will match and cache HIT, while the origin still sees original query string in the request. [...]
-| | - 2 Drop at edge: 2 URLs that are the same except for the query string will match and cache HIT, while the origin will not see original query string in the request. [...]
-| | [...]
-| | **Note:** Choosing to drop query strings at the edge will preclude the use of a Regex Remap Expression. See :ref:`rl-regex-remap`. [...]
-| | [...]
-| | To set the qstring without the use of regex remap, or for further options, see :ref:`rl-qstring-handling`. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geolocation Provider | Choose which Geolocation database provider, company that collects data on the location of IP addresses, to use. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Anonymous Blocking | Set to true to enable blocking of anonymous IPs for this delivery service. **Note:** Requires Geolocation provider's Anonymous IP database. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Limit | Some services are intended to be limited by geography. The possible settings are: [...]
-| | [...]
-| | - None: Do not limit by geography. [...]
-| | - CZF only: If the requesting IP is not in the Coverage Zone File, do not serve the request. [...]
-| | - CZF + US: If the requesting IP is not in the Coverage Zone File or not in the United States, do not serve the request. [...]
-| | [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Limit Countries | How (if at all) is this service to be limited by geography. Example Country Codes: CA, IN, PR. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Limit Redirect URL | Traffic Router will redirect to this URL when Geo Limit check fails. See :ref:`rl-tr-ngb` [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Regional Geoblocking | Define regional geo-blocking rules for delivery services in a JSON format and set it to True/False. [...]
-| | See `regional geo-blocking <http://traffic-control-cdn.readthedocs.io/en/latest/admin/quick_howto/regionalgeo.html#configure-regional-geo-blocking-rgb>`_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| IPv6 Routing Enabled | Default is "True", entering "False" allows you to turn off CDN response to IPv6 requests [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Range Request Handling | How to treat range requests: [...]
-| | [...]
-| | - 0: Do not cache (ranges requested from files that are already cached due to a non range request will be a HIT) [...]
-| | - 1: Use the `background_fetch <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/background_fetch.en.html>`_ plugin. [...]
-| | - 2: Use the cache_range_requests plugin. [...]
-| | [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass IP | IPv4 address to overflow requests when the Max Bps or Max Tps for this delivery service exceeds. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass IPv6 | IPv6 address to overflow requests when the Max Bps or Max Tps for this delivery service exceeds. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass CNAME | Domain name to overflow requests when the Max Bps or Max Tps for this delivery service exceeds. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| DNS Bypass TTL | TTL for the DNS bypass domain or IP when threshold exceeds [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| HTTP Bypass FQDN | Traffic Router will redirect to this FQDN (with the same path) when the Max Bps or Max Tps for this delivery service exceeds. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Delivery Service DNS TTL | The Time To Live on the DNS record for the Traffic Router A and AAAA records. Setting too high or too low will result in poor caching performance. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Fair Queuing Pacing Rate Bps | The maximum bytes per second a cache will delivery on any single TCP connection. This uses the Linux kernel’s Fair Queuing setsockopt (SO_MAX_PACING_RATE) to limit the rate of delivery. Traffic exceeding this speed will only be rate-limited and not diverted. This option requires net.core.default_qdisc = fq in /etc/sysctl.conf. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Global Max Mbps | The maximum bits per second this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6 will be used (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Global Max TPS | The maximum transactions per se this delivery service can serve across all EDGE caches before traffic will be diverted to the bypass destination. For a DNS delivery service, the Bypass Ipv4 or Ipv6 will be used (depending on whether this was a A or AAAA request), and for HTTP delivery services the Bypass FQDN will be used. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Max DNS Answers | It is used to restrict the number of cache IP addresses that the CCR will hand back. A numeric value from 1 to 15 which determines how many caches your content will be spread across in a particular site. When a customer requests your content they will get 1 to 15 IP addresses back they can use. These are rotated in each response. Ideally the number will reflect the amount of traffic. 1 = trial account with very little traffic, 2 = small prod [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Initial Dispersion | Determines number of machines content will be placed on within a cache group. Setting too high will result in poor caching performance. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Origin Server Base URL | The Origin Server’s base URL which includes the protocol (http or https). Example: ``http://movies.origin.com`` [...]
-| | Must be a domain only, no directories or IP addresses [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Use Multi Site Origin Feature | Set True/False to enable/disable the Multi Site Origin feature for this delivery service. See :ref:`rl-multi-site-origin` [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Delivery Service Profile | Only used if a delivery service uses configurations that specifically require a profile. Example: MSO configurations or cachekey plugin would require a ds profile to be used. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Miss Default Latitude | Default Latitude for this delivery service. When client localization fails for both Coverage Zone and Geo Lookup, this the client will be routed as if it was at this lat. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Geo Miss Default Longitude | Default Longitude for this delivery service. When client localization fails for bot Coverage Zone and Geo Lookup, this the client will be routed as if it was at this long. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Edge Header Rewrite Rules | Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. The action will tell us whether we are adding, removing, or replacing headers. The header name and header value will determine the full header text. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the [...]
-| | [...]
-| | - Action: Set [...]
-| | - Header Name: X-CDN [...]
-| | - Header Value: Foo [...]
-| | - Direction: Edge Response to Client [...]
-| | [...]
-| | See :ref:`rl-header-rewrite`. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Mid Header Rewrite Rules | Headers can be added or altered at each layer of the CDN. You must tell us four things: the action, the header name, the header value, and the direction to apply. The action will tell us whether we are adding, removing, or replacing headers. The header name and header value will determine the full header text. The direction will determine whether we add it before we respond to a request or before we make a request further up the chain in the [...]
-| | [...]
-| | - Action: Set [...]
-| | - Header Name: Host [...]
-| | - Header Value: code_abc123 [...]
-| | - Direction: Mid Request to Origin [...]
-| | [...]
-| | See :ref:`rl-header-rewrite`. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Traffic Router Additional Response Headers | List of header name:value pairs separated by __RETURN__. Listed pairs will be included in all TR HTTP responses. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Traffic Router Log Request Headers | List of header keys separated by __RETURN__. Listed headers will be included in TR access log entries under the “rh=” token. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Regex remap expression | Allows remapping of incoming requests URL using regex pattern matching to search/replace text. [...]
-| | See `ATS documentation on regex_remap <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/regex_remap.en.html>`_. [1]_ [...]
-| | [...]
-| | **Note:** you will not be able to save a Regex Remap Expression if you have Query String Handling set to drop query strings at the edge. See :ref:`rl-regex-remap`. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Cache URL expression | Allows you to manipulate the cache key of the incoming requests. Normally, the cache key is the origin domain. This can be changed so that multiple services can share a cache key, can also be used to preserve cached content if service origin is changed. [...]
-| | [...]
-| | **Note:** Only valid in ATS 6.X and earlier. Must be empty if using ATS 7.X and/or the `cachekey plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/cachekey.en.html>`_. [1]_ [...]
-| | [...]
-| | See `ATS documentation on cacheurl <https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/plugins/cacheurl.en.html>`_. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Raw remap text | For HTTP and DNS delivery services, this will get added to the end of the remap line on the cache verbatim. For ANY_MAP delivery services this is the remap line. [1]_ [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Long Description | Free text field that describes the purpose of the delivery service and will be displayed in the portal as a description field. For example, you can use this field to describe your service. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Long Description 2 | Free text field not currently used in configuration. For example, you can use this field to describe your customer type. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Long Description 3 | Free text field not currently used in configuration. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Info URL | Free text field allowing you to enter a URL which provides information about the service. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Check Path | A path (ex: /crossdomain.xml) to verify the connection to the origin server with. This can be used by Check Extension scripts to do periodic health checks against the delivery service. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Origin Shield (Pipe Delimited String) | Add another forward proxy upstream of the mid caches. Example: go_direct=true will allow the Mid to hit the origin directly instead of failing if the origin shield is down. Experimental Feature. [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-| Logs Enabled | Allows you to turn on/off logging for the service [...]
-+--------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [...]
-
-.. [1] These fields are not validated by Traffic Ops to be correct syntactically, and can cause Traffic Server to not start if invalid. Please use with caution.
-.. [2] It is not recommended to change the Routing Name of a Delivery Service after deployment because this changes its Delivery FQDN (i.e. ``<routing-name>.<deliveryservice>.<cdn-domain>``), which means that SSL certificates may need to be updated and clients using the Delivery Service will need to be transitioned to the new Delivery URL.
-
-
-.. index::
- Delivery Service Type
-
-.. _rl-ds-types:
-
-Delivery Service Types
-++++++++++++++++++++++
-One of the most important settings when creating the delivery service is the selection of the delivery service *type*. This type determines the routing method and the primary storage for the delivery service.
-
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+=================+========================================================================================================================================================================================================================================================================================================================================+
-| HTTP | HTTP Content Routing - The Traffic Router DNS auth server returns its own IP address on DNS queries, and the client gets redirected to a specific cache |
-| | in the nearest cache group using HTTP 302. Use this for long sessions like HLS/HDS/Smooth live streaming, where a longer setup time is not a. |
-| | problem. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNS | DNS Content Routing - The Traffic Router DNS auth server returns an edge cache IP address to the client right away. The client will find the cache quickly |
-| | but the Traffic Router can not route to a cache that already has this content in the cache group. Use this for smaller objects like web page images / objects. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| HTTP_NO_CACHE | HTTP Content Routing, but the caches will not actually cache the content, they act as just proxies. The MID tier is bypassed. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| HTTP_LIVE | HTTP Content routing, but where for "standard" HTTP content routing the objects are stored on disk, for this delivery service type the objects are stored |
-| | on the RAM disks. Use this for linear TV. The MID tier is bypassed for this type. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| HTTP_LIVE_NATNL | HTTP Content routing, same as HTTP_LIVE, but the MID tier is NOT bypassed. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNS_LIVE_NATNL | DNS Content routing, but where for "standard" DNS content routing the objects are stored on disk, for this delivery service type the objects are stored |
-| | on the RAM disks. Use this for linear TV. The MID tier is NOT bypassed for this type. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNS_LIVE | DNS Content routing, same as DNS_LIVE_NATNL, but the MID tier is bypassed. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| ANY_MAP | ANY_MAP is not known to Traffic Router. For this deliveryservice, the "Raw remap text" field in the input form will be used as the remap line on the cache. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| STEERING | The Delivery Service will be used to route to other delivery services. The target delivery services and the routing weights for those delivery services will be defined by an admin or steering user. For more information see the `steering feature <../traffic_router.html#steering-feature>`_ documentation |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| CLIENT_STEERING | Similar to STEERING except that a client can send a request to Traffic Router with a query param of `trred=false`, and Traffic Router will return an HTTP 200 response with a body that contains a list of Delivery Service URLs that the client can connect to. Therefore, the client is doing the steering, not the Traffic Router. |
-+-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-.. _rl-federations:
-
-Federations
-+++++++++++
- Federations allow for other (federated) CDNs (at a different ISP, MSO, etc) to add a list of resolvers and a CNAME to a delivery service Traffic Ops. When a request is made from one of federated CDN's clients, Traffic Router will return the CNAME configured in the federation mapping. This allows the federated CDN to serve the content without the content provider changing the URL, or having to manage multiple URLs.
-
- Before adding a federation in the Traffic Ops UI, a user with the federations role needs to be created. This user will be assigned to the federation and will be able to add resolvers to the federation via the Traffic Ops `Federation API <../../development/traffic_ops_api/v12/federation.html>`_.
-
-.. index::
- Header Rewrite
-
-.. _rl-header-rewrite:
-
-Header Rewrite Options and DSCP
-+++++++++++++++++++++++++++++++
-Most header manipulation and per-delivery service configuration overrides are done using the `ATS Header Rewrite Plugin <https://docs.trafficserver.apache.org/en/latest/admin-guide/plugins/header_rewrite.en.html>`_. Traffic Control allows you to enter header rewrite rules to be applied at the edge and at the mid level. The syntax used in Traffic Ops is the same as the one described in the ATS documentation, except for some special strings that will get replaced:
-
-+-------------------+--------------------------+
-| Traffic Ops Entry | Gets Replaced with |
-+===================+==========================+
-| __RETURN__ | A newline |
-+-------------------+--------------------------+
-| __CACHE_IPV4__ | The cache's IPv4 address |
-+-------------------+--------------------------+
-
-The deliveryservice screen also allows you to set the DSCP value of traffic sent to the client. This setting also results in a header_rewrite rule to be generated and applied to at the edge.
-
-.. Note:: The DSCP setting in the UI is *only* for setting traffic towards the client, and gets applied *after* the initial TCP handshake is complete, and the HTTP request is received (before that the cache can't determine what deliveryservice this request is for, and what DSCP to apply), so the DSCP feature can not be used for security settings - the TCP SYN-ACK is not going to be DSCP marked.
-
-
-.. index::
- Token Based Authentication
- Signed URLs
-
-.. _rl-signed-urls:
-
-Token Based Authentication
-++++++++++++++++++++++++++
-Token based authentication or *signed URLs* is implemented using the Traffic Server ``url_sig`` plugin. To sign a URL at the signing portal take the full URL, without any query string, and add on a query string with the following parameters:
-
-Client IP address
- The client IP address that this signature is valid for.
-
- ``C=<client IP address>``
-
-Expiration
- The Expiration time (seconds since epoch) of this signature.
-
- ``E=<expiration time in secs since unix epoch>``
-
-Algorithm
- The Algorithm used to create the signature. Only 1 (HMAC_SHA1)
- and 2 (HMAC_MD5) are supported at this time
-
- ``A=<algorithm number>``
-
-Key index
- Index of the key used. This is the index of the key in the
- configuration file on the cache. The set of keys is a shared
- secret between the signing portal and the edge caches. There
- is one set of keys per reverse proxy domain (fqdn).
-
- ``K=<key index used>``
-Parts
- Parts to use for the signature, always excluding the scheme
- (http://). parts0 = fqdn, parts1..x is the directory parts
- of the path, if there are more parts to the path than letters
- in the parts param, the last one is repeated for those.
- Examples:
-
- 1: use fqdn and all of URl path
- 0110: use part1 and part 2 of path only
- 01: use everything except the fqdn
-
- ``P=<parts string (0's and 1's)>``
-
-Signature
- The signature over the parts + the query string up to and
- including "S=".
-
- ``S=<signature>``
-
-.. seealso:: The url_sig `README <https://github.com/apache/trafficserver/blob/master/plugins/experimental/url_sig/README>`_.
-
-Generate URL Sig Keys
-^^^^^^^^^^^^^^^^^^^^^
-To generate a set of random signed url keys for this delivery service and store them in Traffic Vault, click the **Generate URL Sig Keys** button at the bottom of the delivery service details screen.
-
-
-.. rl-parent-selection:
-
-Parent Selection
-++++++++++++++++
-
-Parameters in the Edge (child) profile that influence this feature:
-
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| Name | Filename | Default | Description |
-+===============================================+================+===============+=======================================================+
-| CONFIG proxy.config. | records.config | INT 1 | enable parent selection. This is a required setting. |
-| http.parent_proxy_routing_enable | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 1 | required for parent selection. |
-| url_remap.remap_required | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 0 | See |
-| http.no_dns_just_forward_to_parent | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 1 | |
-| http.uncacheable_requests_bypass_parent | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 1 | |
-| http.parent_proxy_routing_enable | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 300 | |
-| http.parent_proxy.retry_time | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 10 | |
-| http.parent_proxy.fail_threshold | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 4 | |
-| http.parent_proxy.total_connect_attempts | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 2 | |
-| http.parent_proxy.per_parent_connect_attempts | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 30 | |
-| http.parent_proxy.connect_attempts_timeout | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 0 | |
-| http.forward.proxy_auth_to_parent | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 0 | |
-| http.parent_proxy_routing_enable | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | STRING | |
-| http.parent_proxy.file | | parent.config | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| CONFIG proxy.config. | records.config | INT 3 | |
-| http.parent_proxy.connect_attempts_timeout | | | |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-| algorithm | parent.config | urlhash | The algorithm to use. |
-+-----------------------------------------------+----------------+---------------+-------------------------------------------------------+
-
-
-Parameters in the Mid (parent) profile that influence this feature:
-
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Filename | Default | Description |
-+================+===============+=========+===================================================================================================================================================================================+
-| domain_name | CRConfig.json | - | Only parents with the same value as the edge are going to be used as parents (to keep separation between CDNs) |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| weight | parent.config | 1.0 | The weight of this parent, translates to the number of replicas in the consistent hash ring. This parameter only has effect with algorithm at the client set to "consistent_hash" |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| port | parent.config | 80 | The port this parent is listening on as a forward proxy. |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| use_ip_address | parent.config | 0 | 1 means use IP(v4) address of this parent in the parent.config, 0 means use the host_name.domain_name concatenation. |
-+----------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-.. _rl-qstring-handling:
-
-Qstring Handling
-++++++++++++++++
-
-Delivery services have a Query String Handling option that, when set to ignore, will automatically add a regex remap to that delivery service's config. There may be times this is not preferred, or there may be requirements for one delivery service or server(s) to behave differently. When this is required, the psel.qstring_handling parameter can be set in either the delivery service profile or the server profile, but it is important to note that the server profile will override ALL deli [...]
-
-+-----------------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Filename | Default | Description |
-+=======================+===============+=========+===================================================================================================================================================================================+
-| psel.qstring_handling | parent.config | - | Sets qstring handling without the use of regex remap for a delivery service when assigned to a delivery service profile, and overrides qstring handling for all delivery services |
-| | | | for associated servers when assigned to a server profile. Value must be "consider" or "ignore". |
-+-----------------------+---------------+---------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-.. _rl-multi-site-origin:
-
-Multi Site Origin
-+++++++++++++++++
-
-.. Note:: The configuration of this feature changed significantly between ATS version 5 and >= 6. Some configuration in Traffic Control is different as well. This documentation assumes ATS 6 or higher. See :ref:`rl-multi-site-origin-qht` for more details.
-
-Normally, the mid servers are not aware of any redundancy at the origin layer. With Multi Site Origin enabled this changes - Traffic Server (and Traffic Ops) are now made aware of the fact there are multiple origins, and can be configured to do more advanced failover and loadbalancing actions. A prerequisite for MSO to work is that the multiple origin sites serve identical content with identical paths, and both are configured to serve the same origin hostname as is configured in the deli [...]
-
-With This feature enabled, origin servers (or origin server VIP names for a site) are going to be entered as servers in to the Traiffic Ops UI. Server type is "ORG".
-
-Parameters in the mid profile that influence this feature:
-
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| Name | Filename | Default | Description |
-+==========================================================================+================+============+====================================================================================================+
-| CONFIG proxy.config. http.parent_proxy_routing_enable | records.config | INT 1 | enable parent selection. This is a required setting. |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-| CONFIG proxy.config. url_remap.remap_required | records.config | INT 1 | required for parent selection. |
-+--------------------------------------------------------------------------+----------------+------------+----------------------------------------------------------------------------------------------------+
-
-
-Parameters in the deliveryservice profile that influence this feature:
-
-+---------------------------------------------+----------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Name | Filename | Default | Description |
-+=============================================+================+=================+=================================================================================================================================+
-| mso.parent_retry | parent.config | \- | Either ``simple_retry``, ``dead_server_retry`` or ``both``. |
-+---------------------------------------------+----------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------+
-| mso.algorithm | parent.config | consistent_hash | The algorithm to use. ``consisten_hash``, ``strict``, ``true``, ``false``, or ``latched``. |
-| | | | |
-| | | | - ``consisten_hash`` - spreads requests across multiple parents simultaneously based on hash of content URL. |
-| | | | - ``strict`` - strict Round Robin spreads requests across multiple parents simultaneously based on order of requests. |
-| | | | - ``true`` - same as strict, but ensures that requests from the same IP always go to the same parent if available. |
-| | | | - ``false`` - uses only a single parent at any given time and switches to a new parent only if the current parent fails. |
-| | | | - ``latched`` - same as false, but now, a failed parent will not be retried. |
-+---------------------------------------------+----------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------+
-| mso.unavailable_server_retry_response_codes | parent.config | "503" | Quoted, comma separated list of HTTP status codes that count as a unavailable_server_retry_response_code. |
-+---------------------------------------------+----------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------+
-| mso.max_unavailable_server_retries | parent.config | 1 | How many times an unavailable server will be retried. |
-+---------------------------------------------+----------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------+
-| mso.simple_retry_response_codes | parent.config | "404" | Quoted, comma separated list of HTTP status codes that count as a simple retry response code. |
-+---------------------------------------------+----------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------+
-| mso.max_simple_retries | parent.config | 1 | How many times a simple retry will be done. |
-+---------------------------------------------+----------------+-----------------+---------------------------------------------------------------------------------------------------------------------------------+
-
-
-
-see :ref:`rl-multi-site-origin-qht` for a *quick how to* on this feature.
-
-.. _rl-ccr-profile:
-
-Traffic Router Profile
-++++++++++++++++++++++
-
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Config_file | Description |
-+=========================================+========================+===========================================================================================================================================================================================================+
-| location | dns.zone | Location to store the DNS zone files in the local file system of Traffic Router. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| location | http-log4j.properties | Location to find the log4j.properties file for Traffic Router. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| location | dns-log4j.properties | Location to find the dns-log4j.properties file for Traffic Router. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| location | geolocation.properties | Location to find the log4j.properties file for Traffic Router. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| CDN_name | rascal-config.txt | The human readable name of the CDN for this profile. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| CoverageZoneJsonURL | CRConfig.xml | The location (URL) to retrieve the coverage zone map file in JSON format from. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| geolocation.polling.url | CRConfig.json | The location (URL) to retrieve the geo database file from. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| geolocation.polling.interval | CRConfig.json | How often to refresh the coverage geo location database in ms |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| coveragezone.polling.interval | CRConfig.json | How often to refresh the coverage zone map in ms |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| coveragezone.polling.url | CRConfig.json | The location (URL) to retrieve the coverage zone map file in JSON format from. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| deepcoveragezone.polling.interval | CRConfig.json | How often to refresh the deep coverage zone map in ms |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| deepcoveragezone.polling.url | CRConfig.json | The location (URL) to retrieve the deep coverage zone map file in JSON format from. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.expire | CRConfig.json | The value for the expire field the Traffic Router DNS Server will respond with on Start of Authority (SOA) records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.minimum | CRConfig.json | The value for the minimum field the Traffic Router DNS Server will respond with on SOA records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.admin | CRConfig.json | The DNS Start of Authority admin. Should be a valid support email address for support if DNS is not working correctly. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.retry | CRConfig.json | The value for the retry field the Traffic Router DNS Server will respond with on SOA records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.soa.refresh | CRConfig.json | The TTL the Traffic Router DNS Server will respond with on A records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.ttls.NS | CRConfig.json | The TTL the Traffic Router DNS Server will respond with on NS records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.ttls.SOA | CRConfig.json | The TTL the Traffic Router DNS Server will respond with on SOA records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.ttls.AAAA | CRConfig.json | The Time To Live (TTL) the Traffic Router DNS Server will respond with on AAAA records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.ttls.A | CRConfig.json | The TTL the Traffic Router DNS Server will respond with on A records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.ttls.DNSKEY | CRConfig.json | The TTL the Traffic Router DNS Server will respond with on DNSKEY records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| tld.ttls.DS | CRConfig.json | The TTL the Traffic Router DNS Server will respond with on DS records. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| api.port | server.xml | The TCP port Traffic Router listens on for API (REST) access. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| api.cache-control.max-age | CRConfig.json | The value of the ``Cache-Control: max-age=`` header in the API responses of Traffic Router. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| api.auth.url | CRConfig.json | The API authentication URL (https://${tmHostname}/api/1.1/user/login); ${tmHostname} is a search and replace token used by Traffic Router to construct the correct URL) |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| consistent.dns.routing | CRConfig.json | Control whether DNS Delivery Services use consistent hashing on the edge FQDN to select caches for answers. May improve performance if set to true; defaults to false |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| dnssec.enabled | CRConfig.json | Whether DNSSEC is enabled; this parameter is updated via the DNSSEC administration user interface. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| dnssec.allow.expired.keys | CRConfig.json | Allow Traffic Router to use expired DNSSEC keys to sign zones; default is true. This helps prevent DNSSEC related outages due to failed Traffic Control components or connectivity issues. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| dynamic.cache.primer.enabled | CRConfig.json | Allow Traffic Router to attempt to prime the dynamic zone cache; defaults to true |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| dynamic.cache.primer.limit | CRConfig.json | Limit the number of permutations to prime when dynamic zone cache priming is enabled; defaults to 500 |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| keystore.maintenance.interval | CRConfig.json | The interval in seconds which Traffic Router will check the keystore API for new DNSSEC keys |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| keystore.api.url | CRConfig.json | The keystore API URL (https://${tmHostname}/api/1.1/cdns/name/${cdnName}/dnsseckeys.json; ${tmHostname} and ${cdnName} are search and replace tokens used by Traffic Router to construct the correct URL) |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| keystore.fetch.timeout | CRConfig.json | The timeout in milliseconds for requests to the keystore API |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| keystore.fetch.retries | CRConfig.json | The number of times Traffic Router will attempt to load keys before giving up; defaults to 5 |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| keystore.fetch.wait | CRConfig.json | The number of milliseconds Traffic Router will wait before a retry |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| signaturemanager.expiration.multiplier | CRConfig.json | Multiplier used in conjunction with a zone's maximum TTL to calculate DNSSEC signature durations; defaults to 5 |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| zonemanager.threadpool.scale | CRConfig.json | Multiplier used to determine the number of cores to use for zone signing operations; defaults to 0.75 |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| zonemanager.cache.maintenance.interval | CRConfig.json | The interval in seconds which Traffic Router will check for zones that need to be resigned or if dynamic zones need to be expired from cache |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| zonemanager.dynamic.response.expiration | CRConfig.json | A string (e.g.: 300s) that defines how long a dynamic zone |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNSKEY.generation.multiplier | CRConfig.json | Used to deteremine when new keys need to be regenerated. Keys are regenerated if expiration is less than the generation multiplier * the TTL. If the parameter does not exist, the default is 10. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| DNSKEY.effective.multiplier | CRConfig.json | Used when creating an effective date for a new key set. New keys are generated with an effective date of old key expiration - (effective multiplier * TTL). Default is 2. |
-+-----------------------------------------+------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-
-.. index::
- Regex Remap Expression
-
-.. _rl-regex-remap:
-
-Regex Remap Expression
-++++++++++++++++++++++
-The regex remap expression allows to to use a regex and resulting match group(s) in order to modify the request URIs that are sent to origin. For example: ::
-
- ^/original/(.*) http://origin.example.com/remapped/$1
-
-.. Note:: If **Query String Handling** is set to ``2 Drop at edge``, then you will not be allowed to save a regex remap expression, as dropping query strings actually relies on a regex remap of its own. However, if there is a need to both drop query strings **and** remap request URIs, this can be accomplished by setting **Query String Handling** to ``1 Do not use in cache key, but pass up to origin``, and then using a custom regex remap expression to do the necessary remapping, while sim [...]
-
- ^/([^?]*).* http://origin.example.com/remapped/$1
-
-.. index::
- HOST_REGEXP
- PATH_REGEXP
- HEADER_REGEXP
- Delivery Service regexp
-
-.. _rl-ds-regexp:
-
-Delivery Service Regexp
-+++++++++++++++++++++++
-This table defines how requests are matched to the delivery service. There are 3 type of entries possible here:
-
-+---------------+----------------------------------------------------------------------+--------------+-----------+
-| Name | Description | DS Type | Status |
-+===============+======================================================================+==============+===========+
-| HOST_REGEXP | This is the regular expresion to match the host part of the URL. | DNS and HTTP | Supported |
-+---------------+----------------------------------------------------------------------+--------------+-----------+
-| PATH_REGEXP | This is the regular expresion to match the path part of the URL. | HTTP | Beta |
-+---------------+----------------------------------------------------------------------+--------------+-----------+
-| HEADER_REGEXP | This is the regular expresion to match on any header in the request. | HTTP | Beta |
-+---------------+----------------------------------------------------------------------+--------------+-----------+
-
-The **Order** entry defines the order in which the regular expressions get evaluated. To support ``CNAMES`` from domains outside of the Traffic Control top level DNS domain, enter multiple ``HOST_REGEXP`` lines.
-
-Example:
- Example foo.
-
-.. Note:: In most cases is is sufficient to have just one entry in this table that has a ``HOST_REGEXP`` Type, and Order ``0``. For the *movies* delivery service in the Kabletown CDN, the entry is simply single ``HOST_REGEXP`` set to ``.*\.movies\..*``. This will match every url that has a hostname that ends with ``movies.cdn1.kabletown.net``, since ``cdn1.kabletown.net`` is the Kabletown CDN's DNS domain.
-
-.. index::
- Static DNS Entries
-
-.. _rl-static-dns:
-
-Static DNS Entries
-++++++++++++++++++
-Static DNS entries allow you to create other names *under* the delivery service domain. You can enter any valid hostname, and create a CNAME, A or AAAA record for it by clicking the **Static DNS** button at the bottom of the delivery service details screen.
-
-.. index::
- Server Assignments
-
-.. _rl-assign-edges:
-
-Server Assignments
-++++++++++++++++++
-Click the **Server Assignments** button at the bottom of the screen to assign servers to this delivery service. Servers can be selected by drilling down in a tree, starting at the profile, then the cache group, and then the individual servers. Traffic Router will only route traffic for this delivery service to servers that are assigned to it.
-
-
-.. _rl-asn-czf:
-
-The Coverage Zone File and ASN Table
-++++++++++++++++++++++++++++++++++++
-The Coverage Zone File (CZF) should contain a cachegroup name to network prefix mapping in the form: ::
-
- {
- "coverageZones": {
- "cache-group-01": {
- "coordinates": {
- "latitude": 1.1,
- "longitude": 2.2
- },
- "network6": [
- "1234:5678::/64",
- "1234:5679::/64"
- ],
- "network": [
- "192.168.8.0/24",
- "192.168.9.0/24"
- ]
- },
- "cache-group-02": {
- "coordinates": {
- "latitude": 3.3,
- "longitude": 4.4
- },
- "network6": [
- "1234:567a::/64",
- "1234:567b::/64"
- ],
- "network": [
- "192.168.4.0/24",
- "192.168.5.0/24"
- ]
- }
- }
- }
-
-The CZF is an input to the Traffic Control CDN, and as such does not get generated by Traffic Ops, but rather, it gets consumed by Traffic Router. Some popular IP management systems output a very similar file to the CZF but in stead of a cachegroup an ASN will be listed. Traffic Ops has the "Networks (ASNs)" view to aid with the conversion of files like that to a Traffic Control CZF file; this table is not used anywhere in Traffic Ops, but can be used to script the conversion using the API.
-
-The script that generates the CZF file is not part of Traffic Control, since it is different for each situation.
-
-.. note:: The ``"coordinates"`` section is optional and may be used by Traffic Router for localization in the case of a CZF "hit" where the zone name does not map to a Cache Group name in Traffic Ops (i.e. Traffic Router will route to the closest Cache Group(s) geographically).
-
-.. _rl-deep-czf:
-
-The Deep Coverage Zone File
-+++++++++++++++++++++++++++
-The Deep Coverage Zone File (DCZF) format is similar to the CZF format but adds a ``caches`` list under each ``deepCoverageZone``: ::
-
- {
- "deepCoverageZones": {
- "location-01": {
- "coordinates": {
- "latitude": 5.5,
- "longitude": 6.6
- },
- "network6": [
- "1234:5678::/64",
- "1234:5679::/64"
- ],
- "network": [
- "192.168.8.0/24",
- "192.168.9.0/24"
- ],
- "caches": [
- "edge-01",
- "edge-02"
- ]
- },
- "location-02": {
- "coordinates": {
- "latitude": 7.7,
- "longitude": 8.8
- },
- "network6": [
- "1234:567a::/64",
- "1234:567b::/64"
- ],
- "network": [
- "192.168.4.0/24",
- "192.168.5.0/24"
- ],
- "caches": [
- "edge-02",
- "edge-03"
- ]
- }
- }
- }
-
-Each entry in the ``caches`` list is the hostname of an edge cache registered in Traffic Ops which will be used for "deep" caching in that Deep Coverage Zone. Unlike a regular CZF, coverage zones in the DCZF do not map to a Cache Group in Traffic Ops, so currently the deep coverage zone name only needs to be unique.
-
-If the Traffic Router gets a DCZF "hit" for a requested Delivery Service that has Deep Caching enabled, the client will be routed to an available "deep" cache from that zone's ``caches`` list.
-
-.. note:: The ``"coordinates"`` section is optional.
-
-
-.. _rl-working-with-profiles:
-
-Parameters and Profiles
-=======================
-Parameters are shared between profiles if the set of ``{ name, config_file, value }`` is the same. To change a value in one profile but not in others, the parameter has to be removed from the profile you want to change it in, and a new parameter entry has to be created (**Add Parameter** button at the bottom of the Parameters view), and assigned to that profile. It is easy to create new profiles from the **Misc > Profiles** view - just use the **Add/Copy Profile** button at the bottom of [...]
-
-.. seealso:: :ref:`rl-param-prof` in the *Configuring Traffic Ops* section.
-
-
-
-Tools
-=====
-
-.. index::
- ISO
- Generate ISO
-
-.. _rl-generate-iso:
-
-Generate ISO
-++++++++++++
-
-Generate ISO is a tool for building custom ISOs for building caches on remote hosts. Currently it only supports Centos 6, but if you're brave and pure of heart you MIGHT be able to get it to work with other unix-like OS's.
-
-The interface is *mostly* self explainatory as it's got hints.
-
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Field | Explaination |
-+===============================+=================================================================================================================================+
-|Choose a server from list: | This option gets all the server names currently in the Traffic Ops database and will autofill known values. |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| OS Version: | There needs to be an _osversions.cfg_ file in the ISO directory that maps the name of a directory to a name that shows up here. |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Hostname: | This is the FQDN of the server to be installed. It is required. |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Root password: | If you don't put anything here it will default to the salted MD5 of "Fred". Whatever put is MD5 hashed and writte to disk. |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| DHCP: | if yes, other IP settings will be ignored |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| IP Address: | Required if DHCP=no |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Netmask: | Required if DHCP=no |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Gateway: | Required if DHCP=no |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| IPV6 Address: | Optional. /64 is assumed if prefix is omitted |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| IPV6 Gateway: | Ignored if an IPV4 gateway is specified |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Network Device: | Optional. Typical values are bond0, eth4, etc. Note: if you enter bond0, a LACP bonding config will be written |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| MTU: | If unsure, set to 1500 |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-| Specify disk for OS install: | Optional. Typical values are "sda". |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------------------+
-
-
-When you click the **Download ISO** button the folling occurs (all paths relative to the top level of the directory specified in _osversions.cfg_):
-
-#. Reads /etc/resolv.conf to get a list of nameservers. This is a rather ugly hack that is in place until we get a way of configuring it in the interface.
-#. Writes a file in the ks_scripts/state.out that contains directory from _osversions.cfg_ and the mkisofs string that we'll call later.
-#. Writes a file in the ks_scripts/network.cfg that is a bunch of key=value pairs that set up networking.
-#. Creates an MD5 hash of the password you specify and writes it to ks_scripts/password.cfg. Note that if you do not specify a password "Fred" is used. Also note that we have experienced some issues with webbrowsers autofilling that field.
-#. Writes out a disk configuration file to ks_scripts/disk.cfg.
-#. mkisofs is called against the directory configured in _osversions.cfg_ and an ISO is generated in memory and delivered to your webbrowser.
-
-You now have a customized ISO that can be used to install Red Hat and derivative Linux installations with some modifications to your ks.cfg file.
-
-Kickstart/Anaconda will mount the ISO at /mnt/stage2 during the install process (at least with 6).
-
-You can directly include the password file anywhere in your ks.cfg file (usually in the top) by doing %include /mnt/stage2/ks_scripts/password.cfg
-
-What we currently do is have 2 scripts, one to do hard drive configuration and one to do network configuration. Both are relatively specific to the environment they were created in, and both are *probably* wrong for other organizations, however they are currently living in the "misc" directory as examples of how to do things.
-
-We trigger those in a %pre section in ks.cfg and they will write config files to /tmp. We will then include those files in the appropriate places using %pre.
-
-For example this is a section of our ks.cfg file: ::
-
- %include /mnt/stage2/ks_scripts/packages.txt
-
- %pre
- python /mnt/stage2/ks_scripts/create_network_line.py
- bash /mnt/stage2/ks_scripts/drive_config.sh
- %end
-
-These two scripts will then run _before_ anaconda sets up it's internal structures, then a bit further up in the ks.cfg file (outside of the %pre %end block) we do an ::
-
- %include /mnt/stage2/ks_scripts/password.cfg
- ...
- %include /tmp/network_line
-
- %include /tmp/drive_config
- ...
-
-This snarfs up the contents and inlines them.
-
-If you only have one kind of hardware on your CDN it is probably best to just put the drive config right in the ks.cfg.
-
-If you have simple networking needs (we use bonded interfaces in most, but not all locations and we have several types of hardware meaning different ethernet interface names at the OS level etc.) then something like this: ::
-
- #!/bin/bash
- source /mnt/stage2/ks_scripts/network.cfg
- echo "network --bootproto=static --activate --ipv6=$IPV6ADDR --ip=$IPADDR --netmask=$NETMASK --gateway=$GATEWAY --ipv6gateway=$GATEWAY --nameserver=$NAMESERVER --mtu=$MTU --hostname=$HOSTNAME" >> /tmp/network.cfg
- # Note that this is an example and may not work at all.
-
-
-You could also put this in the %pre section. Lots of ways to solve it.
-
-We have included the two scripts we use in the "misc" directory of the git repo:
-
-* kickstart_create_network_line.py
-* kickstart_drive_config.sh
-
-These scripts were written to support a very narrow set of expectations and environment and are almost certainly not suitable to just drop in, but they might provide a good starting point.
-
-.. _rl-queue-updates:
-
-Queue Updates and Snapshot CRConfig
-+++++++++++++++++++++++++++++++++++
-When changing delivery services special care has to be taken so that Traffic Router will not send traffic to caches for delivery services that the cache doesn't know about yet. In general, when adding delivery services, or adding servers to a delivery service, it is best to update the caches before updating Traffic Router and Traffic Monitor. When deleting delivery services, or deleting server assignments to delivery services, it is best to update Traffic Router and Traffic Monitor first [...]
-
-.. index::
- Cache Updates
- Queue Updates
-
-Queue Updates
-^^^^^^^^^^^^^
-Every 15 minutes the caches should run a *syncds* to get all changes needed from Traffic Ops. The files that will be updated by the syncds job are:
-
-- records.config
-- remap.config
-- parent.config
-- cache.config
-- hosting.config
-- url\_sig\_(.*)\.config
-- hdr\_rw\_(.*)\.config
-- regex_revalidate.config
-- ip_allow.config
-
-A cache will only get updated when the update flag is set for it. To set the update flag, use the *Queue Updates* menu - here you can schedule updates for a whole CDN or a cache group:
-
- #. Click **Tools > Queue Updates**.
- #. Select the CDN to queueu uodates for, or All.
- #. Select the cache group to queue updates for, or All
- #. Click the **Queue Updates** button.
- #. When the Queue Updates for this Server? (all) window opens, click **OK**.
-
-To schedule updates for just one cache, use the "Server Checks" page, and click the |checkmark| in the *UPD* column. The UPD column of Server Checks page will change show a |clock| when updates are pending for that cache.
-
-
-.. index::
- Snapshot CRConfig
-
-.. _rl-snapshot-crconfig:
-
-Snapshot CRConfig
-^^^^^^^^^^^^^^^^^
-
-Every 60 seconds Traffic Monitor will check with Traffic Ops to see if a new CRConfig snapshot exists; Traffic Monitor polls Traffic Ops for a new CRConfig, and Traffic Router polls Traffic Monitor for the same file. This is necessary to ensure that Traffic Monitor sees configuration changes first, which helps to ensure that the health and state of caches and delivery services propagates properly to Traffic Router. See :ref:`rl-ccr-profile` for more information on the CRConfig file.
-
-To create a new snapshot, use the *Tools > Snapshot CRConfig* menu:
-
- #. Click **Tools > Snapshot CRConfig**.
- #. Verify the selection of the correct CDN from the Choose CDN drop down and click **Diff CRConfig**.
- On initial selection of this, the CRConfig Diff window says the following:
-
- There is no existing CRConfig for [cdn] to diff against... Is this the first snapshot???
- If you are not sure why you are getting this message, please do not proceed!
- To proceed writing the snapshot anyway click the 'Write CRConfig' button below.
-
- If there is an older version of the CRConfig, a window will pop up showing the differences
- between the active CRConfig and the CRConfig about to be written.
-
- #. Click **Write CRConfig**.
- #. When the This will push out a new CRConfig.json. Are you sure? window opens, click **OK**.
- #. The Successfully wrote CRConfig.json! window opens, click **OK**.
-
-
-.. index::
- Invalidate Content
- Purge
-
-.. _rl-purge:
-
-Invalidate Content
-==================
-Invalidating content on the CDN is sometimes necessary when the origin was mis-configured and something is cached in the CDN that needs to be removed. Given the size of a typical Traffic Control CDN and the amount of content that can be cached in it, removing the content from all the caches may take a long time. To speed up content invalidation, Traffic Ops will not try to remove the content from the caches, but it makes the content inaccessible using the *regex_revalidate* ATS plugin. [...]
-
-.. Note:: This method forces a HTTP *revalidation* of the content, and not a new *GET* - the origin needs to support revalidation according to the HTTP/1.1 specification, and send a ``200 OK`` or ``304 Not Modified`` as applicable.
-
-To invalidate content:
-
- 1. Click **Tools > Invalidate Content**
- 2. Fill out the form fields:
-
- - Select the **Delivery Service**
- - Enter the **Path Regex** - this should be a `PCRE <http://www.pcre.org/>`_ compatible regular expression for the path to match for forcing the revalidation. Be careful to only match on the content you need to remove - revalidation is an expensive operation for many origins, and a simple ``/.*`` can cause an overload condition of the origin.
- - Enter the **Time To Live** - this is how long the revalidation rule will be active for. It usually makes sense to make this the same as the ``Cache-Control`` header from the origin which sets the object time to live in cache (by ``max-age`` or ``Expires``). Entering a longer TTL here will make the caches do unnecessary work.
- - Enter the **Start Time** - this is the start time when the revalidation rule will be made active. It is pre-populated with the current time, leave as is to schedule ASAP.
-
- 3. Click the **Submit** button.
-
-
-Manage DNSSEC Keys
-====================
-
-In order to support `DNSSEC <https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions>`_ in Traffic Router, Traffic Ops provides some actions for managing DNSSEC keys for a CDN and associated Delivery Services. DNSSEC Keys consist of a Key Signing Keys (KSK) which are used to sign other DNSKEY records as well as Zone Signing Keys (ZSK) which are used to sign other records. DNSSEC Keys are stored in `Traffic Vault <../../overview/traffic_vault.html>`_ and should only be acce [...]
-
-To Manage DNSSEC Keys:
- 1. Click **Tools -> Manage DNSSEC Keys**
- 2. Choose a CDN and click **Manage DNSSEC Keys**
-
- - If keys have not yet been generated for a CDN, this screen will be mostly blank with just the **CDN** and **DNSSEC Active?** fields being populated.
- - If keys have been generated for the CDN, the Manage DNSSEC Keys screen will show the TTL and Top Level Domain (TLD) KSK Expiration for the CDN as well as DS Record information which will need to be added to the parent zone of the TLD in order for DNSSEC to work.
-
-The Manage DNSSEC Keys screen also allows a user to perform the following actions:
-
-**Activate/Deactivate DNSSEC for a CDN**
-
-Fairly straight forward, this button set the **dnssec.enabled** param to either **true** or **false** on the Traffic Router profile for the CDN. The Activate/Deactivate option is only available if DNSSEC keys exist for CDN. In order to active DNSSEC for a CDN a user must first generate keys and then click the **Active DNSSEC** button.
-
-**Generate Keys**
-
-Generate Keys will generate DNSSEC keys for the CDN TLD as well as for each Delivery Service in the CDN. It is important to note that this button will create a new KSK for the TLD and, therefore, a new DS Record. Any time a new DS Record is created, it will need to be added to the parent zone of the TLD in order for DNSSEC to work properly. When a user clicks the **Generate Keys** button, they will be presented with a screen with the following fields:
-
- - **CDN:** This is not editable and displays the CDN for which keys will be generated
- - **ZSK Expiration (Days):** Sets how long (in days) the Zone Signing Key will be valid for the CDN and associated Delivery Services. The default is 30 days.
- - **KSK Expiration (Days):** Sets how long (in days) the Key Signing Key will be valid for the CDN and associated Delivery Services. The default is 365 days.
- - **Effective Date (GMT):** The time from which the new keys will be active. Traffic Router will use this value to determine when to start signing with the new keys and stop signing with the old keys.
-
-Once these fields have been correctly entered, a user can click Generate Keys. The user will be presented with a confirmation screen to help them understand the impact of generating the keys. If a user confirms, the keys will be generated and stored in Traffic Vault.
-
-**Regenerate KSK**
-
-Regenerate KSK will create a new Key Signing Key for the CDN TLD. A new DS Record will also be generated and need to be put into the parent zone in order for DNSSEC to work correctly. The **Regenerate KSK** button is only available if keys have already been generated for a CDN. The intent of the button is to provide a mechanism for generating a new KSK when a previous one expires or if necessary for other reasons such as a security breach. When a user goes to generate a new KSK they ar [...]
-
- - **CDN:** This is not editable and displays the CDN for which keys will be generated
- - **KSK Expiration (Days):** Sets how long (in days) the Key Signing Key will be valid for the CDN and associated Delivery Services. The default is 365 days.
- - **Effective Date (GMT):** The time from which the new KSK and DS Record will be active. Since generating a new KSK will generate a new DS Record that needs to be added to the parent zone, it is very important to make sure that an effective date is chosen that allows for time to get the DS Record into the parent zone. Failure to get the new DS Record into the parent zone in time could result in DNSSEC errors when Traffic Router tries to sign responses.
-
-Once these fields have been correctly entered, a user can click Generate KSK. The user will be presented with a confirmation screen to help them understand the impact of generating the KSK. If a user confirms, the KSK will be generated and stored in Traffic Vault.
-
-Additionally, Traffic Ops also performs some systematic management of DNSSEC keys. This management is necessary to help keep keys in sync for Delivery Services in a CDN as well as to make sure keys do not expire without human intervention.
-
-**Generation of keys for new Delivery Services**
-
-If a new Delivery Service is created and added to a CDN that has DNSSEC enabled, Traffic Ops will create DNSSEC keys for the Delivery Service and store them in Traffic Vault.
-
-**Regeneration of expiring keys for a Delivery Service**
-
-Traffic Ops has a process, controlled by cron, to check for expired or expiring keys and re-generate them. The process runs at 5 minute intervals to check and see if keys are expired or close to expiring (withing 10 minutes by default). If keys are expired for a Delivery Service, traffic ops will regenerate new keys and store them in Traffic Vault. This process is the same for the CDN TLD ZSK, however Traffic Ops will not re-generate the CDN TLD KSK systematically. The reason is that [...]
diff --git a/docs/latest/_sources/admin/traffic_portal/installation.rst.txt b/docs/latest/_sources/admin/traffic_portal/installation.rst.txt
deleted file mode 100644
index 55b064b..0000000
--- a/docs/latest/_sources/admin/traffic_portal/installation.rst.txt
+++ /dev/null
@@ -1,51 +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.
-..
-
-*****************************
-Traffic Portal Administration
-*****************************
-The following are requirements to ensure an accurate set up:
-
-* CentOS 6.7 or 7
-* Node.js 6.0.x or above
-
-**Installing Traffic Portal**
-
- - Download the Traffic Portal RPM from `Apache Jenkins <https://builds.apache.org/view/S-Z/view/TrafficControl/job/incubator-trafficcontrol-master-build/>`_ or build the Traffic Portal RPM from source (./pkg -v traffic_portal_build).
- - Copy the Traffic Portal RPM to your server
- - curl --silent --location https://rpm.nodesource.com/setup_6.x | sudo bash -
- - sudo yum install -y nodejs
- - sudo yum install -y <traffic_portal rpm>
-
-**Configuring Traffic Portal**
-
- - update /etc/traffic_portal/conf/config.js (if upgrade, reconcile config.js with config.js.rpmnew and then delete config.js.rpmnew)
- - update /opt/traffic_portal/public/traffic_portal_properties.json (if upgrade, reconcile traffic_portal_properties.json with traffic_portal_properties.json.rpmnew and then delete traffic_portal_properties.json.rpmnew)
- - [OPTIONAL] update /opt/traffic_portal/public/resources/assets/css/custom.css (to customize traffic portal skin)
-
-**Starting Traffic Portal**
-
- - sudo service traffic_portal start
-
-**Stopping Traffic Portal**
-
- - sudo service traffic_portal stop
-
-
-
-
-
-
-
diff --git a/docs/latest/_sources/admin/traffic_portal/usingtrafficportal.rst.txt b/docs/latest/_sources/admin/traffic_portal/usingtrafficportal.rst.txt
deleted file mode 100644
index c7247e3..0000000
--- a/docs/latest/_sources/admin/traffic_portal/usingtrafficportal.rst.txt
+++ /dev/null
@@ -1,800 +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.
-..
-
-.. _usingtrafficportal:
-
-Traffic Portal - Using
-%%%%%%%%%%%%%%%%%%%%%%
-
-Traffic Portal is the official replacement for the legacy Traffic Ops UI. Traffic Portal consumes the Traffic Ops API. The following high-level items are available in the Traffic Portal menu.
-
-.. image:: ./images/tp_menu.png
-
-Dashboard
-=========
-
-The Dashboard is the default landing page for Traffic Portal. It provides a real-time view into the main performance indicators of the CDNs managed by Traffic Control. It also displays various statistics about the overall health of your CDN.
-
-* **Current Bandwidth**: The current bandwidth of all of your CDNs.
-* **Current Connections**: The current number of connections to all of your CDNs.
-* **Healthy Caches**: Number of healthy caches across all CDNs. Click the link to view the healthy caches on the cache stats page.
-* **Unhealthy Caches**: Number of unhealthy caches across all CDNs. Click the link to view the unhealthy caches on the cache stats page.
-* **Online Caches**: Number of online caches. Traffic Monitor will not monitor the state of ONLINE servers. True health is unknown.
-* **Reported Caches**: Number of caches with REPORTED status.
-* **Offline Caches**: Number of caches with OFFLINE status.
-* **Admin Down Caches**: Number of caches with ADMIN_DOWN status.
-
-Each component of this view is updated at the intervals defined in tp.domain.com/traffic_portal_properties.json.
-
-CDNs
-====
-
-A table of CDNs with the following columns:
-
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+======================================================================================================================+
-| Name | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Domain | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| DNSSEC Enabled | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-
-CDN management includes the ability to (where applicable):
-
-- create a new CDN
-- update an existing CDN
-- delete an existing CDN
-- queue/clear updates on all servers in a CDN
-- diff CDN snapshot
-- create CDN snapshot
-- manage CDN DNSSEC keys
-- manage CDN federations
-- view CDN delivery services
-- view CDN profiles
-- view CDN servers
-
-Monitor
-=======
-
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +===============+====================================================================================================================================+
- | Cache Checks | A real time view into the status of each cache. |
- | | This view is sourced by the Traffic Monitor data thru the Traffic Ops API and is updated on demand. |
- | | See :ref:`tp-cache-checks` for details. |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Cache Stats | A table showing the results of the periodic check extension scripts that are run. See :ref:`tp-cache-stats` for details. |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-
-Services
-========
-
- +----------------------------------+-----------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +==================================+=================================================================================================================+
- | Delivery Services | Settings for your delivery services. Only the delivery services defined by a user's tenancy are visible. |
- | | See :ref:`tp-delivery-services` for details. |
- +----------------------------------+-----------------------------------------------------------------------------------------------------------------+
- | Delivery Service Requests | If enabled in tp.domain.com/traffic_portal_properties.json, all delivery service changes (create, update and |
- | | delete) are captured as a delivery service request and must be reviewed before fulfillment/deployment. |
- | | See :ref:`tp-delivery-service-requests` for details. |
- +----------------------------------+-----------------------------------------------------------------------------------------------------------------+
-
-Configure
-=========
-
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +===============+====================================================================================================================================+
- | Servers | Manage servers. See :ref:`tp-servers` |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Profiles | Manage profiles. See :ref:`tp-profiles` |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Parameters | Manage parameters. See :ref:`tp-parameters` |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Types | Manage types. See :ref:`tp-types` |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
- | Statuses | Manage server statuses. See :ref:`tp-statuses` |
- +---------------+------------------------------------------------------------------------------------------------------------------------------------+
-
-Topology
-========
-
- +----------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +================+===================================================================================================================================+
- | Cache Groups | Manage cache groups. See :ref:`tp-cache-groups` |
- +----------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Phys Locations | Manage profiles. See :ref:`tp-phys-locations` |
- +----------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Divisions | Manage divisions. See :ref:`tp-divisions` |
- +----------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | Regions | Manage regions. See :ref:`tp-regions` |
- +----------------+-----------------------------------------------------------------------------------------------------------------------------------+
- | ASNs | Manage autonomous system numbers (ASN). See :ref:`tp-asns` |
- +----------------+-----------------------------------------------------------------------------------------------------------------------------------+
-
-Tools
-=====
-
- +--------------------+-------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +====================+===============================================================================================================================+
- | Invalidate Content | Manage invalidate content jobs. See :ref:`tp-jobs` |
- +--------------------+-------------------------------------------------------------------------------------------------------------------------------+
- | Generate ISO | Generate a bootable image for any of the servers in the Servers table (or any server for that matter). See :ref:`tp-gen-iso` |
- +--------------------+-------------------------------------------------------------------------------------------------------------------------------+
-
-User Admin
-==========
-
- +--------------------+-------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +====================+===============================================================================================================================+
- | Users | Manage users. See :ref:`tp-users` |
- +--------------------+-------------------------------------------------------------------------------------------------------------------------------+
- | Tenants | Manage tenants. See :ref:`tp-tenants` |
- +--------------------+-------------------------------------------------------------------------------------------------------------------------------+
- | Roles | Manage roles. See :ref:`tp-roles` |
- +--------------------+-------------------------------------------------------------------------------------------------------------------------------+
-
-
-Other
-=====
-
- Custom menu items. By default, you get a link to Traffic Control docs. See :ref:`tp-menu-other`
-
- +--------------------+--------------------------------------------------------------------------------------------------------------------------------+
- | Option | Description |
- +====================+================================================================================================================================+
- | Docs | Link to trafficcontrol.apache.org |
- +--------------------+--------------------------------------------------------------------------------------------------------------------------------+
-
-------------
-
-Monitor
-=======
-
-.. image:: ./images/tp_menu_monitor.png
-
-.. _tp-cache-checks:
-
-Cache Checks
-++++++++++++
-The cache checks page is intended to give an overview of the caches managed by Traffic Control as well as their status.
-
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+==========+============================================================================================================================================+
-| Hostname | Cache host name |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| Profile | The name of the profile applied to the cache |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| Status | The status of the cache (ONLINE, REPORTED, ADMIN_DOWN, OFFLINE) |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| UPD | Config updates pending for an edge or mid |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| RVL | Content invalidation requests are pending for and edge or mid |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| ILO | Ping the iLO interface for EDGE or MID servers |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| 10G | Ping the IPv4 address of the EDGE or MID servers |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| FQDN | DNS check that matches what the DNS servers responds with compared to |
-| | what Traffic Ops has. |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| DSCP | Checks the DSCP value of packets from the edge server to the Traffic |
-| | Ops server. |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| 10G6 | Ping the IPv6 address of the EDGE or MID servers |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| MTU | Ping the EDGE or MID using the configured MTU from Traffic Ops |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| RTR | Content Router checks. Checks the health of the Content Routers. Checks the health of the caches using the Content Routers. |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| CHR | Cache Hit Ratio in percent. |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| CDU | Total Cache Disk Usage in percent. |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| ORT | Operational Readiness Test. Uses the ORT script on the edge and mid servers to determine if the configuration in Traffic Ops matches the |
-| | configuration on the edge or mid. The user that this script runs as must have an ssh key on the edge servers. |
-+----------+--------------------------------------------------------------------------------------------------------------------------------------------+
-
-.. _tp-cache-stats:
-
-Cache Stats
-+++++++++++
-Displays health by cache group/profile.
-
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+==============+========================================================================================================================================+
-| Profile | Name of the profile applied to the edge or mid cache |
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-| Host | ALL or grouped by profile |
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-| Cache Group | Cache Group Name |
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-| Healthy | True/False as determined by Traffic Monitor |
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-| Status | Status of the cache or cache group |
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-| Connections | Number of connections |
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-| MbpsOut | MbpsOut |
-+--------------+----------------------------------------------------------------------------------------------------------------------------------------+
-
-Services
-========
-
-.. image:: ./images/tp_menu_services.png
-
-.. _tp-delivery-services:
-
-Delivery Services
-+++++++++++++++++
-
-A table of your delivery services with the following columns:
-
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+=======================================================================================================================+
-| Key (XML ID) | A unique string that identifies this delivery service. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Tenant | The tenant that the delivery service is assigned to. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Origin | The Origin Server's base URL. This includes the protocol (http or https). Example: ``http://movies.origin.com`` |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Active | When this is set to false, Traffic Router will not serve DNS or HTTP responses for this delivery service. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Type | The type of content routing this delivery service will use. See :ref:`rl-ds-types`. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Protocol | The protocol to serve this delivery service to the clients with: |
-| | |
-| | - HTTP |
-| | - HTTPS |
-| | - HTTP and HTTPS |
-| | - HTTP to HTTPS |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| CDN | The CDN that the delivery service belongs to. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| IPv6 Enabled | When set to true, the Traffic Router will respond to AAAA DNS requests for the routed name of this delivery service. |
-| | Otherwise, only A records will be served. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| DSCP | The DSCP value to mark IP packets to the client with. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Signing Algorithm | See :ref:`rl-signed-urls`. |
-| | - None |
-| | - URL Signature Keys |
-| | - URI Signing Keys |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Query String Handling | How to treat query strings: |
-| | |
-| | - use in cache key and hand up to origin (each unique query string is treated as a unique URL.) |
-| | - do not use in cache key, but pass up to origin (2 URLs that are the same except for the query string will match, |
-| | and cache HIT, while the origin still sees original query string in the request.) |
-| | - drop at edge (2 URLs that are the same except for the query string will match, and cache HIT, while the origin |
-| | will not see original query string in the request.) |
-| | |
-| | Dropping query strings at the edge will preclude the use of a Regex Remap Expression. See :ref:`rl-regex-remap`. |
-| | |
-| | To set the qstring without the use of regex remap, or for further options, see :ref:`rl-qstring-handling`. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-| Last Updated | Timestamp when the delivery service was last updated. |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------------+
-
-Delivery service management includes the ability to (where applicable):
-
-- create a new delivery service
-- clone an existing delivery service
-- update an existing delivery service
-- delete an existing delivery service
-- compare delivery services
-- manage delivery service SSL keys
-- manage delivery service URL signature keys
-- manage delivery service URI signing keys
-- view and assign delivery service servers
-- create, update and delete delivery service regexes
-- view and create delivery service invalidate content jobs
-- manage steering targets
-
-
-.. _tp-delivery-service-requests:
-
-Delivery Service Requests
-+++++++++++++++++++++++++
-
-A table of your delivery service requests with the following columns:
-
-.. image:: ./images/tp_table_ds_requests.png
-
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+======================================================================================================================+
-| Delivery Service | A unique string that identifies the delivery service that the request is associated with. |
-| | This unique string is also known as delivery service key or XML ID. |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Type | The type of delivery service request: |
-| | |
-| | - create (a request to create a new delivery service) |
-| | - update (a request to update an existing delivery service) |
-| | - delete (a request to delete an existing delivery service) |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Status | The status of the delivery service request: |
-| | |
-| | - draft (the delivery service request is NOT ready for review and fulfillment) |
-| | - submitted (the delivery service request is ready for review and fulfillment) |
-| | - rejected (the delivery service request has been rejected and cannot be modified) |
-| | - pending (the delivery service request has been fulfilled but the changes have yet to be deployed) |
-| | - complete (the delivery service request has been fulfilled and the changes have been deployed) |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Author | The user responsible for creating the delivery service request. |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Assignee | The user responsible for fulfilling the delivery service request. Currently, the operations role or above is |
-| | required to assign delivery service requests. |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Last Edited By | The last user to edit the delivery service request. |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Created | Relative time indicating when the delivery service was created. |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Actions | Actions that can be performed on a delivery service request: |
-| | |
-| | - fulfill (Implement the changes captured in the delivery service request.) |
-| | - reject (Reject the changes captured in the delivery service request.) |
-| | - delete (Delete the delivery service request.) |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-
-Delivery service request management includes the ability to (where applicable):
-
-- create a new delivery service request
-- update an existing delivery service request
-- delete an existing delivery service request
-- update the status of a delivery service request
-- assign a delivery service request
-- reject a delivery service request
-- fulfill a delivery service request
-- complete a delivery service request
-
-See :ref:`ds_requests` for details.
-
-Configure
-=========
-
-.. image:: ./images/tp_menu_configure.png
-
-.. _tp-servers:
-
-Servers
-+++++++
-
-A table of servers with the following columns:
-
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+======================================================================================================================+
-| UPD | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Host | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Domain | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| IP | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| IPv6 | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Status | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Type | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Profile | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| CDN | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Cache Group | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| ISO | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-
-Server management includes the ability to (where applicable):
-
-- create a new server
-- update an existing server
-- delete an existing server
-- queue/clear updates on a server
-- update server status
-- view server delivery services
-- view server config files
-- clone delivery service assignments
-- assign delivery services to server
-
-.. _tp-profiles:
-
-Profiles
-++++++++
-
-A table of profiles with the following columns:
-
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+======================================================================================================================+
-| Name | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Type | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Routing Disabled | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Description | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| CDN | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-
-Profile management includes the ability to (where applicable):
-
-- create a new profile
-- update an existing profile
-- delete an existing profile
-- clone a profile
-- export a profile
-- view profile parameters
-- view profile delivery services
-- view profile servers
-
-See :ref:`rl-working-with-profiles` for details.
-
-.. _tp-parameters:
-
-Parameters
-++++++++++
-
-A table of parameters with the following columns:
-
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+======================================================================================================================+
-| Name | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Config File | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Value | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-
-Parameter management includes the ability to (where applicable):
-
-- create a new parameter
-- update an existing parameter
-- delete an existing parameter
-- view parameter profiles
-
-.. _tp-types:
-
-Types
-+++++
-
-A table of types with the following columns:
-
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+======================================================================================================================+
-| Name | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Use In Table | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-| Description | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------------+
-
-Type management includes the ability to (where applicable):
-
-- create a new type
-- update an existing type
-- delete an existing type
-- view delivery services assigned to a type
-- view servers assigned to a type
-- view cache groups assigned to a type
-
-.. _tp-statuses:
-
-Statuses
-++++++++
-
-A table of statuses with the following columns:
-
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+=====================================================================================================================+
-| Name | |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-| Description | |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-
-Status management includes the ability to (where applicable):
-
-- create a new status
-- update an existing status
-- delete an existing status
-- view status servers
-
-Topology
-========
-
-.. image:: ./images/tp_menu_topology.png
-
-.. _tp-cache-groups:
-
-Cache Groups
-++++++++++++
-
-A table of cache groups with the following columns:
-
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+=====================================================================================================================+
-| Name | |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-| Short Name | |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-| Type | |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-| Latitude | |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-| Longitude | |
-+-------------------------------+---------------------------------------------------------------------------------------------------------------------+
-
-Cache group management includes the ability to (where applicable):
-
-- create a new cache group
-- update an existing cache group
-- delete an existing cache group
-- queue/clear updates for all servers in a cache group
-- view cache group ASNs
-- view and assign cache group parameters
-- view cache group servers
-
-.. _tp-phys-locations:
-
-Phys Locations
-++++++++++++++
-
-A table of physical locations with the following columns:
-
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+===================================================================================================================+
-| Name | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-| Short Name | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-| Address | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-| City | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-| State | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-| Region | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-
-Physical location management includes the ability to (where applicable):
-
-- create a new physical location
-- update an existing physical location
-- delete an existing physical location
-- view physical location servers
-
-.. _tp-divisions:
-
-Divisions
-+++++++++
-
-A table of divisions with the following columns:
-
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+===================================================================================================================+
-| Name | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------------+
-
-Division management includes the ability to (where applicable):
-
-- create a new division
-- update an existing division
-- delete an existing division
-- view division regions
-
-.. _tp-regions:
-
-Regions
-+++++++
-
-A table of regions with the following columns:
-
-+-------------------------------+------------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+==================================================================================================================+
-| Name | |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------+
-| Division | |
-+-------------------------------+------------------------------------------------------------------------------------------------------------------+
-
-Region management includes the ability to (where applicable):
-
-- create a new region
-- update an existing region
-- delete an existing region
-- view region physical locations
-
-.. _tp-asns:
-
-ASNs
-++++
-
-A table of ASNs with the following columns:
-
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+=================================================================================================================+
-| ASN | |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------+
-| Cache Group | |
-+-------------------------------+-----------------------------------------------------------------------------------------------------------------+
-
-ASN management includes the ability to (where applicable):
-
-- create a new ASN
-- update an existing ASN
-- delete an existing ASN
-
-Tools
-=====
-
-.. image:: ./images/tp_menu_tools.png
-
-.. _tp-jobs:
-
-Invalidate Content
-++++++++++++++++++
-
-A table of invalidate content jobs with the following columns:
-
-+-------------------------------+----------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+================================================================================================================+
-| Delivery Service | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------+
-| Asset URL | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------+
-| Parameters | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------+
-| Start | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------+
-| Created By | |
-+-------------------------------+----------------------------------------------------------------------------------------------------------------+
-
-Invalidate content includes the ability to (where applicable):
-
-- create a new invalidate content job
-
-.. _tp-gen-iso:
-
-Generate ISO
-++++++++++++
-
-See :ref:`rl-generate-iso`
-
-User Admin
-==========
-
-.. image:: ./images/tp_menu_user_admin.png
-
-.. _tp-users:
-
-Users
-+++++
-
-A table of users with the following columns:
-
-+-------------------------------+--------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+==============================================================================================================+
-| Full Name | |
-+-------------------------------+--------------------------------------------------------------------------------------------------------------+
-| Username | |
-+-------------------------------+--------------------------------------------------------------------------------------------------------------+
-| Email | |
-+-------------------------------+--------------------------------------------------------------------------------------------------------------+
-| Tenant | |
-+-------------------------------+--------------------------------------------------------------------------------------------------------------+
-| Role | |
-+-------------------------------+--------------------------------------------------------------------------------------------------------------+
-
-User management includes the ability to (where applicable):
-
-- register a new user
-- create a new user
-- update an existing user
-- view delivery services visible to a user
-
-.. _tp-tenants:
-
-Tenants
-+++++++
-
-A table of tenants with the following columns:
-
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+=============================================================================================================+
-| Name | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-| Active | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-| Parent | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-
-Tenant management includes the ability to (where applicable):
-
-- create a new tenant
-- update an existing tenant
-- delete an existing tenant
-- view users assigned to a tenant
-- view delivery services assigned to a tenant
-
-.. _tp-roles:
-
-Roles
-+++++
-
-A table of roles with the following columns:
-
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-| Name | Description |
-+===============================+=============================================================================================================+
-| Name | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-| Privilege Level | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-| Description | |
-+-------------------------------+-------------------------------------------------------------------------------------------------------------+
-
-Role management includes the ability to (where applicable):
-
-- view all roles
-
-Other
-=====
-
-.. image:: ./images/tp_menu_other.png
-
-.. _tp-menu-other:
-
-Custom Menu Items
-+++++++++++++++++
-
-This section is configurable in tp.domain.com/traffic_portal_properties.json in the customMenu section.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/docs/latest/_sources/admin/traffic_router.rst.txt b/docs/latest/_sources/admin/traffic_router.rst.txt
deleted file mode 100644
index b8ed3ba..0000000
--- a/docs/latest/_sources/admin/traffic_router.rst.txt
+++ /dev/null
@@ -1,588 +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.
-..
-
-*****************************
-Traffic Router Administration
-*****************************
-.. contents::
- :depth: 2
- :backlinks: top
-
-Installing Traffic Router
-==========================
-The following are requirements to ensure an accurate set up:
-
-* CentOS 6
-* 4 vCPUs
-* 8GB RAM
-* Successful install of Traffic Ops
-* Successful install of Traffic Monitor
-* Administrative access to Traffic Ops
-
-.. Note:: Hardware requirements are generally doubled if DNSSEC is enabled
-
-1. If no suitable profile exists, create a new profile for Traffic Router.
-
-2. Enter the Traffic Router server into Traffic Ops, assign it to a Traffic Router profile, and ensure that its status is set to ``ONLINE``.
-3. Ensure the FQDN of the Traffic Router is resolvable in DNS. This FQDN must be resolvable by the clients expected to use this CDN.
-4. Install a traffic router: ``sudo yum install traffic_router``.
-5. Edit ``/opt/traffic_router/conf/traffic_monitor.properties`` and specify the correct online Traffic Monitor(s) for your CDN. See :ref:`rl-tr-config-files`
- # traffic_monitor.properties: url that should normally point to this file
- traffic_monitor.properties=file:/opt/traffic_router/conf/traffic_monitor.properties
-
- # Frequency for reloading this file
- # traffic_monitor.properties.reload.period=60000
-
-
-6. Start Tomcat: ``sudo service tomcat start``, and test lookups with dig and curl against that server.
- To restart, ``sudo service tomcat stop``, kill the traffic router process, and ``sudo service tomcat start``
- Also, crconfig previously recieved will be cached, and needs to be removed manually to actually be reloaded /opt/traffic_router/db/cr-config.json
-7. Snapshot CRConfig; See :ref:`rl-snapshot-crconfig`
-
-.. Note:: Once the CRConfig is snapshotted, live traffic will be sent to the new Traffic Routers provided that their status is set to ``ONLINE``.
-
-8. Ensure that the parent domain (e.g.: kabletown.net) for the CDN's top level domain (e.g.: cdn.kabletown.net) contains a delegation (NS records) for the new Traffic Router, and that the value specified matches the FQDN used in step 3.
-
-Configuring Traffic Router
-==========================
-
-.. Note:: Starting with Traffic Router 1.5, many of the configuration files under ``/opt/traffic_router/conf`` are only needed to override the default configuration values for Traffic Router. Most of the given default values will work well for any CDN. Critical values that must be changed are hostnames and credentials for communicating with other Traffic Control components such as Traffic Ops and Traffic Monitor.
-
-.. Note:: Pre-existing installations having configuration files in ``/opt/traffic_router/conf`` will still be used and honored for Traffic Router 1.5 and onward.
-
-For the most part, the configuration files and parameters that follow are used to get Traffic Router online and communicating with various Traffic Control components. Once Traffic Router is successfully communicating with Traffic Control, configuration is mostly performed in Traffic Ops, and is distributed throughout Traffic Control via the CRConfig snapshot process. See :ref:`rl-snapshot-crconfig` for more information. Please see the parameter documentation for Traffic Router in the Usi [...]
-
-.. _rl-tr-config-files:
-
-Configuration files
--------------------
-
-+----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| File name | Parameter | Description | Default Value |
-+============================+===========================================+=====================================================================================================+===================================================+
-| traffic_monitor.properties | traffic_monitor.bootstrap.hosts | Traffic Monitor FQDNs and port if necessary, separated by a semicolon (;) | N/A |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | traffic_monitor.bootstrap.local | Use only the Traffic Monitors specified in config file | false |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | traffic_monitor.properties | Path to the traffic_monitor.properties file; used internally to monitor the file for changes | /opt/traffic_router/traffic_monitor.properties |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | traffic_monitor.properties.reload.period | The interval in milliseconds which Traffic Router will reload this configuration file | 60000 |
-+----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| dns.properties | dns.tcp.port | TCP port that Traffic Router will use for incoming DNS requests | 53 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | dns.tcp.backlog | Maximum length of the queue for incoming TCP connection requests | 0 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | dns.udp.port | UDP port that Traffic Router will use for incoming DNS requests | 53 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | dns.max-threads | Maximum number of threads used to process incoming DNS requests | 1000 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | dns.zones.dir | Path to auto generated zone files for reference | /opt/traffic_router/var/auto-zones |
-+----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| traffic_ops.properties | traffic_ops.username | Username to access the APIs in Traffic Ops (must be in the admin role) | admin |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | traffic_ops.password | Password for the user specified in traffic_ops.username | N/A |
-+----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| cache.properties | cache.geolocation.database | Full path to the local copy of the MaxMind geolocation binary database file | /opt/traffic_router/db/GeoIP2-City.mmdb |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.geolocation.database.refresh.period | The interval in milliseconds which Traffic Router will poll for a new geolocation database | 604800000 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.czmap.database | Full path to the local copy of the coverage zone file | /opt/traffic_router/db/czmap.json |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.czmap.database.refresh.period | The interval in milliseconds which Traffic Router will poll for a new coverage zone file | 10800000 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.dczmap.database | Full path to the local copy of the deep coverage zone file | /opt/traffic_router/db/dczmap.json |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.dczmap.database.refresh.period | The interval in milliseconds which Traffic Router will poll for a new deep coverage zone file | 10800000 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.health.json | Full path to the local copy of the health state | /opt/traffic_router/db/health.json |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.health.json.refresh.period | The interval in milliseconds which Traffic Router will poll for a new health state file | 1000 |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.config.json | Full path to the local copy of the CRConfig | /opt/traffic_router/db/cr-config.json |
-| +-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| | cache.config.json.refresh.period | The interval in milliseconds which Traffic Router will poll for a new CRConfig | 60000 |
-+----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-| log4j.properties | various parameters | Configuration of log4j is documented on their site; adjust as necessary based on needs | N/A |
-+----------------------------+-------------------------------------------+-----------------------------------------------------------------------------------------------------+---------------------------------------------------+
-
-.. _rl-tr-dnssec:
-
-DNSSEC
-======
-
-Overview
---------
-Domain Name System Security Extensions (DNSSEC) is a set of extensions to DNS that provides a cryptographic mechanism for resolvers to verify the authenticity of responses served by an authoritative DNS server.
-
-Several RFCs (4033, 4044, 4045) describe the low level details and define the extensions, RFC 7129 provides clarification around authenticated denial of existence of records, and finally RFC 6781 describes operational best practices for administering an authoritative DNSSEC enabled DNS server. The authenticated denial of existence RFC describes how an authoritative DNS server responds in NXDOMAIN and NODATA scenarios when DNSSEC is enabled.
-
-Traffic Router currently supports DNSSEC with NSEC, however, NSEC3 and more configurable options will be provided in the future.
-
-Operation
----------
-Upon startup or a configuration change, Traffic Router obtains keys from the keystore API in Traffic Ops which returns key signing keys (KSK) and zone signing keys (ZSK) for each delivery service that is a subdomain off the CDN's top level domain (TLD), in addition to the keys for the CDN TLD itself. Each key has timing information that allows Traffic Router to determine key validity (expiration, inception, and effective dates) in addition to the appropriate TTL to use for the DNSKEY rec [...]
-
-Once Traffic Router obtains the key data from the API, it converts each public key into the appropriate record types (DNSKEY, DS) to place in zones and uses the private key to sign zones. DNSKEY records are added to each delivery service's zone (e.g.: mydeliveryservice.cdn.kabletown.net) for every valid key that exists, in addition to the CDN TLD's zone. A DS record is generated from each zone's KSK and is placed in the CDN TLD's zone (e.g.: cdn.kabletown.net); the DS record for the CDN [...]
-
-The DNSKEY to DS record relationship allows resolvers to validate signatures across zone delegation points; with Traffic Control, we control all delegation points below the CDN's TLD, **however, the DS record for the CDN TLD must be placed in the parent zone (e.g.: kabletown.net), which is not managed by Traffic Control**. As such, the DS record (available in the Traffic Ops DNSSEC administration UI) must be placed in the parent zone prior to enabling DNSSEC, and prior to generating a ne [...]
-
-Rolling Zone Signing Keys
--------------------------
-Traffic Router currently follows the zone signing key pre-publishing operational best practice described in `section 4.1.1.1 of RFC 6781`_. Once DNSSEC is enabled for a CDN in Traffic Ops, key rolls are triggered via Traffic Ops via the automated key generation process, and Traffic Router selects the active zone signing keys based on the expiration information returned from the keystore API in Traffic Ops.
-
-.. _section 4.1.1.1 of RFC 6781: https://tools.ietf.org/html/rfc6781#section-4.1.1.1
-
-Troubleshooting and log files
-=============================
-Traffic Router log files are in ``/opt/traffic_router/var/log``, and Tomcat log files are in ``/opt/tomcat/logs``. Application related logging is in ``/opt/traffic_router/var/log/traffic_router.log``, while access logs are written to ``/opt/traffic_router/var/log/access.log``.
-
-Event Log File Format
-=====================
-
-Summary
--------
-
-All access events to Traffic Router are logged to the file ``/opt/traffic_router/var/log/access.log``
-This file grows up to 200Mb and gets rolled into older log files, 10 log files total are kept (total of up to 2Gb of logged events per traffic router)
-
-Traffic Router logs access events in a format that largely following `ATS event logging format
-<https://docs.trafficserver.apache.org/en/6.0.x/admin/event-logging-formats.en.html>`_
-
---------------
-
-Sample Message
---------------
-
-Items within brackets below are detailed under the HTTP and DNS sections
-::
-
- 144140678.000 qtype=DNS chi=192.168.10.11 ttms=789 [Fields Specific to the DNS request] rtype=CZ rloc="40.252611,58.439389" rdtl=- rerr="-" [Fields Specific to the DNS result]
- 144140678.000 qtype=HTTP chi=192.168.10.11 ttms=789 [Fields Specific to the HTTP request] rtype=GEO rloc="40.252611,58.439389" rdtl=- rerr="-" [Fields Specific to the HTTP result]
-
-.. Note:: The above message samples contain fields that are always present for every single access event to Traffic Router
-
-**Message Format**
-- Each event that is logged is a series of space separated key value pairs except for the first item.
-- The first item is always the epoch in seconds with a decimal field precision of up to milliseconds
-- Each key value pair is in the form of unquoted string, equals character, optionally quoted string
-- Values that are quoted strings may contain space characters
-- Values that are not quoted should not contains any space characters
-
-.. Note:: Any value that is a single dash character or a dash character enclosed in quotes represents an empty value
-
---------
-
-Fields Always Present
----------------------
-
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-|Name |Description |Data |
-+======+=================================================================================+====================================================================================+
-|qtype |Whether the request was for DNS or HTTP |Always DNS or HTTP |
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-|chi |The IP address of the requester |Depends on whether this was a DNS or HTTP request, see below sections |
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-|ttms |The amount of time in milliseconds it took Traffic Router to process the request |A number greater than or equal to zero |
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-|rtype |Routing Result Type |One of ERROR, CZ, DEEP_CZ, GEO, MISS, STATIC_ROUTE, DS_REDIRECT, DS_MISS, INIT, FED |
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-|rloc |GeoLocation of result |Latitude and Longitude in Decimal Degrees |
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-|rdtl |Result Details Associated with unusual conditions |One of DS_NOT_FOUND, DS_NO_BYPASS, DS_BYPASS, DS_CZ_ONLY, DS_CZ_BACKUP_CG |
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-|rerr |Message about internal Traffic Router Error |String |
-+------+---------------------------------------------------------------------------------+------------------------------------------------------------------------------------+
-
-
-**rtype meanings**
-
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|Name |Meaning |
-+=============+========================================================================================================================================================================+
-|ERROR |An internal error occurred within Traffic Router, more details may be found in the rerr field |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|CZ |The result was derived from Coverage Zone data based on the address in the chi field |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|DEEP_CZ |The result was derived from Deep Coverage Zone data based on the address in the chi field |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|GEO |The result was derived from geolocation service based on the address in the chi field |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|MISS |Traffic Router was unable to resolve a DNS request or find a cache for the requested resource |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|STATIC_ROUTE |_*DNS Only*_ No DNS Delivery Service supports the hostname portion of the requested url |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|DS_MISS |_*HTTP Only*_ No HTTP Delivery Service supports either this request's URL path or headers |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|DS_REDIRECT |The result is using the Bypass Destination configured for the matched Delivery Service when that Delivery Service is unavailable or does not have the requested resource|
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|FED |_*DNS Only*_ The result was obtained through federated coverage zone data outside of any delivery service |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|GEO_REDIRECT |The request was redirected (302) based on the National Geo blocking (Geo Limit Redirect URL) configured on the Delivery Service. |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|RGALT |The request was redirected (302) to the Regional Geo blocking URL. Regional Geo blocking is enabled on the Delivery Service and is configured through the |
-| |regional_geoblock.polling.url setting for the Traffic Router profile. |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-|RGDENY |_*DNS Only*_ The result was obtained through federated coverage zone data outside of any delivery service The request was regionally blocked because there was no rule |
-| |for the request made. |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-| "-" |The request was not redirected. This is usually a result of a DNS request to the Traffic Router or an explicit denial for that request. |
-+-------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
-
-
-**rdtl meanings**
-
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|Name |Meaning |
-+=======================================+============================================================================================================================================+
-|DS_NOT_FOUND |Always goes with rtypes STATIC_ROUTE and DS_MISS |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|DS_BYPASS |Used Bypass Destination for Redirect of Delivery Service |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|DS_NO_BYPASS |No valid Bypass Destination is configured for the matched Delivery Service and the delivery service does not have the requested resource |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|DS_CZ_ONLY |The selected Delivery Service only supports resource lookup based on Coverage Zone data |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|DS_CLIENT_GEO_UNSUPPORTED |Traffic Router did not find a resource supported by coverage zone data and was unable to determine the geolocation of the requesting client |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|GEO_NO_CACHE_FOUND |Traffic Router could not find a resource via geolocation data based on the requesting client's geolocation |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|NO_DETAILS |This entry is for a standard request. |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|REGIONAL_GEO_ALTERNATE_WITHOUT_CACHE |This goes with the rtype RGDENY. The URL is being regionally Geo blocked. |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|REGIONAL_GEO_NO_RULE |The request was blocked because there was no rule in the Delivery Service for the request. |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-| "-" |The request was not redirected. This is usually a result of a DNS request to the Traffic Router or an explicit denial for that request. |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-|DS_CZ_BACKUP_CG |Traffic Router found a backup cache via fallback (cr-config's edgeLocation) / coordinates (CZF) configuration |
-+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------+
-
-
----------------
-
-HTTP Specifics
---------------
-
-Sample Message
-::
-
- 1452197640.936 qtype=HTTP chi=69.241.53.218 url="http://foo.mm-test.jenkins.cdnlab.comcast.net/some/asset.m3u8" cqhm=GET cqhv=HTTP/1.1 rtype=GEO rloc="40.252611,58.439389" rdtl=- rerr="-" pssc=302 ttms=0 rurl="http://odol-atsec-sim-114.mm-test.jenkins.cdnlab.comcast.net:8090/some/asset.m3u8" rh="Accept: */*" rh="myheader: asdasdasdasfasg"
-
-**Request Fields**
-
-+-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
-|Name |Description |Data |
-+=====+=========================================================================================================================================+===========================================+
-|url |Requested URL with query string |String |
-+-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
-|cqhm |Http Method |e.g GET, POST |
-+-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
-|cqhv |Http Protocol Version |e.g. HTTP/1.1 |
-+-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
-|rh |One or more of these key value pairs may exist in a logged event and are controlled by the configuration of the matched Delivery Service |Key value pair of the format "name: value" |
-+-----+-----------------------------------------------------------------------------------------------------------------------------------------+-------------------------------------------+
-
-**Response Fields**
-
-+-----+----------------------------------------------------------+------------+
-|Name |Description |Data |
-+=====+==========================================================+============+
-|rurl |The resulting url of the resource requested by the client |A URL String|
-+-----+----------------------------------------------------------+------------+
-
-------------
-
-DNS Specifics
--------------
-
-Sample Message
-::
-
- 144140678.000 qtype=DNS chi=192.168.10.11 ttms=123 xn=65535 fqdn=www.example.com. type=A class=IN ttl=12345 rcode=NOERROR rtype=CZ rloc="40.252611,58.439389" rdtl=- rerr="-" ans="192.168.1.2 192.168.3.4 0:0:0:0:0:ffff:c0a8:102 0:0:0:0:0:ffff:c0a8:304"
-
-**Request Fields**
-
-.. _qname: http://www.zytrax.com/books/dns/ch15/#qname
-
-.. _qtype: http://www.zytrax.com/books/dns/ch15/#qtype
-
-+------+------------------------------------------------------------------+--------------------------------------------------------+
-|Name |Description |Data |
-+======+==================================================================+========================================================+
-|xn |The ID from the client DNS request header |a number from 0 to 65535 |
-+------+------------------------------------------------------------------+--------------------------------------------------------+
-|fqdn |The qname field from the client DNS request message (i.e. The |A series of DNS labels/domains separated by '.' |
-| |fully qualified domain name the client is requesting be resolved) |characters and ending with a '.' character (see qname_) |
-+------+------------------------------------------------------------------+--------------------------------------------------------+
-|type |The qtype field from the client DNS request message (i.e. |Examples are A (IpV4), AAAA (IpV6), NS (Name Service), |
-| |the type of resolution that's requested such as IPv4, IPv6) | SOA (Start of Authority), and CNAME, (see qtype_) |
-+------+------------------------------------------------------------------+--------------------------------------------------------+
-|class |The qclass field from the client DNS request message (i.e. The |Either IN (Internet resource) or ANY (Traffic router |
-| |class of resource being requested) | rejects requests with any other value of class) |
-+------+------------------------------------------------------------------+--------------------------------------------------------+
-
-**Response Fields**
-
-+------+---------------------------------------------------------------------+-----------------------------------------------------+
-|Name | Description | Data |
-+======+=====================================================================+=====================================================+
-|ttl | The 'time to live' in seconds for the answer provided by Traffic |A number from 0 to 4294967295 |
-| | Router (clients can reliably use this answer for this long without | |
-| | re-querying traffic router) | |
-+------+---------------------------------------------------------------------+-----------------------------------------------------+
-|rcode | The result code for the DNS answer provided by Traffic Router | One of NOERROR (success), NOTIMP (request is not |
-| | | NOTIMP (request is not supported), |
-| | | REFUSED (request is refused to be answered), or |
-| | | NXDOMAIN (the domain/name requested does not exist) |
-+------+---------------------------------------------------------------------+-----------------------------------------------------+
-
-.. _rl-tr-ngb:
-
-GeoLimit Failure Redirect feature
-=================================
-
-Overview
---------
-This feature is also called 'National GeoBlock' feature which is short for 'NGB' feature. In this section, the acronym 'NGB' will be used for this feature.
-
-In the past, if the Geolimit check fails (for example, the client ip is not in the 'US' region but the geolimit is set to 'CZF + US'), the router will return 503 response; but with this feature, when the check fails, it will return 302 if the redirect url is set in the delivery service.
-
-The Geolimit check failure has such scenarios:
-1) When the GeoLimit is set to 'CZF + only', if the client ip is not in the the CZ file, the check fails
-2) When the GeoLimit is set to any region, like 'CZF + US', if the client ip is not in such region, and the client ip is not in the CZ file, the check fails
-
-
-Configuration
--------------
-To enable the NGB feature, the DS must be configured with the proper redirect url. And the setting lays at 'Delivery Services'->Edit->'GeoLimit Redirect URL'. If no url is put in this field, the feature is disabled.
-
-The URL has 3 kinds of formats, which have different meanings:
-
-1. URL with no domain. If no domain is in the URL (like 'vod/dance.mp4'), the router will try to find a proper cache server within the delivery service and return the redirect url with the format like 'http://<cache server name>.<delivery service's FQDN>/<configured relative path>'
-
-2. URL with domain that matches with the delivery service. For this URL, the router will also try to find a proper cache server within the delivery service and return the same format url as point 1.
-
-3. URL with domain that doesn't match with the delivery service. For this URL, the router will return the configured url directly to the client.
-
-
-.. _rl-deep-cache:
-
-Deep Caching - Deep Coverage Zone Topology
-==========================================
-
-Overview
---------
-
-Deep Caching is a feature that enables clients to be routed to the closest
-possible "deep" edge caches on a per Delivery Service basis. The term "deep" is
-used in the networking sense, meaning that the edge caches are located deep in
-the network where the number of network hops to a client is as minimal as
-possible. This deep caching topology is desirable because storing content closer
-to the client gives better bandwidth savings, and sometimes the cost of
-bandwidth usage in the network outweighs the cost of adding storage. While it
-may not be feasible to cache an entire copy of the CDN's contents in every deep
-location (for the best possible bandwidth savings), storing just a relatively
-small amount of the CDN's most requested content can lead to very high bandwidth
-savings.
-
-Getting started
----------------
-
-What you need:
-
-#. Edge caches deployed in "deep" locations and registered in Traffic Ops
-#. A Deep Coverage Zone File (DCZF) mapping these deep cache hostnames to specific network prefixes (see :ref:`rl-deep-czf` for details)
-#. Deep caching parameters in the Traffic Router Profile (see :ref:`rl-ccr-profile` for details):
-
- * ``deepcoveragezone.polling.interval``
- * ``deepcoveragezone.polling.url``
-
-#. Deep Caching enabled on one or more HTTP Delivery Services (i.e. ``deepCachingType`` = ALWAYS)
-
-How it works
-------------
-
-Deep Coverage Zone routing is very similar to that of regular Coverage Zone
-routing, except that the DCZF is preferred over the regular CZF for Delivery
-Services with DC (Deep Caching) enabled. If the client requests a DC-enabled
-Delivery Service and their IP address gets a "hit" in the DCZF, Traffic Router
-will attempt to route that client to one of the available deep caches in the
-client's corresponding zone. If there are no deep caches available for a
-client's request, Traffic Router will "fall back" to the regular CZF and
-continue regular CZF routing from there.
-
-
-.. _rl-tr-steering:
-
-Steering feature
-================
-
-Overview
---------
-A Steering delivery service is a delivery service that is used to "steer" traffic to other delivery services. A Steering delivery service will have target delivery services configured for it with weights assigned to them. Traffic Router uses the weights to make a consistent hash ring which it then uses to make sure that requests are routed to a target based on the configured weights. This consistent hash ring is separate from the consistent hash ring used in cache selection.
-
-Special regular expressions called Filters can also be configured for target delivery services to pin traffic to a specific delivery service. For example, if a filter called .*/news/.* for a target called target-ds-1 is created, any requests to traffic router with 'news' in them will be routed to target-ds-1. This will happen regardless of the configured weights.
-
-A client can bypass the steering functionality by providing a header called X-TC-Steering-Option with the xml_id of the target delivery service to route to. When Traffic Router receives this header it will route to the requested target delivery service regardless of weight configuration.
-
-Some other points of interest:
-
-- Steering is currently only available for HTTP delivery services that are a part of the same CDN.
-- A new role called STEERING has been added to the traffic ops database. Only users with Admin or Steering privileges can modify steering assignments for a Delivery Service.
-- A new API has been created in Traffic Ops under /internal. This API is used by a Steering user to add filters and modify assignments. (Filters can only be added via the API).
-- Traffic Router uses the steering API in Traffic Ops to poll for steering assignments, the assignments are then used when routing traffic.
-
-A couple simple use cases for steering are:
-
-#. Migrating traffic from one delivery service to another over time.
-#. Trying out new functionality for a subset of traffic with an experimental delivery service.
-#. Load balancing between delivery services.
-
-
-
-Configuration
--------------
-
-The following needs to be completed for Steering to work correctly:
-
-#. Two target delivery services are created in Traffic Ops. They must both be HTTP delivery services part of the same CDN.
-#. A delivery service with type STEERING is created in Traffic Ops.
-#. Target delivery services are assigned to the steering delivery service using Traffic Ops.
-#. A user with the role of Steering is created.
-#. Using the API, the steering user assigns weights to the target delivery services.
-#. If desired, the steering user can create filters for the target delivery services.
-
-For more information see the `steering how-to guide <quick_howto/steering.html>`_.
-
-HTTPS for Http Type Delivery Services
-=====================================
-
-Starting with version 1.7 Traffic Router added the ability to allow https traffic between itself and clients on a per http type delivery service basis.
-
-.. Warning::
- The establishing of an HTTPS connection is much more computationally demanding than an HTTP connection.
- Since each client will in turn get redirected to ATS, Traffic Router is most always creating a new HTTPS connection for all HTTPS traffic.
- It is likely to mean that an existing Traffic Router will have some decrease in performance depending on the amount of https traffic you want to support
- As noted for DNSSEC, you may need to plan to scale Traffic Router vertically and/or horizontally to handle the new load
-
-The summary for setting up https is to:
-
-#. Select one of 'https', 'http and https', or 'http to https' for the delivery service
-#. Generate private keys for the delivery service using a wildcard domain such as ``*.my-delivery-service.my-cdn.example.com``
-#. Obtain and import signed certificate chain
-#. Snapshot CR Config
-
-Clients may make HTTPS requests delivery services only after Traffic Router receives the certificate chain from Traffic Ops and the new CR Config.
-
-Protocol Options
-----------------
-
-*https only*
- Traffic Router will only redirect (send a 302) to clients communicating with a secure connection, all other clients will receive a 503
-*http and https*
- Traffic Router will redirect both secure and non-secure clients
-*http to https*
- Traffic Router will redirect non-secure clients with a 302 and a location that is secure (i.e. starting with 'https' instead of 'http'), secure clients will remain on https
-*http*
- Any secure client will get an SSL handshake error. Non-secure clients will experience the same behavior as prior to 1.7
-
-Certificate Retrieval
----------------------
-
-.. Warning::
- If you have https delivery services in your CDN, Traffic Router will not accept **any** connections until it is able to
- fetch certificates from Traffic Ops and load them into memory. Traffic Router does not persist certificates to the java keystore or anywhere else.
-
-Traffic Router fetches certificates into memory:
-
-* At startup time
-* When it receives a new CR Config
-* Once an hour from whenever the most recent of the last of the above occurred
-
-.. Note::
- To adjust the frequency when Traffic Router fetches certificates add the parameter 'certificates.polling.interval' to CR Config and
- setting it to the desired time in milliseconds.
-
-.. Note::
- Taking a snapshot of CR Config may be used at times to avoid waiting the entire polling cycle for a new set of certificates.
-
-.. Warning::
- If a snapshot of CR Config is made that involves a delivery service missing its certificates, Traffic Router will ignore **ALL** changes in that CR-Config
- until one of the following occurs:
- * It receives certificates for that delivery service
- * Another snapshot of CR Config is created and the delivery service without certificates is changed so it's HTTP protocol is set to 'http'
-
-Certificate Chain Ordering
---------------------------
-
-The ordering of certificates within the certificate bundle matters. It must be:
-
-#. Primary Certificate (e.g. the one created for ``*.my-delivery-service.my-cdn.example.com``)
-#. Intermediate Certificate(s)
-#. Root Certificate from CA (optional)
-
-.. Warning::
- If something is wrong with the certificate chain (e.g. the order of the certificates is backwards or for the wrong domain) the
- client will get an SSL handshake. Inspection of /opt/tomcat/logs/catalina.out is likely to yield information to reveal this.
-
-To see the ordering of certificates you may have to manually split up your certificate chain and use openssl on each individual certificate
-
-Suggested Way of Setting up an HTTPS Delivery Service
------------------------------------------------------
-
-Do the following in Traffic Ops:
-
-#. Select one of 'https', 'http and https', or 'http to https' for the protocol field of a delivery service and click 'Save'.
-#. Click 'Manage SSL Keys'.
-#. Click 'Generate New Keys'.
-#. Copy the contents of the Certificate Signing Request field and save it locally.
-#. Click 'Load Keys'.
-#. Select 'http' for the protocol field of the delivery service and click 'Save' (to avoid preventing other CR Config updates from being blocked by Traffic Router)
-#. Follow your standard procedure for obtaining your signed certificate chain from a CA.
-#. After receiving your certificate chain import it into Traffic Ops.
-#. Edit the delivery service.
-#. Restore your original choice for the protocol field and click save.
-#. Click 'Manage SSL Keys'.
-#. Click 'Paste Existing Keys'.
-#. Paste the certificate chain into the CRT field.
-#. Click 'Load Keys'.
-#. Take a new snapshot of CR Config.
-
-Once this is done you should be able to test you are getting correctly redirected by Traffic Router using curl commands to https destinations on your delivery service.
-
-A new testing tool was created for load testing traffic router, it allows you to generate requests from your local box to multiple delivery services of a single cdn.
-You can control which cdn, delivery services, how many transactions per delivery service, and how many concurrent requests.
-During the test it will provide feedback about request latency and transactions per second.
-
-While it is running it is suggested that you monitor your Traffic Router nodes for memory and CPU utilization.
-
-Tuning Recommendations
-======================
-
-The following is an example of /opt/tomcat/bin/setenv.sh that has been tested on a multi core server running under HTTPS load test requests.
-This is following the general recommendation to use the G1 garbage collector for JVM applications running on multi core machines.
-In addition to using the G1 garbage collector the InitiatingHeapOccupancyPercent was lowered to run garbage collection more frequently which
-improved overall throughput for Traffic Router and reduced 'Stop the World' garbage collection. Note that setting the min and max heap settings
-in setenv.sh will override init scripts in /etc/init.d/tomcat.
-
- /opt/tomcat/bin/setenv.sh::
-
-
- #! /bin/sh
- export CATALINA_OPTS="$CATALINA_OPTS -server"
- export CATALINA_OPTS="$CATALINA_OPTS -Xms2g -Xmx2g"
- export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseG1GC"
- export CATALINA_OPTS="$CATALINA_OPTS -XX:+UnlockExperimentalVMOptions"
- export CATALINA_OPTS="$CATALINA_OPTS -XX:InitiatingHeapOccupancyPercent=30"
diff --git a/docs/latest/_sources/admin/traffic_server.rst.txt b/docs/latest/_sources/admin/traffic_server.rst.txt
deleted file mode 100644
index 828cb47..0000000
--- a/docs/latest/_sources/admin/traffic_server.rst.txt
+++ /dev/null
@@ -1,149 +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.
-..
-
-*****************************
-Traffic Server Administration
-*****************************
-Installing Traffic Server
-=========================
-
-#. Build the Traffic Server RPM. The best way to do this is to follow the Traffic Server documents: ::
-
- https://docs.trafficserver.apache.org/en/latest/getting-started/index.en.html#installation
-
-#. Build the astats RPM using the appropriate version number: ::
-
- https://github.com/apache/incubator-trafficcontrol/tree/<version>/traffic_server
-
- Sample link: ::
-
- https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_server
-
-#. Install Traffic Server and astats: ::
-
- sudo yum -y install trafficserver-*.rpm astats_over_http*.rpm
-
-#. Add the server using the Traffic Ops web interface:
-
- #. Select **Servers**.
- #. Scroll to the bottom of the page and click **Add Server**.
- #. Complete the "Required Info:" section:
- * Set 'Interface Name' to the name of the interface from which traffic server delivers content.
- * Set 'Type' to 'MID' or 'EDGE'.
- #. Click **Submit**.
- #. Click **Save**.
- #. Click **Online Server**.
- #. Verify that the server status is now listed as **Reported**
-
-#. Install the ORT script and run it in 'badass' mode to create the initial configuration, see :ref:`reference-traffic-ops-ort`
-
-#. Start the service: ``sudo service trafficserver start``
-
-#. Configure traffic server to start automatically: ``sudo systemctl enable trafficserver``
-
-#. Verify that the installation is good:
-
- #. Make sure that the service is running: ``sudo systemctl status trafficserver``
-
- #. Assuming a traffic monitor is already installed, browse to it, i.e. http://<trafficmonitorURL>, and verify that the traffic server appears in the "Cache States" table, in white.
-
-
-.. _reference-traffic-ops-ort:
-
-Configuring Traffic Server
-==========================
-All of the Traffic Server application configuration files are generated by Traffic Ops and installed by way of the traffic_ops_ort.pl script.
-The traffic_ops_ort.pl should be installed on all caches (by puppet or other non Traffic Ops means), usually in /opt/ort. It is used to do the initial install of the config files when the cache is being deployed, and to keep the config files up to date when the cache is already in service. The usage message of the script is shown below: ::
-
- $ sudo /opt/ort/traffic_ops_ort.pl
- ====-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-====
- Usage: ./traffic_ops_ort.pl <Mode> <Log_Level> <Traffic_Ops_URL> <Traffic_Ops_Login> [optional flags]
- <Mode> = interactive - asks questions during config process.
- <Mode> = report - prints config differences and exits.
- <Mode> = badass - attempts to fix all config differences that it can.
- <Mode> = syncds - syncs delivery services with what is configured in Traffic Ops.
- <Mode> = revalidate - checks for updated revalidations in Traffic Ops and applies them. Requires Traffic Ops 2.1.
-
- <Log_Level> => ALL, TRACE, DEBUG, INFO, WARN, ERROR, FATAL, NONE
-
- <Traffic_Ops_URL> = URL to Traffic Ops host. Example: https://trafficops.company.net
-
- <Traffic_Ops_Login> => Example: 'username:password'
-
- [optional flags]:
- dispersion=<time> => wait a random number between 0 and <time> before starting. Default = 300.
- login_dispersion=<time> => wait a random number between 0 and <time> before login. Default = 0.
- retries=<number> => retry connection to Traffic Ops URL <number> times. Default = 3.
- wait_for_parents=<0|1> => do not update if parent_pending = 1 in the update json. Default = 1, wait for parents.
- ====-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-====
- $
-
-Installing the ORT script
---------------------------
-
-#. Build the ORT script RPM from the Apache Build Server and install it: ::
-
- https://builds.apache.org/view/S-Z/view/TrafficControl/
-
- Sample command: ::
-
- sudo wget https://builds.apache.org/view/S-Z/view/TrafficControl/job/incubator-trafficcontrol-2.1.x-build/lastSuccessfulBuild/artifact/dist/traffic_ops_ort-2.1.0-6807.1dcd512f.el7.x86_64.rpm
- sudo yum install traffic_ops_ort*.rpm
-
-#. Install modules required by ORT if needed: ``sudo yum -y install perl-JSON perl-Crypt-SSLeay``
-
-#. For initial configuration or when major changes (like a Profile change) need to be made, run the script in "badass mode". All required rpm packages
- will be installed, all Traffic Server config files will be fetched and installed, and (if needed) the Traffic Server application will be restarted.
-
- Example run below: ::
-
- $ sudo /opt/ort/traffic_ops_ort.pl --dispersion=0 badass warn https://ops.$tcDomain admin:admin123
-
- .. Note:: First run gives a lot of state errors that are expected. The "badass" mode fixes these issue s. Run it a second time, this should be cleaner.
- Also, note that many ERROR messages emitted by ORT are actually information messages. Do not panic.
-
-#. Create a cron entry for running ort in 'syncds' mode every 15 minutes.
- This makes traffic control check periodically if 'Queue Updates' was run on Traffic Ops, and it so, get the updated configuration.
-
- Run ``sudo crontab -e`` and add the following line ::
-
- */15 * * * * /opt/ort/traffic_ops_ort.pl syncds warn https://traffops.kabletown.net admin:password --login_dispersion=30 --dispersion=180 > /tmp/ort/syncds.log 2>&1
-
- Changing ``https://traffops.kabletown.net``, ``admin``, and ``password`` to your CDN URL and credentials.
-
- .. Note:: By default, running ort on an edge traffic server waits for it's parent (mid) servers to download their configuration before
- it downloads it's own configuration. Because of this, scheduling ort for running every 15 minutes (with 5 minutes default dispersion) means
- that it might take up to ~35 minutes for a "Queue Updates" operation to affect all traffic servers. To customize this dispersion time, use
- the command line option --dispersion=x where x is the number of seconds for the dispersion period. Servers will select a random number from
- within this dispersion period to being pulling down configuration files from Traffic Ops. Another option, --login_dispersion=x can be used.
- This option creates a dispersion period after the job begins during which ORT will wait before logging in and checking Traffic Ops for updates
- to the server. This defaults to 0. If use_reval_pending, a.k.a. Rapid Revalidate is enabled, edges will NOT wait for their parents to download
- their configuration before downloading their own.
-
- .. Note:: In 'syncds' mode, the ort script updates only configurations that might be changed as part of normal operations, such as:
-
- * Delivery Services
- * SSL certificates
- * Traffic Monitor IP addresses
- * Logging configuration
- * Revalidation requests (By default. If Rapid Revalidate is enabled, this will only be checked by using a separate revalidate command in ORT.)
-
-
-#. If Rapid Revalidate is enabled in Traffic Ops, create a second cron job for revalidation checks. ORT will not check revalidation files if Rapid Revalidate
- is enabled. This setting allows for a separate check to be performed every 60 seconds to verify if a revalidation update has been made.
-
- Run ``sudo crontab -e`` and add the following line ::
-
- */1 * * * * /opt/ort/traffic_ops_ort.pl revalidate warn https://traffops.kabletown.net admin:password --login_dispersion=30 > /tmp/ort/syncds.log 2>&1
diff --git a/docs/latest/_sources/admin/traffic_stats.rst.txt b/docs/latest/_sources/admin/traffic_stats.rst.txt
deleted file mode 100644
index a1d20b3..0000000
--- a/docs/latest/_sources/admin/traffic_stats.rst.txt
+++ /dev/null
@@ -1,188 +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.
-..
-
-****************************
-Traffic Stats Administration
-****************************
-
-Traffic Stats consists of three seperate components: Traffic Stats, InfluxDB, and Grafana. See below for information on installing and configuring each component as well as configuring the integration between the three and Traffic Ops.
-
-Installation
-========================
-
-**Installing Traffic Stats:**
-
- - See the `downloads <https://trafficcontrol.apache.org/downloads/index.html>`_ page for Traffic Control to get the latest release.
- - Follow our build `intructions <https://github.com/apache/incubator-trafficcontrol/tree/master/build>`_ to generate an RPM.
- - Copy the RPM to your server
- - perform the following command: ``sudo rpm -ivh <traffic_stats rpm>``
-
-**Installing InfluxDB:**
-
- **As of Traffic Stats 1.8.0, InfluxDb 1.0.0 or higher is required. For InfluxDb versions less than 1.0.0 use Traffic Stats 1.7.x**
-
- In order to store traffic stats data you will need to install `InfluxDB <https://docs.influxdata.com/influxdb/latest/introduction/installation/>`_. While not required, it is recommended to use some sort of high availability option like `Influx enterprise <https://portal.influxdata.com/>`_, `Influxdb Relay <https://github.com/influxdata/influxdb-relay>`_, or another `high availability option <https://www.influxdata.com/high-availability/>`_.
-
-
-**Installing Grafana:**
-
- Grafana is used to display Traffic Stats/InfluxDB data in Traffic Ops. Grafana is typically run on the same server as Traffic Stats but this is not a requirement. Grafana can be installed on any server that can access InfluxDB and can be accessed by Traffic Ops. Documentation on installing Grafana can be found on the `Grafana website <http://docs.grafana.org/installation/>`__.
-
-Configuration
-=========================
-
-**Configuring Traffic Stats:**
-
- Traffic Stats' configuration file can be found in /opt/traffic_stats/conf/traffic_stats.cfg.
- The following values need to be configured:
-
- - *toUser:* The user used to connect to Traffic Ops
- - *toPasswd:* The password to use when connecting to Traffic Ops
- - *toUrl:* The URL of the Traffic Ops server used by Traffic Stats
- - *influxUser:* The user to use when connecting to InfluxDB (if configured on InfluxDB, else leave default)
- - *influxPassword:* That password to use when connecting to InfluxDB (if configured, else leave blank)
- - *pollingInterval:* The interval at which Traffic Monitor is polled and stats are stored in InfluxDB
- - *statusToMon:* The status of Traffic Monitor to poll (poll ONLINE or OFFLINE traffic monitors)
- - *seelogConfig:* The absolute path of the seelong config file
- - *dailySummaryPollingInterval:* The interval, in seconds, at which Traffic Stats checks to see if daily stats need to be computed and stored.
- - *cacheRetentionPolicy:* The default retention policy for cache stats
- - *dsRetentionPolicy:* The default retention policy for deliveryservice stats
- - *dailySummaryRetentionPolicy:* The retention policy to be used for the daily stats
- - *influxUrls:* An array of influxdb hosts for Traffic Stats to write stats to.
-
-**Configuring InfluxDB:**
-
- As mentioned above, it is recommended that InfluxDb be running in some sort of high availability configuration. There are several ways to achieve high availabilty so it is best to consult the high availability options on the `InfuxDB website <https://www.influxdata.com/high-availability/>`_.
-
- Once InfluxDB is installed and configured, databases and retention policies need to be created. Traffic Stats writes to three different databases: cache_stats, deliveryservice_stats, and daily_stats. More information about the databases and what data is stored in each can be found on the `overview <../overview/traffic_stats.html>`_ page.
-
- To easily create databases, retention policies, and continuous queries, run create_ts_databases from the /opt/traffic_stats/influxdb_tools directory on your Traffic Stats server. See the `InfluxDb Tools <traffic_stats.html#influxdb-tools>`_ section below for more information.
-
-**Configuring Grafana:**
-
- In Traffic Ops the Health -> Graph View tab can be configured to display grafana graphs using influxDb data. In order for this to work correctly, you will need two things 1) a parameter added to traffic ops with the graph URL (more information below) and 2) the graphs created in grafana. See below for how to create some simple graphs in grafana. These instructions assume that InfluxDB has been configured and that data has been written to it. If this is not true, you will not see an [...]
-
- - Login to grafana as an admin user http://grafana_url:3000/login
- - Choose Data Sources and then Add New
- - Enter the necessary information to configure your data source
- - Click on the 'Home' dropdown at the top of the screen and choose New at the bottom
- - Click on the green menu bar (with 3 lines) at the top and choose Add Panel -> Graph
- - Where it says 'No Title (click here)' click and choose edit
- - Choose your data source at the bottom
- - You can have grafana help you create a query, or you can create your own. Here is a sample query:
-
- ``SELECT sum(value)*1000 FROM "monthly"."bandwidth.cdn.1min" WHERE $timeFilter GROUP BY time(60s), cdn``
- - Once you have the graph the way you want it, click the 'Save Dashboard' button at the top
- - You should now have a new saved graph
-
- In order for Traffic Ops users to see Grafana graphs, Grafana will need to allow anonymous access. Information on how to configure anonymous access can be found on the configuration page of the `Grafana Website <http://docs.grafana.org/installation/configuration/#authanonymous>`_.
-
- Traffic Ops uses custom dashboards to display information about individual delivery services or cache groups. In order for the custom graphs to display correctly, the `traffic_ops_*.js <https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_stats/grafana/>`_ files need to be in the ``/usr/share/grafana/public/dashboards/`` directory on the grafana server. If your Grafana server is the same as your Traffic Stats server the RPM install process will take care of putting t [...]
-
- More information on custom scripted graphs can be found in the `scripted dashboards <http://docs.grafana.org/reference/scripting/>`_ section of the Grafana documentation.
-
-**Configuring Traffic Ops for Traffic Stats:**
-
- - The influxDb servers need to be added to Traffic Ops with profile = InfluxDB. Make sure to use port 8086 in the configuration.
- - The traffic stats server should be added to Traffic Ops with profile = Traffic Stats.
- - Parameters for which stats will be collected are added with the release, but any changes can be made via parameters that are assigned to the Traffic Stats profile.
-
-**Configuring Traffic Ops to use Grafana Dashboards**
-
- To configure Traffic Ops to use Grafana Dashboards, you need to enter the following parameters and assign them to the GLOBAL profile. This assumes you followed the above instructions to install and configure InfluxDB and Grafana. You will need to place 'cdn-stats','deliveryservice-stats', and 'daily-summary' with the name of your dashboards.
-
- +---------------------------+------------------------------------------------------------------------------------------------+
- | parameter name | parameter value |
- +===========================+================================================================================================+
- | all_graph_url | https://<grafana_url>/dashboard/db/deliveryservice-stats |
- +---------------------------+------------------------------------------------------------------------------------------------+
- | cachegroup_graph_url | https://<grafanaHost>/dashboard/script/traffic_ops_cachegroup.js?which= |
- +---------------------------+------------------------------------------------------------------------------------------------+
- | deliveryservice_graph_url | https://<grafanaHost>/dashboard/script/traffic_ops_devliveryservice.js?which= |
- +---------------------------+------------------------------------------------------------------------------------------------+
- | server_graph_url | https://<grafanaHost>/dashboard/script/traffic_ops_server.js?which= |
- +---------------------------+------------------------------------------------------------------------------------------------+
- | visual_status_panel_1 | https://<grafanaHost>/dashboard-solo/db/cdn-stats?panelId=2&fullscreen&from=now-24h&to=now-60s |
- +---------------------------+------------------------------------------------------------------------------------------------+
- | visual_status_panel_2 | https://<grafanaHost>/dashboard-solo/db/cdn-stats?panelId=1&fullscreen&from=now-24h&to=now-60s |
- +---------------------------+------------------------------------------------------------------------------------------------+
- | daily_bw_url | https://<grafanaHost>/dashboard-solo/db/daily-summary?panelId=1&fullscreen&from=now-3y&to=now |
- +---------------------------+------------------------------------------------------------------------------------------------+
- | daily_served_url | https://<grafanaHost>/dashboard-solo/db/daily-summary?panelId=2&fullscreen&from=now-3y&to=now |
- +---------------------------+------------------------------------------------------------------------------------------------+
-
-InfluxDb Tools
-=========================
-
-Under the Traffic Stats source directory there is a directory called influxdb_tools. These tools are meant to be used as one-off scripts to help a user quickly get new databases and continuous queries setup in influxdb.
-They are specific for traffic stats and are not meant to be generic to influxdb. Below is an brief description of each script along with how to use it.
-
-**create/create_ts_databases.go**
- This script creates all `databases <https://docs.influxdata.com/influxdb/latest/concepts/key_concepts/#database>`_, `retention policies <https://docs.influxdata.com/influxdb/latest/concepts/key_concepts/#retention-policy>`_, and `continuous queries <https://docs.influxdata.com/influxdb/v0.11/query_language/continuous_queries/>`_ required by traffic stats.
-
- **How to use create_ts_databases:**
-
- Pre-Requisites:
-
- 1. Go 1.7 or later
- 2. configured $GOPATH (e.g. export GOPATH=~/go)
-
- Using create_ts_databases.go
-
- 1. go to the traffic_stats/influxdb_tools/create directory
-
- 2. build it by running ``go build create_ts_databases.go`` or simply ``go build``
-
- 3. Run it:
- - ``./create_ts_databases -help`` or ``./create -help``
- - optional flags:
- - url - The influxdb url and port
- - replication - The number of nodes in the cluster
- - user - The user to use
- - password - The password to use
- - example: ``./create_ts_databases -url=localhost:8086 -replication=3 -user=joe -password=mysecret`` or ``./create -url=localhost:8086 -replication=3 -user=joe -password=mysecret``
-
-**sync_ts_databases**
- This script is used to sync one influxdb environment to another. Only data from continuous queries is synced as it is downsampled data and much smaller in size than syncing raw data. Possible use cases are syncing from Production to Development or Syncing a new cluster once brought online.
-
- **How to use sync_ts_databases:**
-
- Pre-Requisites:
-
- 1. Go 1.7 or later
- 2. configured $GOPATH (e.g. export GOPATH=~/go)
-
- Using sync_ts_databases.go:
-
- 1. go to the traffic_stats/influxdb_tools/create directory
-
- 2. build it by running ``go build sync_ts_databases.go`` or simply ``go build``
-
- 3. Run it
- - ``./sync_ts_databases -help`` or ``./sync -help``
- - required flags:
- - source-url - The URL of the source database
- - target-url - The URL of the target database
-
- -optional flags:
- - database - The database to sync (default = sync all databases)
- - days - Days in the past to sync (default = sync all data)
- - source-user - The user of the source database
- - source-pass - The password for the source database
- - target-user - The user of the target database
- - target-pass - The password for the target database
-
- - example: `./sync -source-url=http://idb-01.foo.net:8086 -target-url=http://idb-01.foo.net:8086 -database=cache_stats -days=7 -source-user=admin source-pass=mysecret`
-
diff --git a/docs/latest/_sources/admin/traffic_vault.rst.txt b/docs/latest/_sources/admin/traffic_vault.rst.txt
deleted file mode 100644
index 2f6508a..0000000
--- a/docs/latest/_sources/admin/traffic_vault.rst.txt
+++ /dev/null
@@ -1,188 +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.
-..
-
-****************************
-Traffic Vault Administration
-****************************
-Installing Traffic Vault
-========================
-In order to successfully store private keys you will need to install Riak.
-The latest version of Riak can be downloaded on the Riak `website <http://docs.basho.com/riak/latest/downloads/>`_.
-The installation instructions for Riak can be found `here <http://docs.basho.com/riak/latest/ops/building/installing/>`__.
-
-Production is currently running version 2.0.5 of Riak, but the latest version should suffice.
-
-
-Configuring Traffic Vault
-=========================
-The following steps were taken to configure Riak in our environments.
-
-Riak configuration file configuration
--------------------------------------
-
-The following steps need to be performed on each Riak server in the cluster:
-
-* Log into riak server as root
-
-* cd to /etc/riak/
-
-* Update the following in riak.conf to reflect your IP:
- - nodename = riak@a-host.sys.kabletown.net
- - listener.http.internal = a-host.sys.kabletown.net:8098 (can be 80 - This endpoint will not work with sec enabled)
- - listener.protobuf.internal = a-host.sys.kabletown.net:8087 (can be different port if you want)
- - listener.https.internal = a-host.sys.kabletown.net:8088 (can be 443)
-
-* Updated the following conf file to point to your cert files
- - ssl.certfile = /etc/riak/certs/server.crt
- - ssl.keyfile = /etc/riak/certs/server.key
- - ssl.cacertfile = /etc/pki/tls/certs/ca-bundle.crt
-
-* Add a line at the bottom of the config for tlsv1
- - tls_protocols.tlsv1 = on
-
-* Once the config file has been updated restart riak
- - ``/etc/init.d/riak restart``
-
-* Validate server is running by going to the following URL:
- - https://<serverHostname>:8088/ping
-
-Riak-admin configuration
--------------------------
-
-Riak-admin is a command line utility that needs to be run as root on a server in the riak cluster.
-
-Assumptions:
- * Riak 2.0.2 or greater is installed
- * SSL Certificates have been generated (signed or self-signed)
- * Root access to riak servers
-
-Add admin user and riakuser to riak
- * Admin user will be a super user
- * Riakuser will be the application user
-
-Login to one of the riak servers in the cluster as root (any will do)
-
- 1. Enable security
-
- ``riak-admin security enable``
-
- 2. Add groups
-
- ``riak-admin security add-group admins``
-
- ``riak-admin security add-group keysusers``
- 3. Add users
-
- .. Note:: username and password should be stored in /opt/traffic_ops/app/conf/<environment>/riak.conf
- ..
-
- ``riak-admin security add-user admin password=<AdminPassword> groups=admins``
-
- ``riak-admin security add-user riakuser password=<RiakUserPassword> groups=keysusers``
-
- 4. Grant access for admin and riakuser
-
- ``riak-admin security add-source riakuser 0.0.0.0/0 password``
-
- ``riak-admin security add-source admin 0.0.0.0/0 password``
-
- 5. Grant privs to admins for everything
-
- ``riak-admin security grant riak_kv.list_buckets,riak_kv.list_keys,riak_kv.get,riak_kv.put,riak_kv.delete on any to admins``
-
- 6. Grant privs to keysuser for ssl, dnssec, and url_sig_keys buckets only
-
- ``riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default ssl to keysusers``
-
- ``riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default dnssec to keysusers``
-
- ``riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default url_sig_keys to keysusers``
-
- ``riak-admin security grant riak_kv.get,riak_kv.put,riak_kv.delete on default cdn_uri_sig_keys to keysusers``
-
-.. seealso:: For more information on security in Riak, see the `Riak Security documentation <http://docs.basho.com/riak/2.0.4/ops/advanced/security/>`_.
-.. seealso:: For more information on authentication and authorization in Riak, see the `Riak Authentication and Authorization documentation <http://docs.basho.com/riak/2.0.4/ops/running/authz/>`_.
-
-
-Traffic Ops Configuration
--------------------------
-
-There are a couple configurations that are necessary in Traffic Ops.
-
-1. Database Updates
- * The servers in the Riak cluster need to be added to the server table (TCP Port = 8088, type = RIAK, profile = RIAK_ALL)
-
-2. Configuration updates
- * /opt/traffic_ops/app/conf/<environment>/riak.conf needs to be updated to reflect the correct username and password for accessing riak.
-
-Configuring Riak Search
-=======================
-
-In order to more effectively support retrieval of SSL certificates by Traffic Router and Traffic Ops ORT, Traffic Vault uses `Riak search <http://docs.basho.com/riak/kv/latest/using/reference/search/>`_. Riak Search uses `Apache Solr <http://lucene.apache.org/solr>`_ for indexing and searching of records. The following explains how to enable, configure, and validate Riak Search.
-
-Riak Configuration
-------------------
-
-On Each Riak Server:
-
-1. If java is not already installed on your Riak server, install Java
- * To see if Java is already installed: ``java -version``
- * To install Java: ``yum install -y jdk``
-
-2. enable search in riak.conf
- * ``vim /etc/riak/riak.conf``
- * look for search and change ``search = off`` to ``search = on``
-
-3. Restart Riak so search is on
- * ``service riak restart``
-
-One time configuration:
-
-1. **On one of the Riak servers in the cluster run the following riak-admin commands**
-
-``riak-admin security grant search.admin on schema to admin``
-
-``riak-admin security grant search.admin on index to admin``
-
-``riak-admin security grant search.query on index to admin``
-
-``riak-admin security grant search.query on index sslkeys to admin``
-
-``riak-admin security grant search.query on index to riakuser``
-
-``riak-admin security grant search.query on index sslkeys to riakuser``
-
-``riak-admin security grant riak_core.set_bucket on any to admin``
-
-2. Add the search schema to Riak. This schema is a simple Apache Solr configuration file which will index all records on cdn, hostname, and deliveryservice.
- * Get the schema file by either cloning the project and going to `traffic_ops/app/config/misc/riak_search` or from `github <https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_ops/app/conf/misc/riak_search>`_.
- * Use curl to add the schema to riak: ``curl -kvs -XPUT "https://admin:pass@riakserver:8088/search/schema/sslkeys" -H 'Content-Type:application/xml' -d @sslkeys.xml``
-
-3. Add search index to Riak
- * run the following curl command: ``curl -kvs -XPUT "https://admin:pass@riakserver:8088/search/index/sslkeys" -H 'Content-Type: application/json' -d '{"schema":"sslkeys"}'``
-
-4. Associate the sslkeys index to the ssl bucket in Riak
- * run the following curl command: ``curl -kvs -XPUT "https://admin:pass@riakserver:8088/buckets/ssl/props" -H'content-type:application/json' -d'{"props":{"search_index":"sslkeys"}}'``
-
-Riak Search (using Apache Solr) will now index all NEW records that are added to the "ssl" bucket. The cdn, deliveryservice, and hostname fields are indexed and when a search is performed riak will return the indexed fields along with the crt and key values for a ssl record. In order to add the indexed fields to current records and to get the current records added, a standalone script needs to be run. This does not need to be done on new installs. The following explains how to run the [...]
-
-1. Get script from github either by cloning the project and going to `traffic_ops/app/script` or from `here <https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_ops/app/script/update_riak_for_search.pl>`_
-2. Run the script by performing the following command ``./update_riak_for_search.pl -to_url=https://traffic-ops.kabletown.net -to_un=user -to_pw=password``
-
-Validate the search is working by querying against Riak directly:
-``curl -kvs "https://admin:password@riakserver:8088/search/query/sslkeys?wt=json&q=cdn:mycdn"``
-
-Validation can also be done by querying Traffic Ops:
-``curl -Lvs -H "Cookie: $COOKIE" https://traffic-ops.kabletown.net/api/1.2/cdns/name/mycdn/sslkeys.json``
diff --git a/docs/latest/_sources/api/index.rst.txt b/docs/latest/_sources/api/index.rst.txt
deleted file mode 100644
index 6cdf32e..0000000
--- a/docs/latest/_sources/api/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.
-..
-
-APIs
-****
-A guide to external RESTful APIs for Traffic Ops
-
-.. toctree::
- :maxdepth: 2
-
- traffic_ops_api
- routes
- v11/index
- v12/index
- v13/index
-
diff --git a/docs/latest/_sources/api/routes.rst.txt b/docs/latest/_sources/api/routes.rst.txt
deleted file mode 100644
index 1c849b3..0000000
--- a/docs/latest/_sources/api/routes.rst.txt
+++ /dev/null
@@ -1,118 +0,0 @@
-.. raw:: html
-
- <style>
- table {
- table-layout: fixed;
- width: 100%;
- }
-
- td {
- word-wrap:break-word;
- }
- table.docutils col:nth-child(1) {
- width: 30%;
- }
- table.docutils col:nth-child(2) {
- width: 30%;
- }
- table.docutils col:nth-child(3) {
- width: 30%;
- }
- .wy-nav-content {
- max-width: 1200px;
- width: 90%;
- }
- </style>
-
-..
-..
-.. 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.
-..
-
-
-.. _to-api-routes:
-
-API Routes
-==========
-
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| 1.0 | 1.1 | 1.2 |
-+====================================+====================================================+====================================================+
-| /asns | :ref:`to-api-v11-asns-route` | :ref:`to-api-v12-asns-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /availableds | :ref:`to-api-v11-ds-route` | :ref:`to-api-v12-ds-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| *Not Implemented* | *Not Implemented* | :ref:`to-api-v12-cache-stats-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datacrans | /api/1.1/crans.json | /api/1.2/crans.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datacrans/orderby/:field | /api/1.1/crans.json | /api/1.2/crans.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datadeliveryservice | :ref:`to-api-v11-ds-route` | :ref:`to-api-v12-ds-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datadeliveryserviceserver | /api/1.1/deliveryserviceserver.json | /api/1.2/deliveryserviceserver.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datadomains | /api/1.1/cdns/domains.json | /api/1.2/cdns/domains.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| *Not Implemented* | *Not Implemented* | :ref:`to-api-v12-ds-stats-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datahwinfo | :ref:`to-api-v11-hwinfo-route` | :ref:`to-api-v12-hwinfo-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datalinks | /api/1.1/deliveryserviceserver.json | /api/1.2/deliveryserviceserver.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datalinks/orderby/:field | /api/1.1/deliveryserviceserver.json | /api/1.2/deliveryserviceserver.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datalogs | :ref:`to-api-v11-change-logs-route` | :ref:`to-api-v12-change-logs-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datalocation/orderby/id | :ref:`to-api-v11-cachegroups-route` | :ref:`to-api-v12-cachegroups-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datalocationparameters | :ref:`to-api-v11-cachegroups-route` | :ref:`to-api-v12-cachegroups-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataparameter | :ref:`to-api-v11-parameters-route` | :ref:`to-api-v12-parameters-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataparameter/:parameter | /api/1.1/parameters/profile/:parameter.json | /api/1.2/parameters/profile/:parameter.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataphys_location | :ref:`to-api-v11-phys-loc-route` | :ref:`to-api-v12-phys-loc-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataprofile | :ref:`to-api-v11-profiles-route` | :ref:`to-api-v12-profiles-route` |
-| | | |
-| /dataprofile/orderby/name | | |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataregion | :ref:`to-api-v11-regions-route` | :ref:`to-api-v12-regions-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datarole | :ref:`to-api-v11-roles-route` | :ref:`to-api-v12-roles-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datarole/orderby/:field | :ref:`to-api-v11-roles-route` | :ref:`to-api-v12-roles-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataserver | :ref:`to-api-v11-servers-route` | :ref:`to-api-v12-servers-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataserver/orderby/:field | :ref:`to-api-v11-servers-route` | :ref:`to-api-v12-servers-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /dataserverdetail/select/:hostname | /api/1.1/servers/hostname/:hostname/details.json | /api/1.2/servers/hostname/:hostname/details.json |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datastaticdnsentry | :ref:`to-api-v11-static-dns-route` | :ref:`to-api-v12-static-dns-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datastatus | :ref:`to-api-v11-statuses-route` | :ref:`to-api-v12-statuses-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datastatus/orderby/name | :ref:`to-api-v11-statuses-route` | :ref:`to-api-v12-statuses-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datatype | :ref:`to-api-v11-types-route` | :ref:`to-api-v12-types-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datatype/orderby/:field | :ref:`to-api-v11-types-route` | :ref:`to-api-v12-types-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datauser | :ref:`to-api-v11-users-route` | :ref:`to-api-v12-users-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| /datauser/orderby/:field | :ref:`to-api-v11-users-route` | :ref:`to-api-v12-users-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
-| *Not Implemented* | *Not Implemented* | :ref:`to-api-v12-configfiles_ats-route` |
-+------------------------------------+----------------------------------------------------+----------------------------------------------------+
diff --git a/docs/latest/_sources/api/traffic_ops_api.rst.txt b/docs/latest/_sources/api/traffic_ops_api.rst.txt
deleted file mode 100644
index 0ced0ae..0000000
--- a/docs/latest/_sources/api/traffic_ops_api.rst.txt
+++ /dev/null
@@ -1,196 +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.
-..
-
-API Overview
-************
-The Traffic Ops API provides programmatic access to read and write CDN data providing authorized API consumers with the ability to monitor CDN performance and configure CDN settings and parameters.
-
-Response Structure
-------------------
-All successful responses have the following structure: ::
-
- {
- "response": <JSON object with main response>,
- }
-
-To make the documentation easier to read, only the ``<JSON object with main response>`` is documented, even though the response and version fields are always present.
-
-Using API Endpoints
--------------------
-1. Authenticate with your Traffic Portal or Traffic Ops user account credentials.
-2. Upon successful user authentication, note the mojolicious cookie value in the response headers.
-3. Pass the mojolicious cookie value, along with any subsequent calls to an authenticated API endpoint.
-
-Example: ::
-
- [jvd@laika ~]$ curl -H "Accept: application/json" http://localhost:3000/api/1.1/usage/asns.json
- {"alerts":[{"level":"error","text":"Unauthorized, please log in."}]}
- [jvd@laika ~]$
- [jvd@laika ~]$ curl -v -H "Accept: application/json" -v -X POST --data '{ "u":"admin", "p":"secret_passwd" }' http://localhost:3000/api/1.1/user/login
- * Hostname was NOT found in DNS cache
- * Trying ::1...
- * connect to ::1 port 3000 failed: Connection refused
- * Trying 127.0.0.1...
- * Connected to localhost (127.0.0.1) port 3000 (#0)
- > POST /api/1.1/user/login HTTP/1.1
- > User-Agent: curl/7.37.1
- > Host: localhost:3000
- > Accept: application/json
- > Content-Length: 32
- > Content-Type: application/x-www-form-urlencoded
- >
- * upload completely sent off: 32 out of 32 bytes
- < HTTP/1.1 200 OK
- < Connection: keep-alive
- < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
- < Access-Control-Allow-Origin: http://localhost:8080
- < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
- < Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862; expires=Sun, 19 Apr 2015 00:10:01 GMT; path=/; HttpOnly
- < Content-Type: application/json
- < Date: Sat, 18 Apr 2015 20:10:01 GMT
- < Access-Control-Allow-Credentials: true
- < Content-Length: 81
- < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
- * Server Mojolicious (Perl) is not blacklisted
- < Server: Mojolicious (Perl)
- <
- * Connection #0 to host localhost left intact
- {"alerts":[{"level":"success","text":"Successfully logged in."}]}
- [jvd@laika ~]$
-
- [jvd@laika ~]$ curl -H'Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;' -H "Accept: application/json" http://localhost:3000/api/1.1/asns.json
- {"response":{"asns":[{"lastUpdated":"2012-09-17 15:41:22", .. asn data deleted .. ,}
- [jvd@laika ~]$
-
-API Errors
-----------
-
-**Response Properties**
-
-+----------------------+--------+------------------------------------------------+
-| Parameter | Type | Description |
-+======================+========+================================================+
-|``alerts`` | array | A collection of alert messages. |
-+----------------------+--------+------------------------------------------------+
-| ``>level`` | string | Success, info, warning or error. |
-+----------------------+--------+------------------------------------------------+
-| ``>text`` | string | Alert message. |
-+----------------------+--------+------------------------------------------------+
-
-The 3 most common errors returned by Traffic Ops are:
-
-401 Unauthorized
- When you don't supply the right cookie, this is the response. ::
-
- [jvd@laika ~]$ curl -v -H "Accept: application/json" http://localhost:3000/api/1.1/usage/asns.json
- * Hostname was NOT found in DNS cache
- * Trying ::1...
- * connect to ::1 port 3000 failed: Connection refused
- * Trying 127.0.0.1...
- * Connected to localhost (127.0.0.1) port 3000 (#0)
- > GET /api/1.1/usage/asns.json HTTP/1.1
- > User-Agent: curl/7.37.1
- > Host: localhost:3000
- > Accept: application/json
- >
- < HTTP/1.1 401 Unauthorized
- < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
- < Content-Length: 84
- * Server Mojolicious (Perl) is not blacklisted
- < Server: Mojolicious (Perl)
- < Connection: keep-alive
- < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
- < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
- < Access-Control-Allow-Origin: http://localhost:8080
- < Date: Sat, 18 Apr 2015 20:36:12 GMT
- < Content-Type: application/json
- < Access-Control-Allow-Credentials: true
- <
- * Connection #0 to host localhost left intact
- {"alerts":[{"level":"error","text":"Unauthorized, please log in."}]}
- [jvd@laika ~]$
-
-404 Not Found
- When the resource (path) is non existent Traffic Ops returns a 404::
-
- [jvd@laika ~]$ curl -v -H'Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;' -H "Accept: application/json" http://localhost:3000/api/1.1/asnsjj.json
- * Hostname was NOT found in DNS cache
- * Trying ::1...
- * connect to ::1 port 3000 failed: Connection refused
- * Trying 127.0.0.1...
- * Connected to localhost (127.0.0.1) port 3000 (#0)
- > GET /api/1.1/asnsjj.json HTTP/1.1
- > User-Agent: curl/7.37.1
- > Host: localhost:3000
- > Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;
- > Accept: application/json
- >
- < HTTP/1.1 404 Not Found
- * Server Mojolicious (Perl) is not blacklisted
- < Server: Mojolicious (Perl)
- < Content-Length: 75
- < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
- < Content-Type: application/json
- < Date: Sat, 18 Apr 2015 20:37:43 GMT
- < Access-Control-Allow-Credentials: true
- < Set-Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAzODYzLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--8a5a61b91473bc785d4073fe711de8d2c63f02dd; expires=Sun, 19 Apr 2015 00:37:43 GMT; path=/; HttpOnly
- < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
- < Connection: keep-alive
- < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
- < Access-Control-Allow-Origin: http://localhost:8080
- <
- * Connection #0 to host localhost left intact
- {"alerts":[{"text":"Resource not found.","level":"error"}]}
- [jvd@laika ~]$
-
-500 Internal Server Error
- When you are asking for a correct path, but the database doesn't match, it returns a 500::
-
- [jvd@laika ~]$ curl -v -H'Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;' -H "Accept: application/json" http://localhost:3000/api/1.1/servers/hostname/jj/details.json
- * Hostname was NOT found in DNS cache
- * Trying ::1...
- * connect to ::1 port 3000 failed: Connection refused
- * Trying 127.0.0.1...
- * Connected to localhost (127.0.0.1) port 3000 (#0)
- > GET /api/1.1/servers/hostname/jj/details.json HTTP/1.1
- > User-Agent: curl/7.37.1
- > Host: localhost:3000
- > Cookie: mojolicious=eyJleHBpcmVzIjoxNDI5NDAyMjAxLCJhdXRoX2RhdGEiOiJhZG1pbiJ9--f990d03b7180b1ece97c3bb5ca69803cd6a79862;
- > Accept: application/json
- >
- < HTTP/1.1 500 Internal Server Error
- * Server Mojolicious (Perl) is not blacklisted
- < Server: Mojolicious (Perl)
- < Cache-Control: no-cache, no-store, max-age=0, must-revalidate
- < Content-Length: 93
- < Set-Cookie: mojolicious=eyJhdXRoX2RhdGEiOiJhZG1pbiIsImV4cGlyZXMiOjE0Mjk0MDQzMDZ9--1b08977e91f8f68b0ff5d5e5f6481c76ddfd0853; expires=Sun, 19 Apr 2015 00:45:06 GMT; path=/; HttpOnly
- < Content-Type: application/json
- < Date: Sat, 18 Apr 2015 20:45:06 GMT
- < Access-Control-Allow-Credentials: true
- < Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
- < Connection: keep-alive
- < Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
- < Access-Control-Allow-Origin: http://localhost:8080
- <
- * Connection #0 to host localhost left intact
- {"alerts":[{"level":"error","text":"An error occurred. Please contact your administrator."}]}
- [jvd@laika ~]$
-
- The rest of the API documentation will only document the ``200 OK`` case, where no errors have occured.
-
-TrafficOps Native Client Libraries
-----------------------------------
-
-TrafficOps client libraries are available in both Golang and Python. You can read more about them at https://github.com/apache/incubator-trafficcontrol/tree/master/traffic_control/clients
diff --git a/docs/latest/_sources/api/v11/asn.rst.txt b/docs/latest/_sources/api/v11/asn.rst.txt
deleted file mode 100644
index b6960d7..0000000
--- a/docs/latest/_sources/api/v11/asn.rst.txt
+++ /dev/null
@@ -1,69 +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.
-..
-
-
-.. _to-api-v11-asn:
-
-ASN
-===
-
-.. _to-api-v11-asns-route:
-
-/api/1.1/asns
-+++++++++++++
-
-**GET /api/1.1/asns**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +------------------+--------+-------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +==================+========+=========================================================================+
- | ``asns`` | array | A collection of asns |
- +------------------+--------+-------------------------------------------------------------------------+
- | ``>lastUpdated`` | string | The Time / Date this server entry was last updated |
- +------------------+--------+-------------------------------------------------------------------------+
- | ``>id`` | string | Local unique identifier for the ASN |
- +------------------+--------+-------------------------------------------------------------------------+
- | ``>asn`` | string | Autonomous System Numbers per APNIC for identifying a service provider. |
- +------------------+--------+-------------------------------------------------------------------------+
- | ``>cachegroup`` | string | Related cachegroup name |
- +------------------+--------+-------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "asns": [
- {
- "lastUpdated": "2012-09-17 21:41:22",
- "id": "27",
- "asn": "7015",
- "cachegroup": "us-ma-woburn"
- },
- {
- "lastUpdated": "2012-09-17 21:41:22",
- "id": "28",
- "asn": "7016",
- "cachegroup": "us-pa-pittsburgh"
- }
- ]
- },
- }
-
diff --git a/docs/latest/_sources/api/v11/cachegroup.rst.txt b/docs/latest/_sources/api/v11/cachegroup.rst.txt
deleted file mode 100644
index 5278645..0000000
--- a/docs/latest/_sources/api/v11/cachegroup.rst.txt
+++ /dev/null
@@ -1,317 +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.
-..
-
-.. _to-api-v11-cachegroup:
-
-Cache Group
-===========
-
-.. _to-api-v11-cachegroups-route:
-
-/api/1.1/cachegroups
-++++++++++++++++++++
-
-**GET /api/1.1/cachegroups**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +===================================+========+==========================================================================+
- | ``id`` | string | Local unique identifier for the Cache Group |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``lastUpdated`` | string | The Time / Date this entry was last updated |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``latitude`` | string | Latitude for the Cache Group |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``longitude`` | string | Longitude for the Cache Group |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``name`` | string | The name of the Cache Group entry |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``parentCachegroupId`` | string | Parent cachegroup ID. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``parentCachegroupName`` | string | Parent cachegroup name. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``secondaryParentCachegroupId`` | string | Secondary parent cachegroup ID. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``secondaryParentCachegroupName`` | string | Secondary parent cachegroup name. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``shortName`` | string | Abbreviation of the Cache Group Name |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``typeId`` | string | Unique identifier for the 'Type' of Cache Group entry |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``typeName`` | string | The name of the type of Cache Group entry |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "id": "21",
- "lastUpdated": "2012-09-25 20:27:28",
- "latitude": "0",
- "longitude": "0",
- "name": "dc-chicago",
- "parentCachegroupId": null,
- "parentCachegroupName": null,
- "secondaryParentCachegroupId": null,
- "secondaryParentCachegroupName": null,
- "shortName": "dcchi",
- "typeName": "MID_LOC",
- "typeId": "4"
- },
- {
- "id": "22",
- "lastUpdated": "2012-09-25 20:27:28",
- "latitude": "0",
- "longitude": "0",
- "name": "dc-chicago-1",
- "parentCachegroupId": null,
- "parentCachegroupName": null,
- "secondaryParentCachegroupId": null,
- "secondaryParentCachegroupName": null,
- "shortName": "dcchi",
- "typeName": "MID_LOC",
- "typeId": "4"
- }
- ],
- }
-
-|
-
-**GET /api/1.1/cachegroups/trimmed**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``name`` | string | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "name": "dc-chicago"
- },
- {
- "name": "dc-cmc"
- }
- ],
- }
-
-|
-
-**GET /api/1.1/cachegroups/:id**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +===================================+========+==========================================================================+
- | ``id`` | string | Local unique identifier for the Cache Group |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``lastUpdated`` | string | The Time / Date this entry was last updated |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``latitude`` | string | Latitude for the Cache Group |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``longitude`` | string | Longitude for the Cache Group |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``name`` | string | The name of the Cache Group entry |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``parentCachegroupId`` | string | Parent cachegroup ID. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``parentCachegroupName`` | string | Parent cachegroup name. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``secondaryParentCachegroupId`` | string | Secondary parent cachegroup ID. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``secondaryParentCachegroupName`` | string | Secondary parent cachegroup name. |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``shortName`` | string | Abbreviation of the Cache Group Name |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``typeId`` | string | Unique identifier for the 'Type' of Cache Group entry |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
- | ``typeName`` | string | The name of the type of Cache Group entry |
- +-----------------------------------+--------+--------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "id": "21",
- "lastUpdated": "2012-09-25 20:27:28",
- "latitude": "0",
- "longitude": "0",
- "name": "dc-chicago",
- "parentCachegroupId": null,
- "parentCachegroupName": null,
- "secondaryParentCachegroupId": null,
- "secondaryParentCachegroupName": null,
- "shortName": "dcchi",
- "typeName": "MID_LOC",
- "typeId": "4"
- }
- ],
- }
-
-|
-
-
-**GET /api/1.1/cachegroup/:parameter_id/parameter**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +------------------+----------+-------------+
- | Name | Required | Description |
- +==================+==========+=============+
- | ``parameter_id`` | yes | |
- +------------------+----------+-------------+
-
- **Response Properties**
-
- +-----------------+--------+-------------+
- | Parameter | Type | Description |
- +=================+========+=============+
- | ``cachegroups`` | array | |
- +-----------------+--------+-------------+
- | ``>name`` | string | |
- +-----------------+--------+-------------+
- | ``>id`` | string | |
- +-----------------+--------+-------------+
-
- **Response Example** ::
-
- {
- "response": {
- "cachegroups": [
- {
- "name": "dc-chicago",
- "id": "21"
- },
- {
- "name": "dc-cmc",
- "id": "22"
- }
- ]
- },
- }
-
-
-**GET /api/1.1/cachegroupparameters**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +--------------------------+--------+-----------------------------------------+
- | Parameter | Type | Description |
- +==========================+========+=========================================+
- | ``cachegroupParameters`` | array | A collection of cache group parameters. |
- +--------------------------+--------+-----------------------------------------+
- | ``>parameter`` | string | |
- +--------------------------+--------+-----------------------------------------+
- | ``>last_updated`` | string | |
- +--------------------------+--------+-----------------------------------------+
- | ``>cachegroup`` | string | |
- +--------------------------+--------+-----------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "cachegroupParameters": [
- {
- "parameter": "379",
- "last_updated": "2013-08-05 18:49:37",
- "cachegroup": "us-ca-sanjose"
- },
- {
- "parameter": "380",
- "last_updated": "2013-08-05 18:49:37",
- "cachegroup": "us-ca-sanjose"
- },
- {
- "parameter": "379",
- "last_updated": "2013-08-05 18:49:37",
- "cachegroup": "us-ma-woburn"
- }
- ]
- },
- }
-
-
-|
-
-**GET /api/1.1/cachegroups/:parameter_id/parameter/available**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +------------------+----------+-------------+
- | Name | Required | Description |
- +==================+==========+=============+
- | ``parameter_id`` | yes | |
- +------------------+----------+-------------+
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``name`` | | |
- +----------------------+--------+------------------------------------------------+
- |``id`` | | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "name": "dc-chicago",
- "id": "21"
- },
- {
- "name": "dc-cmc",
- "id": "22"
- }
- ],
- }
-
diff --git a/docs/latest/_sources/api/v11/cdn.rst.txt b/docs/latest/_sources/api/v11/cdn.rst.txt
deleted file mode 100644
index 91c926c..0000000
--- a/docs/latest/_sources/api/v11/cdn.rst.txt
+++ /dev/null
@@ -1,1088 +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.
-..
-
-.. _to-api-v11-cdn-health:
-
-CDN
-===
-
-.. _to-api-v11-cdn-health-route:
-
-/api/1.1/cdns
-+++++++++++++
-
-**GET /api/1.1/cdns**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +-------------------+--------+-------------------------------------------------+
- | Parameter | Type | Description |
- +===================+========+=================================================+
- | ``id`` | string | CDN id. |
- +-------------------+--------+-------------------------------------------------+
- | ``name`` | string | CDN name. |
- +-------------------+--------+-------------------------------------------------+
- | ``dnssecEnabled`` | bool | DNSSEC enabled. |
- +-------------------+--------+-------------------------------------------------+
- | ``lastUpdated`` | string | |
- +-------------------+--------+-------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "id": "1"
- "name": "over-the-top",
- "dnssecEnabled": false,
- "lastUpdated": "2014-10-02 08:22:43"
- },
- {
- "id": "2"
- "name": "cdn2",
- "dnssecEnabled": true,
- "lastUpdated": "2014-10-02 08:22:43"
- }
- ]
- }
-
-|
-
-**GET /api/1.1/cdns/:id**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------+----------+---------------------------------------------+
- | Name | Required | Description |
- +===========+==========+=============================================+
- | ``id`` | yes | CDN id. |
- +-----------+----------+---------------------------------------------+
-
- **Response Properties**
-
- +-------------------+--------+-------------------------------------------------+
- | Parameter | Type | Description |
- +===================+========+=================================================+
- | ``id`` | string | CDN id. |
- +-------------------+--------+-------------------------------------------------+
- | ``name`` | string | CDN name. |
- +-------------------+--------+-------------------------------------------------+
- | ``dnssecEnabled`` | bool | DNSSEC enabled. |
- +-------------------+--------+-------------------------------------------------+
- | ``lastUpdated`` | string | |
- +-------------------+--------+-------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "id": "2"
- "name": "cdn2",
- "dnssecEnabled": false,
- "lastUpdated": "2014-10-02 08:22:43"
- }
- ]
- }
-
-|
-
-**GET /api/1.1/cdns/name/:name**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------+----------+---------------------------------------------+
- | Name | Required | Description |
- +===========+==========+=============================================+
- | ``name`` | yes | CDN name. |
- +-----------+----------+---------------------------------------------+
-
- **Response Properties**
-
- +-------------------+--------+-------------------------------------------------+
- | Parameter | Type | Description |
- +===================+========+=================================================+
- | ``id`` | string | CDN id. |
- +-------------------+--------+-------------------------------------------------+
- | ``name`` | string | CDN name. |
- +-------------------+--------+-------------------------------------------------+
- | ``dnssecEnabled`` | bool | DNSSEC enabled. |
- +-------------------+--------+-------------------------------------------------+
- | ``lastUpdated`` | string | |
- +-------------------+--------+-------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "id": "2"
- "name": "cdn2",
- "dnssecEnabled": false,
- "lastUpdated": "2014-10-02 08:22:43"
- }
- ]
- }
-
-|
-
-Health
-++++++
-
-**GET /api/1.1/cdns/health**
-
- Retrieves the health of all locations (cache groups) for all CDNs.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +------------------+--------+-------------------------------------------------+
- | Parameter | Type | Description |
- +==================+========+=================================================+
- | ``totalOnline`` | int | Total number of online caches across all CDNs. |
- +------------------+--------+-------------------------------------------------+
- | ``totalOffline`` | int | Total number of offline caches across all CDNs. |
- +------------------+--------+-------------------------------------------------+
- | ``cachegroups`` | array | A collection of cache groups. |
- +------------------+--------+-------------------------------------------------+
- | ``>online`` | int | The number of online caches for the cache group |
- +------------------+--------+-------------------------------------------------+
- | ``>offline`` | int | The number of offline caches for the cache |
- | | | group. |
- +------------------+--------+-------------------------------------------------+
- | ``>name`` | string | Cache group name. |
- +------------------+--------+-------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "totalOnline": 148,
- "totalOffline": 0,
- "cachegroups": [
- {
- "online": 8,
- "offline": 0,
- "name": "us-co-denver"
- },
- {
- "online": 7,
- "offline": 0,
- "name": "us-de-newcastle"
- }
- ]
- },
- }
-
-
-|
-
-**GET /api/1.1/cdns/:name/health**
-
- Retrieves the health of all locations (cache groups) for a given CDN.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------------+----------+---------------------------------------------------+
- | Name | Required | Description |
- +=================+==========+===================================================+
- |``name`` | yes | |
- +-----------------+----------+---------------------------------------------------+
-
- **Response Properties**
-
- +------------------+--------+-------------------------------------------------+
- | Parameter | Type | Description |
- +==================+========+=================================================+
- | ``totalOnline`` | int | Total number of online caches across the |
- | | | specified CDN. |
- +------------------+--------+-------------------------------------------------+
- | ``totalOffline`` | int | Total number of offline caches across the |
- | | | specified CDN. |
- +------------------+--------+-------------------------------------------------+
- | ``cachegroups`` | array | A collection of cache groups. |
- +------------------+--------+-------------------------------------------------+
- | ``>online`` | int | The number of online caches for the cache group |
- +------------------+--------+-------------------------------------------------+
- | ``>offline`` | int | The number of offline caches for the cache |
- | | | group. |
- +------------------+--------+-------------------------------------------------+
- | ``>name`` | string | Cache group name. |
- +------------------+--------+-------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "totalOnline": 148,
- "totalOffline": 0,
- "cachegroups": [
- {
- "online": 8,
- "offline": 0,
- "name": "us-co-denver"
- },
- {
- "online": 7,
- "offline": 0,
- "name": "us-de-newcastle"
- }
- ]
- },
- }
-
-|
-
-**GET /api/1.1/cdns/usage/overview**
-
- Retrieves the high-level CDN usage metrics.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``currentGbps`` | number | |
- +----------------------+--------+------------------------------------------------+
- |``tps`` | int | |
- +----------------------+--------+------------------------------------------------+
- |``maxGbps`` | int | |
- +----------------------+--------+------------------------------------------------+
-
-
- **Response Example** ::
-
- {
- "response": {
- "currentGbps": 149.368167,
- "tps": 36805,
- "maxGbps": 3961
- }
- }
-
-
-**GET /api/1.1/cdns/capacity**
-
- Retrieves the aggregate capacity percentages of all locations (cache groups) for a given CDN.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``availablePercent`` | number | |
- +----------------------+--------+------------------------------------------------+
- |``unavailablePercent``| number | |
- +----------------------+--------+------------------------------------------------+
- |``utilizedPercent`` | number | |
- +----------------------+--------+------------------------------------------------+
- |``maintenancePercent``| number | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "availablePercent": 89.0939840205533,
- "unavailablePercent": 0,
- "utilizedPercent": 10.9060020300395,
- "maintenancePercent": 0.0000139494071146245
- }
- }
-
-|
-
-.. _to-api-v11-cdn-routing:
-
-Routing
-+++++++
-
-**GET /api/1.1/cdns/routing**
-
- Retrieves the aggregate routing percentages of all locations (cache groups) for a given CDN.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +-----------------+--------+-----------------------------------------+
- | Parameter | Type | Description |
- +=================+========+=========================================+
- | ``staticRoute`` | number | Used pre-configured DNS entries. |
- +-----------------+--------+-----------------------------------------+
- | ``miss`` | number | No location available for client IP. |
- +-----------------+--------+-----------------------------------------+
- | ``geo`` | number | Used 3rd party geo-IP mapping. |
- +-----------------+--------+-----------------------------------------+
- | ``err`` | number | Error localizing client IP. |
- +-----------------+--------+-----------------------------------------+
- | ``cz`` | number | Used Coverage Zone geo-IP mapping. |
- +-----------------+--------+-----------------------------------------+
- | ``dsr`` | number | Overflow traffic sent to secondary CDN. |
- +-----------------+--------+-----------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "staticRoute": 0,
- "miss": 0,
- "geo": 37.8855391018869,
- "err": 0,
- "cz": 62.1144608981131,
- "dsr": 0
- }
- }
-
-|
-
-.. _to-api-v11-cdn-metrics:
-
-Metrics
-+++++++
-
-**GET /api/1.1/cdns/metric_types/:metric/start_date/:start/end_date/:end**
-
-*Note: this route is not currently implemented in Traffic Ops. See https://github.com/apache/incubator-trafficcontrol/issues/2309*
-
- Retrieves edge metrics of one or all locations (cache groups).
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------------+----------+---------------------------+
- | Name | Required | Description |
- +=================+==========+===========================+
- | ``metric_type`` | yes | ooff, origin_tps |
- +-----------------+----------+---------------------------+
- | ``start`` | yes | UNIX time, yesterday, now |
- +-----------------+----------+---------------------------+
- | ``end`` | yes | UNIX time, yesterday, now |
- +-----------------+----------+---------------------------+
-
- **Response Properties**
-
- +---------------------+--------+-------------+
- | Parameter | Type | Description |
- +=====================+========+=============+
- | ``stats`` | hash | |
- +---------------------+--------+-------------+
- | ``>count`` | string | |
- +---------------------+--------+-------------+
- | ``>98thPercentile`` | string | |
- +---------------------+--------+-------------+
- | ``>min`` | string | |
- +---------------------+--------+-------------+
- | ``>max`` | string | |
- +---------------------+--------+-------------+
- | ``>5thPercentile`` | string | |
- +---------------------+--------+-------------+
- | ``>95thPercentile`` | string | |
- +---------------------+--------+-------------+
- | ``>mean`` | string | |
- +---------------------+--------+-------------+
- | ``>sum`` | string | |
- +---------------------+--------+-------------+
- | ``data`` | array | |
- +---------------------+--------+-------------+
- | ``>time`` | int | |
- +---------------------+--------+-------------+
- | ``>value`` | number | |
- +---------------------+--------+-------------+
- | ``label`` | string | |
- +---------------------+--------+-------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "stats": {
- "count": 1,
- "98thPercentile": 1668.03,
- "min": 1668.03,
- "max": 1668.03,
- "5thPercentile": 1668.03,
- "95thPercentile": 1668.03,
- "mean": 1668.03,
- "sum": 1668.03
- },
- "data": [
- [
- 1425135900000,
- 1668.03
- ],
- [
- 1425136200000,
- null
- ]
- ],
- "label": "Origin TPS"
- }
- ],
- }
-
-|
-
-.. _to-api-v11-cdn-domains:
-
-Domains
-+++++++
-
-**GET /api/1.1/cdns/domains**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``profileId`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``parameterId`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``profileName`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``profileDescription``| string | |
- +----------------------+--------+------------------------------------------------+
- |``domainName`` | string | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "profileId": "5",
- "parameterId": "404",
- "profileName": "CR_FOO",
- "profileDescription": "Content Router for foo.domain.net",
- "domainName": "foo.domain.net"
- },
- {
- "profileId": "8",
- "parameterId": "405",
- "profileName": "CR_BAR",
- "profileDescription": "Content Router for bar.domain.net",
- "domainName": "bar.domain.net"
- }
- ],
- }
-
-|
-
-.. _to-api-v11-cdn-topology:
-
-Topology
-++++++++
-
-**GET /api/1.1/cdns/:cdn_name/configs**
-
- Retrieves CDN config information based upon the provided cdn name.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +--------------+----------+-----------------------+
- | Name | Required | Description |
- +==============+==========+=======================+
- | ``cdn_name`` | yes | Your cdn name or, all |
- +--------------+----------+-----------------------+
-
- **Response Properties**
-
- +-----------------------+--------+-----------------------------------------------+
- | Parameter | Type | Description |
- +=======================+========+===============================================+
- |``id`` | string | |
- +-----------------------+--------+-----------------------------------------------+
- |``value`` | string | |
- +-----------------------+--------+-----------------------------------------------+
- |``name`` | string | |
- +-----------------------+--------+-----------------------------------------------+
- |``config_file`` | string | |
- +-----------------------+--------+-----------------------------------------------+
-
- **Response Example** ::
-
- TBD
-
-|
-
-**GET /api/1.1/cdns/:name/configs/monitoring**
-
- Retrieves CDN monitoring information.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +----------+----------+-------------+
- | Name | Required | Description |
- +==========+==========+=============+
- | ``name`` | yes | CDN name |
- +----------+----------+-------------+
-
- **Response Properties**
-
- +-------------------------------------------------+--------+--------------------+
- | Parameter | Type | Description |
- +=================================================+========+====================+
- | ``trafficServers`` | array | A collection of |
- | | | Traffic Servers. |
- +-------------------------------------------------+--------+--------------------+
- | ``>profile`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>ip`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>status`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>cacheGroup`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>ip6`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>port`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>hostName`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>fqdn`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>interfaceName`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>type`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>hashId`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``cacheGroups`` | array | A collection of |
- | | | cache groups. |
- +-------------------------------------------------+--------+--------------------+
- | ``>coordinates`` | hash | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>longitude`` | number | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>latitude`` | number | |
- +-------------------------------------------------+--------+--------------------+
- | ``>name`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``config`` | hash | |
- +-------------------------------------------------+--------+--------------------+
- | ``>hack.ttl`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>tm.healthParams.polling.url`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>tm.dataServer.polling.url`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>health.timepad`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>tm.polling.interval`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>health.threadPool`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>health.polling.interval`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>health.event-count`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>tm.crConfig.polling.url`` | number | |
- +-------------------------------------------------+--------+--------------------+
- | ``>CDN_name`` | number | |
- +-------------------------------------------------+--------+--------------------+
- | ``trafficMonitors`` | array | A collection of |
- | | | Traffic Monitors. |
- +-------------------------------------------------+--------+--------------------+
- | ``>profile`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>location`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>ip`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>status`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>ip6`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>port`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>hostName`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>fqdn`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``deliveryServices`` | array | A collection of |
- | | | delivery services. |
- +-------------------------------------------------+--------+--------------------+
- | ``>xmlId`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>totalTpsThreshold`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>status`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>totalKbpsThreshold`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``profiles`` | array | A collection of |
- | | | profiles. |
- +-------------------------------------------------+--------+--------------------+
- | ``>parameters`` | hash | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>health.connection.timeout`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>health.polling.url`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>health.threshold.queryTime`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>history.count`` | int | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>health.threshold.availableBandwidthInKbps`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>>health.threshold.loadavg`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>name`` | string | |
- +-------------------------------------------------+--------+--------------------+
- | ``>type`` | string | |
- +-------------------------------------------------+--------+--------------------+
-
- **Response Example**
- ::
-
- TBD
-
-|
-
-**GET /api/1.1/cdns/:name/configs/routing**
-
- Retrieves CDN routing information.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +----------+----------+-------------+
- | Name | Required | Description |
- +==========+==========+=============+
- | ``name`` | yes | |
- +----------+----------+-------------+
-
- **Response Properties**
-
- +-------------------------------------+---------+-----------------------------------+
- | Parameter | Type | Description |
- +=====================================+=========+===================================+
- | ``trafficServers`` | array | A collection of Traffic Servers. |
- +-------------------------------------+---------+-----------------------------------+
- | ``>profile`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ip`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>status`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>cacheGroup`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ip6`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>port`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>deliveryServices`` | array | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>xmlId`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>remaps`` | array | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>hostName`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>fqdn`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>interfaceName`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>type`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>hashId`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``stats`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>trafficOpsPath`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>cdnName`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>trafficOpsVersion`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>trafficOpsUser`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>date`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>trafficOpsHost`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``cacheGroups`` | array | A collection of cache groups. |
- +-------------------------------------+---------+-----------------------------------+
- | ``>coordinates`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>longitude`` | number | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>latitude`` | number | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>name`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``config`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.soa.admin`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tcoveragezone.polling.interval`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>geolocation.polling.interval`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.soa.expire`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>coveragezone.polling.url`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.soa.minimum`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>geolocation.polling.url`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>domain_name`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.ttls.AAAA`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.soa.refresh`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.ttls.NS`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.ttls.SOA`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>geolocation6.polling.interval`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.ttls.A`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>tld.soa.retry`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>geolocation6.polling.url`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``trafficMonitors`` | array | A collection of Traffic Monitors. |
- +-------------------------------------+---------+-----------------------------------+
- | ``>profile`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>location`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ip`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>status`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ip6`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>port`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>hostName`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>fqdn`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``deliveryServices`` | array | A collection of delivery |
- | | | services. |
- +-------------------------------------+---------+-----------------------------------+
- | ``>xmlId`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ttl`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>geoEnabled`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>coverageZoneOnly`` | boolean | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>matchSets`` | array | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>protocol`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>matchList`` | array | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>>regex`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>>matchType`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>bypassDestination`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>maxDnsIpsForLocation`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>ttl`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>type`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ttls`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>A`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>SOA`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>NS`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>AAAA`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>missCoordinates`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>longitude`` | number | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>latitude`` | number | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>soa`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>admin`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>retry`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>minimum`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>refresh`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>>expire`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``trafficRouters`` | hash | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>profile`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>location`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ip`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>status`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>ip6`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>port`` | int | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>hostName`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>fqdn`` | string | |
- +-------------------------------------+---------+-----------------------------------+
- | ``>apiPort`` | int | |
- +-------------------------------------+---------+-----------------------------------+
-
-
-**Response Example**
-
-::
- TBD
-
-
-.. _to-api-v11-cdn-dnsseckeys:
-
-DNSSEC Keys
-+++++++++++
-
-**GET /api/1.1/cdns/name/:name/dnsseckeys**
-
- Gets a list of dnsseckeys for CDN and all associated Delivery Services.
- Before returning response to user, check to make sure keys aren't expired. If they are expired, generate new ones.
- Before returning response to user, make sure dnssec keys for all delivery services exist. If they don't exist, create them.
-
- Authentication Required: Yes
-
- Role(s) Required: Admin
-
- **Request Route Parameters**
-
- +----------+----------+-------------+
- | Name | Required | Description |
- +==========+==========+=============+
- | ``name`` | yes | |
- +----------+----------+-------------+
-
- **Response Properties**
-
- +------------------------+--------+---------------------------------------------------------+
- | Parameter | Type | Description |
- +========================+========+=========================================================+
- | ``cdn name/ds xml_id`` | string | identifier for ds or cdn |
- +------------------------+--------+---------------------------------------------------------+
- | ``>zsk/ksk`` | array | collection of zsk/ksk data |
- +------------------------+--------+---------------------------------------------------------+
- | ``>>ttl`` | string | time-to-live for dnssec requests |
- +------------------------+--------+---------------------------------------------------------+
- | ``>>inceptionDate`` | string | epoch timestamp for when the keys were created |
- +------------------------+--------+---------------------------------------------------------+
- | ``>>expirationDate`` | string | epoch timestamp representing the expiration of the keys |
- +------------------------+--------+---------------------------------------------------------+
- | ``>>private`` | string | encoded private key |
- +------------------------+--------+---------------------------------------------------------+
- | ``>>public`` | string | encoded public key |
- +------------------------+--------+---------------------------------------------------------+
- | ``>>name`` | string | domain name |
- +------------------------+--------+---------------------------------------------------------+
- | ``version`` | string | API version |
- +------------------------+--------+---------------------------------------------------------+
-
-
- **Response Example** ::
-
- {
- "response": {
- "cdn1": {
- "zsk": {
- "ttl": "60",
- "inceptionDate": "1426196750",
- "private": "zsk private key",
- "public": "zsk public key",
- "expirationDate": "1428788750",
- "name": "foo.kabletown.com."
- },
- "ksk": {
- "name": "foo.kabletown.com.",
- "expirationDate": "1457732750",
- "public": "ksk public key",
- "private": "ksk private key",
- "inceptionDate": "1426196750",
- "ttl": "60"
- }
- },
- "ds-01": {
- "zsk": {
- "ttl": "60",
- "inceptionDate": "1426196750",
- "private": "zsk private key",
- "public": "zsk public key",
- "expirationDate": "1428788750",
- "name": "ds-01.foo.kabletown.com."
- },
- "ksk": {
- "name": "ds-01.foo.kabletown.com.",
- "expirationDate": "1457732750",
- "public": "ksk public key",
- "private": "ksk private key",
- "inceptionDate": "1426196750"
- }
- },
- ... repeated for each ds in the cdn
- },
- }
-
-|
-
-**GET /api/1.1/cdns/name/:name/dnsseckeys/delete**
-
- Delete dnssec keys for a cdn and all associated delivery services.
-
- Authentication Required: Yes
-
- Role(s) Required: Admin
-
- **Request Route Parameters**
-
- +----------+----------+----------------------------------------------------------+
- | Name | Required | Description |
- +==========+==========+==========================================================+
- | ``name`` | yes | name of the CDN for which you want to delete dnssec keys |
- +----------+----------+----------------------------------------------------------+
-
- **Response Properties**
-
- +--------------+--------+------------------+
- | Parameter | Type | Description |
- +==============+========+==================+
- | ``response`` | string | success response |
- +--------------+--------+------------------+
-
- **Response Example**
- ::
-
- {
- "response": "Successfully deleted dnssec keys for <cdn>"
- }
-
-|
-
-**POST /api/1.1/deliveryservices/dnsseckeys/generate**
-
- Generates zsk and ksk keypairs for a cdn and all associated delivery services.
-
- Authentication Required: Yes
-
- Role(s) Required: Admin
-
- **Request Properties**
-
- +-----------------------+---------+------------------------------------------------+
- | Parameter | Type | Description |
- +=======================+=========+================================================+
- | ``key`` | string | name of the cdn |
- +-----------------------+---------+------------------------------------------------+
- | ``name`` | string | domain name of the cdn |
- +-----------------------+---------+------------------------------------------------+
- | ``ttl`` | string | time to live |
- +-----------------------+---------+------------------------------------------------+
- | ``kskExpirationDays`` | string | Expiration (in days) for the key signing keys |
- +-----------------------+---------+------------------------------------------------+
- | ``zskExpirationDays`` | string | Expiration (in days) for the zone signing keys |
- +-----------------------+---------+------------------------------------------------+
-
- **Request Example** ::
-
- {
- "key": "cdn1",
- "name" "ott.kabletown.com",
- "ttl": "60",
- "kskExpirationDays": "365",
- "zskExpirationDays": "90"
- }
-
- **Response Properties**
-
- +--------------+--------+-----------------+
- | Parameter | Type | Description |
- +==============+========+=================+
- | ``response`` | string | response string |
- +--------------+--------+-----------------+
- | ``version`` | string | API version |
- +--------------+--------+-----------------+
-
- **Response Example** ::
-
-
- {
- "response": "Successfully created dnssec keys for cdn1"
- }
-
diff --git a/docs/latest/_sources/api/v11/changelog.rst.txt b/docs/latest/_sources/api/v11/changelog.rst.txt
deleted file mode 100644
index 22b1ff1..0000000
--- a/docs/latest/_sources/api/v11/changelog.rst.txt
+++ /dev/null
@@ -1,154 +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.
-..
-
-
-.. _to-api-v11-change-logs:
-
-Change Logs
-===========
-
-.. _to-api-v11-change-logs-route:
-
-/api/1.1/logs
-+++++++++++++
-
-**GET /api/1.1/logs.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +-----------------+--------+--------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +=================+========+==========================================================================+
- | ``ticketNum`` | string | Optional field to cross reference with any bug tracking systems |
- +-----------------+--------+--------------------------------------------------------------------------+
- | ``level`` | string | Log categories for each entry, examples: 'UICHANGE', 'OPER', 'APICHANGE'.|
- +-----------------+--------+--------------------------------------------------------------------------+
- | ``lastUpdated`` | string | Local unique identifier for the Log |
- +-----------------+--------+--------------------------------------------------------------------------+
- | ``user`` | string | Current user who made the change that was logged |
- +-----------------+--------+--------------------------------------------------------------------------+
- | ``id`` | string | Local unique identifier for the Log entry |
- +-----------------+--------+--------------------------------------------------------------------------+
- | ``message`` | string | Log detail about what occurred |
- +-----------------+--------+--------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "ticketNum": null,
- "level": "OPER",
- "lastUpdated": "2015-02-04 22:59:13",
- "user": "userid852",
- "id": "22661",
- "message": "Snapshot CRConfig created."
- },
- {
- "ticketNum": null,
- "level": "APICHANGE",
- "lastUpdated": "2015-02-03 17:04:20",
- "user": "userid853",
- "id": "22658",
- "message": "Update server odol-atsec-nyc-23.kbaletown.net status=REPORTED"
- },
- ],
- }
-
-|
-
-**GET /api/1.1/logs/:days/days.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +----------+----------+-----------------+
- | Name | Required | Description |
- +==========+==========+=================+
- | ``days`` | yes | Number of days. |
- +----------+----------+-----------------+
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``ticketNum`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``level`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``lastUpdated`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``user`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``id`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``message`` | string | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "ticketNum": null,
- "level": "OPER",
- "lastUpdated": "2015-02-04 22:59:13",
- "user": "userid852",
- "id": "22661",
- "message": "Snapshot CRConfig created."
- },
- {
- "ticketNum": null,
- "level": "APICHANGE",
- "lastUpdated": "2015-02-03 17:04:20",
- "user": "userid853",
- "id": "22658",
- "message": "Update server odol-atsec-nyc-23.kabletown.net status=REPORTED"
- }
- ],
- }
-
-|
-
-**GET /api/1.1/logs/newcount.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``newLogcount`` | int | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "newLogcount": 0
- }
- }
-
diff --git a/docs/latest/_sources/api/v11/deliveryservice.rst.txt b/docs/latest/_sources/api/v11/deliveryservice.rst.txt
deleted file mode 100644
index 1d01d61..0000000
--- a/docs/latest/_sources/api/v11/deliveryservice.rst.txt
+++ /dev/null
@@ -1,1286 +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.
-..
-
-
-.. _to-api-v11-ds:
-
-Delivery Service
-================
-
-.. _to-api-v11-ds-route:
-
-/api/1.1/deliveryservices
-+++++++++++++++++++++++++
-
-**GET /api/1.1/deliveryservices**
-
- Retrieves all delivery services. See also `Using Traffic Ops - Delivery Service <http://trafficcontrol.apache.org/docs/latest/admin/traffic_ops_using.html#delivery-service>`_.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +==========================+========+======================================================================================================================================+
- | ``active`` | bool | true if active, false if inactive. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``cacheurl`` | string | Cache URL rule to apply to this delivery service. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``ccrDnsTtl`` | string | The TTL of the DNS response for A or AAAA queries requesting the IP address of the tr. host. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``cdnId`` | string | Id of the CDN to which the delivery service belongs to. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``cdnName`` | string | Name of the CDN to which the delivery service belongs to. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``checkPath`` | string | The path portion of the URL to check this deliveryservice for health. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``displayName`` | string | The display name of the delivery service. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dnsBypassIp`` | string | The IPv4 IP to use for bypass on a DNS deliveryservice - bypass starts when serving more than the |
- | | | globalMaxMbps traffic on this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dnsBypassIp6`` | string | The IPv6 IP to use for bypass on a DNS deliveryservice - bypass starts when serving more than the |
- | | | globalMaxMbps traffic on this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dnsBypassTtl`` | string | The TTL of the DNS bypass response. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dscp`` | string | The Differentiated Services Code Point (DSCP) with which to mark downstream (EDGE -> customer) traffic. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``edgeHeaderRewrite`` | string | The EDGE header rewrite actions to perform. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoLimitRedirectUrl`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoLimit`` | string | - 0: None - no limitations |
- | | | - 1: Only route on CZF file hit |
- | | | - 2: Only route on CZF hit or when from USA |
- | | | |
- | | | Note that this does not prevent access to content or makes content secure; it just prevents |
- | | | routing to the content by Traffic Router. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoLimitCountries`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoProvider`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``globalMaxMbps`` | string | The maximum global bandwidth allowed on this deliveryservice. If exceeded, the traffic routes to the |
- | | | dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for HTTP deliveryservices. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``globalMaxTps`` | string | The maximum global transactions per second allowed on this deliveryservice. When this is exceeded |
- | | | traffic will be sent to the dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for |
- | | | HTTP deliveryservices |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``httpBypassFqdn`` | string | The HTTP destination to use for bypass on an HTTP deliveryservice - bypass starts when serving more than the |
- | | | globalMaxMbps traffic on this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``id`` | string | The deliveryservice id (database row number). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``infoUrl`` | string | Use this to add a URL that points to more information about that deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``initialDispersion`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``ipv6RoutingEnabled`` | bool | false: send IPv4 address of Traffic Router to client on HTTP type del. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``lastUpdated`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``logsEnabled`` | bool | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``longDesc`` | string | Description field 1. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``longDesc1`` | string | Description field 2. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``longDesc2`` | string | Description field 2. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``>>type`` | string | The type of MatchList (one of :ref:to-api-v11-types use_in_table='regex'). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``>>setNumber`` | string | The set Number of the matchList. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``>>pattern`` | string | The regexp for the matchList. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``maxDnsAnswers`` | string | The maximum number of IPs to put in a A/AAAA response for a DNS deliveryservice (0 means all |
- | | | available). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``midHeaderRewrite`` | string | The MID header rewrite actions to perform. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``missLat`` | string | The latitude to use when the client cannot be found in the CZF or the Geo lookup. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``missLong`` | string | The longitude to use when the client cannot be found in the CZF or the Geo lookup. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``multiSiteOrigin`` | bool | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin` |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``multiSiteOriginAlgor`` | bool | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin` |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``orgServerFqdn`` | string | The origin server base URL (FQDN when used in this instance, includes the |
- | | | protocol (http:// or https://) for use in retrieving content from the origin server. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``originShield`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``profileDescription`` | string | The description of the Traffic Router Profile with which this deliveryservice is associated. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``profileId`` | string | The id of the Traffic Router Profile with which this deliveryservice is associated. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``profileName`` | string | The name of the Traffic Router Profile with which this deliveryservice is associated. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``protocol`` | string | - 0: serve with http:// at EDGE |
- | | | - 1: serve with https:// at EDGE |
- | | | - 2: serve with both http:// and https:// at EDGE |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``qstringIgnore`` | string | - 0: no special query string handling; it is for use in the cache-key and pass up to origin. |
- | | | - 1: ignore query string in cache-key, but pass it up to parent and or origin. |
- | | | - 2: drop query string at edge, and do not use it in the cache-key. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``rangeRequestHandling`` | string | How to treat range requests: |
- | | | |
- | | | - 0 Do not cache (ranges requested from files taht are already cached due to a non range request will be a HIT) |
- | | | - 1 Use the `background_fetch <https://docs.trafficserver.apache.org/en/latest/reference/plugins/background_fetch.en.html>`_ plugin. |
- | | | - 2 Use the cache_range_requests plugin. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``regexRemap`` | string | Regex Remap rule to apply to this delivery service at the Edge tier. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``regionalGeoBlocking`` | bool | Regex Remap rule to apply to this delivery service at the Edge tier. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``remapText`` | string | Additional raw remap line text. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``signed`` | bool | - false: token based auth (see :ref:token-based-auth) is not enabled for this deliveryservice. |
- | | | - true: token based auth is enabled for this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``signingAlgorithm`` | string | - null: token based auth (see :ref:token-based-auth) is not enabled for this deliveryservice. |
- | | | - "url_sig": URL Sign token based auth is enabled for this deliveryservice. |
- | | | - "uri_signing": URI Signing token based auth is enabled for this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``sslKeyVersion`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``trRequestHeaders`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``trResponseHeaders`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``type`` | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice'). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``typeId`` | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice'). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``xmlId`` | string | Unique string that describes this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "active": true,
- "cacheurl": null,
- "ccrDnsTtl": "3600",
- "cdnId": "2",
- "cdnName": "over-the-top",
- "checkPath": "",
- "displayName": "My Cool Delivery Service",
- "dnsBypassCname": "",
- "dnsBypassIp": "",
- "dnsBypassIp6": "",
- "dnsBypassTtl": "30",
- "dscp": "40",
- "edgeHeaderRewrite": null,
- "exampleURLs": [
- "http://edge.foo-ds.foo.bar.net"
- ],
- "geoLimit": "0",
- "geoLimitCountries": null,
- "geoLimitRedirectURL": null,
- "geoProvider": "0",
- "globalMaxMbps": null,
- "globalMaxTps": "0",
- "httpBypassFqdn": "",
- "id": "442",
- "infoUrl": "",
- "initialDispersion": "1",
- "ipv6RoutingEnabled": true,
- "lastUpdated": "2016-01-26 08:49:35",
- "logsEnabled": false,
- "longDesc": "",
- "longDesc1": "",
- "longDesc2": "",
- "matchList": [
- {
- "pattern": ".*\\.foo-ds\\..*",
- "setNumber": "0",
- "type": "HOST_REGEXP"
- }
- ],
- "maxDnsAnswers": "0",
- "midHeaderRewrite": null,
- "missLat": "41.881944",
- "missLong": "-87.627778",
- "multiSiteOrigin": false,
- "multiSiteOriginAlgorithm": null,
- "orgServerFqdn": "http://baz.boo.net",
- "originShield": null,
- "profileDescription": "Content Router for over-the-top",
- "profileId": "5",
- "profileName": "ROUTER_TOP",
- "protocol": "0",
- "qstringIgnore": "1",
- "rangeRequestHandling": "0",
- "regexRemap": null,
- "regionalGeoBlocking": false,
- "remapText": null,
- "signed": false,
- "signingAlgorithm": null,
- "sslKeyVersion": "0",
- "trRequestHeaders": null,
- "trResponseHeaders": "Access-Control-Allow-Origin: *",
- "type": "HTTP",
- "typeId": "8",
- "xmlId": "foo-ds"
- }
- { .. },
- { .. }
- ]
- }
-
-|
-
-
-**GET /api/1.1/deliveryservices/:id**
-
- Retrieves a specific delivery service. See also `Using Traffic Ops - Delivery Service <http://trafficcontrol.apache.org/docs/latest/admin/traffic_ops_using.html#delivery-service>`_.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +==========================+========+======================================================================================================================================+
- | ``active`` | bool | true if active, false if inactive. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``cacheurl`` | string | Cache URL rule to apply to this delivery service. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``ccrDnsTtl`` | string | The TTL of the DNS response for A or AAAA queries requesting the IP address of the tr. host. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``cdnId`` | string | Id of the CDN to which the delivery service belongs to. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``cdnName`` | string | Name of the CDN to which the delivery service belongs to. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``checkPath`` | string | The path portion of the URL to check this deliveryservice for health. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``displayName`` | string | The display name of the delivery service. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dnsBypassIp`` | string | The IPv4 IP to use for bypass on a DNS deliveryservice - bypass starts when serving more than the |
- | | | globalMaxMbps traffic on this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dnsBypassIp6`` | string | The IPv6 IP to use for bypass on a DNS deliveryservice - bypass starts when serving more than the |
- | | | globalMaxMbps traffic on this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dnsBypassTtl`` | string | The TTL of the DNS bypass response. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``dscp`` | string | The Differentiated Services Code Point (DSCP) with which to mark downstream (EDGE -> customer) traffic. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``edgeHeaderRewrite`` | string | The EDGE header rewrite actions to perform. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``exampleURLs`` | array | Entry points into the CDN for this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoLimitRedirectUrl`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoLimit`` | string | - 0: None - no limitations |
- | | | - 1: Only route on CZF file hit |
- | | | - 2: Only route on CZF hit or when from USA |
- | | | |
- | | | Note that this does not prevent access to content or makes content secure; it just prevents |
- | | | routing to the content by Traffic Router. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoLimitCountries`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``geoProvider`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``globalMaxMbps`` | string | The maximum global bandwidth allowed on this deliveryservice. If exceeded, the traffic routes to the |
- | | | dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for HTTP deliveryservices. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``globalMaxTps`` | string | The maximum global transactions per second allowed on this deliveryservice. When this is exceeded |
- | | | traffic will be sent to the dnsByPassIp* for DNS deliveryservices and to the httpBypassFqdn for |
- | | | HTTP deliveryservices |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``httpBypassFqdn`` | string | The HTTP destination to use for bypass on an HTTP deliveryservice - bypass starts when serving more than the |
- | | | globalMaxMbps traffic on this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``id`` | string | The deliveryservice id (database row number). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``infoUrl`` | string | Use this to add a URL that points to more information about that deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``initialDispersion`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``ipv6RoutingEnabled`` | bool | false: send IPv4 address of Traffic Router to client on HTTP type del. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``lastUpdated`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``logsEnabled`` | bool | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``longDesc`` | string | Description field 1. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``longDesc1`` | string | Description field 2. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``longDesc2`` | string | Description field 2. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``matchList`` | array | Array of matchList hashes. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``>>type`` | string | The type of MatchList (one of :ref:to-api-v11-types use_in_table='regex'). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``>>setNumber`` | string | The set Number of the matchList. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``>>pattern`` | string | The regexp for the matchList. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``maxDnsAnswers`` | string | The maximum number of IPs to put in a A/AAAA response for a DNS deliveryservice (0 means all |
- | | | available). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``midHeaderRewrite`` | string | The MID header rewrite actions to perform. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``missLat`` | string | The latitude to use when the client cannot be found in the CZF or the Geo lookup. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``missLong`` | string | The longitude to use when the client cannot be found in the CZF or the Geo lookup. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``multiSiteOrigin`` | bool | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin` |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``multiSiteOriginAlgor`` | bool | Is the Multi Site Origin feature enabled for this delivery service (0=false, 1=true). See :ref:`rl-multi-site-origin` |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``orgServerFqdn`` | string | The origin server base URL (FQDN when used in this instance, includes the |
- | | | protocol (http:// or https://) for use in retrieving content from the origin server. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``originShield`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``profileDescription`` | string | The description of the Traffic Router Profile with which this deliveryservice is associated. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``profileId`` | string | The id of the Traffic Router Profile with which this deliveryservice is associated. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``profileName`` | string | The name of the Traffic Router Profile with which this deliveryservice is associated. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``protocol`` | string | - 0: serve with http:// at EDGE |
- | | | - 1: serve with https:// at EDGE |
- | | | - 2: serve with both http:// and https:// at EDGE |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``qstringIgnore`` | string | - 0: no special query string handling; it is for use in the cache-key and pass up to origin. |
- | | | - 1: ignore query string in cache-key, but pass it up to parent and or origin. |
- | | | - 2: drop query string at edge, and do not use it in the cache-key. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``rangeRequestHandling`` | string | How to treat range requests: |
- | | | |
- | | | - 0 Do not cache (ranges requested from files taht are already cached due to a non range request will be a HIT) |
- | | | - 1 Use the `background_fetch <https://docs.trafficserver.apache.org/en/latest/reference/plugins/background_fetch.en.html>`_ plugin. |
- | | | - 2 Use the cache_range_requests plugin. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``regexRemap`` | string | Regex Remap rule to apply to this delivery service at the Edge tier. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``regionalGeoBlocking`` | bool | Regex Remap rule to apply to this delivery service at the Edge tier. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``remapText`` | string | Additional raw remap line text. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``signed`` | bool | - false: token based auth (see :ref:token-based-auth) is not enabled for this deliveryservice. |
- | | | - true: token based auth is enabled for this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``signingAlgorithm`` | string | - null: token based auth (see :ref:token-based-auth) is not enabled for this deliveryservice. |
- | | | - "url_sig": URL Sign token based auth is enabled for this deliveryservice. |
- | | | - "uri_signing": URI Signing token based auth is enabled for this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``sslKeyVersion`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``trRequestHeaders`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``trResponseHeaders`` | string | |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``type`` | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice'). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``typeId`` | string | The type of this deliveryservice (one of :ref:to-api-v11-types use_in_table='deliveryservice'). |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
- | ``xmlId`` | string | Unique string that describes this deliveryservice. |
- +--------------------------+--------+--------------------------------------------------------------------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "active": true,
- "cacheurl": null,
- "ccrDnsTtl": "3600",
- "cdnId": "2",
- "cdnName": "over-the-top",
- "checkPath": "",
- "displayName": "My Cool Delivery Service",
- "dnsBypassCname": "",
- "dnsBypassIp": "",
- "dnsBypassIp6": "",
- "dnsBypassTtl": "30",
- "dscp": "40",
- "edgeHeaderRewrite": null,
- "exampleURLs": [
- "http://edge.foo-ds.foo.bar.net"
- ],
- "geoLimit": "0",
- "geoLimitCountries": null,
- "geoLimitRedirectURL": null,
- "geoProvider": "0",
- "globalMaxMbps": null,
- "globalMaxTps": "0",
- "httpBypassFqdn": "",
- "id": "442",
- "infoUrl": "",
- "initialDispersion": "1",
- "ipv6RoutingEnabled": true,
- "lastUpdated": "2016-01-26 08:49:35",
- "logsEnabled": false,
- "longDesc": "",
- "longDesc1": "",
- "longDesc2": "",
- "matchList": [
- {
- "pattern": ".*\\.foo-ds\\..*",
- "setNumber": "0",
- "type": "HOST_REGEXP"
- }
- ],
- "maxDnsAnswers": "0",
- "midHeaderRewrite": null,
- "missLat": "41.881944",
- "missLong": "-87.627778",
- "multiSiteOrigin": false,
- "multiSiteOriginAlgorithm": null,
- "orgServerFqdn": "http://baz.boo.net",
- "originShield": null,
- "profileDescription": "Content Router for over-the-top",
- "profileId": "5",
- "profileName": "ROUTER_TOP",
- "protocol": "0",
- "qstringIgnore": "1",
- "rangeRequestHandling": "0",
- "regexRemap": null,
- "regionalGeoBlocking": false,
- "remapText": null,
- "signed": false,
- "signingAlgorithm": null,
- "sslKeyVersion": "0",
- "trRequestHeaders": null,
- "trResponseHeaders": "Access-Control-Allow-Origin: *",
- "type": "HTTP",
- "typeId": "8",
- "xmlId": "foo-ds"
- }
- ]
- }
-
-|
-
-
-.. _to-api-v11-ds-health:
-
-Health
-++++++
-
-**GET /api/1.1/deliveryservices/:id/state.json**
-
- Retrieves the failover state for a delivery service.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +------------------+---------+-------------------------------------------------+
- | Parameter | Type | Description |
- +==================+=========+=================================================+
- | ``failover`` | hash | |
- +------------------+---------+-------------------------------------------------+
- | ``>locations`` | array | |
- +------------------+---------+-------------------------------------------------+
- | ``>destination`` | string | |
- +------------------+---------+-------------------------------------------------+
- | ``>configured`` | boolean | |
- +------------------+---------+-------------------------------------------------+
- | ``>enabled`` | boolean | |
- +------------------+---------+-------------------------------------------------+
- | ``enabled`` | boolean | |
- +------------------+---------+-------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "failover": {
- "locations": [ ],
- "destination": null,
- "configured": false,
- "enabled": false
- },
- "enabled": true
- }
- }
-
-|
-
-**GET /api/1.1/deliveryservices/:id/health.json**
-
- Retrieves the health of all locations (cache groups) for a delivery service.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +------------------+--------+-------------------------------------------------+
- | Parameter | Type | Description |
- +==================+========+=================================================+
- | ``totalOnline`` | int | Total number of online caches across all CDNs. |
- +------------------+--------+-------------------------------------------------+
- | ``totalOffline`` | int | Total number of offline caches across all CDNs. |
- +------------------+--------+-------------------------------------------------+
- | ``cachegroups`` | array | A collection of cache groups. |
- +------------------+--------+-------------------------------------------------+
- | ``>online`` | int | The number of online caches for the cache group |
- +------------------+--------+-------------------------------------------------+
- | ``>offline`` | int | The number of offline caches for the cache |
- | | | group. |
- +------------------+--------+-------------------------------------------------+
- | ``>name`` | string | Cache group name. |
- +------------------+--------+-------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "totalOnline": 148,
- "totalOffline": 0,
- "cachegroups": [
- {
- "online": 8,
- "offline": 0,
- "name": "us-co-denver"
- },
- {
- "online": 7,
- "offline": 0,
- "name": "us-de-newcastle"
- }
- ]
- }
- }
-
-
-|
-
-**GET /api/1.1/deliveryservices/:id/capacity.json**
-
- Retrieves the capacity percentages of a delivery service.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------------+----------+---------------------------------------------------+
- | Name | Required | Description |
- +=================+==========+===================================================+
- |id | yes | delivery service id. |
- +-----------------+----------+---------------------------------------------------+
-
- **Response Properties**
-
- +------------------------+--------+---------------------------------------------------+
- | Parameter | Type | Description |
- +========================+========+===================================================+
- | ``availablePercent`` | number | The percentage of server capacity assigned to |
- | | | the delivery service that is available. |
- +------------------------+--------+---------------------------------------------------+
- | ``unavailablePercent`` | number | The percentage of server capacity assigned to the |
- | | | delivery service that is unavailable. |
- +------------------------+--------+---------------------------------------------------+
- | ``utilizedPercent`` | number | The percentage of server capacity assigned to the |
- | | | delivery service being used. |
- +------------------------+--------+---------------------------------------------------+
- | ``maintenancePercent`` | number | The percentage of server capacity assigned to the |
- | | | delivery service that is down for maintenance. |
- +------------------------+--------+---------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "availablePercent": 89.0939840205533,
- "unavailablePercent": 0,
- "utilizedPercent": 10.9060020300395,
- "maintenancePercent": 0.0000139494071146245
- },
- }
-
-
-|
-
-**GET /api/1.1/deliveryservices/:id/routing.json**
-
- Retrieves the routing method percentages of a delivery service.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------------+----------+---------------------------------------------------+
- | Name | Required | Description |
- +=================+==========+===================================================+
- |id | yes | delivery service id. |
- +-----------------+----------+---------------------------------------------------+
-
- **Response Properties**
-
- +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +=================+========+=============================================================================================================================+
- | ``staticRoute`` | number | The percentage of Traffic Router responses for this deliveryservice satisfied with pre-configured DNS entries. |
- +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
- | ``miss`` | number | The percentage of Traffic Router responses for this deliveryservice that were a miss (no location available for client IP). |
- +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
- | ``geo`` | number | The percentage of Traffic Router responses for this deliveryservice satisfied using 3rd party geo-IP mapping. |
- +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
- | ``err`` | number | The percentage of Traffic Router requests for this deliveryservice resulting in an error. |
- +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
- | ``cz`` | number | The percentage of Traffic Router requests for this deliveryservice satisfied by a CZF hit. |
- +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
- | ``dsr`` | number | The percentage of Traffic Router requests for this deliveryservice satisfied by sending the |
- | | | client to the overflow CDN. |
- +-----------------+--------+-----------------------------------------------------------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "staticRoute": 0,
- "miss": 0,
- "geo": 37.8855391018869,
- "err": 0,
- "cz": 62.1144608981131,
- "dsr": 0
- },
- }
-
-|
-
-.. _to-api-v11-ds-metrics:
-
-Metrics
-+++++++
-
-**GET /api/1.1/deliveryservices/:id/server_types/:type/metric_types/start_date/:start/end_date/:end.json**
-
- Retrieves detailed and summary metrics for MIDs or EDGEs for a delivery service.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +------------------+----------+-----------------------------------------------------------------------------+
- | Name | Required | Description |
- +==================+==========+=============================================================================+
- | ``id`` | yes | The delivery service id. |
- +------------------+----------+-----------------------------------------------------------------------------+
- | ``server_types`` | yes | EDGE or MID. |
- +------------------+----------+-----------------------------------------------------------------------------+
- | ``metric_types`` | yes | One of the following: "kbps", "tps", "tps_2xx", "tps_3xx", "tps_4xx", |
- | | | "tps_5xx". |
- +------------------+----------+-----------------------------------------------------------------------------+
- | ``start_date`` | yes | UNIX time |
- +------------------+----------+-----------------------------------------------------------------------------+
- | ``end_date`` | yes | UNIX time |
- +------------------+----------+-----------------------------------------------------------------------------+
-
- **Request Query Parameters**
-
- +------------------+----------+-----------------------------------------------------------------------------+
- | Name | Required | Description |
- +==================+==========+=============================================================================+
- | ``stats`` | no | Flag used to return only summary metrics |
- +------------------+----------+-----------------------------------------------------------------------------+
-
- **Response Properties**
-
- +----------------------+--------+-------------+
- | Parameter | Type | Description |
- +======================+========+=============+
- | ``stats`` | hash | |
- +----------------------+--------+-------------+
- | ``>>count`` | int | |
- +----------------------+--------+-------------+
- | ``>>98thPercentile`` | number | |
- +----------------------+--------+-------------+
- | ``>>min`` | number | |
- +----------------------+--------+-------------+
- | ``>>max`` | number | |
- +----------------------+--------+-------------+
- | ``>>5thPercentile`` | number | |
- +----------------------+--------+-------------+
- | ``>>95thPercentile`` | number | |
- +----------------------+--------+-------------+
- | ``>>median`` | number | |
- +----------------------+--------+-------------+
- | ``>>mean`` | number | |
- +----------------------+--------+-------------+
- | ``>>stddev`` | number | |
- +----------------------+--------+-------------+
- | ``>>sum`` | number | |
- +----------------------+--------+-------------+
- | ``data`` | array | |
- +----------------------+--------+-------------+
- | ``>>item`` | array | |
- +----------------------+--------+-------------+
- | ``>>time`` | number | |
- +----------------------+--------+-------------+
- | ``>>value`` | number | |
- +----------------------+--------+-------------+
- | ``label`` | string | |
- +----------------------+--------+-------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "stats": {
- "count": 988,
- "98thPercentile": 16589105.55958,
- "min": 3185442.975,
- "max": 17124754.257,
- "5thPercentile": 3901253.95445,
- "95thPercentile": 16013210.034,
- "median": 8816895.576,
- "mean": 8995846.31741194,
- "stddev": 3941169.83683573,
- "sum": 333296106.060112
- },
- "data": [
- [
- 1414303200000,
- 12923518.466
- ],
- [
- 1414303500000,
- 12625139.65
- ]
- ],
- "label": "MID Kbps"
- }
- ],
- }
-
-
-.. _to-api-v11-ds-server:
-
-Server
-++++++
-
-**GET /api/1.1/deliveryserviceserver.json**
-
- Authentication Required: Yes
-
- Role(s) Required: Yes
-
- **Request Query Parameters**
-
- +-----------+----------+----------------------------------------+
- | Name | Required | Description |
- +===========+==========+========================================+
- | ``page`` | no | The page number for use in pagination. |
- +-----------+----------+----------------------------------------+
- | ``limit`` | no | For use in limiting the result set. |
- +-----------+----------+----------------------------------------+
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``lastUpdated`` | array | |
- +----------------------+--------+------------------------------------------------+
- |``server`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``deliveryService`` | string | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "page": 2,
- "orderby": "deliveryservice",
- "response": [
- {
- "lastUpdated": "2014-09-26 17:53:43",
- "server": "20",
- "deliveryService": "1"
- },
- {
- "lastUpdated": "2014-09-26 17:53:44",
- "server": "21",
- "deliveryService": "1"
- },
- ],
- "limit": 2
- }
-
-|
-
-.. _to-api-v11-ds-sslkeys:
-
-SSL Keys
-+++++++++
-
-**GET /api/1.1/deliveryservices/xmlId/:xmlid/sslkeys.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------+----------+----------------------------------------+
- | Name | Required | Description |
- +===========+==========+========================================+
- | ``xmlId`` | yes | xml_id of the desired delivery service |
- +-----------+----------+----------------------------------------+
-
- **Request Query Parameters**
-
- +-------------+----------+--------------------------------+
- | Name | Required | Description |
- +=============+==========+================================+
- | ``version`` | no | The version number to retrieve |
- +-------------+----------+--------------------------------+
-
- **Response Properties**
-
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +==================+========+=========================================================================================================================================+
- | ``crt`` | string | base64 encoded crt file for delivery service |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``csr`` | string | base64 encoded csr file for delivery service |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``key`` | string | base64 encoded private key file for delivery service |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``businessUnit`` | string | The business unit entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``city`` | string | The city entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``organization`` | string | The organization entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``hostname`` | string | The hostname entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``country`` | string | The country entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``state`` | string | The state entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``version`` | string | The version of the certificate record in Riak |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "certificate": {
- "crt": "crt",
- "key": "key",
- "csr": "csr"
- },
- "businessUnit": "CDN_Eng",
- "city": "Denver",
- "organization": "KableTown",
- "hostname": "foober.com",
- "country": "US",
- "state": "Colorado",
- "version": "1"
- }
- }
-
-|
-
-**GET /api/1.1/deliveryservices/hostname/:hostname/sslkeys.json**
-
- Authentication Required: Yes
-
- Role Required: Admin
-
- **Request Route Parameters**
-
- +--------------+----------+---------------------------------------------------+
- | Name | Required | Description |
- +==============+==========+===================================================+
- | ``hostname`` | yes | pristine hostname of the desired delivery service |
- +--------------+----------+---------------------------------------------------+
-
- **Request Query Parameters**
-
- +-------------+----------+--------------------------------+
- | Name | Required | Description |
- +=============+==========+================================+
- | ``version`` | no | The version number to retrieve |
- +-------------+----------+--------------------------------+
-
- **Response Properties**
-
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +==================+========+=========================================================================================================================================+
- | ``crt`` | string | base64 encoded crt file for delivery service |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``csr`` | string | base64 encoded csr file for delivery service |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``key`` | string | base64 encoded private key file for delivery service |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``businessUnit`` | string | The business unit entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``city`` | string | The city entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``organization`` | string | The organization entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``hostname`` | string | The hostname entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``country`` | string | The country entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``state`` | string | The state entered by the user when generating certs. Field is optional and if not provided by the user will not be in response |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
- | ``version`` | string | The version of the certificate record in Riak |
- +------------------+--------+-----------------------------------------------------------------------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- "certificate": {
- "crt": "crt",
- "key": "key",
- "csr": "csr"
- },
- "businessUnit": "CDN_Eng",
- "city": "Denver",
- "organization": "KableTown",
- "hostname": "foober.com",
- "country": "US",
- "state": "Colorado",
- "version": "1"
- }
- }
-
-|
-
-**GET /api/1.1/deliveryservices/xmlId/:xmlid/sslkeys/delete.json**
-
- Authentication Required: Yes
-
- Role Required: Operations
-
- **Request Route Parameters**
-
- +-----------+----------+----------------------------------------+
- | Name | Required | Description |
- +===========+==========+========================================+
- | ``xmlId`` | yes | xml_id of the desired delivery service |
- +-----------+----------+----------------------------------------+
-
- **Request Query Parameters**
-
- +-------------+----------+--------------------------------+
- | Name | Required | Description |
- +=============+==========+================================+
- | ``version`` | no | The version number to retrieve |
- +-------------+----------+--------------------------------+
-
- **Response Properties**
-
- +--------------+--------+------------------+
- | Parameter | Type | Description |
- +==============+========+==================+
- | ``response`` | string | success response |
- +--------------+--------+------------------+
-
- **Response Example** ::
-
- {
- "response": "Successfully deleted ssl keys for <xml_id>"
- }
-
-|
-
-**POST /api/1.1/deliveryservices/sslkeys/generate**
-
- Generates SSL crt, csr, and private key for a delivery service
-
- Authentication Required: Yes
-
- Role(s) Required: Operations
-
- **Request Properties**
-
- +--------------+---------+-------------------------------------------------+
- | Parameter | Type | Description |
- +==============+=========+=================================================+
- | ``key`` | string | xml_id of the delivery service |
- +--------------+---------+-------------------------------------------------+
- | ``version`` | string | version of the keys being generated |
- +--------------+---------+-------------------------------------------------+
- | ``hostname`` | string | the *pristine hostname* of the delivery service |
- +--------------+---------+-------------------------------------------------+
- | ``country`` | string | |
- +--------------+---------+-------------------------------------------------+
- | ``state`` | string | |
- +--------------+---------+-------------------------------------------------+
- | ``city`` | string | |
- +--------------+---------+-------------------------------------------------+
- | ``org`` | string | |
- +--------------+---------+-------------------------------------------------+
- | ``unit`` | boolean | |
- +--------------+---------+-------------------------------------------------+
-
- **Request Example** ::
-
- {
- "key": "ds-01",
- "businessUnit": "CDN Engineering",
- "version": "3",
- "hostname": "tr.ds-01.ott.kabletown.com",
- "certificate": {
- "key": "some_key",
- "csr": "some_csr",
- "crt": "some_crt"
- },
- "country": "US",
- "organization": "Kabletown",
- "city": "Denver",
- "state": "Colorado"
- }
-
-|
-
- **Response Properties**
-
- +--------------+--------+-----------------+
- | Parameter | Type | Description |
- +==============+========+=================+
- | ``response`` | string | response string |
- +--------------+--------+-----------------+
- | ``version`` | string | API version |
- +--------------+--------+-----------------+
-
- **Response Example** ::
-
- {
- "response": "Successfully created ssl keys for ds-01"
- }
-
-|
-
-**POST /api/1.1/deliveryservices/sslkeys/add**
-
- Allows user to add SSL crt, csr, and private key for a delivery service.
-
- Authentication Required: Yes
-
- Role(s) Required: Operations
-
- **Request Properties**
-
- +-------------+--------+-------------------------------------+
- | Parameter | Type | Description |
- +=============+========+=====================================+
- | ``key`` | string | xml_id of the delivery service |
- +-------------+--------+-------------------------------------+
- | ``version`` | string | version of the keys being generated |
- +-------------+--------+-------------------------------------+
- | ``csr`` | string | |
- +-------------+--------+-------------------------------------+
- | ``crt`` | string | |
- +-------------+--------+-------------------------------------+
- | ``key`` | string | |
- +-------------+--------+-------------------------------------+
-
- **Request Example** ::
-
- {
- "key": "ds-01",
- "version": "1",
- "certificate": {
- "key": "some_key",
- "csr": "some_csr",
- "crt": "some_crt"
- }
- }
-
-|
-
- **Response Properties**
-
- +--------------+--------+-----------------+
- | Parameter | Type | Description |
- +==============+========+=================+
- | ``response`` | string | response string |
- +--------------+--------+-----------------+
- | ``version`` | string | API version |
- +--------------+--------+-----------------+
-
- **Response Example** ::
-
- {
- "response": "Successfully added ssl keys for ds-01"
- }
-
-
-|
-
-**POST /api/1.1/deliveryservices/request**
-
- Allows a user to send delivery service request details to a specified email address.
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Properties**
-
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | Parameter | Type | Required | Description |
- +========================================+========+==========+=============================================================================================+
- | ``emailTo`` | string | yes | The email to which the delivery service request will be sent. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``details`` | hash | yes | Parameters for the delivery service request. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>customer`` | string | yes | Name of the customer to associated with the delivery service. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>deliveryProtocol`` | string | yes | Eg. http or http/https |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>routingType`` | string | yes | Eg. DNS or HTTP Redirect |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>serviceDesc`` | string | yes | A description of the delivery service. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>peakBPSEstimate`` | string | yes | Used to manage cache efficiency and plan for capacity. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>peakTPSEstimate`` | string | yes | Used to manage cache efficiency and plan for capacity. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>maxLibrarySizeEstimate`` | string | yes | Used to manage cache efficiency and plan for capacity. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>originURL`` | string | yes | The URL path to the origin server. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>hasOriginDynamicRemap`` | bool | yes | This is a feature which allows services to use multiple origin URLs for the same service. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>originTestFile`` | string | yes | A URL path to a test file available on the origin server. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>hasOriginACLWhitelist`` | bool | yes | Is access to your origin restricted using an access control list (ACL or whitelist) of Ips? |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>originHeaders`` | string | no | Header values that must be passed to requests to your origin. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>otherOriginSecurity`` | string | no | Other origin security measures that need to be considered for access. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>queryStringHandling`` | string | yes | How to handle query strings that come with the request. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>rangeRequestHandling`` | string | yes | How to handle range requests. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>hasSignedURLs`` | bool | yes | Are Urls signed? |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>hasNegativeCachingCustomization`` | bool | yes | Any customization required for negative caching? |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>negativeCachingCustomizationNote`` | string | yes | Negative caching customization instructions. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>serviceAliases`` | array | no | Service aliases which will be used for this service. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>rateLimitingGBPS`` | int | no | Rate Limiting - Bandwidth (Gigabits per second) |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>rateLimitingTPS`` | int | no | Rate Limiting - Transactions/Second |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>overflowService`` | string | no | An overflow point (URL or IP address) used if rate limits are met. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>headerRewriteEdge`` | string | no | Headers can be added or altered at each layer of the CDN. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>headerRewriteMid`` | string | no | Headers can be added or altered at each layer of the CDN. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>headerRewriteRedirectRouter`` | string | no | Headers can be added or altered at each layer of the CDN. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
- | ``>notes`` | string | no | Additional instructions to provide the delivery service provisioning team. |
- +----------------------------------------+--------+----------+---------------------------------------------------------------------------------------------+
-
- **Request Example** ::
-
- {
- "emailTo": "foo@bar.com",
- "details": {
- "customer": "XYZ Corporation",
- "contentType": "video-on-demand",
- "deliveryProtocol": "http",
- "routingType": "dns",
- "serviceDesc": "service description goes here",
- "peakBPSEstimate": "less-than-5-Gbps",
- "peakTPSEstimate": "less-than-1000-TPS",
- "maxLibrarySizeEstimate": "less-than-200-GB",
- "originURL": "http://myorigin.com",
- "hasOriginDynamicRemap": false,
- "originTestFile": "http://myorigin.com/crossdomain.xml",
- "hasOriginACLWhitelist": true,
- "originHeaders": "",
- "otherOriginSecurity": "",
- "queryStringHandling": "ignore-in-cache-key-and-pass-up",
- "rangeRequestHandling": "range-requests-not-used",
- "hasSignedURLs": true,
- "hasNegativeCachingCustomization": true,
- "negativeCachingCustomizationNote": "negative caching instructions",
- "serviceAliases": [
- "http://alias1.com",
- "http://alias2.com"
- ],
- "rateLimitingGBPS": 50,
- "rateLimitingTPS": 5000,
- "overflowService": "http://overflowcdn.com",
- "headerRewriteEdge": "",
- "headerRewriteMid": "",
- "headerRewriteRedirectRouter": "",
- "notes": ""
- }
- }
-
-|
-
- **Response Properties**
-
- +-------------+--------+----------------------------------+
- | Parameter | Type | Description |
- +=============+========+==================================+
- | ``alerts`` | array | A collection of alert messages. |
- +-------------+--------+----------------------------------+
- | ``>level`` | string | Success, info, warning or error. |
- +-------------+--------+----------------------------------+
- | ``>text`` | string | Alert message. |
- +-------------+--------+----------------------------------+
- | ``version`` | string | |
- +-------------+--------+----------------------------------+
-
- **Response Example** ::
-
- {
- "alerts": [
- {
- "level": "success",
- "text": "Delivery Service request sent to foo@bar.com."
- }
- ]
- }
-
-|
diff --git a/docs/latest/_sources/api/v11/hwinfo.rst.txt b/docs/latest/_sources/api/v11/hwinfo.rst.txt
deleted file mode 100644
index cc45b38..0000000
--- a/docs/latest/_sources/api/v11/hwinfo.rst.txt
+++ /dev/null
@@ -1,67 +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.
-..
-
-
-.. _to-api-v11-hwinfo:
-
-Hardware Info
-=============
-
-.. _to-api-v11-hwinfo-route:
-
-/api/1.1/hwinfo
-+++++++++++++++
-
-**GET /api/1.1/hwinfo.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +--------------------+--------+----------------------------------------------------------------------+
- | Parameter | Type | Description |
- +====================+========+======================================================================+
- | ``serverId`` | string | Local unique identifier for this specific server's hardware info |
- +--------------------+--------+----------------------------------------------------------------------+
- | ``serverHostName`` | string | Hostname for this specific server's hardware info |
- +--------------------+--------+----------------------------------------------------------------------+
- | ``lastUpdated`` | string | The Time and Date for the last update for this server. |
- +--------------------+--------+----------------------------------------------------------------------+
- | ``val`` | string | Freeform value used to track anything about a server's hardware info |
- +--------------------+--------+----------------------------------------------------------------------+
- | ``description`` | string | Freeform description for this specific server's hardware info |
- +--------------------+--------+----------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "serverId": "odol-atsmid-cen-09",
- "lastUpdated": "2014-05-27 09:06:02",
- "val": "D1S4",
- "description": "Physical Disk 0:1:0"
- },
- {
- "serverId": "odol-atsmid-cen-09",
- "lastUpdated": "2014-05-27 09:06:02",
- "val": "D1S4",
- "description": "Physical Disk 0:1:1"
- }
- ],
- }
-
diff --git a/docs/latest/_sources/api/v11/index.rst.txt b/docs/latest/_sources/api/v11/index.rst.txt
deleted file mode 100644
index bb50b22..0000000
--- a/docs/latest/_sources/api/v11/index.rst.txt
+++ /dev/null
@@ -1,40 +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.
-..
-
-API 1.1 Reference
-*****************
-Traffic Ops v1.1 API Documentation
-
-.. toctree::
- :maxdepth: 1
-
- asn
- cachegroup
- cdn
- changelog
- deliveryservice
- hwinfo
- parameter
- phys_location
- profile
- region
- role
- server
- static_dns
- status
- system
- to_extension
- type
- user
diff --git a/docs/latest/_sources/api/v11/parameter.rst.txt b/docs/latest/_sources/api/v11/parameter.rst.txt
deleted file mode 100644
index 1b83d01..0000000
--- a/docs/latest/_sources/api/v11/parameter.rst.txt
+++ /dev/null
@@ -1,136 +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.
-..
-
-.. _to-api-v11-parameter:
-
-Parameter
-=========
-
-.. _to-api-v11-parameters-route:
-
-/api/1.1/parameters
-+++++++++++++++++++
-
-**GET /api/1.1/parameters.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +------------------+---------+--------------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +==================+=========+================================================================================+
- | ``last_updated`` | string | The Time / Date this server entry was last updated |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``secure`` | boolean | When true, the parameter is accessible only by admin users. Defaults to false. |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``value`` | string | The parameter value, only visible to admin if secure is true |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``name`` | string | The parameter name |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``config_file`` | string | The parameter config_file |
- +------------------+---------+--------------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "last_updated": "2012-09-17 21:41:22",
- "secure": 0,
- "value": "foo.bar.net",
- "name": "domain_name",
- "config_file": "FooConfig.xml"
- },
- {
- "last_updated": "2012-09-17 21:41:22",
- "secure": 0,
- "value": "0,1,2,3,4,5,6",
- "name": "Drive_Letters",
- "config_file": "storage.config"
- },
- {
- "last_updated": "2012-09-17 21:41:22",
- "secure": 0,
- "value": "STRING __HOSTNAME__",
- "name": "CONFIG proxy.config.proxy_name",
- "config_file": "records.config"
- }
- ],
- }
-
-|
-
-**GET /api/1.1/parameters/profile/:name.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +------------------+----------+-------------+
- | Name | Required | Description |
- +==================+==========+=============+
- | ``profile_name`` | yes | |
- +------------------+----------+-------------+
-
- **Response Properties**
-
- +------------------+---------+--------------------------------------------------------------------------------+
- | Parameter | Type | Description |
- +==================+=========+================================================================================+
- | ``last_updated`` | string | The Time / Date this server entry was last updated |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``secure`` | boolean | When true, the parameter is accessible only by admin users. Defaults to false. |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``value`` | string | The parameter value, only visible to admin if secure is true |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``name`` | string | The parameter name |
- +------------------+---------+--------------------------------------------------------------------------------+
- | ``config_file`` | string | The parameter config_file |
- +------------------+---------+--------------------------------------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "last_updated": "2012-09-17 21:41:22",
- "secure": 0,
- "value": "foo.bar.net",
- "name": "domain_name",
- "config_file": "FooConfig.xml"
- },
- {
- "last_updated": "2012-09-17 21:41:22",
- "secure": 0,
- "value": "0,1,2,3,4,5,6",
- "name": "Drive_Letters",
- "config_file": "storage.config"
- },
- {
- "last_updated": "2012-09-17 21:41:22",
- "secure": 0,
- "value": "STRING __HOSTNAME__",
- "name": "CONFIG proxy.config.proxy_name",
- "config_file": "records.config"
- }
- ],
- }
-
-
diff --git a/docs/latest/_sources/api/v11/phys_location.rst.txt b/docs/latest/_sources/api/v11/phys_location.rst.txt
deleted file mode 100644
index 6ebaff0..0000000
--- a/docs/latest/_sources/api/v11/phys_location.rst.txt
+++ /dev/null
@@ -1,449 +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.
-..
-
-.. _to-api-v11-phys-loc:
-
-Physical Location
-=================
-
-.. _to-api-v11-phys-loc-route:
-
-/api/1.1/phys_locations
-+++++++++++++++++++++++
-
-**GET /api/1.1/phys_locations**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``address`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``city`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``comments`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``email`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``id`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``lastUpdated`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``name`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``phone`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``poc`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``region`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``regionId`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``shortName`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``state`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``zip`` | string | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "region": "Mile High",
- "region": "4",
- "poc": "Jane Doe",
- "lastUpdated": "2014-10-02 08:22:43",
- "name": "Albuquerque",
- "comments": "Albuquerque",
- "phone": "(123) 555-1111",
- "state": "NM",
- "email": "jane.doe@email.com",
- "city": "Albuquerque",
- "zip": "87107",
- "id": "2",
- "address": "123 East 3rd St",
- "shortName": "Albuquerque"
- },
- {
- "region": "Mile High",
- "region": "4",
- "poc": "Jane Doe",
- "lastUpdated": "2014-10-02 08:22:43",
- "name": "Albuquerque",
- "comments": "Albuquerque",
- "phone": "(123) 555-1111",
- "state": "NM",
- "email": "jane.doe@email.com",
- "city": "Albuquerque",
- "zip": "87107",
- "id": "2",
- "address": "123 East 3rd St",
- "shortName": "Albuquerque"
- }
- ]
- }
-
-|
-
-**GET /api/1.1/phys_locations/trimmed.json**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+---------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+=========+================================================+
- |``name`` | string | |
- +----------------------+---------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "name": "Albuquerque"
- },
- {
- "name": "Ashburn"
- }
- ]
- }
-
-|
-
-
-**GET /api/1.1/phys_locations/:id**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------+----------+---------------------------------------------+
- | Name | Required | Description |
- +===========+==========+=============================================+
- | ``id`` | yes | Physical location ID. |
- +-----------+----------+---------------------------------------------+
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``address`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``city`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``comments`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``email`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``id`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``lastUpdated`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``name`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``phone`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``poc`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``region`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``regionId`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``shortName`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``state`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``zip`` | string | |
- +----------------------+--------+------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "region": "Mile High",
- "region": "4",
- "poc": "Jane Doe",
- "lastUpdated": "2014-10-02 08:22:43",
- "name": "Albuquerque",
- "comments": "Albuquerque",
- "phone": "(123) 555-1111",
- "state": "NM",
- "email": "jane.doe@email.com",
- "city": "Albuquerque",
- "zip": "87107",
- "id": "2",
- "address": "123 East 3rd St",
- "shortName": "Albuquerque"
- }
- ]
- }
-
-|
-
-**PUT /api/1.1/phys_locations/:id**
- Update a physical location
-
- Authentication Required: Yes
-
- Role(s) Required: admin or oper
-
- **Request Route Parameters**
-
- +-------------------+----------+------------------------------------------------+
- | Name | Type | Description |
- +===================+==========+================================================+
- | ``id`` | int | Physical location id. |
- +-------------------+----------+------------------------------------------------+
-
- **Request Properties**
-
- +-------------------+----------+------------------------------------------------+
- | Parameter | Required | Description |
- +===================+==========+================================================+
- | ``address`` | yes | Physical location address. |
- +-------------------+----------+------------------------------------------------+
- | ``city`` | yes | Physical location city. |
- +-------------------+----------+------------------------------------------------+
- | ``comments`` | no | Physical location comments. |
- +-------------------+----------+------------------------------------------------+
- | ``email`` | no | Physical location email. |
- +-------------------+----------+------------------------------------------------+
- | ``name`` | yes | Physical location name. |
- +-------------------+----------+------------------------------------------------+
- | ``phone`` | no | Physical location phone. |
- +-------------------+----------+------------------------------------------------+
- | ``poc`` | no | Physical location point of contact. |
- +-------------------+----------+------------------------------------------------+
- | ``regionId`` | no | Physical location region ID. |
- +-------------------+----------+------------------------------------------------+
- | ``shortName`` | yes | Physical location short name. |
- +-------------------+----------+------------------------------------------------+
- | ``state`` | yes | Physical location state. |
- +-------------------+----------+------------------------------------------------+
- | ``zip`` | yes | Physical location zip. |
- +-------------------+----------+------------------------------------------------+
-
- **Request Example** ::
-
- {
- "regionId": "1",
- "poc": "Jane Doesssss",
- "name": "Albuquerque",
- "comments": "Albuquerque",
- "phone": "(123) 555-1111",
- "state": "NM",
- "email": "jane.doe@email.com",
- "city": "Albuquerque",
- "zip": "87107",
- "address": "123 East 9rd St",
- "shortName": "Albuquerque"
- }
-
-|
-
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
- +======================+========+================================================+
- |``address`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``city`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``comments`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``email`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``id`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``lastUpdated`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``name`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``phone`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``poc`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``region`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``regionId`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``shortName`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``state`` | string | |
- +----------------------+--------+------------------------------------------------+
- |``zip`` | string | |
- +----------------------+--------+------------------------------------------------+
-
-
- **Response Example** ::
-
- {
- "alerts": [
- {
- "level": "success",
- "text": "Physical location update was successful."
- }
- ],
- "response": [
- {
- "region": "Mile High",
- "region": "4",
- "poc": "Jane Doe",
- "lastUpdated": "2014-10-02 08:22:43",
- "name": "Albuquerque",
- "comments": "Albuquerque",
- "phone": "(123) 555-1111",
- "state": "NM",
- "email": "jane.doe@email.com",
- "city": "Albuquerque",
- "zip": "87107",
- "id": "2",
- "address": "123 East 3rd St",
- "shortName": "Albuquerque"
- }
- ]
- }
-
-|
-
-
-**POST /api/1.1/regions/:region_name/phys_locations**
- Create physical location.
-
- Authentication Required: Yes
-
- Role(s) Required: admin or oper
-
- region_name: the name of the region to create physical location into.
-
- **Request Route Parameters**
-
- +-----------------+----------+-----------------------------------+
- | Name | Required | Description |
- +=================+==========+===================================+
- | ``region_name`` | yes | The name of the physical location |
- +-----------------+----------+-----------------------------------+
-
- **Request Properties**
-
- +-----------------+----------+---------------------------------------------------+
- | Parameter | Required | Description |
- +=================+==========+===================================================+
- | ``name`` | yes | The name of the location |
- +-----------------+----------+---------------------------------------------------+
- | ``shortName`` | yes | The short name of the location |
- +-----------------+----------+---------------------------------------------------+
- | ``address`` | yes | |
- +-----------------+----------+---------------------------------------------------+
- | ``city`` | yes | |
- +-----------------+----------+---------------------------------------------------+
- | ``state`` | yes | |
- +-----------------+----------+---------------------------------------------------+
- | ``zip`` | yes | |
- +-----------------+----------+---------------------------------------------------+
- | ``phone`` | no | |
- +-----------------+----------+---------------------------------------------------+
- | ``poc`` | no | Point of contact |
- +-----------------+----------+---------------------------------------------------+
- | ``email`` | no | |
- +-----------------+----------+---------------------------------------------------+
- | ``comments`` | no | |
- +-----------------+----------+---------------------------------------------------+
-
- **Request Example** ::
-
- {
- "name" : "my physical location1",
- "shortName" : "myphylocation1",
- "address" : "",
- "city" : "Shanghai",
- "state": "SH",
- "zip": "200000",
- "comments": "this is physical location1"
- }
-
-|
-
- **Response Properties**
-
- +-----------------+--------+---------------------------------------------------+
- | Parameter | Type | Description |
- +=================+========+===================================================+
- | ``id`` | string | The id of the physical location created. |
- +-----------------+--------+---------------------------------------------------+
- | ``name`` | string | The name of the location |
- +-----------------+--------+---------------------------------------------------+
- | ``shortName`` | string | The short name of the location |
- +-----------------+--------+---------------------------------------------------+
- | ``regionName`` | string | The region name the physical location belongs to. |
- +-----------------+--------+---------------------------------------------------+
- | ``regionId`` | string | |
- +-----------------+--------+---------------------------------------------------+
- | ``address`` | string | |
- +-----------------+--------+---------------------------------------------------+
- | ``city`` | string | |
- +-----------------+--------+---------------------------------------------------+
- | ``state`` | string | |
- +-----------------+--------+---------------------------------------------------+
- | ``zip`` | string | |
- +-----------------+--------+---------------------------------------------------+
- | ``phone`` | string | |
- +-----------------+--------+---------------------------------------------------+
- | ``poc`` | string | Point of contact |
- +-----------------+--------+---------------------------------------------------+
- | ``email`` | string | |
- +-----------------+--------+---------------------------------------------------+
- | ``comments`` | string | |
- +-----------------+--------+---------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": {
- 'shortName': 'myphylocati',
- 'regionName': 'myregion1',
- 'name': 'my physical location1',
- 'poc': '',
- 'phone': '',
- 'comments': 'this is physical location1',
- 'state': 'SH',
- 'email': '',
- 'zip': '20000',
- 'region_id': '20',
- 'city': 'Shanghai',
- 'address': '',
- 'id': '200'
- }
- }
-
-|
-
diff --git a/docs/latest/_sources/api/v11/profile.rst.txt b/docs/latest/_sources/api/v11/profile.rst.txt
deleted file mode 100644
index 5c37690..0000000
--- a/docs/latest/_sources/api/v11/profile.rst.txt
+++ /dev/null
@@ -1,129 +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.
-..
-
-.. _to-api-v11-profile:
-
-Profiles
-========
-
-.. _to-api-v11-profiles-route:
-
-/api/1.1/profiles
-+++++++++++++++++
-
-**GET /api/1.1/profiles**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +-----------------+--------+----------------------------------------------------+
- | Parameter | Type | Description |
- +=================+========+====================================================+
- | ``lastUpdated`` | array | The Time / Date this server entry was last updated |
- +-----------------+--------+----------------------------------------------------+
- | ``name`` | string | The name for the profile |
- +-----------------+--------+----------------------------------------------------+
- | ``id`` | string | Primary key |
- +-----------------+--------+----------------------------------------------------+
- | ``description`` | string | The description for the profile |
- +-----------------+--------+----------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "lastUpdated": "2012-10-08 19:34:45",
- "name": "CCR_TOP",
- "id": "8",
- "description": "Content Router for top.foobar.net"
- }
- ]
- }
-
-|
-
-**GET /api/1.1/profiles/trimmed**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +-----------------+--------+----------------------------------------------------+
- | Parameter | Type | Description |
- +=================+========+====================================================+
- | ``name`` | string | The name for the profile |
- +-----------------+--------+----------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "name": "CCR_TOP"
- }
- ]
- }
-
-|
-
-**GET /api/1.1/profiles/:id**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Request Route Parameters**
-
- +-----------------+------------+------------------------------------------------+
- | Parameter | Required | Description |
- +=================+============+================================================+
- | ``id`` | yes | The ID of the profile. |
- +-----------------+------------+------------------------------------------------+
-
- **Response Properties**
-
- +-----------------+--------+----------------------------------------------------+
- | Parameter | Type | Description |
- +=================+========+====================================================+
- | ``lastUpdated`` | array | The Time / Date this server entry was last updated |
- +-----------------+--------+----------------------------------------------------+
- | ``name`` | string | The name for the profile |
- +-----------------+--------+----------------------------------------------------+
- | ``id`` | string | Primary key |
- +-----------------+--------+----------------------------------------------------+
- | ``description`` | string | The description for the profile |
- +-----------------+--------+----------------------------------------------------+
-
- **Response Example** ::
-
- {
- "response": [
- {
- "lastUpdated": "2012-10-08 19:34:45",
- "name": "CCR_TOP",
- "id": "8",
- "description": "Content Router for top.foobar.net"
- }
- ]
- }
-
-|
-
diff --git a/docs/latest/_sources/api/v11/region.rst.txt b/docs/latest/_sources/api/v11/region.rst.txt
deleted file mode 100644
index d521f33..0000000
--- a/docs/latest/_sources/api/v11/region.rst.txt
+++ /dev/null
@@ -1,235 +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.
-..
-
-.. _to-api-v11-region:
-
-Regions
-=======
-
-.. _to-api-v11-regions-route:
-
-/api/1.1/regions
-++++++++++++++++
-
-**GET /api/1.1/regions**
-
- Authentication Required: Yes
-
- Role(s) Required: None
-
- **Response Properties**
-
- +----------------------+--------+------------------------------------------------+
- | Parameter | Type | Description |
... 117079 lines suppressed ...
[trafficcontrol-website] 02/04: HTTPS URLs
Posted by zr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
zrhoffman pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/trafficcontrol-website.git
commit ba4ac972c1fb0435427a376acd2122bc08d99755
Author: Zach Hoffman <zr...@apache.org>
AuthorDate: Mon Sep 28 13:47:36 2020 -0600
HTTPS URLs
---
.htaccess | 6 +++---
index.html | 2 +-
mailing_lists/index.html | 2 +-
releases/index.html | 6 +++---
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/.htaccess b/.htaccess
index 96f52d3..5327330 100644
--- a/.htaccess
+++ b/.htaccess
@@ -1,3 +1,3 @@
-RedirectMatch 301 /docs(.*) http://traffic-control-cdn.readthedocs.io/en$1
-RedirectMatch 301 /licenses(.*) http://www.apache.org/licenses$1
-RedirectMatch 301 /foundation(.*) http://www.apache.org/foundation$1
+RedirectMatch 301 /docs(.*) https://traffic-control-cdn.readthedocs.io/en$1
+RedirectMatch 301 /licenses(.*) https://www.apache.org/licenses$1
+RedirectMatch 301 /foundation(.*) https://www.apache.org/foundation$1
diff --git a/index.html b/index.html
index 0f8e97f..992bbed 100644
--- a/index.html
+++ b/index.html
@@ -54,7 +54,7 @@
Community
</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="http://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
+ <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
<a class="dropdown-item" href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
<a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
<a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
diff --git a/mailing_lists/index.html b/mailing_lists/index.html
index cfcfc6e..8e1b2f7 100644
--- a/mailing_lists/index.html
+++ b/mailing_lists/index.html
@@ -54,7 +54,7 @@
Community
</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="http://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
+ <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
<a class="dropdown-item" href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
<a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
<a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
diff --git a/releases/index.html b/releases/index.html
index d789895..84cd0b9 100644
--- a/releases/index.html
+++ b/releases/index.html
@@ -54,7 +54,7 @@
Community
</a>
<div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="http://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
+ <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
<a class="dropdown-item" href="/contributing">Contributing</a>
<a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
<a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
@@ -103,7 +103,7 @@
<li><a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz.sha512">SHA-512</a></li>
<li><a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz.asc">ASC</a></li>
<li><a href="https://downloads.apache.org/trafficcontrol/KEYS">KEYS</a></li>
- <li><a href="http://trafficcontrol.apache.org/downloads/profiles/4.1.x/">Default Profiles</a></li>
+ <li><a href="https://trafficcontrol.apache.org/downloads/profiles/4.1.x/">Default Profiles</a></li>
</ul>
</p>
<h4>Release Notes</h4>
@@ -197,7 +197,7 @@ gpg: Good signature from "Rawlin Peters (apache signing key) <ra...@apache.org>
<li><a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz.sha512">SHA-512</a></li>
<li><a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz.asc">ASC</a></li>
<li><a href="https://downloads.apache.org/trafficcontrol/KEYS">KEYS</a></li>
- <li><a href="http://trafficcontrol.apache.org/downloads/profiles/4.0.x/">Default Profiles</a></li>
+ <li><a href="https://trafficcontrol.apache.org/downloads/profiles/4.0.x/">Default Profiles</a></li>
</ul>
</p>
<h4>Release Notes</h4>
[trafficcontrol-website] 03/04: Reformat pages
Posted by zr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
zrhoffman pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/trafficcontrol-website.git
commit 248b6be24fa15955a98856c4823b4454eb9df385
Author: Zach Hoffman <zr...@apache.org>
AuthorDate: Mon Sep 28 13:51:17 2020 -0600
Reformat pages
---
index.html | 489 +++++++++++++++--------------
mailing_lists/index.html | 317 ++++++++++---------
releases/index.html | 776 +++++++++++++++++++++++++++++------------------
security/index.html | 267 ++++++++--------
4 files changed, 1057 insertions(+), 792 deletions(-)
diff --git a/index.html b/index.html
index 992bbed..53bb250 100644
--- a/index.html
+++ b/index.html
@@ -1,6 +1,6 @@
<!DOCTYPE html>
<html lang="en">
- <head>
+<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
@@ -8,237 +8,274 @@
<!-- Boostrap -->
<link rel="stylesheet"
- href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
- integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
- crossorigin="anonymous">
+ href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
+ integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
+ crossorigin="anonymous">
<script defer src="https://use.fontawesome.com/releases/v5.0.10/js/all.js"
- integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
- crossorigin="anonymous"></script>
+ integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
+ crossorigin="anonymous"></script>
<link rel="icon" type="image/png" href="/resources/favicon.png">
- </head>
- <body>
- <nav class="navbar navbar-expand-lg navbar-dark bg-dark">
- <a class="navbar-brand" href="#">
- <img id="fluo-img" height="40px" src="./resources/tc_logo_c_only.png" alt="Apache Traffic Control">
- </a>
- <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
- <span class="navbar-toggler-icon"></span>
- </button>
-
- <div class="collapse navbar-collapse" id="navbarSupportedContent">
- <ul class="navbar-nav mr-auto">
- <li class="nav-item active">
- <a class="nav-link" href="#">Home <span class="sr-only">(current)</span></a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="/releases/">Releases</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="docs//latest/index.html">Docs</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="docs/latest/api/index.html">API</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="/security/">Security</a>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Community
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
- <a class="dropdown-item" href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
- <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
- <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
- <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
- <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
+</head>
+<body>
+<nav class="navbar navbar-expand-lg navbar-dark bg-dark">
+ <a class="navbar-brand" href="#">
+ <img id="fluo-img" height="40px" src="./resources/tc_logo_c_only.png" alt="Apache Traffic Control">
+ </a>
+ <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent"
+ aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
+ <span class="navbar-toggler-icon"></span>
+ </button>
+
+ <div class="collapse navbar-collapse" id="navbarSupportedContent">
+ <ul class="navbar-nav mr-auto">
+ <li class="nav-item active">
+ <a class="nav-link" href="#">Home <span class="sr-only">(current)</span></a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="/releases/">Releases</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="docs//latest/index.html">Docs</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="docs/latest/api/index.html">API</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="/security/">Security</a>
+ </li>
+ <li class="nav-item dropdown">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Community
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
+ <a class="dropdown-item"
+ href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
+ <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
+ <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
+ <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
+ <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
+ </div>
+ </li>
+ </ul>
+
+ <ul class="navbar-nav navbar-right">
+
+ <li class="nav-item dropdown">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Apache Software Foundation<span class="caret"></span>
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
+ <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
+ <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
+ <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of
+ Conduct</a>
+ </div>
+ </li>
+ </ul>
+ </div>
+</nav>
+
+<div class="container">
+ <div class="jumbotron" style="text-align: center;">
+ <div class="mx-auto"><img src="./resources/Traffic-Control-Logo-FINAL-Black-Text.png"
+ alt="Apache Traffic Control" height="200px"/></div>
+ <p class="lead">Apache Traffic Control allows you to build a large scale content delivery network using open
+ source. Built around Apache Traffic Server as the caching software, Traffic Control implements all the core
+ functions of a modern CDN.</p>
+ <a style="margin-right: 20px" href="/releases/" class="btn btn-success btn-sm navbar-btn"><i
+ class="fa fa-download fa-lg"></i> Download</a>
+ <a style="margin-right: 20px" href="https://github.com/apache/trafficcontrol" target="_blank"
+ class="btn btn-dark btn-sm navbar-btn"><i class="fab fa-github fa-lg"></i> GitHub</a>
+ <a href="https://twitter.com/trafficctrlcdn" target="_blank" class="btn btn-primary btn-sm navbar-btn"><i
+ class="fab fa-twitter fa-lg"></i> Follow</a>
+ </div> <!-- End Jumbotron -->
+
+ <div class="row">
+ <div class="col">
+ <p class="lead">With Apache Traffic Control, operators can setup a Content Delivery Network to quickly and
+ efficiently deliver content to their users. Traffic Control is a highly distributed, scalable and
+ redundant solution meeting the needs of operators from small to large.
+ </div>
+ </div>
+
+ <h3>News</h3>
+ <div class="row">
+ <div class="col-sm-12">
+ <div class="card">
+ <div class="card-body">
+ <span class="far fa-newspaper fa-7x float-right" style="color: #343a40;"></span>
+ <ul>
+ <li><strong>June 17, 2020</strong> - Apache Traffic Control 4.1.0 Released</li>
+ </ul>
+ <ul>
+ <li><strong>March 26, 2020</strong> - Apache Traffic Control 4.0.0 Released</li>
+ </ul>
+
+
+ </div>
</div>
- </li>
- </ul>
-
- <ul class="navbar-nav navbar-right">
-
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Apache Software Foundation<span class="caret"></span>
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
- <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
- <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
- <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a>
+ </div>
+ </div>
+ <br/>
+
+ <h3>Features</h3>
+ <div class="row">
+
+ <div class="col-sm-12">
+ <div class="card-deck">
+ <div class="card border-light">
+ <span class="fas fa-bolt fa-7x mx-auto" style="color: #343a40; margin-top: 5px;"></span>
+ <div class="card-body">
+ <h5 class="card-title">Reduced Latency</h5>
+ <p class="card-text">Locating caches and content closer to users decreases the round trip time
+ needed to deliver content. </p>
+ </div>
+ </div>
+
+ <div class="card border-light">
+ <span class="fas fa-cloud-download-alt fa-7x mx-auto" style="color:#343a40;"></span>
+ <div class="card-body">
+ <h5 class="card-title">Reduced Bandwidth Costs</h5>
+ <p class="card-text">Caching content in memory and on disk reduces the load on origin servers
+ and across bottleneck links.</p>
+ </div>
+ </div>
+
+ <div class="card border-light">
+ <span class="fas fa-heart fa-7x mx-auto" style="color: #343a40;"></span>
+ <div class="card-body">
+ <h5 class="card-title">Improved Quality of Experience</h5>
+ <p class="card-text">Reducing round trip time and increasing delivery bandwidth improves end
+ user quality of experience</p>
+ </div>
+ </div>
</div>
- </li>
- </ul>
- </div>
- </nav>
-
- <div class="container">
- <div class="jumbotron" style="text-align: center;">
- <div class="mx-auto"><img src="./resources/Traffic-Control-Logo-FINAL-Black-Text.png" alt="Apache Traffic Control" height="200px"/></div>
- <p class="lead">Apache Traffic Control allows you to build a large scale content delivery network using open source. Built around Apache Traffic Server as the caching software, Traffic Control implements all the core functions of a modern CDN.</p>
- <a style="margin-right: 20px" href="/releases/" class="btn btn-success btn-sm navbar-btn"><i class="fa fa-download fa-lg"></i> Download</a>
- <a style="margin-right: 20px" href="https://github.com/apache/trafficcontrol" target="_blank" class="btn btn-dark btn-sm navbar-btn"><i class="fab fa-github fa-lg"></i> GitHub</a>
- <a href="https://twitter.com/trafficctrlcdn" target="_blank" class="btn btn-primary btn-sm navbar-btn"><i class="fab fa-twitter fa-lg"></i> Follow</a>
- </div> <!-- End Jumbotron -->
-
- <div class="row">
- <div class="col">
- <p class="lead">With Apache Traffic Control, operators can setup a Content Delivery Network to quickly and efficiently deliver content to their users. Traffic Control is a highly distributed, scalable and redundant solution meeting the needs of operators from small to large.
- </div>
- </div>
-
- <h3>News</h3>
- <div class="row">
- <div class="col-sm-12">
- <div class="card">
- <div class="card-body">
- <span class="far fa-newspaper fa-7x float-right" style="color: #343a40;"></span>
- <ul><li><strong>June 17, 2020</strong> - Apache Traffic Control 4.1.0 Released</li></ul>
- <ul><li><strong>March 26, 2020</strong> - Apache Traffic Control 4.0.0 Released</li></ul>
-
-
- </div>
- </div>
- </div>
- </div>
- <br/>
-
- <h3>Features</h3>
- <div class="row">
-
- <div class="col-sm-12">
- <div class="card-deck">
- <div class="card border-light">
- <span class="fas fa-bolt fa-7x mx-auto" style="color: #343a40; margin-top: 5px;"></span>
- <div class="card-body">
- <h5 class="card-title">Reduced Latency</h5>
- <p class="card-text">Locating caches and content closer to users decreases the round trip time needed to deliver content. </p>
- </div>
- </div>
-
- <div class="card border-light">
- <span class="fas fa-cloud-download-alt fa-7x mx-auto" style="color:#343a40;"></span>
- <div class="card-body">
- <h5 class="card-title">Reduced Bandwidth Costs</h5>
- <p class="card-text">Caching content in memory and on disk reduces the load on origin servers and across bottleneck links.</p>
- </div>
- </div>
-
- <div class="card border-light">
- <span class="fas fa-heart fa-7x mx-auto" style="color: #343a40;"></span>
- <div class="card-body">
- <h5 class="card-title">Improved Quality of Experience</h5>
- <p class="card-text">Reducing round trip time and increasing delivery bandwidth improves end user quality of experience</p>
- </div>
- </div>
- </div>
- </div>
- </div> <!-- End Features Row -->
- <hr/>
-
- <h4>Modules</h4>
- <div class="row">
- <div class="col-sm-12">
- <div class="card-deck">
- <div class="card border-light">
- <div class="card-body">
- <h4 class="card-title"><a href="docs/latest/overview/traffic_ops.html" style="color: black;">Traffic Ops</a></h4>
- <p class="card-text">Traffic Ops is the RESTful API service for management and monitoring of all servers in the CDN.</p>
- </div>
- </div>
-
- <div class="card border-light">
- <div class="card-body">
- <h4 class="card-title"><a href="docs//latest/overview/traffic_router.html" style="color: black;">Traffic Router</a></h4>
- <p class="card-text">Traffic Router uses DNS and HTTP302 to redirect clients to the closest available cache on the CDN. </p>
- </div>
- </div>
-
- <div class="card border-light">
- <div class="card-body">
- <h4 class="card-title"><a href="docs/latest/overview/traffic_stats.html" style="color: black;">Traffic Stats</a></h4>
- <p class="card-text">Traffic Stats acquires and stores real-time metrics and statistics into an InfluxDB for charting and alerting.</p>
- </div>
- </div>
- </div>
- </div>
- </div>
- <br/>
-
- <!-- Modules Row 2-->
- <div class="row">
- <div class="col-sm-4">
- <div class="card border-light">
- <div class="card-body">
- <h4 class="card-title"><a href="docs/latest/overview/traffic_portal.html" style="color: black;">Traffic Portal</a></h4>
- <p class="card-text">Traffic Portal is the web GUI for managing and monitoring the CDN via the Traffic Ops API.</p>
- </div>
- </div>
- </div>
-
- <div class="col-sm-4">
- <div class="card border-light">
- <div class="card-body">
- <h4 class="card-title"><a href="docs/latest/overview/traffic_monitor.html" style="color: black;">Traffic Monitor</a></h4>
- <p class="card-text">Traffic Monitor uses HTTP to poll the health of caches and provide this information to Traffic Router. </p>
- </div>
- </div>
- </div>
-
- <div class="col-sm-4">
- <div class="card border-light">
- <div class="card-body">
- <h4 class="card-title">Grove</h4>
- <p class="card-text">Grove is an experimental high performance, live-focused HTTP cache written entirely in Go.</p>
- </div>
- </div>
- </div>
- </div>
- <br/>
-
-
-
- <!-- Start Footer -->
- <div class="row">
- <div class="col-sm-12 center-block">
- <footer>
- <hr/>
- <p>
- <a href="https://www.apache.org/foundation/contributing">
- <img src="https://www.apache.org/images/SupportApache-small.png"
- id="asf-logo"
- height="100"
- alt="Apache"
- class="float-left"
- style="margin-right: 15px;"></a>
-
- Copyright © 2020 <a href="https://www.apache.org">The Apache Software Foundation</a>.
- Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
- </p>
- <p>
- Apache®, the names of Apache projects and their logos, and the multicolor feather
- logo are registered trademarks or trademarks of The Apache Software Foundation
- in the United States and/or other countries.
- </p>
- </footer>
</div>
- </div>
+ </div> <!-- End Features Row -->
+ <hr/>
+
+ <h4>Modules</h4>
+ <div class="row">
+ <div class="col-sm-12">
+ <div class="card-deck">
+ <div class="card border-light">
+ <div class="card-body">
+ <h4 class="card-title"><a href="docs/latest/overview/traffic_ops.html" style="color: black;">Traffic
+ Ops</a></h4>
+ <p class="card-text">Traffic Ops is the RESTful API service for management and monitoring of all
+ servers in the CDN.</p>
+ </div>
+ </div>
+
+ <div class="card border-light">
+ <div class="card-body">
+ <h4 class="card-title"><a href="docs//latest/overview/traffic_router.html"
+ style="color: black;">Traffic Router</a></h4>
+ <p class="card-text">Traffic Router uses DNS and HTTP302 to redirect clients to the closest
+ available cache on the CDN. </p>
+ </div>
+ </div>
+
+ <div class="card border-light">
+ <div class="card-body">
+ <h4 class="card-title"><a href="docs/latest/overview/traffic_stats.html" style="color: black;">Traffic
+ Stats</a></h4>
+ <p class="card-text">Traffic Stats acquires and stores real-time metrics and statistics into an
+ InfluxDB for charting and alerting.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ <br/>
+
+ <!-- Modules Row 2-->
+ <div class="row">
+ <div class="col-sm-4">
+ <div class="card border-light">
+ <div class="card-body">
+ <h4 class="card-title"><a href="docs/latest/overview/traffic_portal.html" style="color: black;">Traffic
+ Portal</a></h4>
+ <p class="card-text">Traffic Portal is the web GUI for managing and monitoring the CDN via the
+ Traffic Ops API.</p>
+ </div>
+ </div>
+ </div>
+
+ <div class="col-sm-4">
+ <div class="card border-light">
+ <div class="card-body">
+ <h4 class="card-title"><a href="docs/latest/overview/traffic_monitor.html" style="color: black;">Traffic
+ Monitor</a></h4>
+ <p class="card-text">Traffic Monitor uses HTTP to poll the health of caches and provide this
+ information to Traffic Router. </p>
+ </div>
+ </div>
+ </div>
+
+ <div class="col-sm-4">
+ <div class="card border-light">
+ <div class="card-body">
+ <h4 class="card-title">Grove</h4>
+ <p class="card-text">Grove is an experimental high performance, live-focused HTTP cache written
+ entirely in Go.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ <br/>
+
+
+ <!-- Start Footer -->
+ <div class="row">
+ <div class="col-sm-12 center-block">
+ <footer>
+ <hr/>
+ <p>
+ <a href="https://www.apache.org/foundation/contributing">
+ <img src="https://www.apache.org/images/SupportApache-small.png"
+ id="asf-logo"
+ height="100"
+ alt="Apache"
+ class="float-left"
+ style="margin-right: 15px;"></a>
+
+ Copyright © 2020 <a
+ href="https://www.apache.org">The Apache Software Foundation</a>.
+ Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
+ </p>
+ <p>
+ Apache®, the names of Apache projects and their logos, and the multicolor feather
+ logo are registered trademarks or trademarks of The Apache Software Foundation
+ in the United States and/or other countries.
+ </p>
+ </footer>
+ </div>
</div>
+</div>
- <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo" crossorigin="anonymous"></script>
- <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js" integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ" crossorigin="anonymous"></script>
- <script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js" integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm" crossorigin="anonymous"></script>
- </body>
+<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js"
+ integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo"
+ crossorigin="anonymous"></script>
+<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js"
+ integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ"
+ crossorigin="anonymous"></script>
+<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js"
+ integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm"
+ crossorigin="anonymous"></script>
+</body>
</html>
diff --git a/mailing_lists/index.html b/mailing_lists/index.html
index 8e1b2f7..faa30d3 100644
--- a/mailing_lists/index.html
+++ b/mailing_lists/index.html
@@ -1,164 +1,179 @@
<!DOCTYPE html>
<html lang="en">
- <head>
+<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
+ <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<title>Apache Traffic Control Mailing Lists</title>
<!-- Boostrap -->
<link rel="stylesheet"
- href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
- integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
- crossorigin="anonymous">
+ href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
+ integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
+ crossorigin="anonymous">
<script defer src="https://use.fontawesome.com/releases/v5.0.10/js/all.js"
- integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
- crossorigin="anonymous"></script>
+ integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
+ crossorigin="anonymous"></script>
<link rel="icon" type="image/png" href="/resources/favicon.png">
-
- </head>
- <body>
- <nav class="navbar navbar-expand-lg navbar-dark bg-dark">
- <a class="navbar-brand" href="/">
- <img id="fluo-img" height="40px" src="/resources/tc_logo_c_only.png" alt="Apache Traffic Control">
- </a>
- <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
- <span class="navbar-toggler-icon"></span>
- </button>
-
- <div class="collapse navbar-collapse" id="navbarSupportedContent">
- <ul class="navbar-nav mr-auto">
- <li class="nav-item">
- <a class="nav-link" href="/">Home</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="/releases/">Releases</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/index.html">Docs</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/api/index.html">API</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="#">Security<span class="sr-only">(current)</span></a>
- </li>
- <li class="nav-item dropdown active">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Community
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
- <a class="dropdown-item" href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
- <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
- <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
- <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
- <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
- </div>
- </li>
- </ul>
-
- <ul class="navbar-nav navbar-right">
-
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Apache Software Foundation<span class="caret"></span>
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
- <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
- <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
- <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a>
- </div>
- </li>
- </ul>
- </div>
- </nav>
-
- <div class="container">
-
- <h1>Apache Traffic Control - Mailing Lists</h1>
- <p>The following lists are the preferred methods of communication for the Traffic Control Project. Archives are available at <a href="https://lists.apache.org/list.html?trafficcontrol.apache.org">Apache Mail Archives</a>.</p>
- <p>Subscription instructions and further Apache Foundation-wide mailing lists can be found at <a href="https://apache.org/foundation/mailinglists.html">Apache Mailing Lists</a></p>
-
- <table class="table">
- <thead>
- <tr>
- <th>Name</th>
- <th>Address</th>
- <th>Description</th>
- </tr>
- </thead>
- <tr>
- <td>Users</td>
- <td><a href="mailto:users@trafficcontrol.apache.org">users@trafficcontrol.apache.org</a></td>
- <td>General list for questions and answers, suitable for all users</td>
- </tr>
-
- <tr>
- <td>Development</td>
- <td><a href="mailto:dev@trafficcontrol.apache.org">dev@trafficcontrol.apache.org</a></td>
- <td>Development proposals, discussion and release voting</td>
- </tr>
-
- <tr>
- <td>Security</td>
- <td><a href="mailto:security@trafficcontrol.apache.org">security@trafficcontrol.apache.org</a></td>
- <td>Reporting of security vulnerabilities</td>
- </tr>
-
- <tr>
- <td>Commits</td>
- <td><a href="mailto:commits@trafficcontrol.apache.org">commits@trafficcontrol.apache.org</a></td>
- <td>Archive mailer for all Traffic Control commits</td>
- </tr>
-
- <tr>
- <td>Issues</td>
- <td><a href="mailto:issues@trafficcontrol.apache.org">issues@trafficcontrol.apache.org</a></td>
- <td>Archive mailer for all Traffic Control Github Issues/PullRequests</td>
- </tr>
-
- </table>
-
- <!-- Start Footer -->
- <div class="row">
- <div class="col-sm-12 center-block">
- <footer>
- <hr/>
- <p>
- <a href="https://www.apache.org/foundation/contributing">
- <img src="https://www.apache.org/images/SupportApache-small.png"
- id="asf-logo"
- height="100"
- alt="Apache"
- class="float-left"
- style="margin-right: 15px;"></a>
-
- Copyright © 2020 <a href="https://www.apache.org">The Apache Software Foundation</a>.
- Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
- </p>
- <p>
- Apache®, the names of Apache projects and their logos, and the multicolor feather
- logo are registered trademarks or trademarks of The Apache Software Foundation
- in the United States and/or other countries.
- </p>
- </footer>
+
+</head>
+<body>
+<nav class="navbar navbar-expand-lg navbar-dark bg-dark">
+ <a class="navbar-brand" href="/">
+ <img id="fluo-img" height="40px" src="/resources/tc_logo_c_only.png" alt="Apache Traffic Control">
+ </a>
+ <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent"
+ aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
+ <span class="navbar-toggler-icon"></span>
+ </button>
+
+ <div class="collapse navbar-collapse" id="navbarSupportedContent">
+ <ul class="navbar-nav mr-auto">
+ <li class="nav-item">
+ <a class="nav-link" href="/">Home</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="/releases/">Releases</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/index.html">Docs</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/api/index.html">API</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="#">Security<span class="sr-only">(current)</span></a>
+ </li>
+ <li class="nav-item dropdown active">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Community
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
+ <a class="dropdown-item"
+ href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
+ <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
+ <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
+ <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
+ <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
+ </div>
+ </li>
+ </ul>
+
+ <ul class="navbar-nav navbar-right">
+
+ <li class="nav-item dropdown">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Apache Software Foundation<span class="caret"></span>
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
+ <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
+ <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
+ <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of
+ Conduct</a>
+ </div>
+ </li>
+ </ul>
+ </div>
+</nav>
+
+<div class="container">
+
+ <h1>Apache Traffic Control - Mailing Lists</h1>
+ <p>The following lists are the preferred methods of communication for the Traffic Control Project. Archives are
+ available at <a href="https://lists.apache.org/list.html?trafficcontrol.apache.org">Apache Mail Archives</a>.
+ </p>
+ <p>Subscription instructions and further Apache Foundation-wide mailing lists can be found at <a
+ href="https://apache.org/foundation/mailinglists.html">Apache Mailing Lists</a></p>
+
+ <table class="table">
+ <thead>
+ <tr>
+ <th>Name</th>
+ <th>Address</th>
+ <th>Description</th>
+ </tr>
+ </thead>
+ <tr>
+ <td>Users</td>
+ <td><a href="mailto:users@trafficcontrol.apache.org">users@trafficcontrol.apache.org</a></td>
+ <td>General list for questions and answers, suitable for all users</td>
+ </tr>
+
+ <tr>
+ <td>Development</td>
+ <td><a href="mailto:dev@trafficcontrol.apache.org">dev@trafficcontrol.apache.org</a></td>
+ <td>Development proposals, discussion and release voting</td>
+ </tr>
+
+ <tr>
+ <td>Security</td>
+ <td><a href="mailto:security@trafficcontrol.apache.org">security@trafficcontrol.apache.org</a></td>
+ <td>Reporting of security vulnerabilities</td>
+ </tr>
+
+ <tr>
+ <td>Commits</td>
+ <td><a href="mailto:commits@trafficcontrol.apache.org">commits@trafficcontrol.apache.org</a></td>
+ <td>Archive mailer for all Traffic Control commits</td>
+ </tr>
+
+ <tr>
+ <td>Issues</td>
+ <td><a href="mailto:issues@trafficcontrol.apache.org">issues@trafficcontrol.apache.org</a></td>
+ <td>Archive mailer for all Traffic Control Github Issues/PullRequests</td>
+ </tr>
+
+ </table>
+
+ <!-- Start Footer -->
+ <div class="row">
+ <div class="col-sm-12 center-block">
+ <footer>
+ <hr/>
+ <p>
+ <a href="https://www.apache.org/foundation/contributing">
+ <img src="https://www.apache.org/images/SupportApache-small.png"
+ id="asf-logo"
+ height="100"
+ alt="Apache"
+ class="float-left"
+ style="margin-right: 15px;"></a>
+
+ Copyright © 2020 <a
+ href="https://www.apache.org">The Apache Software Foundation</a>.
+ Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
+ </p>
+ <p>
+ Apache®, the names of Apache projects and their logos, and the multicolor feather
+ logo are registered trademarks or trademarks of The Apache Software Foundation
+ in the United States and/or other countries.
+ </p>
+ </footer>
</div>
- </div>
</div>
-
- <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo" crossorigin="anonymous"></script>
- <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js" integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ" crossorigin="anonymous"></script>
- <script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js" integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm" crossorigin="anonymous"></script>
- </body>
+</div>
+
+<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js"
+ integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo"
+ crossorigin="anonymous"></script>
+<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js"
+ integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ"
+ crossorigin="anonymous"></script>
+<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js"
+ integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm"
+ crossorigin="anonymous"></script>
+</body>
</html>
diff --git a/releases/index.html b/releases/index.html
index 84cd0b9..ba46409 100644
--- a/releases/index.html
+++ b/releases/index.html
@@ -1,160 +1,197 @@
<!DOCTYPE html>
<html lang="en">
- <head>
+<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
+ <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<title>Apache Traffic Control Releases</title>
<!-- Boostrap -->
<link rel="stylesheet"
- href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
- integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
- crossorigin="anonymous">
+ href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
+ integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
+ crossorigin="anonymous">
<script defer src="https://use.fontawesome.com/releases/v5.0.10/js/all.js"
- integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
- crossorigin="anonymous"></script>
+ integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
+ crossorigin="anonymous"></script>
<link rel="icon" type="image/png" href="/resources/favicon.png">
-
- </head>
- <body>
- <nav class="navbar navbar-expand-lg navbar-dark bg-dark">
- <a class="navbar-brand" href="/">
- <img id="fluo-img" height="40px" src="/resources/tc_logo_c_only.png" alt="Apache Traffic Control">
- </a>
- <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
- <span class="navbar-toggler-icon"></span>
- </button>
-
- <div class="collapse navbar-collapse" id="navbarSupportedContent">
- <ul class="navbar-nav mr-auto">
- <li class="nav-item">
- <a class="nav-link" href="/">Home</a>
- </li>
- <li class="nav-item active">
- <a class="nav-link" href="#">Releases<span class="sr-only">(current)</span></a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/index.html">Docs</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/api/index.html">API</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="/security/">Security</a>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Community
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
- <a class="dropdown-item" href="/contributing">Contributing</a>
- <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
- <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
- <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
- <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
- </div>
- </li>
- </ul>
- <ul class="navbar-nav navbar-right">
-
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Apache Software Foundation<span class="caret"></span>
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
- <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
- <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
- <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a>
- </div>
- </li>
- </ul>
- </div>
- </nav>
- <br/>
-
- <div class="container">
+</head>
+<body>
+<nav class="navbar navbar-expand-lg navbar-dark bg-dark">
+ <a class="navbar-brand" href="/">
+ <img id="fluo-img" height="40px" src="/resources/tc_logo_c_only.png" alt="Apache Traffic Control">
+ </a>
+ <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent"
+ aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
+ <span class="navbar-toggler-icon"></span>
+ </button>
+
+ <div class="collapse navbar-collapse" id="navbarSupportedContent">
+ <ul class="navbar-nav mr-auto">
+ <li class="nav-item">
+ <a class="nav-link" href="/">Home</a>
+ </li>
+ <li class="nav-item active">
+ <a class="nav-link" href="#">Releases<span class="sr-only">(current)</span></a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/index.html">Docs</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/api/index.html">API</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="/security/">Security</a>
+ </li>
+ <li class="nav-item dropdown">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Community
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="https://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
+ <a class="dropdown-item" href="/contributing">Contributing</a>
+ <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
+ <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
+ <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
+ <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
+ </div>
+ </li>
+ </ul>
+
+ <ul class="navbar-nav navbar-right">
+
+ <li class="nav-item dropdown">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Apache Software Foundation<span class="caret"></span>
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
+ <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
+ <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
+ <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of
+ Conduct</a>
+ </div>
+ </li>
+ </ul>
+ </div>
+</nav>
+<br/>
+
+<div class="container">
- <h1>Apache Traffic Control - Current Release</h1>
- <br/>
+ <h1>Apache Traffic Control - Current Release</h1>
+ <br/>
- <!-- Release 4.1.0 -->
- <div class="row">
+ <!-- Release 4.1.0 -->
+ <div class="row">
<div class="col-sm-12">
- <div class="card-deck">
- <div class="card">
- <div class="card-body">
- <h3 class="card-title"><b>Apache Traffic Control 4.1.0 - June 17th, 2020</b></h3>
- <p class="card-text">Apache Traffic Control 4.1.0 is available here:
- <ul>
- <li><a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz">Tarball</a></li>
- <li><a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz.sha512">SHA-512</a></li>
- <li><a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz.asc">ASC</a></li>
- <li><a href="https://downloads.apache.org/trafficcontrol/KEYS">KEYS</a></li>
- <li><a href="https://trafficcontrol.apache.org/downloads/profiles/4.1.x/">Default Profiles</a></li>
- </ul>
- </p>
- <h4>Release Notes</h4>
- <h5>New Features</h5>
- <p class="card-text">
- <ul>
- <li>Added support for Let's Encrypt</li>
- <li>Support for ATS Slice plugin in Traffic Ops, including new Delivery Service Raw Remap <code>__RANGE_DIRECTIVE__</code> directive</li>
- <li>Ability to enable EDNS0 client subnet at the delivery service level</li>
- <li>New IPv6 changes:
- <ul>
- <li>Traffic Portal and Traffic Ops now accept IPv6-only servers</li>
- <li>Traffic Monitor now polls caches over IPv6 in addition to IPv4, separating the availability status of each (make sure to update the <code>allow_ip6</code> profile parameter to include the IPv6 addresses of your Traffic Monitors, otherwise they will fail to poll over IPv6 and consider those caches to be unavailable over IPv6)</li>
- <li>Traffic Router will route IPv4 clients to caches with IPv4 availability and route IPv6 clients to caches with IPv6 availability</li>
- </ul>
- </li>
- <li>Traffic Router DNSSEC zone diffing performance enhancement</li>
- <li>Traffic Monitor optimistic quorum</li>
- <li>Traffic Ops API 2.0. This new major API version contains several new routes but does not contain many deprecated routes from API 1.x (which will be available until the ATC 5.0 release). API clients should begin migrating to API 2.0 as soon as possible. For the full lists of new or deprecated routes, please see the <a href="https://github.com/apache/trafficcontrol/blob/master/CHANGELOG.md#410---2020-04-23">changelog</a>.</li>
- <li>Ability to choose the TLS version used for Traffic Ops to make requests to Traffic Vault. Note: the default is now TLSv1.1, which may require configuration changes to Riak. See <a href="https://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_vault.html#tv-admin-enable-tlsv1-1" rel="nofollow">Enabling TLS 1.1</a></li>
- </ul>
- </p>
- <h5>Bug Fixes</h5>
- <p class="card-text">
- <ul>
- <li>This release contains many new bug fixes. For the full list, please see the <a href="https://github.com/apache/trafficcontrol/blob/master/CHANGELOG.md#410---2020-04-23">changelog</a>.</li>
- </ul>
- </p>
- <h5>Removals</h5>
- <p class="card-text">
- <ul>
- <li>The Traffic Ops <code>db/admin.pl</code> script has now been removed. Please use the <code>db/admin</code> binary instead.</li>
- <li>Removed from Traffic Portal the ability to view cache server config files as the contents are no longer reliable through the TO API due to the introduction of <code>atstccfg</code>.</li>
- <li>Traffic Ops Python client no longer supports Python 2.</li>
- </ul>
- </p>
-
+ <div class="card-deck">
+ <div class="card">
+ <div class="card-body">
+ <h3 class="card-title"><b>Apache Traffic Control 4.1.0 - June 17th, 2020</b></h3>
+ <p class="card-text">Apache Traffic Control 4.1.0 is available here:
+ <ul>
+ <li>
+ <a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz">Tarball</a>
+ </li>
+ <li>
+ <a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz.sha512">SHA-512</a>
+ </li>
+ <li>
+ <a href="https://downloads.apache.org/trafficcontrol/4.1.0/apache-trafficcontrol-4.1.0.tar.gz.asc">ASC</a>
+ </li>
+ <li><a href="https://downloads.apache.org/trafficcontrol/KEYS">KEYS</a></li>
+ <li><a href="https://trafficcontrol.apache.org/downloads/profiles/4.1.x/">Default
+ Profiles</a></li>
+ </ul>
+ </p>
+ <h4>Release Notes</h4>
+ <h5>New Features</h5>
+ <p class="card-text">
+ <ul>
+ <li>Added support for Let's Encrypt</li>
+ <li>Support for ATS Slice plugin in Traffic Ops, including new Delivery Service Raw Remap
+ <code>__RANGE_DIRECTIVE__</code> directive
+ </li>
+ <li>Ability to enable EDNS0 client subnet at the delivery service level</li>
+ <li>New IPv6 changes:
+ <ul>
+ <li>Traffic Portal and Traffic Ops now accept IPv6-only servers</li>
+ <li>Traffic Monitor now polls caches over IPv6 in addition to IPv4, separating the
+ availability status of each (make sure to update the <code>allow_ip6</code>
+ profile parameter to include the IPv6 addresses of your Traffic Monitors,
+ otherwise they will fail to poll over IPv6 and consider those caches to be
+ unavailable over IPv6)
+ </li>
+ <li>Traffic Router will route IPv4 clients to caches with IPv4 availability and
+ route IPv6 clients to caches with IPv6 availability
+ </li>
+ </ul>
+ </li>
+ <li>Traffic Router DNSSEC zone diffing performance enhancement</li>
+ <li>Traffic Monitor optimistic quorum</li>
+ <li>Traffic Ops API 2.0. This new major API version contains several new routes but does not
+ contain many deprecated routes from API 1.x (which will be available until the ATC 5.0
+ release). API clients should begin migrating to API 2.0 as soon as possible. For the
+ full lists of new or deprecated routes, please see the <a
+ href="https://github.com/apache/trafficcontrol/blob/master/CHANGELOG.md#410---2020-04-23">changelog</a>.
+ </li>
+ <li>Ability to choose the TLS version used for Traffic Ops to make requests to Traffic
+ Vault. Note: the default is now TLSv1.1, which may require configuration changes to
+ Riak. See <a
+ href="https://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_vault.html#tv-admin-enable-tlsv1-1"
+ rel="nofollow">Enabling TLS 1.1</a></li>
+ </ul>
+ </p>
+ <h5>Bug Fixes</h5>
+ <p class="card-text">
+ <ul>
+ <li>This release contains many new bug fixes. For the full list, please see the <a
+ href="https://github.com/apache/trafficcontrol/blob/master/CHANGELOG.md#410---2020-04-23">changelog</a>.
+ </li>
+ </ul>
+ </p>
+ <h5>Removals</h5>
+ <p class="card-text">
+ <ul>
+ <li>The Traffic Ops <code>db/admin.pl</code> script has now been removed. Please use the
+ <code>db/admin</code> binary instead.
+ </li>
+ <li>Removed from Traffic Portal the ability to view cache server config files as the
+ contents are no longer reliable through the TO API due to the introduction of <code>atstccfg</code>.
+ </li>
+ <li>Traffic Ops Python client no longer supports Python 2.</li>
+ </ul>
+ </p>
+
- </div>
+ </div>
+ </div>
</div>
- </div>
</div>
- </div>
+ </div>
- <br/>
- <h2>Signing Keys</h2>
- <p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures.</p>
+ <br/>
+ <h2>Signing Keys</h2>
+ <p>It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures.</p>
- <p>The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the `ASC` signature file for the relevant distribution. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using:
+ <p>The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the `ASC` signature file
+ for the relevant distribution. Make sure you get these files from the main distribution directory, rather than
+ from a mirror. Then verify the signatures using:
-<pre style="background-color: #C0C0C0; padding: 0px 20px 20px 20px;"><code>
+ <pre style="background-color: #C0C0C0; padding: 0px 20px 20px 20px;"><code>
% pgpk -a KEYS % pgpv apache-trafficcontrol-4.1.0.tar.gz.asc
</code>
or
@@ -169,175 +206,334 @@ or
</code> </pre>
-<pre style="background-color: #C0C0C0; padding: 0px 20px 20px 20px;"><code>
+ <pre style="background-color: #C0C0C0; padding: 0px 20px 20px 20px;"><code>
$ gpg --verify apache-trafficcontrol-4.1.0.tar.gz.asc apache-trafficcontrol-4.1.0.tar.gz
gpg: Signature made Tue Feb 11 09:38:30 2020 MST
gpg: using RSA key BF4A8D7307B8EEC7BFB4D8CB8A0712500C70C06E
gpg: Good signature from "Rawlin Peters (apache signing key) <ra...@apache.org>" [ultimate]
</code></pre>
- </p>
+ </p>
- <p>Additionally, you should verify the SHA signature on the files. A unix program called `sha` or `shasum` is included in many unix distributions. It is also available as part of GNU Textutils. An MD5 signature (deprecated) consists of 32 hex characters, and a SHA512 signature consists of 128 hex characters. Ensure your generated signature string matches the signature string published in the files above.
- </p>
+ <p>Additionally, you should verify the SHA signature on the files. A unix program called `sha` or `shasum` is
+ included in many unix distributions. It is also available as part of GNU Textutils. An MD5 signature
+ (deprecated) consists of 32 hex characters, and a SHA512 signature consists of 128 hex characters. Ensure your
+ generated signature string matches the signature string published in the files above.
+ </p>
- <br/>
- <h2>Past Releases</h2>
+ <br/>
+ <h2>Past Releases</h2>
- <!-- Release 4.0.0 -->
- <div class="row">
+ <!-- Release 4.0.0 -->
+ <div class="row">
<div class="col-sm-12">
- <div class="card-deck">
- <div class="card">
- <div class="card-body">
- <h3 class="card-title"><b>Apache Traffic Control 4.0.0 - March 26th, 2020</b></h3>
- <p class="card-text">Apache Traffic Control 4.0.0 is available here:
- <ul>
- <li><a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz">Tarball</a></li>
- <li><a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz.sha512">SHA-512</a></li>
- <li><a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz.asc">ASC</a></li>
- <li><a href="https://downloads.apache.org/trafficcontrol/KEYS">KEYS</a></li>
- <li><a href="https://trafficcontrol.apache.org/downloads/profiles/4.0.x/">Default Profiles</a></li>
- </ul>
- </p>
- <h4>Release Notes</h4>
- <h5>Traffic Ops</h5>
- <p class="card-text">
- <ul>
- <li><strong>Server Capabilities</strong>: server capabilities can now be created and assigned to servers. Delivery services can now <em>require</em> certain server capabilities, and servers that lack the required capabilities will not serve those delivery services. As as an example, by default, <code>MID</code> caches will serve all delivery services in a given CDN, but this feature can be used to allow a only a subset of <code>MID</code> caches to serve certain deliv [...]
- <li><strong>Certificate deletion upon delivery service deletion</strong>: Snapshotting the CRConfig now deletes HTTPS certificates in Riak for delivery services which have been deleted in Traffic Ops.</li>
- <li><strong>SSO login using OAuth</strong>: Traffic Ops now provides the ability to login using an OAuth provider, and this functionality is now integrated in Traffic Portal. A field is added to cdn.conf to configure whitelisted URLs for Json Key Set URL returned from OAuth provider. Added fields to traffic_portal_properties.json to configure SSO through OAuth for Traffic Portal.</li>
- <li><strong>API rewrite from Perl to Go</strong>: A large number of API endpoints were rewritten from Perl to Go</li>
- <li><strong>API Routing Blacklist</strong>: via the <code>routing_blacklist</code> field in <code>cdn.conf</code>, enable certain whitelisted Go routes to be handled by Perl instead (via the <code>perl_routes</code> list) in case a regression is found in the Go handler, and explicitly disable any routes via the <code>disabled_routes</code> list. Requests to disabled routes are immediately given a 503 response. Both fields are lists of Route IDs, and route information [...]
- <li><strong>Regional Geo-blocking for steering delivery services</strong>: Regional Geo-blocking is now supported for steering-based delivery services</li>
- <li>Added pagination support to some Traffic Ops endpoints via three new query parameters, limit and offset/page</li>
- <li>Traffic Ops now supports a "sortOrder" query parameter on some endpoints to return API responses in descending order</li>
- <li>Traffic Ops now uses a consistent format for audit logs across all Go endpoints</li>
- <li>Added an optional SMTP server configuration to the TO configuration file, api now has ability to send emails</li>
- <li>To support reusing a single riak cluster connection, an optional parameter is added to riak.conf: "HealthCheckInterval". This options takes a 'Duration' value (ie: 10s, 5m) which affects how often the riak cluster is health checked. Default is currently set to: "HealthCheckInterval": "5s".</li>
- <li>Fixed a regression where the <code>Expires</code> cookie header was not being set properly in responses. Also, added the <code>Max-Age</code> cookie header in responses.</li>
- <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3497">#3497</a>: TO API clients that don't specify the latest minor version will overwrite/default any fields introduced in later versions</li>
- <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3587">#3587</a>: Fixed Traffic Ops Golang reverse proxy and Riak logs to be consistent with the format of other error logs.</li>
- <li>Database migrations have been collapsed. Rollbacks to 3.1 and earlier migrations are no longer possible. As always, backup your database before upgrading.</li>
- </ul>
- </p>
- <h6>Deprecations</h6>
- <p class="card-text">
- <ul>
- <li>The TO API <code>/cachegroup_fallbacks</code> endpoint is now deprecated. That functionality was added to the <code>/cachegroups</code> API.</li>
- <li>The <code>db/admin.pl</code> script is now deprecated. There is a new Go <code>db/admin</code> binary to replace the Perl db/admin.pl script, which will be removed in a future release. The new db/admin binary is essentially a drop-in replacement for db/admin.pl since it supports all of the same commands and options; therefore, it should be used in place of db/admin.pl for all the same tasks.</li>
- </ul>
- </p>
- <h6>Breaking Changes</h6>
- <p class="card-text">
- <ul>
- <li>The deprecated Traffic Ops UI has been removed in favor of the Traffic Portal UI</li>
- <li>The location of the Traffic Ops <code>influxdb.conf</code> config file has changed from <code>traffic_ops/app/conf/production/influxdb.conf</code> to <code>traffic_ops/app/conf/influxdb.conf</code>. Please move any existing <code>influxdb.conf</code> to the new location.</li>
- <li>The <code>/api/1.1/osversions</code> endpoint (used for ISO generation) now expects the Perl <code>osversions.cfg</code> configuration file to be JSON. Added a <code>traffic_ops/app/bin/osversions-convert.pl</code> script to convert the <code>osversions.cfg</code> file from Perl to JSON as part of the <code>/osversions</code> endpoint rewrite.</li>
- <li>traffic_ops/app/bin/checks/ToDnssecRefresh.pl now requires "user" and "pass" parameters of an operations-level user! Update your scripts accordingly! This was necessary to move to an API endpoint with proper authentication, which may be safely exposed.</li>
- </ul>
- </p>
- <h5>Traffic Router</h5>
- <p class="card-text">
- <ul>
- <li><strong>Consistent Hash Query Parameters</strong>: Traffic Ops now allows HTTP delivery services to have a set of query parameter keys to be retained for consistent hash generation by Traffic Router. This should be used for query parameters that produce unique content from the origin. For example, if the paths <code>/foo?a=1</code> and <code>/foo?a=2</code> each return unique content, you should add <code>a</code> to the list of consistent hash query parameters fo [...]
- <li><strong>Client Steering Forced Diversity</strong>: force Traffic Router to return more unique edge caches in CLIENT_STEERING results instead of the default behavior which can sometimes return a result of multiple targets using the same edge cache. In the case of edge cache failures, this feature will give clients a chance to retry a different edge cache. This can be enabled with the new <code>client.steering.forced.diversity</code> Traffic Router profile parameter.</li>
- <li><strong>Tunable bounded queue</strong> to support DNS request processing.</li>
- <li><strong>Default Certificate</strong>: TR now generates a self-signed certificate at startup and uses it as the default TLS cert. The default certificate is used whenever a client attempts an SSL handshake for an SNI host which does not match any of the other certificates.</li>
- <li><strong>TLS certificate validation</strong> on certificates imported from Traffic Ops:
- <ul>
- <li>validates modulus of private and public keys</li>
- <li>validates current timestamp falls within the certificate date bracket</li>
- <li>validates certificate subjects against the DS URL</li>
- </ul>
- </li>
- <li>Fixed a bug which would cause <code>REFUSED</code> DNS answers if the zone priming execution did not complete within the configured <code>zonemanager.init.timeout</code> period.</li>
- <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/2821">#2821</a>: Traffic Router may choose wrong certificate when SNI names overlap</li>
- <li>Modified Traffic Router logging format to include an additional field for DNS log entries, namely <code>rhi</code>. This defaults to '-' and is only used when EDNS0 client subnet extensions are enabled and a client subnet is present in the request. When enabled and a subnet is present, the subnet appears in the <code>chi</code> field and the resolver address is in the <code>rhi</code> field.</li>
- <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3476">#3476</a>: Traffic Router returns partial result for CLIENT_STEERING Delivery Services when Regional Geoblocking or Anonymous Blocking is enabled.</li>
- <li>Modified Traffic Router API to be available via HTTPS.</li>
- </ul>
- </p>
- <h5>Traffic Portal</h5>
- <p class="card-text">
- <ul>
- <li>Added a context menu in place of the "Actions" column from the following tables in Traffic Portal: cache group tables, CDN tables, delivery service tables, parameter tables, profile tables, server tables.</li>
- <li>Removed the need to specify line breaks using <code>__RETURN__</code> in delivery service edge/mid header rewrite rules, regex remap expressions, raw remap text and traffic router additional request/response headers.</li>
- <li>Provided the ability to clone delivery service assignments from one cache to another cache of the same type. Issue <a href="https://github.com/apache/trafficcontrol/issues/2963">#2963</a>.</li>
- <li>Delivery service table columns can now be rearranged and their visibility toggled on/off as desired by the user. Hidden table columns are excluded from the table search. These settings are persisted in the browser.</li>
- <li>Server table columns can now be rearranged and their visibility toggled on/off as desired by the user. Hidden table columns are excluded from the table search. These settings are persisted in the browser.</li>
- <li>All tables now include a 'CSV' link to enable the export of table data in CSV format.</li>
- <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3275">#3275</a>: Improved the snapshot diff performance and experience.</li>
- <li>Disabled TLSv1</li>
- <li>The "Clone Delivery Service Assignments" menu item is now hidden on a cache when the cache has zero delivery service assignments to clone.</li>
- <li>Users with a specified role now have the ability to mark any delivery service request as complete.</li>
- <li>Improved <a href="https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/blueprints/profile-param-compare-manage.md">profile comparison view in Traffic Portal</a>.</li>
- </ul>
- </p>
- <h5>ORT</h5>
- <p class="card-text">
- <ul>
- <li><strong>Cache-side ATS config generation</strong>: Added cache-side config generator, <code>atstccfg</code>, installed with ORT. Includes all configs. Includes a plugin system.</li>
- <li>Fixed ATS config generation to omit regex remap, header rewrite, URL Sig, and URI Signing files for delivery services not assigned to that server.</li>
- <li>Changed traffic_ops_ort.pl so that hdr_rw-.config files are compared with strict ordering and line duplication when detecting configuration changes.</li>
- <li>Fix to traffic_ops_ort.pl to strip specific comment lines before checking if a file has changed. Also promoted a changed file message from DEBUG to ERROR for report mode.</li>
- <li><strong>ANYMAP override</strong>: in traffic_ops_ort.pl added the ability to handle ##OVERRIDE## delivery service ANY_MAP raw remap text to replace and comment out a base delivery service remap rules. Note: this is a temporary feature and may be replaced in the future.</li>
- </ul>
- </p>
- <h5>Traffic Monitor</h5>
- <p class="card-text">
- <ul>
- <li>Traffic Monitor now has "gbps" calculated stat, allowing operators to monitor bandwidth in Gbps.</li>
- <li>Added monitoring.json snapshotting. This stores the monitoring json in the same TO database table as the crconfig snapshot. Snapshotting is now required in order to push out monitoring changes.</li>
- <li>UI updated to support HTTP or HTTPS traffic.</li>
- <li>health/stat time now includes full body download (like prior TM <=2.1 version)</li>
- <li>Issue <a href="https://github.com/apache/trafficcontrol/pull/3605">#3605</a>: Fixed Traffic Monitor custom ports in health polling URL.</li>
- <li>Issue <a href="https://github.com/apache/trafficcontrol/pull/3646">#3646</a>: Fixed Traffic Monitor Thresholds.</li>
- </ul>
- </p>
-
+ <div class="card-deck">
+ <div class="card">
+ <div class="card-body">
+ <h3 class="card-title"><b>Apache Traffic Control 4.0.0 - March 26th, 2020</b></h3>
+ <p class="card-text">Apache Traffic Control 4.0.0 is available here:
+ <ul>
+ <li>
+ <a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz">Tarball</a>
+ </li>
+ <li>
+ <a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz.sha512">SHA-512</a>
+ </li>
+ <li>
+ <a href="https://downloads.apache.org/trafficcontrol/4.0.0/apache-trafficcontrol-4.0.0.tar.gz.asc">ASC</a>
+ </li>
+ <li><a href="https://downloads.apache.org/trafficcontrol/KEYS">KEYS</a></li>
+ <li><a href="https://trafficcontrol.apache.org/downloads/profiles/4.0.x/">Default
+ Profiles</a></li>
+ </ul>
+ </p>
+ <h4>Release Notes</h4>
+ <h5>Traffic Ops</h5>
+ <p class="card-text">
+ <ul>
+ <li><strong>Server Capabilities</strong>: server capabilities can now be created and
+ assigned to servers. Delivery services can now <em>require</em> certain server
+ capabilities, and servers that lack the required capabilities will not serve those
+ delivery services. As as an example, by default, <code>MID</code> caches will serve all
+ delivery services in a given CDN, but this feature can be used to allow a only a subset
+ of <code>MID</code> caches to serve certain delivery services (based on the server
+ capabilities assigned to the <code>MID</code> caches and required by the delivery
+ services). See the <a
+ href="https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/blueprints/server-capabilitites.md">blueprint</a>
+ </li>
+ <li><strong>Certificate deletion upon delivery service deletion</strong>: Snapshotting the
+ CRConfig now deletes HTTPS certificates in Riak for delivery services which have been
+ deleted in Traffic Ops.
+ </li>
+ <li><strong>SSO login using OAuth</strong>: Traffic Ops now provides the ability to login
+ using an OAuth provider, and this functionality is now integrated in Traffic Portal. A
+ field is added to cdn.conf to configure whitelisted URLs for Json Key Set URL returned
+ from OAuth provider. Added fields to traffic_portal_properties.json to configure SSO
+ through OAuth for Traffic Portal.
+ </li>
+ <li><strong>API rewrite from Perl to Go</strong>: A large number of API endpoints were
+ rewritten from Perl to Go
+ </li>
+ <li><strong>API Routing Blacklist</strong>: via the <code>routing_blacklist</code> field in
+ <code>cdn.conf</code>, enable certain whitelisted Go routes to be handled by Perl
+ instead (via the <code>perl_routes</code> list) in case a regression is found in the Go
+ handler, and explicitly disable any routes via the <code>disabled_routes</code> list.
+ Requests to disabled routes are immediately given a 503 response. Both fields are lists
+ of Route IDs, and route information (ID, version, method, path, and whether or not it
+ can bypass to Perl) can be found by running <code>./traffic_ops_golang
+ --api-routes</code>. To disable a route or have it bypassed to Perl, find its Route
+ ID using the previous command and put it in the <code>disabled_routes</code> or <code>perl_routes</code>
+ list, respectively.
+ </li>
+ <li><strong>Regional Geo-blocking for steering delivery services</strong>: Regional
+ Geo-blocking is now supported for steering-based delivery services
+ </li>
+ <li>Added pagination support to some Traffic Ops endpoints via three new query parameters,
+ limit and offset/page
+ </li>
+ <li>Traffic Ops now supports a "sortOrder" query parameter on some endpoints to return API
+ responses in descending order
+ </li>
+ <li>Traffic Ops now uses a consistent format for audit logs across all Go endpoints</li>
+ <li>Added an optional SMTP server configuration to the TO configuration file, api now has
+ ability to send emails
+ </li>
+ <li>To support reusing a single riak cluster connection, an optional parameter is added to
+ riak.conf: "HealthCheckInterval". This options takes a 'Duration' value (ie: 10s, 5m)
+ which affects how often the riak cluster is health checked. Default is currently set to:
+ "HealthCheckInterval": "5s".
+ </li>
+ <li>Fixed a regression where the <code>Expires</code> cookie header was not being set
+ properly in responses. Also, added the <code>Max-Age</code> cookie header in responses.
+ </li>
+ <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3497">#3497</a>: TO
+ API clients that don't specify the latest minor version will overwrite/default any
+ fields introduced in later versions
+ </li>
+ <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3587">#3587</a>:
+ Fixed Traffic Ops Golang reverse proxy and Riak logs to be consistent with the format of
+ other error logs.
+ </li>
+ <li>Database migrations have been collapsed. Rollbacks to 3.1 and earlier migrations are no
+ longer possible. As always, backup your database before upgrading.
+ </li>
+ </ul>
+ </p>
+ <h6>Deprecations</h6>
+ <p class="card-text">
+ <ul>
+ <li>The TO API <code>/cachegroup_fallbacks</code> endpoint is now deprecated. That
+ functionality was added to the <code>/cachegroups</code> API.
+ </li>
+ <li>The <code>db/admin.pl</code> script is now deprecated. There is a new Go
+ <code>db/admin</code> binary to replace the Perl db/admin.pl script, which will be
+ removed in a future release. The new db/admin binary is essentially a drop-in
+ replacement for db/admin.pl since it supports all of the same commands and options;
+ therefore, it should be used in place of db/admin.pl for all the same tasks.
+ </li>
+ </ul>
+ </p>
+ <h6>Breaking Changes</h6>
+ <p class="card-text">
+ <ul>
+ <li>The deprecated Traffic Ops UI has been removed in favor of the Traffic Portal UI</li>
+ <li>The location of the Traffic Ops <code>influxdb.conf</code> config file has changed from
+ <code>traffic_ops/app/conf/production/influxdb.conf</code> to <code>traffic_ops/app/conf/influxdb.conf</code>.
+ Please move any existing <code>influxdb.conf</code> to the new location.
+ </li>
+ <li>The <code>/api/1.1/osversions</code> endpoint (used for ISO generation) now expects the
+ Perl <code>osversions.cfg</code> configuration file to be JSON. Added a <code>traffic_ops/app/bin/osversions-convert.pl</code>
+ script to convert the <code>osversions.cfg</code> file from Perl to JSON as part of the
+ <code>/osversions</code> endpoint rewrite.
+ </li>
+ <li>traffic_ops/app/bin/checks/ToDnssecRefresh.pl now requires "user" and "pass" parameters
+ of an operations-level user! Update your scripts accordingly! This was necessary to move
+ to an API endpoint with proper authentication, which may be safely exposed.
+ </li>
+ </ul>
+ </p>
+ <h5>Traffic Router</h5>
+ <p class="card-text">
+ <ul>
+ <li><strong>Consistent Hash Query Parameters</strong>: Traffic Ops now allows HTTP delivery
+ services to have a set of query parameter keys to be retained for consistent hash
+ generation by Traffic Router. This should be used for query parameters that produce
+ unique content from the origin. For example, if the paths <code>/foo?a=1</code> and
+ <code>/foo?a=2</code> each return unique content, you should add <code>a</code> to the
+ list of consistent hash query parameters for that delivery service. This allows clients
+ to be routed to edges for that content more efficiently.
+ </li>
+ <li><strong>Client Steering Forced Diversity</strong>: force Traffic Router to return more
+ unique edge caches in CLIENT_STEERING results instead of the default behavior which can
+ sometimes return a result of multiple targets using the same edge cache. In the case of
+ edge cache failures, this feature will give clients a chance to retry a different edge
+ cache. This can be enabled with the new <code>client.steering.forced.diversity</code>
+ Traffic Router profile parameter.
+ </li>
+ <li><strong>Tunable bounded queue</strong> to support DNS request processing.</li>
+ <li><strong>Default Certificate</strong>: TR now generates a self-signed certificate at
+ startup and uses it as the default TLS cert. The default certificate is used whenever a
+ client attempts an SSL handshake for an SNI host which does not match any of the other
+ certificates.
+ </li>
+ <li><strong>TLS certificate validation</strong> on certificates imported from Traffic Ops:
+ <ul>
+ <li>validates modulus of private and public keys</li>
+ <li>validates current timestamp falls within the certificate date bracket</li>
+ <li>validates certificate subjects against the DS URL</li>
+ </ul>
+ </li>
+ <li>Fixed a bug which would cause <code>REFUSED</code> DNS answers if the zone priming
+ execution did not complete within the configured <code>zonemanager.init.timeout</code>
+ period.
+ </li>
+ <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/2821">#2821</a>:
+ Traffic Router may choose wrong certificate when SNI names overlap
+ </li>
+ <li>Modified Traffic Router logging format to include an additional field for DNS log
+ entries, namely <code>rhi</code>. This defaults to '-' and is only used when EDNS0
+ client subnet extensions are enabled and a client subnet is present in the request. When
+ enabled and a subnet is present, the subnet appears in the <code>chi</code> field and
+ the resolver address is in the <code>rhi</code> field.
+ </li>
+ <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3476">#3476</a>:
+ Traffic Router returns partial result for CLIENT_STEERING Delivery Services when
+ Regional Geoblocking or Anonymous Blocking is enabled.
+ </li>
+ <li>Modified Traffic Router API to be available via HTTPS.</li>
+ </ul>
+ </p>
+ <h5>Traffic Portal</h5>
+ <p class="card-text">
+ <ul>
+ <li>Added a context menu in place of the "Actions" column from the following tables in
+ Traffic Portal: cache group tables, CDN tables, delivery service tables, parameter
+ tables, profile tables, server tables.
+ </li>
+ <li>Removed the need to specify line breaks using <code>__RETURN__</code> in delivery
+ service edge/mid header rewrite rules, regex remap expressions, raw remap text and
+ traffic router additional request/response headers.
+ </li>
+ <li>Provided the ability to clone delivery service assignments from one cache to another
+ cache of the same type. Issue <a
+ href="https://github.com/apache/trafficcontrol/issues/2963">#2963</a>.
+ </li>
+ <li>Delivery service table columns can now be rearranged and their visibility toggled on/off
+ as desired by the user. Hidden table columns are excluded from the table search. These
+ settings are persisted in the browser.
+ </li>
+ <li>Server table columns can now be rearranged and their visibility toggled on/off as
+ desired by the user. Hidden table columns are excluded from the table search. These
+ settings are persisted in the browser.
+ </li>
+ <li>All tables now include a 'CSV' link to enable the export of table data in CSV format.
+ </li>
+ <li>Fixed issue <a href="https://github.com/apache/trafficcontrol/issues/3275">#3275</a>:
+ Improved the snapshot diff performance and experience.
+ </li>
+ <li>Disabled TLSv1</li>
+ <li>The "Clone Delivery Service Assignments" menu item is now hidden on a cache when the
+ cache has zero delivery service assignments to clone.
+ </li>
+ <li>Users with a specified role now have the ability to mark any delivery service request as
+ complete.
+ </li>
+ <li>Improved <a
+ href="https://github.com/apache/trafficcontrol/blob/RELEASE-4.0.0/blueprints/profile-param-compare-manage.md">profile
+ comparison view in Traffic Portal</a>.
+ </li>
+ </ul>
+ </p>
+ <h5>ORT</h5>
+ <p class="card-text">
+ <ul>
+ <li><strong>Cache-side ATS config generation</strong>: Added cache-side config generator,
+ <code>atstccfg</code>, installed with ORT. Includes all configs. Includes a plugin
+ system.
+ </li>
+ <li>Fixed ATS config generation to omit regex remap, header rewrite, URL Sig, and URI
+ Signing files for delivery services not assigned to that server.
+ </li>
+ <li>Changed traffic_ops_ort.pl so that hdr_rw-.config files are compared with strict
+ ordering and line duplication when detecting configuration changes.
+ </li>
+ <li>Fix to traffic_ops_ort.pl to strip specific comment lines before checking if a file has
+ changed. Also promoted a changed file message from DEBUG to ERROR for report mode.
+ </li>
+ <li><strong>ANYMAP override</strong>: in traffic_ops_ort.pl added the ability to handle
+ ##OVERRIDE## delivery service ANY_MAP raw remap text to replace and comment out a base
+ delivery service remap rules. Note: this is a temporary feature and may be replaced in
+ the future.
+ </li>
+ </ul>
+ </p>
+ <h5>Traffic Monitor</h5>
+ <p class="card-text">
+ <ul>
+ <li>Traffic Monitor now has "gbps" calculated stat, allowing operators to monitor bandwidth
+ in Gbps.
+ </li>
+ <li>Added monitoring.json snapshotting. This stores the monitoring json in the same TO
+ database table as the crconfig snapshot. Snapshotting is now required in order to push
+ out monitoring changes.
+ </li>
+ <li>UI updated to support HTTP or HTTPS traffic.</li>
+ <li>health/stat time now includes full body download (like prior TM <=2.1 version)</li>
+ <li>Issue <a href="https://github.com/apache/trafficcontrol/pull/3605">#3605</a>: Fixed
+ Traffic Monitor custom ports in health polling URL.
+ </li>
+ <li>Issue <a href="https://github.com/apache/trafficcontrol/pull/3646">#3646</a>: Fixed
+ Traffic Monitor Thresholds.
+ </li>
+ </ul>
+ </p>
+
- </div>
+ </div>
+ </div>
</div>
- </div>
</div>
- </div>
+ </div>
+
+ <br/>
- <br/>
-
-
-
-
- <!-- Start Footer -->
- <div class="row">
- <div class="col-sm-12 center-block">
- <footer>
- <hr/>
- <p>
- <a href="https://www.apache.org/foundation/contributing">
- <img src="https://www.apache.org/images/SupportApache-small.png"
- id="asf-logo"
- height="100"
- alt="Apache"
- class="float-left"
- style="margin-right: 15px;"></a>
+ <!-- Start Footer -->
+ <div class="row">
+ <div class="col-sm-12 center-block">
+ <footer>
+ <hr/>
+ <p>
+ <a href="https://www.apache.org/foundation/contributing">
+ <img src="https://www.apache.org/images/SupportApache-small.png"
+ id="asf-logo"
+ height="100"
+ alt="Apache"
+ class="float-left"
+ style="margin-right: 15px;"></a>
- Copyright © 2020 <a href="https://www.apache.org">The Apache Software Foundation</a>.
- Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
- </p>
- <p>
- Apache®, the names of Apache projects and their logos, and the multicolor feather
- logo are registered trademarks or trademarks of The Apache Software Foundation
- in the United States and/or other countries.
- </p>
- </footer>
+ Copyright © 2020 <a
+ href="https://www.apache.org">The Apache Software Foundation</a>.
+ Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
+ </p>
+ <p>
+ Apache®, the names of Apache projects and their logos, and the multicolor feather
+ logo are registered trademarks or trademarks of The Apache Software Foundation
+ in the United States and/or other countries.
+ </p>
+ </footer>
</div>
- </div>
</div>
-
- <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo" crossorigin="anonymous"></script>
- <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js" integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ" crossorigin="anonymous"></script>
- <script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js" integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm" crossorigin="anonymous"></script>
- </body>
+</div>
+
+<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js"
+ integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo"
+ crossorigin="anonymous"></script>
+<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js"
+ integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ"
+ crossorigin="anonymous"></script>
+<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js"
+ integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm"
+ crossorigin="anonymous"></script>
+</body>
</html>
diff --git a/security/index.html b/security/index.html
index 4371fbe..6b67033 100644
--- a/security/index.html
+++ b/security/index.html
@@ -1,144 +1,161 @@
<!DOCTYPE html>
<html lang="en">
- <head>
+<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
- <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
+ <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<title>Apache Traffic Control Releases</title>
<!-- Boostrap -->
<link rel="stylesheet"
- href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
- integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
- crossorigin="anonymous">
+ href="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/css/bootstrap.min.css"
+ integrity="sha384-9gVQ4dYFwwWSjIDZnLEWnxCjeSWFphJiwGPXr1jddIhOegiu1FwO5qRGvFXOdJZ4"
+ crossorigin="anonymous">
<script defer src="https://use.fontawesome.com/releases/v5.0.10/js/all.js"
- integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
- crossorigin="anonymous"></script>
+ integrity="sha384-slN8GvtUJGnv6ca26v8EzVaR9DC58QEwsIk9q1QXdCU8Yu8ck/tL/5szYlBbqmS+"
+ crossorigin="anonymous"></script>
<link rel="icon" type="image/png" href="/resources/favicon.png">
-
- </head>
- <body>
- <nav class="navbar navbar-expand-lg navbar-dark bg-dark">
- <a class="navbar-brand" href="/">
- <img id="fluo-img" height="40px" src="/resources/tc_logo_c_only.png" alt="Apache Traffic Control">
- </a>
- <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent" aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
- <span class="navbar-toggler-icon"></span>
- </button>
-
- <div class="collapse navbar-collapse" id="navbarSupportedContent">
- <ul class="navbar-nav mr-auto">
- <li class="nav-item">
- <a class="nav-link" href="/">Home</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="/releases/">Releases</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/index.html">Docs</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/api/index.html">API</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
- </li>
- <li class="nav-item">
- <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
- </li>
- <li class="nav-item active">
- <a class="nav-link" href="#">Security<span class="sr-only">(current)</span></a>
- </li>
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Community
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="http://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
- <a class="dropdown-item" href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
- <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
- <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
- <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
- <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
- </div>
- </li>
- </ul>
- <ul class="navbar-nav navbar-right">
-
- <li class="nav-item dropdown">
- <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown" aria-haspopup="true" aria-expanded="false">
- Apache Software Foundation<span class="caret"></span>
- </a>
- <div class="dropdown-menu" aria-labelledby="navbarDropdown">
- <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
- <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
- <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
- <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
- <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of Conduct</a>
- </div>
- </li>
- </ul>
- </div>
- </nav>
-
- <div class="container">
+</head>
+<body>
+<nav class="navbar navbar-expand-lg navbar-dark bg-dark">
+ <a class="navbar-brand" href="/">
+ <img id="fluo-img" height="40px" src="/resources/tc_logo_c_only.png" alt="Apache Traffic Control">
+ </a>
+ <button class="navbar-toggler" type="button" data-toggle="collapse" data-target="#navbarSupportedContent"
+ aria-controls="navbarSupportedContent" aria-expanded="false" aria-label="Toggle navigation">
+ <span class="navbar-toggler-icon"></span>
+ </button>
+
+ <div class="collapse navbar-collapse" id="navbarSupportedContent">
+ <ul class="navbar-nav mr-auto">
+ <li class="nav-item">
+ <a class="nav-link" href="/">Home</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="/releases/">Releases</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/index.html">Docs</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://traffic-control-cdn.readthedocs.io/en/latest/api/index.html">API</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol/issues">Issues</a>
+ </li>
+ <li class="nav-item">
+ <a class="nav-link" href="https://github.com/apache/trafficcontrol">Repo</a>
+ </li>
+ <li class="nav-item active">
+ <a class="nav-link" href="#">Security<span class="sr-only">(current)</span></a>
+ </li>
+ <li class="nav-item dropdown">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Community
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="http://traffic-control-cdn.slack.com/" target="_blank">Slack</a>
+ <a class="dropdown-item"
+ href="https://github.com/apache/trafficcontrol/blob/master/CONTRIBUTING.md">Contributing</a>
+ <a class="dropdown-item" href="/mailing_lists/">Mailing Lists</a>
+ <a class="dropdown-item" href="https://cwiki.apache.org/confluence/display/TC/">Wiki</a>
+ <a class="dropdown-item" href="https://www.youtube.com/channel/UC2zEj6sERinzx8w8uvyRBYg">YouTube</a>
+ <a class="dropdown-item" href="https://twitter.com/trafficctrlcdn">Twitter</a>
+ </div>
+ </li>
+ </ul>
+
+ <ul class="navbar-nav navbar-right">
+
+ <li class="nav-item dropdown">
+ <a class="nav-link dropdown-toggle" href="#" id="navbarDropdown" role="button" data-toggle="dropdown"
+ aria-haspopup="true" aria-expanded="false">
+ Apache Software Foundation<span class="caret"></span>
+ </a>
+ <div class="dropdown-menu" aria-labelledby="navbarDropdown">
+ <a class="dropdown-item" href="https://www.apache.org">Apache Homepage</a>
+ <a class="dropdown-item" href="https://www.apache.org/licenses/">License</a>
+ <a class="dropdown-item" href="https://www.apache.org/events/current-event">Events</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/sponsorship.html">Sponsorship</a>
+ <a class="dropdown-item" href="https://www.apache.org/security">ASF Security</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/thanks.html">Thanks</a>
+ <a class="dropdown-item" href="https://www.apache.org/foundation/policies/conduct">Code of
+ Conduct</a>
+ </div>
+ </li>
+ </ul>
+ </div>
+</nav>
- <h1>Apache Traffic Control - Security Updates</h1>
+<div class="container">
- <div class="row">
- <div class="col-sm-12">
- <div class="card-deck">
- <div class="card">
- <div class="card-body">
- <h4 class="card-title">Past Vulnerabilities</h4>
- <ul>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2019-12405">CVE-2019-12405: Apache Traffic Control LDAP-based authentication vulnerability</a></li>
- <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7670">CVE-2017-7670: Apache Traffic Control Traffic Router Slowloris Denial of Service Vulnerability</a></li>
- </ul>
- </p>
- </div>
- </div>
- </div>
- </div>
- </div>
+ <h1>Apache Traffic Control - Security Updates</h1>
- <br/><br/>
- <h2>Reporting Vulnerabilities</h2>
- <p>Please use our private security mailing list, <a href="mailto:security@trafficcontrol.apache.org">security@trafficcontrol.apache.org</a>, to disclose any new vulnerability. Disclosing vulnerabilities privately will allow our project team to analyze the report, identify a fix, and begin the full disclosure process. Please include all relevant information to reproduce the issue, and any known workaround or fix.</p>
+ <div class="row">
+ <div class="col-sm-12">
+ <div class="card-deck">
+ <div class="card">
+ <div class="card-body">
+ <h4 class="card-title">Past Vulnerabilities</h4>
+ <ul>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2019-12405">CVE-2019-12405: Apache Traffic
+ Control LDAP-based authentication vulnerability</a></li>
+ <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2017-7670">CVE-2017-7670: Apache Traffic
+ Control Traffic Router Slowloris Denial of Service Vulnerability</a></li>
+ </ul>
+ </p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
-
- <!-- Start Footer -->
- <div class="row">
- <div class="col-sm-12 center-block">
- <footer>
- <hr/>
- <p>
- <a href="https://www.apache.org/foundation/contributing">
- <img src="https://www.apache.org/images/SupportApache-small.png"
- id="asf-logo"
- height="100"
- alt="Apache"
- class="float-left"
- style="margin-right: 15px;"></a>
+ <br/><br/>
+ <h2>Reporting Vulnerabilities</h2>
+ <p>Please use our private security mailing list, <a href="mailto:security@trafficcontrol.apache.org">security@trafficcontrol.apache.org</a>,
+ to disclose any new vulnerability. Disclosing vulnerabilities privately will allow our project team to analyze
+ the report, identify a fix, and begin the full disclosure process. Please include all relevant information to
+ reproduce the issue, and any known workaround or fix.</p>
- Copyright © 2020 <a href="https://www.apache.org">The Apache Software Foundation</a>.
- Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
- </p>
- <p>
- Apache®, the names of Apache projects and their logos, and the multicolor feather
- logo are registered trademarks or trademarks of The Apache Software Foundation
- in the United States and/or other countries.
- </p>
- </footer>
+
+ <!-- Start Footer -->
+ <div class="row">
+ <div class="col-sm-12 center-block">
+ <footer>
+ <hr/>
+ <p>
+ <a href="https://www.apache.org/foundation/contributing">
+ <img src="https://www.apache.org/images/SupportApache-small.png"
+ id="asf-logo"
+ height="100"
+ alt="Apache"
+ class="float-left"
+ style="margin-right: 15px;"></a>
+
+ Copyright © 2020 <a
+ href="https://www.apache.org">The Apache Software Foundation</a>.
+ Licensed under the <a href="https://www.apache.org/licenses/">Apache License, Version 2.0</a>
+ </p>
+ <p>
+ Apache®, the names of Apache projects and their logos, and the multicolor feather
+ logo are registered trademarks or trademarks of The Apache Software Foundation
+ in the United States and/or other countries.
+ </p>
+ </footer>
</div>
- </div>
</div>
-
- <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo" crossorigin="anonymous"></script>
- <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js" integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ" crossorigin="anonymous"></script>
- <script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js" integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm" crossorigin="anonymous"></script>
- </body>
+</div>
+
+<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js"
+ integrity="sha384-q8i/X+965DzO0rT7abK41JStQIAqVgRVzpbzo5smXKp4YfRvH+8abtTE1Pi6jizo"
+ crossorigin="anonymous"></script>
+<script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.0/umd/popper.min.js"
+ integrity="sha384-cs/chFZiN24E4KMATLdqdvsezGxaGsi4hLGOzlXwp5UZB1LY//20VyM2taTB4QvJ"
+ crossorigin="anonymous"></script>
+<script src="https://stackpath.bootstrapcdn.com/bootstrap/4.1.0/js/bootstrap.min.js"
+ integrity="sha384-uefMccjFJAIv6A+rW+L4AHf99KvxDjWSu1z9VI8SKNVmz4sk7buKt/6v9KI65qnm"
+ crossorigin="anonymous"></script>
+</body>
</html>
[trafficcontrol-website] 04/04: ApacheCon @Home news item
Posted by zr...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
zrhoffman pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/trafficcontrol-website.git
commit 0563cad8bd8568063d83cf24ee159385e1a27ba2
Author: Zach Hoffman <zr...@apache.org>
AuthorDate: Mon Sep 28 14:10:23 2020 -0600
ApacheCon @Home news item
---
index.html | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/index.html b/index.html
index 53bb250..96dde7e 100644
--- a/index.html
+++ b/index.html
@@ -119,6 +119,12 @@
<div class="card-body">
<span class="far fa-newspaper fa-7x float-right" style="color: #343a40;"></span>
<ul>
+ <li><strong>September 29, 2020</strong> - Join us for the <a
+ href="https://apachecon.com/acah2020/tracks/content.html" target="_blank">Content
+ Delivery track</a> at ApacheCon @Home!
+ </li>
+ </ul>
+ <ul>
<li><strong>June 17, 2020</strong> - Apache Traffic Control 4.1.0 Released</li>
</ul>
<ul>