mitchell852 closed pull request #1865: Added file with per-DS 
routing names upgrade notes

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/ b/
new file mode 100644
index 0000000000..a9f061cceb
--- /dev/null
+++ b/
@@ -0,0 +1,18 @@
+v2.2.0 [unreleased]
+### Upgrading
+#### Per-DeliveryService Routing Names
+A new Delivery Services feature has been added that might require a few 
pre-upgrade steps: Per-DeliveryService Routing Names. Before this release, DNS 
Delivery Services were hardcoded to use the name "edge", i.e. 
"", and HTTP Delivery Services use the name "tr" (or 
previously "ccr"), i.e. "". As of 2.2, Routing Names will 
default to "cdn" if left unspecified and can be set to any arbitrary non-dotted 
+Pre-2.2 the HTTP Routing Name is configurable via the `` 
option in in the Traffic Router 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
+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 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to