This is an automated email from the ASF dual-hosted git repository.
dewrich pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-trafficcontrol.git
The following commit(s) were added to refs/heads/master by this push:
new 954ad77 Reformat CHANGELOG.md to use the keep-a-changelog format
954ad77 is described below
commit 954ad774ee9165cfd70fb31fc2eb9ad889acd56f
Author: Rawlin Peters <rawlin_pet...@comcast.com>
AuthorDate: Mon Mar 5 16:43:46 2018 -0700
Reformat CHANGELOG.md to use the keep-a-changelog format
---
CHANGELOG.md | 23 +++++++++--------------
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index a9f061c..4034914 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,18 +1,13 @@
-v2.2.0 [unreleased]
--------------------
+# Changelog
+All notable changes to this project will be documented in this file.
-### Upgrading
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).
-#### 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.
"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.
+## [Unreleased]
+### Added
+- Per-DeliveryService Routing Names: you can now choose a Delivery Service's
Routing Name (rather than a hardcoded "tr" or "edge" name). This might require
a few pre-upgrade steps detailed
[here](http://traffic-control-cdn.readthedocs.io/en/latest/admin/traffic_ops/migration_from_20_to_22.html#per-deliveryservice-routing-names)
-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):
+### Changed
+- Reformatted this CHANGELOG file to the keep-a-changelog format
- **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).
+[Unreleased]:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-2.1.0...HEAD
--
To stop receiving notification emails like this one, please contact
dewr...@apache.org.
