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/06/01 20:28:04 UTC

[jira] [Commented] (TC-121) Parametrized traffic-server configuration

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

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

Github user nir-sopher commented on the issue:

    https://github.com/apache/incubator-trafficcontrol/pull/230
  
    PR was rebased so it cam be merged. However, it still needs to be verified again by adding a record to  records.config and checking the value


> Parametrized traffic-server configuration
> -----------------------------------------
>
>                 Key: TC-121
>                 URL: https://issues.apache.org/jira/browse/TC-121
>             Project: Traffic Control
>          Issue Type: Improvement
>          Components: Traffic Ops
>            Reporter: Nir Sopher
>            Priority: Minor
>
> We would like to allow an individual traffic-server configuration, dervied from its profile as well as its specific configuration.
> For example, set the traffic-server to listen the configured IP by setting  proxy-local-incoming-ip-to-bind value.
> In order to do so, variables should be embedded within profile variables values.
> For example:  __CACHE_IPV4__ and  __CACHE_IPV6__ 
> Future variables to discuss: http/s ports, hostname, domain



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