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/01/25 17:16:26 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=15838161#comment-15838161 ]
ASF GitHub Bot commented on TC-121:
-----------------------------------
Github user mitchell852 commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/230
@nir-sopher - if you rename this PR "[TC-121] Allowing variables in traffic-server's profile derived parameters" I think it will link it to the jira issue...
> 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.4#6332)