[
https://issues.apache.org/jira/browse/TC-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16139277#comment-16139277
]
ASF GitHub Bot commented on TC-287:
-----------------------------------
GitHub user rawlinp opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/865
[TC-287] Add support for per-DeliveryService routing names
Add a routing_name column to the DeliveryService table and populate it
to 'tr' and 'edge' for HTTP and DNS delivery services, respectively.
To make upgrading seamless for CDNs using a custom http.routing.name
(configured in the TR), provide a temporary upgrade parameter to
populate the routing name for HTTP Delivery Services. Otherwise HTTP
DSes will get routing_name = "tr".
Replace all hardcoded/assumed routing names of 'edge' or 'tr' in Traffic
Ops with the proper routing name configured for that delivery service.
Update the API/UI to support custom routing names for delivery services.
To prevent breaking the API, "routingName" is an optional field (the DB
schema provides an arbitrary default).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rawlinp/incubator-trafficcontrol
per-cdn-routing-names_2
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafficcontrol/pull/865.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #865
----
commit 1925845dd9c5cc53a87dcff130d1e5843142023f
Author: Rawlin Peters <[email protected]>
Date: 2017-07-31T17:37:50Z
[TC-287] Add support for per-DeliveryService routing names
Add a routing_name column to the DeliveryService table and populate it
to 'tr' and 'edge' for HTTP and DNS delivery services, respectively.
To make upgrading seamless for CDNs using a custom http.routing.name
(configured in the TR), provide a temporary upgrade parameter to
populate the routing name for HTTP Delivery Services. Otherwise HTTP
DSes will get routing_name = "tr".
Replace all hardcoded/assumed routing names of 'edge' or 'tr' in Traffic
Ops with the proper routing name configured for that delivery service.
Update the API/UI to support custom routing names for delivery services.
To prevent breaking the API, "routingName" is an optional field (the DB
schema provides an arbitrary default).
----
> Add support for per-Delivery Service routing/name
> -------------------------------------------------
>
> Key: TC-287
> URL: https://issues.apache.org/jira/browse/TC-287
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops, Traffic Router
> Reporter: Eric Friedrich
> Assignee: Rawlin Peters
> Labels: crconfig, routing
>
> A default routing name/entry point should be added as a profile parameter,
> and this parameter should be used by default as the value of the "routing
> name" or "entry point" on the delivery service in the CRConfig. This value
> should be overridable on a per-delivery service level, which means that the
> delivery service UIs should be enhanced to provide this capability and to
> display the default value.
> Once above is implemented, consume the new delivery service parameter and
> configure accordingly within Traffic Router.
> From:
> https://github.com/Comcast/traffic_control/issues/61
> https://github.com/Comcast/traffic_control/issues/62
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
