You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficcontrol.apache.org by Steve Malenfant <sm...@gmail.com> on 2022/01/12 05:23:38 UTC
Re: Layered Profiles Blueprint
Jeremy,
I missed this whole discussion. I really noticed by checking the latest
commit. I'm sorry if I miss anything prior to that.
I saw in the blueprint this parameter as an example:
| Name |Config File
| Value | Profile |
|--------------------------------------------------|--------------------------|--------------------------------------|-----------|
| location | url_sig_myds.config
| /opt/trafficserver/etc/trafficserver | EDGE |
In the past, these DS specific parameters have been causing trouble
(cloning an older profile with a DS that doesn't exist anymore, but
location still does). Is there anything in this blueprint that helps with
that?
Steve
On Mon, Dec 13, 2021 at 11:44 AM Jeremy Mitchell <mi...@gmail.com>
wrote:
> Hi everyone. If you have feedback for Rima on her blueprint, may I ask that
> you get it in this week so we can move forward with the development of this
> feature: https://github.com/apache/trafficcontrol/pull/6095
>
> 4 months is probably ample time :)
>
> thanks!
>
> On Tue, Aug 10, 2021 at 12:46 PM Shah, Rima <Rima_Shah@comcast.com.invalid
> >
> wrote:
>
> > Hello All,
> >
> >
> > I’ve opened a PR to propose a new feature for Traffic Control: Layered
> > Profiles. Layered Profiles allow assigning multiple profiles, in order,
> to
> > both Servers and Delivery Services. Layered Profiles is exactly as
> powerful
> > as the existing profiles, it doesn't enable any new things. It makes
> > profiles much easier to manage.
> >
> > Please take a look at it and let me know your thoughts.
> >
> > The blueprint can be found at:
> > https://github.com/apache/trafficcontrol/pull/6095
> >
> >
> > Thanks and Regard,
> > Rima Shah
> >
> >
>
Re: Layered Profiles Blueprint
Posted by Jeremy Mitchell <mi...@gmail.com>.
yep, do what rob said. thanks for the guidance rob.
On Wed, Jan 12, 2022 at 9:23 AM Steve Malenfant <sm...@gmail.com>
wrote:
> Thanks Rob, I’ll do some cleanup and see how that goes.
>
> On Wed, Jan 12, 2022 at 10:34 AM Robert O Butts <ro...@apache.org> wrote:
>
> > > In the past, these DS specific parameters have been causing
> > trouble(cloning an older profile with a DS that doesn't exist anymore,
> but
> > location still does). Is there anything in this blueprint that helps with
> > that?
> >
> > Since ATC 5.0 all Delivery Service specific config files are inferred,
> and
> > no longer require location Parameters.
> >
> > Just delete your url_sig_ and other DS (uri_signing_, hdr_rw_,
> > regex_remap_) location Parameters, and the files will be created when
> > necessary.
> >
> >
> > On Tue, Jan 11, 2022 at 10:23 PM Steve Malenfant <sm...@gmail.com>
> > wrote:
> >
> > > Jeremy,
> > >
> > > I missed this whole discussion. I really noticed by checking the latest
> > > commit. I'm sorry if I miss anything prior to that.
> > >
> > > I saw in the blueprint this parameter as an example:
> > > | Name |Config File
> > > | Value | Profile |
> > >
> > >
> >
> |--------------------------------------------------|--------------------------|--------------------------------------|-----------|
> > > | location |
> url_sig_myds.config
> > > | /opt/trafficserver/etc/trafficserver | EDGE |
> > >
> > > In the past, these DS specific parameters have been causing trouble
> > > (cloning an older profile with a DS that doesn't exist anymore, but
> > > location still does). Is there anything in this blueprint that helps
> with
> > > that?
> > >
> > > Steve
> > >
> > > On Mon, Dec 13, 2021 at 11:44 AM Jeremy Mitchell <
> mitchell852@gmail.com>
> > > wrote:
> > >
> > > > Hi everyone. If you have feedback for Rima on her blueprint, may I
> ask
> > > that
> > > > you get it in this week so we can move forward with the development
> of
> > > this
> > > > feature: https://github.com/apache/trafficcontrol/pull/6095
> > > >
> > > > 4 months is probably ample time :)
> > > >
> > > > thanks!
> > > >
> > > > On Tue, Aug 10, 2021 at 12:46 PM Shah, Rima
> > > <Rima_Shah@comcast.com.invalid
> > > > >
> > > > wrote:
> > > >
> > > > > Hello All,
> > > > >
> > > > >
> > > > > I’ve opened a PR to propose a new feature for Traffic Control:
> > Layered
> > > > > Profiles. Layered Profiles allow assigning multiple profiles, in
> > order,
> > > > to
> > > > > both Servers and Delivery Services. Layered Profiles is exactly as
> > > > powerful
> > > > > as the existing profiles, it doesn't enable any new things. It
> makes
> > > > > profiles much easier to manage.
> > > > >
> > > > > Please take a look at it and let me know your thoughts.
> > > > >
> > > > > The blueprint can be found at:
> > > > > https://github.com/apache/trafficcontrol/pull/6095
> > > > >
> > > > >
> > > > > Thanks and Regard,
> > > > > Rima Shah
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Layered Profiles Blueprint
Posted by Steve Malenfant <sm...@gmail.com>.
Thanks Rob, I’ll do some cleanup and see how that goes.
On Wed, Jan 12, 2022 at 10:34 AM Robert O Butts <ro...@apache.org> wrote:
> > In the past, these DS specific parameters have been causing
> trouble(cloning an older profile with a DS that doesn't exist anymore, but
> location still does). Is there anything in this blueprint that helps with
> that?
>
> Since ATC 5.0 all Delivery Service specific config files are inferred, and
> no longer require location Parameters.
>
> Just delete your url_sig_ and other DS (uri_signing_, hdr_rw_,
> regex_remap_) location Parameters, and the files will be created when
> necessary.
>
>
> On Tue, Jan 11, 2022 at 10:23 PM Steve Malenfant <sm...@gmail.com>
> wrote:
>
> > Jeremy,
> >
> > I missed this whole discussion. I really noticed by checking the latest
> > commit. I'm sorry if I miss anything prior to that.
> >
> > I saw in the blueprint this parameter as an example:
> > | Name |Config File
> > | Value | Profile |
> >
> >
> |--------------------------------------------------|--------------------------|--------------------------------------|-----------|
> > | location | url_sig_myds.config
> > | /opt/trafficserver/etc/trafficserver | EDGE |
> >
> > In the past, these DS specific parameters have been causing trouble
> > (cloning an older profile with a DS that doesn't exist anymore, but
> > location still does). Is there anything in this blueprint that helps with
> > that?
> >
> > Steve
> >
> > On Mon, Dec 13, 2021 at 11:44 AM Jeremy Mitchell <mi...@gmail.com>
> > wrote:
> >
> > > Hi everyone. If you have feedback for Rima on her blueprint, may I ask
> > that
> > > you get it in this week so we can move forward with the development of
> > this
> > > feature: https://github.com/apache/trafficcontrol/pull/6095
> > >
> > > 4 months is probably ample time :)
> > >
> > > thanks!
> > >
> > > On Tue, Aug 10, 2021 at 12:46 PM Shah, Rima
> > <Rima_Shah@comcast.com.invalid
> > > >
> > > wrote:
> > >
> > > > Hello All,
> > > >
> > > >
> > > > I’ve opened a PR to propose a new feature for Traffic Control:
> Layered
> > > > Profiles. Layered Profiles allow assigning multiple profiles, in
> order,
> > > to
> > > > both Servers and Delivery Services. Layered Profiles is exactly as
> > > powerful
> > > > as the existing profiles, it doesn't enable any new things. It makes
> > > > profiles much easier to manage.
> > > >
> > > > Please take a look at it and let me know your thoughts.
> > > >
> > > > The blueprint can be found at:
> > > > https://github.com/apache/trafficcontrol/pull/6095
> > > >
> > > >
> > > > Thanks and Regard,
> > > > Rima Shah
> > > >
> > > >
> > >
> >
>
Re: Layered Profiles Blueprint
Posted by Robert O Butts <ro...@apache.org>.
> In the past, these DS specific parameters have been causing
trouble(cloning an older profile with a DS that doesn't exist anymore, but
location still does). Is there anything in this blueprint that helps with
that?
Since ATC 5.0 all Delivery Service specific config files are inferred, and
no longer require location Parameters.
Just delete your url_sig_ and other DS (uri_signing_, hdr_rw_,
regex_remap_) location Parameters, and the files will be created when
necessary.
On Tue, Jan 11, 2022 at 10:23 PM Steve Malenfant <sm...@gmail.com>
wrote:
> Jeremy,
>
> I missed this whole discussion. I really noticed by checking the latest
> commit. I'm sorry if I miss anything prior to that.
>
> I saw in the blueprint this parameter as an example:
> | Name |Config File
> | Value | Profile |
>
> |--------------------------------------------------|--------------------------|--------------------------------------|-----------|
> | location | url_sig_myds.config
> | /opt/trafficserver/etc/trafficserver | EDGE |
>
> In the past, these DS specific parameters have been causing trouble
> (cloning an older profile with a DS that doesn't exist anymore, but
> location still does). Is there anything in this blueprint that helps with
> that?
>
> Steve
>
> On Mon, Dec 13, 2021 at 11:44 AM Jeremy Mitchell <mi...@gmail.com>
> wrote:
>
> > Hi everyone. If you have feedback for Rima on her blueprint, may I ask
> that
> > you get it in this week so we can move forward with the development of
> this
> > feature: https://github.com/apache/trafficcontrol/pull/6095
> >
> > 4 months is probably ample time :)
> >
> > thanks!
> >
> > On Tue, Aug 10, 2021 at 12:46 PM Shah, Rima
> <Rima_Shah@comcast.com.invalid
> > >
> > wrote:
> >
> > > Hello All,
> > >
> > >
> > > I’ve opened a PR to propose a new feature for Traffic Control: Layered
> > > Profiles. Layered Profiles allow assigning multiple profiles, in order,
> > to
> > > both Servers and Delivery Services. Layered Profiles is exactly as
> > powerful
> > > as the existing profiles, it doesn't enable any new things. It makes
> > > profiles much easier to manage.
> > >
> > > Please take a look at it and let me know your thoughts.
> > >
> > > The blueprint can be found at:
> > > https://github.com/apache/trafficcontrol/pull/6095
> > >
> > >
> > > Thanks and Regard,
> > > Rima Shah
> > >
> > >
> >
>