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).

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to