You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/08 15:15:04 UTC

[jira] [Commented] (TC-272) ORT should ignore STEERING deliveryservices

    [ https://issues.apache.org/jira/browse/TC-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000885#comment-16000885 ] 

ASF GitHub Bot commented on TC-272:
-----------------------------------

Github user mtorluemke commented on a diff in the pull request:

    https://github.com/apache/incubator-trafficcontrol/pull/552#discussion_r115272927
  
    --- Diff: traffic_ops/app/lib/API/Configs/ApacheTrafficServer.pm ---
    @@ -1470,6 +1473,9 @@ sub ssl_multicert_dot_config {
     
     		#first one is the one we want
     		my $hostname = $example_urls[0];
    +		if ( $hostname =~ /ccr/ ) {
    --- End diff --
    
    default string for open source builds is 'tr'


> ORT should ignore STEERING deliveryservices
> -------------------------------------------
>
>                 Key: TC-272
>                 URL: https://issues.apache.org/jira/browse/TC-272
>             Project: Traffic Control
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: David Neuman
>            Assignee: Derek Gelinas
>
> With the 2.1 version of Traffic ops ORT, ORT grabs all of the configurations for all of the Delivery services in a CDN and puts it on all caches in the CDN regardless of DS Type and DS server assignments.   This causes an issue with Steering deliveryservice because A) steering DSs shouldn't be on the caches and B) steering DSs are created with certs that start with `ccr.` and ORT does not know how to find those certificates in Traffic Vault which causes ORT to fail.
> ORT should be updated such that Steering delivery service configurations are not put on caches. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)