You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@trafficcontrol.apache.org by Nir Sopher <ni...@qwilt.com> on 2017/01/19 13:36:19 UTC
Parametrized traffic-server configuration
Hi all,
I want to run a traffic-server on a server running another web server
simultaneously.
However, as traffic server listens by default on IP 0.0.0.0, the two web
server collide.
In order to solve this issue, I am trying to use proxy-local-incoming-ip-
to-bind
<https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind>
at
records.config file.
The main issue is that the value of the parameter changes from server to
server.
I would therefore want to add a parameter to the profile using a variable:
- configuring "LOCAL proxy-local-incoming-ip-to-bind" to be something like
"STRING *${ip-address}*".
Is such an ability supported?
Thanks,
Nir
Re: Parametrized traffic-server configuration
Posted by Dan Kirkwood <da...@gmail.com>.
make that a third...
On Mon, Jan 23, 2017 at 7:59 PM, Eric Friedrich (efriedri)
<ef...@cisco.com> wrote:
> I second that, would prefer only incubator required fixes go in 1.8
>
> --Eric
> ________________________________________
> From: Jan van Doorn [jvd@knutsel.com]
> Sent: Monday, January 23, 2017 8:04 PM
> To: users@trafficcontrol.incubator.apache.org
> Subject: Re: Parametrized traffic-server configuration
>
> I don’t think we should be adding any new features or fixes to 1.8 unless absolutely necessary, or license changes for the incubation process.
>
> This is a new feature that should be committed to master, and will get picked up in the next release.
>
> Rgds,
> JvD
>
>
> On Jan 23, 2017, at 5:17 PM, Nir Sopher <ni...@qwilt.com>> wrote:
>
> Is making the change on 1.8.x also OK?
> 10x,
> Nir
>
> On Jan 19, 2017 11:59 PM, "Nir Sopher" <ni...@qwilt.com>> wrote:
> ack
> 10x,
> Nir
>
> On Thu, Jan 19, 2017 at 11:49 PM, Dave Neuman <ne...@apache.org>> wrote:
> Master is best.
>
> On Thu, Jan 19, 2017 at 2:47 PM, Nir Sopher <ni...@qwilt.com>> wrote:
> Got it.
> Thanks:)
>
> On which branch should it be fixed?
>
> Nir
>
> On Thu, Jan 19, 2017 at 3:43 PM, Jan van Doorn <jv...@knutsel.com>> wrote:
> It would require a (small) code change to generic_config sub in Configfiles.pm I think.
>
> We’ve used __CACHE_IPV4__ for other config files, I would try to stick with that convention.
>
> That reminds me as well that all ATS instances are IPv4 and IPv6 capable, so you probably want to add support for something like __CACHE_IPV6__ as well.
>
> Rgds,
> JvD
>
>
> On Jan 19, 2017, at 6:36 AM, Nir Sopher <ni...@qwilt.com>> wrote:
>
> Hi all,
>
> I want to run a traffic-server on a server running another web server simultaneously.
> However, as traffic server listens by default on IP 0.0.0.0, the two web server collide.
>
> In order to solve this issue, I am trying to use proxy-local-incoming-ip-to-bind<https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at records.config file.
> The main issue is that the value of the parameter changes from server to server.
> I would therefore want to add a parameter to the profile using a variable: - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be something like "STRING ${ip-address}".
>
> Is such an ability supported?
>
> Thanks,
> Nir
>
>
>
>
>
RE: Parametrized traffic-server configuration
Posted by "Eric Friedrich (efriedri)" <ef...@cisco.com>.
I second that, would prefer only incubator required fixes go in 1.8
--Eric
________________________________________
From: Jan van Doorn [jvd@knutsel.com]
Sent: Monday, January 23, 2017 8:04 PM
To: users@trafficcontrol.incubator.apache.org
Subject: Re: Parametrized traffic-server configuration
I don’t think we should be adding any new features or fixes to 1.8 unless absolutely necessary, or license changes for the incubation process.
This is a new feature that should be committed to master, and will get picked up in the next release.
Rgds,
JvD
On Jan 23, 2017, at 5:17 PM, Nir Sopher <ni...@qwilt.com>> wrote:
Is making the change on 1.8.x also OK?
10x,
Nir
On Jan 19, 2017 11:59 PM, "Nir Sopher" <ni...@qwilt.com>> wrote:
ack
10x,
Nir
On Thu, Jan 19, 2017 at 11:49 PM, Dave Neuman <ne...@apache.org>> wrote:
Master is best.
On Thu, Jan 19, 2017 at 2:47 PM, Nir Sopher <ni...@qwilt.com>> wrote:
Got it.
Thanks:)
On which branch should it be fixed?
Nir
On Thu, Jan 19, 2017 at 3:43 PM, Jan van Doorn <jv...@knutsel.com>> wrote:
It would require a (small) code change to generic_config sub in Configfiles.pm I think.
We’ve used __CACHE_IPV4__ for other config files, I would try to stick with that convention.
That reminds me as well that all ATS instances are IPv4 and IPv6 capable, so you probably want to add support for something like __CACHE_IPV6__ as well.
Rgds,
JvD
On Jan 19, 2017, at 6:36 AM, Nir Sopher <ni...@qwilt.com>> wrote:
Hi all,
I want to run a traffic-server on a server running another web server simultaneously.
However, as traffic server listens by default on IP 0.0.0.0, the two web server collide.
In order to solve this issue, I am trying to use proxy-local-incoming-ip-to-bind<https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at records.config file.
The main issue is that the value of the parameter changes from server to server.
I would therefore want to add a parameter to the profile using a variable: - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be something like "STRING ${ip-address}".
Is such an ability supported?
Thanks,
Nir
Re: Parametrized traffic-server configuration
Posted by Jan van Doorn <jv...@knutsel.com>.
I don’t think we should be adding any new features or fixes to 1.8 unless absolutely necessary, or license changes for the incubation process.
This is a new feature that should be committed to master, and will get picked up in the next release.
Rgds,
JvD
> On Jan 23, 2017, at 5:17 PM, Nir Sopher <ni...@qwilt.com> wrote:
>
> Is making the change on 1.8.x also OK?
> 10x,
> Nir
>
> On Jan 19, 2017 11:59 PM, "Nir Sopher" <nirs@qwilt.com <ma...@qwilt.com>> wrote:
> ack
> 10x,
> Nir
>
> On Thu, Jan 19, 2017 at 11:49 PM, Dave Neuman <neuman@apache.org <ma...@apache.org>> wrote:
> Master is best.
>
> On Thu, Jan 19, 2017 at 2:47 PM, Nir Sopher <nirs@qwilt.com <ma...@qwilt.com>> wrote:
> Got it.
> Thanks:)
>
> On which branch should it be fixed?
>
> Nir
>
> On Thu, Jan 19, 2017 at 3:43 PM, Jan van Doorn <jvd@knutsel.com <ma...@knutsel.com>> wrote:
> It would require a (small) code change to generic_config sub in Configfiles.pm I think.
>
> We’ve used __CACHE_IPV4__ for other config files, I would try to stick with that convention.
>
> That reminds me as well that all ATS instances are IPv4 and IPv6 capable, so you probably want to add support for something like __CACHE_IPV6__ as well.
>
> Rgds,
> JvD
>
>
>> On Jan 19, 2017, at 6:36 AM, Nir Sopher <nirs@qwilt.com <ma...@qwilt.com>> wrote:
>>
>> Hi all,
>>
>> I want to run a traffic-server on a server running another web server simultaneously.
>> However, as traffic server listens by default on IP 0.0.0.0, the two web server collide.
>>
>> In order to solve this issue, I am trying to use proxy-local-incoming-ip-to-bind <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at records.config file.
>> The main issue is that the value of the parameter changes from server to server.
>> I would therefore want to add a parameter to the profile using a variable: - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be something like "STRING ${ip-address}".
>>
>> Is such an ability supported?
>>
>> Thanks,
>> Nir
>
>
>
>
Re: Parametrized traffic-server configuration
Posted by Nir Sopher <ni...@qwilt.com>.
Is making the change on 1.8.x also OK?
10x,
Nir
On Jan 19, 2017 11:59 PM, "Nir Sopher" <ni...@qwilt.com> wrote:
> ack
> 10x,
> Nir
>
> On Thu, Jan 19, 2017 at 11:49 PM, Dave Neuman <ne...@apache.org> wrote:
>
>> Master is best.
>>
>> On Thu, Jan 19, 2017 at 2:47 PM, Nir Sopher <ni...@qwilt.com> wrote:
>>
>>> Got it.
>>> Thanks:)
>>>
>>> On which branch should it be fixed?
>>>
>>> Nir
>>>
>>> On Thu, Jan 19, 2017 at 3:43 PM, Jan van Doorn <jv...@knutsel.com> wrote:
>>>
>>>> It would require a (small) code change to generic_config sub in
>>>> Configfiles.pm I think.
>>>>
>>>> We’ve used __CACHE_IPV4__ for other config files, I would try to stick
>>>> with that convention.
>>>>
>>>> That reminds me as well that all ATS instances are IPv4 and IPv6
>>>> capable, so you probably want to add support for something like
>>>> __CACHE_IPV6__ as well.
>>>>
>>>> Rgds,
>>>> JvD
>>>>
>>>>
>>>> On Jan 19, 2017, at 6:36 AM, Nir Sopher <ni...@qwilt.com> wrote:
>>>>
>>>> Hi all,
>>>>
>>>> I want to run a traffic-server on a server running another web server
>>>> simultaneously.
>>>> However, as traffic server listens by default on IP 0.0.0.0, the two
>>>> web server collide.
>>>>
>>>> In order to solve this issue, I am trying to use
>>>> proxy-local-incoming-ip-to-bind
>>>> <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at
>>>> records.config file.
>>>> The main issue is that the value of the parameter changes from server
>>>> to server.
>>>> I would therefore want to add a parameter to the profile using a
>>>> variable: - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be
>>>> something like "STRING *${ip-address}*".
>>>>
>>>> Is such an ability supported?
>>>>
>>>> Thanks,
>>>> Nir
>>>>
>>>>
>>>>
>>>
>>
>
Re: Parametrized traffic-server configuration
Posted by Nir Sopher <ni...@qwilt.com>.
ack
10x,
Nir
On Thu, Jan 19, 2017 at 11:49 PM, Dave Neuman <ne...@apache.org> wrote:
> Master is best.
>
> On Thu, Jan 19, 2017 at 2:47 PM, Nir Sopher <ni...@qwilt.com> wrote:
>
>> Got it.
>> Thanks:)
>>
>> On which branch should it be fixed?
>>
>> Nir
>>
>> On Thu, Jan 19, 2017 at 3:43 PM, Jan van Doorn <jv...@knutsel.com> wrote:
>>
>>> It would require a (small) code change to generic_config sub in
>>> Configfiles.pm I think.
>>>
>>> We’ve used __CACHE_IPV4__ for other config files, I would try to stick
>>> with that convention.
>>>
>>> That reminds me as well that all ATS instances are IPv4 and IPv6
>>> capable, so you probably want to add support for something like
>>> __CACHE_IPV6__ as well.
>>>
>>> Rgds,
>>> JvD
>>>
>>>
>>> On Jan 19, 2017, at 6:36 AM, Nir Sopher <ni...@qwilt.com> wrote:
>>>
>>> Hi all,
>>>
>>> I want to run a traffic-server on a server running another web server
>>> simultaneously.
>>> However, as traffic server listens by default on IP 0.0.0.0, the two web
>>> server collide.
>>>
>>> In order to solve this issue, I am trying to use
>>> proxy-local-incoming-ip-to-bind
>>> <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at
>>> records.config file.
>>> The main issue is that the value of the parameter changes from server to
>>> server.
>>> I would therefore want to add a parameter to the profile using a
>>> variable: - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be
>>> something like "STRING *${ip-address}*".
>>>
>>> Is such an ability supported?
>>>
>>> Thanks,
>>> Nir
>>>
>>>
>>>
>>
>
Re: Parametrized traffic-server configuration
Posted by Dave Neuman <ne...@apache.org>.
Master is best.
On Thu, Jan 19, 2017 at 2:47 PM, Nir Sopher <ni...@qwilt.com> wrote:
> Got it.
> Thanks:)
>
> On which branch should it be fixed?
>
> Nir
>
> On Thu, Jan 19, 2017 at 3:43 PM, Jan van Doorn <jv...@knutsel.com> wrote:
>
>> It would require a (small) code change to generic_config sub in
>> Configfiles.pm I think.
>>
>> We’ve used __CACHE_IPV4__ for other config files, I would try to stick
>> with that convention.
>>
>> That reminds me as well that all ATS instances are IPv4 and IPv6 capable,
>> so you probably want to add support for something like __CACHE_IPV6__ as
>> well.
>>
>> Rgds,
>> JvD
>>
>>
>> On Jan 19, 2017, at 6:36 AM, Nir Sopher <ni...@qwilt.com> wrote:
>>
>> Hi all,
>>
>> I want to run a traffic-server on a server running another web server
>> simultaneously.
>> However, as traffic server listens by default on IP 0.0.0.0, the two web
>> server collide.
>>
>> In order to solve this issue, I am trying to use
>> proxy-local-incoming-ip-to-bind
>> <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at
>> records.config file.
>> The main issue is that the value of the parameter changes from server to
>> server.
>> I would therefore want to add a parameter to the profile using a
>> variable: - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be
>> something like "STRING *${ip-address}*".
>>
>> Is such an ability supported?
>>
>> Thanks,
>> Nir
>>
>>
>>
>
Re: Parametrized traffic-server configuration
Posted by Nir Sopher <ni...@qwilt.com>.
Got it.
Thanks:)
On which branch should it be fixed?
Nir
On Thu, Jan 19, 2017 at 3:43 PM, Jan van Doorn <jv...@knutsel.com> wrote:
> It would require a (small) code change to generic_config sub in
> Configfiles.pm I think.
>
> We’ve used __CACHE_IPV4__ for other config files, I would try to stick
> with that convention.
>
> That reminds me as well that all ATS instances are IPv4 and IPv6 capable,
> so you probably want to add support for something like __CACHE_IPV6__ as
> well.
>
> Rgds,
> JvD
>
>
> On Jan 19, 2017, at 6:36 AM, Nir Sopher <ni...@qwilt.com> wrote:
>
> Hi all,
>
> I want to run a traffic-server on a server running another web server
> simultaneously.
> However, as traffic server listens by default on IP 0.0.0.0, the two web
> server collide.
>
> In order to solve this issue, I am trying to use
> proxy-local-incoming-ip-to-bind
> <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at
> records.config file.
> The main issue is that the value of the parameter changes from server to
> server.
> I would therefore want to add a parameter to the profile using a variable:
> - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be something
> like "STRING *${ip-address}*".
>
> Is such an ability supported?
>
> Thanks,
> Nir
>
>
>
Re: Parametrized traffic-server configuration
Posted by Jan van Doorn <jv...@knutsel.com>.
It would require a (small) code change to generic_config sub in Configfiles.pm I think.
We’ve used __CACHE_IPV4__ for other config files, I would try to stick with that convention.
That reminds me as well that all ATS instances are IPv4 and IPv6 capable, so you probably want to add support for something like __CACHE_IPV6__ as well.
Rgds,
JvD
> On Jan 19, 2017, at 6:36 AM, Nir Sopher <ni...@qwilt.com> wrote:
>
> Hi all,
>
> I want to run a traffic-server on a server running another web server simultaneously.
> However, as traffic server listens by default on IP 0.0.0.0, the two web server collide.
>
> In order to solve this issue, I am trying to use proxy-local-incoming-ip-to-bind <https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-local-incoming-ip-to-bind> at records.config file.
> The main issue is that the value of the parameter changes from server to server.
> I would therefore want to add a parameter to the profile using a variable: - configuring "LOCAL proxy-local-incoming-ip-to-bind" to be something like "STRING ${ip-address}".
>
> Is such an ability supported?
>
> Thanks,
> Nir