Re: [VOTE] Release Apache Traffic Control 8.0.1-RC1

[Zach Hoffman]

+1

-Zach

On Wed, Mar 27, 2024 at 11:18 AM R S  wrote:

> Hello All,
>
> I've prepared a release for 8.0.1-RC1. There *isn't any* changes since
> RELEASE-8.0.1-RC0:
>
> The purpose of this new candidate is to get enough votes to either cut a
> release or make a change. Please be kind and vote.
> Also, *note*: These changes have been verified and are running internally
> at Comcast.
>
> https://github.com/apache/trafficcontrol/compare/v8.0.1-rc0...v8.0.1-rc1
>
>
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.1-RC1/CHANGELOG.md
>
> The artifacts are available for download at:
>
> https://dist.apache.org/repos/dist/dev/trafficcontrol/8.0.1/RC1/
>
> BLAKE2 checksum:
>
> 448227ebe681561613ce65db4e20f62ac7f9d043200e2a94915e36facdc9f01f549a97dccaafedfe420b61b896a690850c5965b164ceea1b02d372fcb9250065
>
> SHA512 checksum:
>
> c438f337725caca1b1a1ddb25d1a2ea04b96a9a4d786acd0b24fb3e7455f95e069c9af121ebdcbde2e63168330ba8e2b999a912637de97403acf52e6e06ebdb1
>
> This corresponds to git refs:
>
> Hash:ad667bb9178d96adfdcdff10b51fe6b3a4ce2e1b
> Tag: RELEASE-8.0.1-RC1
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-8.0.1-RC1
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote is open until 22:00 UTC on *Monday, April 1st* and passes if a
> majority of at least 3 +1 PMC votes are cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> Rima Shah
>
> rs...@apache.org
>

Re: [VOTE] Release Apache Traffic Control 8.0.0-RC6

[Zach Hoffman]

+1

-Zach

On Wed, Jan 24, 2024 at 5:28 PM Rawlin Peters  wrote:

> +1
>
> - Rawlin
>
> On Wed, Jan 24, 2024 at 9:51 AM R S  wrote:
> >
> > Hello All,
> >
> > Thank you for all the +1s (5) for RC5. We need one last candidate to
> > include *three* changes.
> >
> > 1. documents now build correctly
> > 2. CIAB build on Mac mini M2 Pro
> > 3. t3c RPM DB check with Rocky Linux 9
> >
> > *Note*: These changes have been running internally and have been stable
> at
> > Comcast.
> >
> > I've prepared a release for 8.0.0-RC6. Changes since RELEASE-8.0.0-RC5:
> >
> > https://github.com/apache/trafficcontrol/compare/v8.0.0-rc5...v8.0.0-rc6
> >
> >
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC6/CHANGELOG.md
> >
> > The artifacts are available for download at:
> >
> > https://dist.apache.org/repos/dist/dev/trafficcontrol/8.0.0/RC6/
> >
> > BLAKE2 checksum:
> >
> >
> 0361e89ea9ba7b26d593d49e10f0cb817851fc98a08380991d3f8116c05687d8f909ed0aabcb25b3383d16c1c244d5045eef395f4d256a98f8f5ff394f6a2dec
> >
> > SHA512 checksum:
> >
> >
> f019d7e6f00e60d7dc6a405f6b96aca494195c337eb1bcba3e5ec06208def19d93a6a15f87c06cb8f461f27a0da9e2a3838e5eea397cc06779f1cd6cd88220c7
> >
> > This corresponds to git refs:
> >
> > Hash:6cb2bca67c27f926ff4b8f84de7818e7a8191b0d
> > Tag: RELEASE-8.0.0-RC6
> >
> > Which can be verified with the following command:
> >
> > $ git tag -v RELEASE-8.0.0-RC6
> >
> > All code signing keys are available here:
> >
> > https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
> >
> > Make sure you refresh from a key server to get all relevant signatures.
> >
> > The vote is open until 22:00 UTC on Monday, Jan 29th 2024 and passes
> > if a majority of at least 3 +1 PMC votes are cast.
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> > Thanks and Regards,
> > Rima Shah
>

Re: [VOTE] Release Apache Traffic Control 8.0.0-RC5

[Zach Hoffman]

PRed a fix: https://github.com/apache/trafficcontrol/pull/7922

On Mon, Jan 22, 2024 at 4:58 PM Zach Hoffman  wrote:

> Hi Jan!
>
> On Fri, Jan 19, 2024 at 4:20 AM Jan van Doorn  wrote:
>
>> +0
>>
>> Not a +1 because I’m not qualified to have an opinion anymore/yet?, but
>> letting you know I may get back in to TC for fun.  How is everyone doing?
>>
>> I was able to build all RPMs (takes a long time!), but I got stuck trying
>> to use CiaB on a Mac mini M2 Pro. Looks like it was because of the arm64
>> architecture? Some quick Makefile hacks and searches on the mailing lists
>> didn’t get me unstuck… Anyone have any pointers on this?
>>
>
> There seems to be 2 issues here. The first issue is that the prebuild
> builder Docker images are only prebuilt for amd64, not arm64 (example: <
> https://hub.docker.com/layers/apache/traffic_ops_builder/8.0.x/images/sha256-115b331d42db9f7356c20fb4ad65c33d211282b48a4b0c75d812238b247a>).
> That issue can be worked around by doing either `pkg -vb traffic_ops_build`
> or `make build-builders traffic_ops/traffic_ops.rpm` for CDN in a Box.
>
> The other issue is that the CDN in a Box makefile does not grab the build
> number if the user is building from a release instead of the git repo.
> Filed: https://github.com/apache/trafficcontrol/issues/
>
> Changing my +1 to -1 due to #7921, let's try to fix this for the 8.0.0
> release.
>
> -Zach
>
>
>>
>> Cheers,
>> JvD
>>
>>
>> > On Jan 17, 2024, at 18:48, R S  wrote:
>> >
>> > Hello All,
>> >
>> > I've prepared a release for 8.0.0-RC5. Changes since RELEASE-8.0.0-RC4:
>> >
>> https://github.com/apache/trafficcontrol/compare/v8.0.0-rc4...v8.0.0-rc5
>> > <
>> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC4/CHANGELOG.md
>> >
>> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC5/CHANGELOG.md
>> >
>> > The artifacts are available for download at:
>> > https://dist.apache.org/repos/dist/dev/trafficcontrol/8.0.0/RC5/
>> >
>> > BLAKE2 checksum:
>> >
>> >
>> a2d12fa11050e20b7ab4c864a058de2781af4a1449e62c5d3cc169fcd6c8bb88dd9f065a2a44d93ed6f64b00802aa0c387f997c7dea0e7331e4b8397022caa68
>> >
>> > SHA512 checksum:
>> >
>> >
>> cb826938cdf23e053326f5b0de0cea36de8d3825c5803392a1ba1cb8406a753c6d523e2662cc82ac33181a7f295ca7b74c8e72ebe848e64ae4ad3d5a67872667
>> >
>> > This corresponds to git refs:
>> >
>> >   Hash:0c515199dbeb3233b32376268e4ee32ad18ebd8b
>> >   Tag: RELEASE-8.0.0-RC5
>> >
>> > Which can be verified with the following command:
>> >
>> >   $ git tag -v RELEASE-8.0.0-RC5
>> >
>> > All code signing keys are available here:
>> >
>> >   https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>> >
>> > Make sure you refresh from a key server to get all relevant signatures.
>> >
>> > The vote is open until 22:00 UTC on Monday, Jan 22nd 2024 and passes
>> > if a majority of at least 3 +1 PMC votes are cast.
>> >   [ ] +1 approve
>> >   [ ] +0 no opinion
>> >   [ ] -1 disapprove (and reason why)
>> >
>> > Thanks!
>> > Rima Shah
>>
>>

Re: [VOTE] Release Apache Traffic Control 8.0.0-RC5

[Zach Hoffman]

Hi Jan!

On Fri, Jan 19, 2024 at 4:20 AM Jan van Doorn  wrote:

> +0
>
> Not a +1 because I’m not qualified to have an opinion anymore/yet?, but
> letting you know I may get back in to TC for fun.  How is everyone doing?
>
> I was able to build all RPMs (takes a long time!), but I got stuck trying
> to use CiaB on a Mac mini M2 Pro. Looks like it was because of the arm64
> architecture? Some quick Makefile hacks and searches on the mailing lists
> didn’t get me unstuck… Anyone have any pointers on this?
>

There seems to be 2 issues here. The first issue is that the prebuild
builder Docker images are only prebuilt for amd64, not arm64 (example: <
https://hub.docker.com/layers/apache/traffic_ops_builder/8.0.x/images/sha256-115b331d42db9f7356c20fb4ad65c33d211282b48a4b0c75d812238b247a>).
That issue can be worked around by doing either `pkg -vb traffic_ops_build`
or `make build-builders traffic_ops/traffic_ops.rpm` for CDN in a Box.

The other issue is that the CDN in a Box makefile does not grab the build
number if the user is building from a release instead of the git repo.
Filed: https://github.com/apache/trafficcontrol/issues/

Changing my +1 to -1 due to #7921, let's try to fix this for the 8.0.0
release.

-Zach


>
> Cheers,
> JvD
>
>
> > On Jan 17, 2024, at 18:48, R S  wrote:
> >
> > Hello All,
> >
> > I've prepared a release for 8.0.0-RC5. Changes since RELEASE-8.0.0-RC4:
> > https://github.com/apache/trafficcontrol/compare/v8.0.0-rc4...v8.0.0-rc5
> > <
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC4/CHANGELOG.md
> >
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC5/CHANGELOG.md
> >
> > The artifacts are available for download at:
> > https://dist.apache.org/repos/dist/dev/trafficcontrol/8.0.0/RC5/
> >
> > BLAKE2 checksum:
> >
> >
> a2d12fa11050e20b7ab4c864a058de2781af4a1449e62c5d3cc169fcd6c8bb88dd9f065a2a44d93ed6f64b00802aa0c387f997c7dea0e7331e4b8397022caa68
> >
> > SHA512 checksum:
> >
> >
> cb826938cdf23e053326f5b0de0cea36de8d3825c5803392a1ba1cb8406a753c6d523e2662cc82ac33181a7f295ca7b74c8e72ebe848e64ae4ad3d5a67872667
> >
> > This corresponds to git refs:
> >
> >   Hash:0c515199dbeb3233b32376268e4ee32ad18ebd8b
> >   Tag: RELEASE-8.0.0-RC5
> >
> > Which can be verified with the following command:
> >
> >   $ git tag -v RELEASE-8.0.0-RC5
> >
> > All code signing keys are available here:
> >
> >   https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
> >
> > Make sure you refresh from a key server to get all relevant signatures.
> >
> > The vote is open until 22:00 UTC on Monday, Jan 22nd 2024 and passes
> > if a majority of at least 3 +1 PMC votes are cast.
> >   [ ] +1 approve
> >   [ ] +0 no opinion
> >   [ ] -1 disapprove (and reason why)
> >
> > Thanks!
> > Rima Shah
>
>

Re: [VOTE] Release Apache Traffic Control 8.0.0-RC5

[Zach Hoffman]

+1

-Zach

On Thu, Jan 18, 2024 at 8:15 PM Rawlin Peters  wrote:

> +1
>
> - Rawlin
>
> On Thu, Jan 18, 2024 at 12:28 PM Eric Friedrich  wrote:
> >
> > +1
> >
> > Verified hashes and signature.
> > RPMs built
> >
> > --Eric
> >
> > On Thu, Jan 18, 2024 at 1:33 PM Jeremy Mitchell 
> > wrote:
> >
> > > +1
> > >
> > > On Wed, Jan 17, 2024 at 11:09 AM Rima Shah  wrote:
> > >
> > > > Corrected top link.
> > > >
> > > >  I've prepared a release for 8.0.0-RC5.
> > > >
> > > > Changes since RELEASE-8.0.0-RC4:
> > > >
> https://github.com/apache/trafficcontrol/compare/v8.0.0-rc4...v8.0.0-rc5
> > > >
> > > >
> > > >
> > >
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC5/CHANGELOG.md
> > > >
> > > > Regards,
> > > > Rima Shah
> > > >
> > > > On 2024/01/17 17:48:56 R S wrote:
> > > > > Hello All,
> > > > >
> > > > > I've prepared a release for 8.0.0-RC5. Changes since
> RELEASE-8.0.0-RC4:
> > > > >
> > >
> https://github.com/apache/trafficcontrol/compare/v8.0.0-rc4...v8.0.0-rc5
> > > > >  <
> > > >
> > >
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC4/CHANGELOG.md
> > > > >
> > > >
> > >
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC5/CHANGELOG.md
> > > > >
> > > > > The artifacts are available for download at:
> > > > > https://dist.apache.org/repos/dist/dev/trafficcontrol/8.0.0/RC5/
> > > > >
> > > > > BLAKE2 checksum:
> > > > >
> > > > >
> > > >
> > >
> a2d12fa11050e20b7ab4c864a058de2781af4a1449e62c5d3cc169fcd6c8bb88dd9f065a2a44d93ed6f64b00802aa0c387f997c7dea0e7331e4b8397022caa68
> > > > >
> > > > > SHA512 checksum:
> > > > >
> > > > >
> > > >
> > >
> cb826938cdf23e053326f5b0de0cea36de8d3825c5803392a1ba1cb8406a753c6d523e2662cc82ac33181a7f295ca7b74c8e72ebe848e64ae4ad3d5a67872667
> > > > >
> > > > > This corresponds to git refs:
> > > > >
> > > > >   Hash:0c515199dbeb3233b32376268e4ee32ad18ebd8b
> > > > >   Tag: RELEASE-8.0.0-RC5
> > > > >
> > > > > Which can be verified with the following command:
> > > > >
> > > > >   $ git tag -v RELEASE-8.0.0-RC5
> > > > >
> > > > > All code signing keys are available here:
> > > > >
> > > > >
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
> > > > >
> > > > > Make sure you refresh from a key server to get all relevant
> signatures.
> > > > >
> > > > > The vote is open until 22:00 UTC on Monday, Jan 22nd 2024 and
> passes
> > > > > if a majority of at least 3 +1 PMC votes are cast.
> > > > >   [ ] +1 approve
> > > > >   [ ] +0 no opinion
> > > > >   [ ] -1 disapprove (and reason why)
> > > > >
> > > > > Thanks!
> > > > > Rima Shah
> > > > >
> > > >
> > >
>

Re: [VOTE] Release Apache Traffic Control 8.0.0-RC1

[Zach Hoffman]

./pkg -vb fails to build the documentation. PR to fix: <
https://github.com/apache/trafficcontrol/pull/7815>

-Zach

On Fri, Sep 22, 2023 at 2:29 PM R S  wrote:

> Hello All,
>
> I've prepared a release for 8.0.0-RC1. Changes since RELEASE-8.0.0-RC0:
>
> https://github.com/apache/trafficcontrol/compare/v8.0.0-rc0...v8.0.0-rc1
>
>
> https://github.com/apache/trafficcontrol/blob/RELEASE-8.0.0-RC1/CHANGELOG.md
>
> The artifacts are available for download at:
> https://dist.apache.org/repos/dist/dev/trafficcontrol/8.0.0/RC1/
>
> BLAKE2 checksum:
>
>
> 908e18b6a9a3e4b2a723259901675e57fae45a7cffb448cf4cae7034e5c5f0d4da06f41a10b314e0fe6f40b1fe4913f1c0c8fe1741f2cfe3a5d0fad3a1ab0846
>
> SHA512 checksum:
>
> 584757784f9ac0a7154d7d9b08dcdd59c7c7e743cc973074108f9e2cad0a205a7fd85749ba777f06ff304f1c0987fedb0d884d86add17a0e4629c9c40b9fdd2d
>
> This corresponds to git refs:
>
> Hash: 29cf2890a75b8b2969ebc868990567b822ca733c
> Tag: RELEASE-8.0.0-RC1
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-8.0.0-RC1
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote is open until 22:00 UTC on Wednesday, September 27 and passes
> if a majority of at least 3 +1 PMC votes are cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> Rima Shah
>
> rs...@apache.org
>

Re: Google Summer of Code Summary

[Zach Hoffman]

Thanks for participating in GSoC, Abdulrahman, thanks for the summary and
ideas, and thanks a ton for all of your valuable contributions!

-Zach

On Mon, Sep 11, 2023 at 7:47 PM Abdulrahman Elawady <
abdoelawady...@gmail.com> wrote:

> Hello everyone,
>
> Today marks the end of my Google Summer of Code program. I wanted to thank
> you a lot for this great opportunity. I learnt a lot from you and explored
> technologies I never thought I would.
>
> Although GSoC is over, I will still be contributing to this project. There
> are a lot of ideas to explore and learn about.
>
> I wrote a brief summary of the project and some ideas to explore in the
> future in this GitHub page, if you want to check it out:
> https://abdelrahmanelawady.github.io/GSoC-2023
>
> Thanks,
> Abdulrahman
>

Re: 2023-07-26 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- GSoC contributor Abdul Elawady's Varnish support blueprint is approved
and merged 
- Abdul's PR for Varnish support in t3c plus Varnish in CDN in a Box is
submitted (but needs review) <
https://github.com/apache/trafficcontrol/pull/7669>
- doap_Traffic_Control.rdf <
https://github.com/apache/trafficcontrol/blob/master/doap_Traffic_Control.rdf>
is out-of-date (says the last release was 2021-05-17, also says the
project's only language used is Go)

-Zach

On Wed, Jul 12, 2023 at 2:03 PM ocket   wrote:

>  If you have anything you want to discuss at the next meeting, reply to
> this email and it's on the agenda.
>

Re: 2023-07-12 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Mailing list threads:
Abdelrahman Elawady, PRed a blueprint for Varnish support in T3C <
https://lists.apache.org/thread/tpnbo2kqszyqqtc4ovlxlm59zynjk8r2> <
https://github.com/apache/trafficcontrol/pull/7620>

Submissions for Community Over Code close on 2023-07-13 <
https://lists.apache.org/thread/99yhcfhd2hh69m0rylc1m96xvwdfy7go>

On Wed, Jul 12, 2023 at 9:38 AM ocket   wrote:

> If you have anything you want to discuss at the next meeting, reply to
> this email and it's on the agenda.
>

Re: Help continuity configuration T3C on ATC

[Zach Hoffman]

Hi Thiago,

You'll get more responses if you ask this question in the #traffic-control
(or #traffic-control-cache-config) channel of the ASF Slack, I just sent an
invite. Usually, the dev@ mailing list is for discussion relating to
writing code contributions for ATC.

-Zach

On Wed, Jun 14, 2023 at 11:04 AM Thiago Duarte  wrote:

> Guys, good afternoon.
>
> I started to study the CDN solution created by you and I'm having some
> difficulties in implementing it. I work in the CDN sector here at a
> telecommunication company and we are looking for solutions where we can use
> hardware
> discontinued, but robust for the implementation of the same CDN we have
> today, but proprietary and limited to current content. In these 2 months
> that I started to read and test the applications, we had a result
> very satisfactory with Traffic_Server, because with it we managed to
> deliver content with CTE "Content Transfer Encoding" and thus be able to
> implement the LL "low latency" and today we cannot due to the limitation of
> our CDN.
>
> However, due to the breadth of delivery services that we have today and
> also the number of servers destined for the cache, we would need to
> implement a mechanism where this is done in an automated way.
>
> For that, I saw that we have T3C that replaces Traffic_Orts, but I'm having
> trouble configuring it. Following some "step by step" failures appear when
> trying to connect to Traffic_Ops in addition to access
> in some specific files. Below is the output when I run the line to
> update/collect Traffic_Ops information:
>
>
> -
>
> INFO: t3cutil.go:62: 2023-06-14T16:48:46.395100258Z: Executable path is
> /usr/bin/t3c
> INFO: t3cutil.go:66: 2023-06-14T16:48:46.395144392Z: Return Installdir
> '/usr/bin'
> INFO: config.go:573: 2023-06-14T16:48:46.437205581Z: t3c-apply is running
> in badass mode
> INFO: config.go:573: 2023-06-14T16:48:46.437286401Z: badass setting
> --service-action=restart
> INFO: config.go:573: 2023-06-14T16:48:46.437309194Z: badass setting
> --install-packages=true
> INFO: config.go:573: 2023-06-14T16:48:46.437326988Z: badass setting
> --ignore-update-flag=true
> INFO: config.go:573: 2023-06-14T16:48:46.437344244Z: badass setting
> --update-ipallow=true
> INFO: config.go:580: 2023-06-14T16:48:46.437364542Z: no override for TSHome
> was found, using the configured default: '/opt/trafficserver'
> INFO: config.go:580: 2023-06-14T16:48:46.437384351Z: ATSVersionStr: ''
> DEBUG: config.go:645: 2023-06-14T16:48:46.437401581Z: LogLocationDebug:
> stderr
> DEBUG: config.go:646: 2023-06-14T16:48:46.437416045Z: LogLocationErr:
> stderr
> DEBUG: config.go:647: 2023-06-14T16:48:46.437421436Z: LogLocationInfo:
> stderr
> DEBUG: config.go:648: 2023-06-14T16:48:46.437426715Z: LogLocationWarn:
> stderr
> DEBUG: config.go:649: 2023-06-14T16:48:46.43743202Z: CacheHostName:
> Traffic-Server-EdgeTier
> DEBUG: config.go:650: 2023-06-14T16:48:46.43744862Z: SvcManagement: SystemD
> DEBUG: config.go:651: 2023-06-14T16:48:46.437566341Z: Retries: 3
> DEBUG: config.go:652: 2023-06-14T16:48:46.437598008Z: ReverseProxyDisable:
> false
> DEBUG: config.go:653: 2023-06-14T16:48:46.437611497Z: SkipOSCheck: false
> DEBUG: config.go:654: 2023-06-14T16:48:46.437622931Z: TOInsecure: false
> DEBUG: config.go:655: 2023-06-14T16:48:46.437634195Z: TOTimeoutMS:
> 300
> DEBUG: config.go:656: 2023-06-14T16:48:46.437656158Z: TOUser: tsduarte
> DEBUG: config.go:657: 2023-06-14T16:48:46.437668816Z: TOPass: Pass len: '8'
> DEBUG: config.go:658: 2023-06-14T16:48:46.437681814Z: TOURL:
> https://10.127.226.93
> DEBUG: config.go:659: 2023-06-14T16:48:46.437694057Z: TSHome:
> /opt/trafficserver
> DEBUG: config.go:660: 2023-06-14T16:48:46.437706487Z: LocalATSVersion:
> DEBUG: config.go:661: 2023-06-14T16:48:46.437719044Z: WaitForParents: false
> DEBUG: config.go:662: 2023-06-14T16:48:46.437732333Z: ServiceAction:
> restart
> DEBUG: config.go:663: 2023-06-14T16:48:46.437752158Z:
> NoConfirmServiceAction: false
> DEBUG: config.go:664: 2023-06-14T16:48:46.437765553Z: YumOptions:
> DEBUG: config.go:665: 2023-06-14T16:48:46.437779434Z: MaxmindLocation:
> INFO: t3c-apply.go:103: 2023-06-14T16:48:46.437794049Z: Trying to acquire
> app lock
> INFO: t3c-apply.go:113: 2023-06-14T16:48:46.437850963Z: Acquired app lock
> INFO: actionlog.go:84: 2023-06-14T16:48:46.438094928Z: ACTION='apply-start'
> STATUS='success'
> INFO: t3c-apply.go:140: 2023-06-14T16:48:46.443609812Z: Successfully
> ensured ATS config directory '/opt/trafficserver/etc/trafficserver' is a
> git repo
> ERROR: t3c-apply.go:158: 2023-06-14T16:48:46.443698981Z: checking for git
> lock file: stat returned error: stat
> /opt/tra

Re: 2023-06-07 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- We are about 2.5 weeks into Google Summer of Code <
https://developers.google.com/open-source/gsoc/timeline>! Since the ATC
devs are listed as a GSoC mentor <
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2023+Ideas+list#GSoC2023Ideaslist-GSOCVarnishCachesupportinApacheTrafficControl>,
being available in #trafficcontrol is important.

- As of June 16, trafficserver will have been in EPEL for a year <
https://github.com/apache/trafficserver/issues/6855#issuecomment-1157795660>,
but Traffic Control still does not support using the EPEL trafficserver RPM
.

- The fix for the increased git security changes (<
https://github.com/apache/trafficcontrol/pull/7546> and <
https://github.com/apache/trafficcontrol/pull/7567>) needs to be backported
to the release branches. Currently, all ATC releases are broken if someone
tries to build from the repo.

-Zach

On Wed, May 31, 2023 at 10:04 AM ocket   wrote:

> If you have anything you want to discuss at the next meeting, reply to this
> email and it's on the agenda.
>

Re: 2023-05-17 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

* The call for presentations for Community Over Code 2023 (formerly
ApacheCon) is now open <
https://lists.apache.org/thread/7s4xf2hl69r66p66sw67v58hmztymnqb>.
Tracks:
- Fintech
- Search
- Big Data, Storage
- Big Data, Compute
- Internet of Things
- Groovy
- Incubator
- Community
- Data Engineering
- Performance Engineering
- Geospatial
- API/Microservices
- Frameworks
- Content Wrangling
- Tomcat and httpd
- Cloud and Runtime
- Streaming
- Sustainability

* Google Summer of Code is underway!

* As our Google Summer of Code contributor pointed out, the response body
is not returned for PUT and POST requests in the TO GO library. Should it
be?

On Wed, May 3, 2023 at 10:13 AM ocket   wrote:

>  If you have anything you want to discuss at the next meeting, reply to
> this email and it's on the agenda.
>

Re: 2023-05-03 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

- ASF Infra has disabled GitBox (specifically, <
https://gitbox.apache.org/repos/asf?p=trafficserver.git;a=shortlog;h=9.1.x;hp=9.1.3>
is not working), so we should only depend on GitHub now
- Need to request a "manual approval" exception PR from AS Infra

Mailing list threads:
- 
https://lists.apache.org/thread/21sg0jhs6qxg17lghd83vk77yc04b1xx



On Wed, Apr 19, 2023 at 1:52 PM ocket   wrote:

>  If you have anything you want to discuss at the next meeting, reply to
> this email and it's on the agenda.
>

Re: New committer: Eric Holguin

[Zach Hoffman]

Great job, Eric!

-Zach

On Mon, Apr 24, 2023 at 4:42 PM Jeremy Mitchell 
wrote:

> The Project Management Committee (PMC) for Apache Traffic Control has
> invited Eric Holguin to become a committer, and we are pleased to announce
> that he has accepted!
>
> He has been contributing to ATC since 2019 and has primarily been focused
> on testing. He has opened over 70 issues (bugs or improvements) and has
> also had over 80 pull requests merged. He is also responsible for adding
> codecov to the ATC repository to highlight code coverage metrics for each
> ATC component.
>
> Being a committer enables easier contribution to the project since
> there is no need to go via the patch submission process. This should
> enable better productivity.
>
> Thanks,
>
> Jeremy Mitchell
>

Re: 2023-04-05 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

consider discussing:

- Trafic Ops testsing now includes API contract tests <
https://github.com/apache/trafficcontrol/tree/67cf92d665/traffic_ops/testing/api_contract>,
which are written in Python. Should we have a Pylint GHA?

- Apache Infra turning of GitHub Actions from automatically running for a
project's past contributors has slowed down PR review, so we should file an
exception like . But
that will require first making our GHAs compliant with Infra's security
standards .

- Google Summer of Code updates

On Wed, Mar 22, 2023 at 10:36 AM ocket   wrote:

>  If you have anything you want to discuss at the next meeting, reply to
> this email and it's on the agenda.
>

Re: 2023-03-22 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- As of this last Monday, Apache Infra has turned off GitHub Actions from
automatically running for a project's past contributors because they're
concerned that someone will hijack one of those contributors' accounts <
https://infra.apache.org/github-actions-policy.html>. Do we want to file an
exception like ?

- Google Summer of Code updates?

-Zach

On Wed, Mar 8, 2023 at 10:21 AM ocket   wrote:

>  If you have anything you want to discuss at the next meeting, reply to
> this email and it's on the agenda
>

Re: 2023-03-08 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

- Should we update to github.com/apache/trafficcontrol/v7 to fix `go get`
issues for ATC users?
- Since ApacheCon is in-person-only this year, would we have better
attendance doing an online TrafficControl summit?

-Zach

On Wed, Feb 22, 2023 at 10:02 AM ocket   wrote:

>  If you have anything you want to discuss at the next meeting, reply to
> this email and it's on the agenda.
>

Fwd: Google Summer of Code 2023 Mentor Registration

[Zach Hoffman]

Apache has been accepted for GSoC 2023, and it's not too late to submit
ideas for Summer of Code. If you are interested in mentoring a project and
are an ATC committer, you can subscribe to ment...@community.apache.org to
get updates.

-Zach

-- Forwarded message -
From: Sanyam Goel 
Date: Thu, Mar 2, 2023 at 6:56 AM
Subject: Google Summer of Code 2023 Mentor Registration
To: 
Cc: , Maxim Solodovnik 


Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted
organizations for
Google Summer of Code 2023! [1,2]

It is now time for mentors to sign up, so please pass this email on to your
community and podlings.
If you aren’t already subscribed to ment...@community.apache.org
you should do so now else you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and
PMC acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an *acknowledgement* from the PMC for which you want to mentor
projects. Use the *below template* and *do not forget to copy
ment...@community.apache.org*. We will
use the email address you indicate to send the invite to be a mentor for
Apache.

PMCs, read carefully, please.

We request that each mentor is acknowledged by a PMC member. This is to
ensure the mentor is in good standing with the community. When you receive
a request for
acknowledgement, please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see the
previous emails for details).
GSoC participants will now begin to explore ideas so if you haven’t already
done so, record your ideas
immediately!

Cheers,
Sanyam


*Mentor request email template:*

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2023 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code
2023 projects for Apache Software Foundation
.

I would like to receive the mentor invite to 






[1] https://summerofcode.withgoogle.com/programs/2023/organizations
[2]
https://summerofcode.withgoogle.com/programs/2023/organizations/apache-software-foundation
[3] https://summerofcode.withgoogle.com/

Re: 2023-02-22 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Should we have a CDN track at ApacheCon this year?

-Zach

On Wed, Feb 22, 2023 at 8:40 AM Holguin, Eric
 wrote:

> I heard that all of the gorilla libraries have been archived, how does it
> affect us?
>
> From: ocket  
> Date: Wednesday, February 8, 2023 at 10:32 AM
> To: dev@trafficcontrol.apache.org 
> Subject: [EXTERNAL] 2023-02-22 TC Working Group Agenda and Meeting Notes
> If you have anything you want to discuss at the next meeting, reply to this
> email and it's on the agenda.
>

Re: New Committer: Rima Shah

[Zach Hoffman]

Good job, Rima!

-Zach

On Thu, Feb 16, 2023 at 2:44 AM ocket   wrote:

> The Project Management Committee (PMC) for Apache Traffic Control
> has invited Rima Shah to become a committer and we are pleased
> to announce that they have accepted.
>
> Being a committer enables easier contribution to the
> project since there is no need to go via the patch
> submission process. This should enable better productivity.
>

Fwd: [Urgent] GSoC 2023 Project Ideas

[Zach Hoffman]

In order to participate in Google Summer of Code this year, ASF needs us
need to create proposals *before* they send in their application (right
away, it sounds like, since the last day for organizations to apply was
yesterday), which is different than previous years.

Create proposals here:
https://issues.apache.org/jira/secure/CreateIssue!default.jspa

The 2022 ideas list:
https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2022+Ideas+list

-Zach

-- Forwarded message -
From: Swapnil M Mane 
Date: Thu, Feb 9, 2023 at 8:26 AM
Subject: [Urgent] GSoC 2023 Project Ideas
To: 
Cc: Maxim Solodovnik , Sanyam Goel ,
, Swapnil M Mane 


Dear mentors,
Thank you for making our GSoC participation in previous years a success.
We highly appreciate your constant support.

We have submitted the GSoC 2023 application on behalf of ASF and have
started collecting project ideas.

**Important** - We have received an update from the GSoC team. It
seems as per some recent guideline changes, they require the project
ideas upfront to process our application.
So collecting project ideas became an URGENT task for us.

If you have any pending tasks from GSoC 2022 or have any new ideas for
the upcoming GSoC 2023, please create a Jira ticket and label it with
"gsoc2023".

There will be two types of projects this year ~175 hours (medium)
and 350 hours (large). There is an option to extend the standard
12-week coding time
frame to a maximum of 22 weeks.
Please add "full-time" label to the JIRA for the 350-hour project OR
"part-time" label for 175 hours project.


So, you will need to add the "gsoc2023" label and ("full-time" OR
"part-time") label to your Jira ticket. More details are available
here.
https://community.apache.org/gsoc.html#prospective-asf-mentors-read-this

We apologize for the short notice and look forward to your prompt
support. Please feel to reach out to us if you got any questions.

Best Regards,
Swapnil M Mane,
On behalf of ASF GSoC Admins

Re: 2023-02-08 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Also, an agenda item from the 2023-01-18 TC WG meeting:
> Consider discussing next time (when Eric Holguin is available for
comment): the PR to remove unused portions of the repository

-Zach

On Wed, Feb 8, 2023 at 9:32 AM Zach Hoffman  wrote:

> Consider discussing:
> - Now that the ATS "Update to 9.1.x" PR was merged, should Alpine image
> build from a branch like the ATS RPM is?
> - Summer of Code 2023 discussions are ramping up, does ATC want to
> participate?
>
> -Zach
>

2023-02-08 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- Now that the ATS "Update to 9.1.x" PR was merged, should Alpine image
build from a branch like the ATS RPM is?
- Summer of Code 2023 discussions are ramping up, does ATC want to
participate?

-Zach

Re: TC Working group meeting frequency

[Zach Hoffman]

+1 for changing it. Working group meetings were originally once a month. 1
week seems a little frequent, but 2 weeks seems just right.

-Zach

On Thu, Jan 19, 2023 at 2:44 PM Steve Hamrick  wrote:

> I'm +1 on changing it. Worst case we can always switch back.
>
> On Wed, Jan 18, 2023 at 9:51 AM ocket   wrote:
> >
> > It's been proposed that we move the weekly TC WG meetings to a bi-weekly
> > cadence. I'd like to take a vote to see how people feel about that.
> >
> > Personally I'm -0. Weekly will make me feel more important because I
> have a
> > meeting to run more often. But actually it doesn't really matter either
> > way. So at the moment from a quick poll in the WG huddle, we are at +1 in
> > favor of bi-weekly atm.
>

Re: 2023-01-18 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

- Move to bi-weekly TC WG meetings?
- The slack invite request always gets caught in ASF Infra's spam filter,
it should be whiteliste

On Wed, Jan 11, 2023 at 10:07 AM ocket   wrote:

>  If you have anything you want to discuss at next week's meeting, respond
> to this email and it's on the agenda.
>

Re: 2022-11-30 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

- We have Codecov now, thanks @ericholguin! How to take advantage of it?
- Any other integrations we should add to the TC repo?

-Zach

On Wed, Nov 23, 2022 at 9:40 AM ocket   wrote:

>  If you have anything you want to discuss at next week's meeting respond to
> this email and it's on the agenda.
>

Re: 2022-11-15 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

- TC Working Group moving to 16:30-17:30 UTC on Wednesdays
- If we add unit tests for Traffic Portal v1, could we remove some flaky
integration tests?
- Why do we have so many stale issues?

Active mailing list threadsA:

- TC Working Group meeting time <
https://lists.apache.org/thread/j9z4krhfg2s9wsx642bfrwyj2nfn03zt>

-Zach

On Tue, Nov 8, 2022 at 10:41 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting
> respond to this email and it's on the agenda.
>

Re: TC Working Group meeting time

[Zach Hoffman]

We had 4 voters, and the only time slot that works for everyone is
Wednesday:

[image: 2022-11-15 TC Working Group meeting time poll.png]
So, let's move the TC Working Group meeting time to 16:30-17:30 UTC on
Wednesdays starting next week.

-Zach

On Thu, Nov 10, 2022 at 10:57 AM Zach Hoffman  wrote:

> The current TC Working Group meeting time (Tuesdays from 16:15 to 17:15
> UTC) does not work for several people, myself included. How do attendees
> feel about 16:30 to 17:30 UTC on Mondays or Wednesdays instead?
>
> If you attend the TC Working Group or want to, please fill out this survey
> to indicate which time slots would work for you (you can check more than
> one):
> https://docs.google.com/forms/d/1kWe9EOj2AMOEynCMN-p7tEOo6cHvEPR4y-0-iezh61g
>
> Let's keep the survey open at least 72 hours for participation.
>
> -Zach
>

TC Working Group meeting time

[Zach Hoffman]

The current TC Working Group meeting time (Tuesdays from 16:15 to 17:15
UTC) does not work for several people, myself included. How do attendees
feel about 16:30 to 17:30 UTC on Mondays or Wednesdays instead?

If you attend the TC Working Group or want to, please fill out this survey
to indicate which time slots would work for you (you can check more than
one):
https://docs.google.com/forms/d/1kWe9EOj2AMOEynCMN-p7tEOo6cHvEPR4y-0-iezh61g

Let's keep the survey open at least 72 hours for participation.

-Zach

Re: 2022-11-08 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

> This is an issue when using nerdctl that happens outside of arm64 and is
not limited to Traffic Router, more investigation is needed to get nerdctl
working for all TC components.

The reason Traffic Router in CDN in a Box for Developers does not work
directly in nerdctl/containerd is that the user running Traffic Router in
that container is not root, it is trying to bind to ports under 1024, and
containerd, unlike docker <
https://github.com/moby/moby/blob/v20.10.21/daemon/oci_linux.go#L776-L779>,
does not automatically let any user bind to ports under 1024. This is fixed
for nerdctl in CDN in a Box for Developers in #7142 <
https://github.com/apache/trafficcontrol/pull/7142/commits/a8ee3be92b>.

> > Traffic Router seemingly doesn't work on arm64, despite being not tied
to an architecture
> How exactly does it not work? It seems to run ok for me on an arm64
(Apple M1).

Maybe worth noting that the Traffic Router RPM is noarch now as of <
https://github.com/apache/trafficcontrol/pull/7176>.

-Zach

On Wed, Nov 9, 2022 at 3:34 PM Holguin, Eric
 wrote:

> > How exactly does it not work? It seems to run ok for me on an arm64
> (Apple M1).
>
> This is an issue when using nerdctl that happens outside of arm64 and is
> not limited to Traffic Router, more investigation is needed to get nerdctl
> working for all TC components.
>
> From: Rawlin Peters 
> Date: Wednesday, November 9, 2022 at 2:36 PM
> To: dev@trafficcontrol.apache.org 
> Subject: [EXTERNAL] Re: 2022-11-08 TC Working Group Agenda and Meeting
> Notes
> > Traffic Router seemingly doesn't work on arm64, despite being
> not tied to an architecture
>
> How exactly does it not work? It seems to run ok for me on an arm64 (Apple
> M1).
>
> On Tue, Nov 8, 2022 at 10:40 AM ocket   wrote:
> >
> > 1. Attendance
> > - Srijeet Chatterjee
> > - Zach Hoffman
> > 2. arm64 suport updates
> > - builder images now support arm64
> > - PR #7176 makes the build system support arm64
> > - Traffic Router seemingly doesn't work on arm64, despite being
> > not tied to an architecture
> > - podman and rancher don't work either - but also not directly
> > using containerd
> > 3. Issue Grooming
> > - #6161 - left a comment noting that the issue still exists, added
> > "low impact" and "low difficulty" labels
> > - #7045 - Needs rebase, needs outstanding review feedback addressed
> > - #6454 - No action
> > - #6871 - Change title to be more accurate/appropriate
> > - #3537 - Add comment asking if an issue should be opened to track
> > the effort to move from parent.config to strategies.yaml
> > - #3086 - Added "bug" label
> > - #4023 - left comment asking if the system_stats ATS plugin
> > solves the issue
> > - #957 - Added "Needs more Info" label
> > - #1131 - Left a comment asking if the newer spec file in the
> > cache-config tests directory should replace the older one under the
> > top-level traffic_server directory
> > - #2293 - Added "high difficulty" label
> >
> > On Tue, Nov 8, 2022 at 9:21 AM Zach Hoffman 
> wrote:
> > >
> > > Consider discussing:
> > > - aarch suport updates:
> > > * The builder images now support arm64
> > > * PR to make the build system support aarch64 <
> https://github.com/apache/trafficcontrol/pull/7176>
> > >
> > > On Tue, Nov 1, 2022 at 10:17 AM ocket  
> wrote:
> > >
> > > > If you have anything you want to discuss at next week's meeting
> > > > respond to this email and it's on the agenda.
> > > >
>

Re: 2022-11-08 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- aarch suport updates:
* The builder images now support arm64
* PR to make the build system support aarch64 <
https://github.com/apache/trafficcontrol/pull/7176>

On Tue, Nov 1, 2022 at 10:17 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting
> respond to this email and it's on the agenda.
>

Re: 2022-11-01 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Considering discussing

* Revisiting aarch64 support:
- The `ghcr.io/apache/trafficcontrol/ci/trafficserver-alpine` Docker
image was was x86_64-only, a PR is out there that builds it or arm64 too <
https://github.com/apache/trafficcontrol/pull/7165>
- What parts of the repo do not currently work for aarch64 users?

* Hacktoberfest summary

* No active mailing lists

On Tue, Nov 1, 2022 at 9:15 AM Zach Hoffman  wrote:

> If you have anything you want to discuss at next week's meeting respond
> to this email and it's on the agenda.
>

2022-11-01 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

If you have anything you want to discuss at next week's meeting respond
to this email and it's on the agenda.

Re: 2022-10-25 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

- Would a different TC working group time get better participation?

On Tue, Oct 25, 2022 at 9:20 AM Zach Hoffman  wrote:

> If you have anything you want to discuss at next week's meeting respond
> to this email and it's on the agenda.
>
> Consider discussing:
>
> - What would be the benefits and drawbacks from splitting T3C out into its
> own repo?
> - What would it take to update Traffic Router (and the Java TO client) to
> OpenJDK 13?
>
> -Zach
>

2022-10-25 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

If you have anything you want to discuss at next week's meeting respond
to this email and it's on the agenda.

Consider discussing:

- What would be the benefits and drawbacks from splitting T3C out into its
own repo?
- What would it take to update Traffic Router (and the Java TO client) to
OpenJDK 13?

-Zach

Re: 2022-10-04 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- Hacktoberfest says, to projects wanting to accept Hacktoberfest
contributions :
> * Add the “hacktoberfest” topic to your repository to opt-in to
Hacktoberfest and indicate you’re looking for contributions.
> * Apply the “hacktoberfest” label to issues you want contributors to
help with in your GitHub or GitLab project.
> * Choose issues that have a well-defined scope and are self-contained.
> * Adopt a code of conduct to create a greater sense of inclusion and
community for contributors.
> * Be ready to review pull/merge requests, accepting those that are
valid by merging them, leaving an overall approving review, or by adding
the “hacktoberfest-accepted” label.
> * Reject any spammy requests you receive by labeling them as “spam,”
and any other invalid contributions by closing them or labeling them as
“invalid.”

Active mailing list threads:
- Converting Traffic Router to Kotlin would be easy <
https://lists.apache.org/thread/2frjxnkw10hbthvgll5pckt5kcpl111h>

-Zach

On Tue, Sep 27, 2022 at 9:27 AM Taylor Frey  wrote:

> If you have anything you want to discuss at next week's meeting
> respond to this email and it's on the agenda.
>

Re: [EXTERNAL] Converting Traffic Router to Kotlin would be easy

[Zach Hoffman]

t; > making
> > > > small, incremental improvements to the cleanliness of TR with minimal
> > > risk
> > > > to stability.
> > > >
> > > >
> > > > Somewhat less of a concern is shrinking the pool of developers by
> > > choosing
> > > > a less mature, less widely adopted language. I understand Kotlin is
> on
> > > the
> > > > rise and is in demand but is still dwarfed by the 20+ years of Java.
> > > >
> > > > --Eric
> > > >
> > > >
> > > >
> > > > On Tue, Jun 22, 2021, 7:14 PM Chris Lemmons 
> > wrote:
> > > >
> > > > > I don't have a strong opinion on Kotlin; I haven't used it to any
> > real
> > > > > degree. I do know it interoperates with the Java API and compiles
> > down
> > > > > to the JVM. So in terms of the openness of the platform, it's not
> any
> > > > > more "open" than Oracle's OpenJDK. It does compile down to native
> > > > > code, but then we'd need to replace (or convert and maintain) all
> our
> > > > > dependent libraries.
> > > > >
> > > > > So if Kotlin helps with maintainability, I say we go for it. I
> don't
> > > > > know that we're winning any additional openness we don't already
> > have,
> > > > > though.
> > > > >
> > > > > On Tue, Jun 22, 2021 at 4:44 PM Taylor Frey  >
> > > wrote:
> > > > > >
> > > > > > I too +1
> > > > > >
> > > > > > My experience porting a Java project to Kotlin was specific to
> > > Android in
> > > > > > the past (re: years ago). I recall my general impression of
> Kotlin
> > to
> > > > > have
> > > > > > some extraneous and unnecessary syntactic sugar (What's up with
> the
> > > > > > for/loop keywords?), but it was an overall solid language. I
> > > appreciate
> > > > > the
> > > > > > terseness and brevity of things like variable declarations w/
> > > implicit
> > > > > data
> > > > > > types and `data classes`, which addresses a long standing
> complaint
> > > about
> > > > > > Java's overly verbose syntax. Language aside, the automated
> porting
> > > back
> > > > > > then wasn't exactly perfect, but a few things have changed since
> > > then; 1)
> > > > > > the language specification has solidified over the years, 2)
> > tooling
> > > has
> > > > > > matured, and 3) is manageable to manually intervene if necessary.
> > > > > >
> > > > > > > As a side note, because of Oracle's aggressive legal practices,
> > and
> > > > > > because
> > > > > > they really do want you to think that they own Java (see:
> > Google
> > > LLC
> > > > > v.
> > > > > > Oracle America, Inc.), using Java in Apache Traffic Control
> is
> > > not
> > > > > > really
> > > > > > in the spirit of free software. Kotlin is an Apache
> > 2.0-licensed
> > > > > > project,
> > > > > > so switching to Kotlin would be a true FOSS win for the ATC
> > > > > community.
> > > > > >
> > > > > > I think the true benefit is moving away from the Java API, which
> is
> > > under
> > > > > > such contention, without changing underlying implementation (such
> > as
> > > a
> > > > > > transition to another, non-JVM, language might incur).
> > > > > >
> > > > > > On Tue, Jun 22, 2021 at 11:42 AM Chatterjee, Srijeet
> > > > > >  wrote:
> > > > > >
> > > > > > > +1
> > > > > > > Sounds like a fun project!
> > > > > > >
> > > > > > > --Srijeet
> > > > > > >
> > > > > > > On 6/21/21, 8:43 PM, "Zach Hoffman" 
> > wrote:
> > > > > > >
> > > > > > > Hi Traffic Control!
> > > > > > >
> > > > > > > As you all may know, the current implementation of Traffic
> > > Router
> > > > > runs
> > > > > > > 

Re: Slack Invite request

[Zach Hoffman]

Invite sent!

-Zach

On Thu, Sep 29, 2022 at 5:55 AM Tim Arnold  wrote:

> Will someone please invite me to the ASF Slack so I can join the
> #traffic-control channel?

Re: Slack Invite request

[Zach Hoffman]

Invited!

-Zach

On Fri, Sep 23, 2022 at 1:37 PM Alihussain Lilamwala, Ammar (Network Data
Science Manager)  wrote:

> Will someone please invite me to the ASF Slack so I can join the
> #traffic-control channel?
>
> Kind Regards
> Ammar Lilamwala
> Content Distribution and Strategy Manager
> Network Data Science & Software | Network Planning & Operations
> Group Comms & Infrastructure | Sky
>
> Information in this email including any attachments may be privileged,
> confidential and is intended exclusively for the addressee. The views
> expressed may not be official policy, but the personal views of the
> originator. If you have received it in error, please notify the sender by
> return e-mail and delete it from your system. You should not reproduce,
> distribute, store, retransmit, use or disclose its contents to anyone.
> Please note we reserve the right to monitor all e-mail communication
> through our internal and external networks. SKY and the SKY marks are
> trademarks of Sky Limited and Sky International AG and are used under
> licence.
>
> Sky UK Limited (Registration No. 2906991), Sky-In-Home Service Limited
> (Registration No. 2067075), Sky Subscribers Services Limited (Registration
> No. 2340150) and Sky CP Limited (Registration No. 9513259) are direct or
> indirect subsidiaries of Sky Limited (Registration No. 2247735). All of the
> companies mentioned in this paragraph are incorporated in England and Wales
> and share the same registered office at Grant Way, Isleworth, Middlesex TW7
> 5QD
>

Re: [EXTERNAL] Converting Traffic Router to Kotlin would be easy

[Zach Hoffman]

ility.
> Some
> > > > of the nastier bugs in TR have stemmed from NullPointerExceptions due
> > > > to not knowing that an argument was nullable, and with Kotlin's
> > > > built-in nullable vs non-nullable types, that problem is way less
> > > > likely to occur.
> > > >
> > > > If we were to develop TR 2.0 for instance (instead of just converting
> > > > TR 1.0), I'd hope we could use a language like Kotlin which has
> solved
> > > > the Billion Dollar Mistake.
> > > >
> > > > - Rawlin
> > > >
> > > > On Tue, Jun 22, 2021 at 9:14 PM Eric Friedrich 
> > > wrote:
> > > > >
> > > > > Zach-
> > > > >
> > > > >   First of all, thanks for trying to build a bigger tent here, I
> really
> > > > > appreciate that effort.
> > > > >
> > > > > (Personal comments, not as chair)
> > > > >
> > > > > I agree that Traffic Router is difficult to work on, and that
> presents
> > > a
> > > > > large barrier to entry. However, I don't think that is a result of
> > > > language
> > > > > choice. Rather, I think the TR code itself is badly in need of a
> clean
> > > > up,
> > > > > to improve modularity and to give some thought to extensibility.
> > > > >
> > > > > Recently one of my coworkers added a new feature to TR. He is
> > > incredibly
> > > > > experienced with Java, but had many problems trying to create a
> clean
> > > > > integration.
> > > > >
> > > > > Converting TR to Kotlin wouldn't improve or solve any of these
> issues.
> > > I
> > > > > fear that even as we try to attract new contributors,  they would
> be
> > > > > frustrated with the state of TR and not continue as ongoing
> > > contributors.
> > > > >
> > > > > The solution to that is not easy, nor is it fast. It's a process of
> > > > making
> > > > > small, incremental improvements to the cleanliness of TR with
> minimal
> > > > risk
> > > > > to stability.
> > > > >
> > > > >
> > > > > Somewhat less of a concern is shrinking the pool of developers by
> > > > choosing
> > > > > a less mature, less widely adopted language. I understand Kotlin
> is on
> > > > the
> > > > > rise and is in demand but is still dwarfed by the 20+ years of
> Java.
> > > > >
> > > > > --Eric
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Jun 22, 2021, 7:14 PM Chris Lemmons 
> > > wrote:
> > > > >
> > > > > > I don't have a strong opinion on Kotlin; I haven't used it to any
> > > real
> > > > > > degree. I do know it interoperates with the Java API and compiles
> > > down
> > > > > > to the JVM. So in terms of the openness of the platform, it's
> not any
> > > > > > more "open" than Oracle's OpenJDK. It does compile down to native
> > > > > > code, but then we'd need to replace (or convert and maintain)
> all our
> > > > > > dependent libraries.
> > > > > >
> > > > > > So if Kotlin helps with maintainability, I say we go for it. I
> don't
> > > > > > know that we're winning any additional openness we don't already
> > > have,
> > > > > > though.
> > > > > >
> > > > > > On Tue, Jun 22, 2021 at 4:44 PM Taylor Frey <
> taylor.f...@gmail.com>
> > > > wrote:
> > > > > > >
> > > > > > > I too +1
> > > > > > >
> > > > > > > My experience porting a Java project to Kotlin was specific to
> > > > Android in
> > > > > > > the past (re: years ago). I recall my general impression of
> Kotlin
> > > to
> > > > > > have
> > > > > > > some extraneous and unnecessary syntactic sugar (What's up
> with the
> > > > > > > for/loop keywords?), but it was an overall solid language. I
> > > > appreciate
> > > > > > the
> > > > > > > terseness and brevity of things like variable de

Re: 2022-08-30 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- We should use ATS 9.1 everywhere where ATC is currently using ATS 8.1
- When should we support Rocky Linux 9 (RHEL 9)?

Active mailing list threads:

- [ANNOUNCE] Release Apache Traffic Control 7.0.1 <
https://lists.apache.org/thread/ghl847dgpm2zwhnm3yq03l29ybh8os6d>

-Zach

On Tue, Aug 23, 2022 at 9:30 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting
> respond to this email and it's on the agenda.
>

Re: [VOTE] Release Apache Traffic Control 7.0.1-RC0

[Zach Hoffman]

+1

On Wed, Aug 24, 2022 at 10:33 AM ocket   wrote:

> Confirmed the fix. +1
>
> On Wed, Aug 24, 2022 at 9:09 AM Rawlin Peters  wrote:
> >
> > +1
> >
> > - Rawlin
> >
> >
> > On Tue, Aug 23, 2022 at 10:02 AM Jeremy Mitchell 
> wrote:
> > >
> > > +1
> > >
> > > On Wed, Aug 17, 2022 at 1:01 PM Steve Hamrick 
> wrote:
> > >
> > > > Correction, the vote will remain open for at least 72 hours and will
> close
> > > > *after* *19:00 UTC August 20th*.
> > > >
> > > > Thanks,
> > > > Steve Hamrick shamr...@apache.org
> > > >
> > > >
> > > > On Wed, Aug 17, 2022 at 12:54 PM Steve Hamrick 
> > > > wrote:
> > > >
> > > > > Hello All,
> > > > >
> > > > > I've prepared a release for 7.0.1-RC0. Changes since RELEASE-7.0.0
> > > > >
> > > > >
> > > >
> https://github.com/apache/trafficcontrol/compare/RELEASE-7.0.0...RELEASE-7.0.1-RC0
> > > > >
> > > >
> https://github.com/apache/trafficcontrol/blob/RELEASE-7.0.1-RC0/CHANGELOG.md
> > > > >
> > > > > The artifacts are available for download at:
> > > > >
> > > > >
> https://dist.apache.org/repos/dist/dev/trafficcontrol/7.0.1/RC0
> > > > >
> > > > > BLAKE2 checksum:
> > > > >
> > > >
> 2838f959fa8832cbdf6ea35c8271b4e8c17996f53d91817b6a55c619a0006c4686fa7ecde0fa76cd40b9e327ab8e738c0e5fd1e7d9e5e8acc795f5e9cd38d0f5
> > > > apache-trafficcontrol-7.0.1.tar.gz
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > SHA512 checksum:
> > > > >
> > > >
> fc6c7328979d0ed369bb76ac6bd2a961aa626f905bb8a9e192f2ca703e2f888053ebd4b5e63381023229b9f2544cf1161f55c59e38ab6a82ac9aef52f7e8462f
> > > > apache-trafficcontrol-7.0.1.tar.gz
> > > > >
> > > > >
> > > > > This corresponds to git refs:
> > > > >
> > > > >   Hash: c076b138a88d21daf1a17d594b83f4c03020c179
> > > > >   Tag: RELEASE-7.0.1-RC0
> > > > >
> > > > > Which can be verified with the following command:
> > > > >
> > > > >   $ git tag -v RELEASE-7.0.1-RC0
> > > > >
> > > > > All code signing keys are available here:
> > > > >
> > > > >
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
> > > > >
> > > > > Make sure you refresh from a key server to get all relevant
> signatures.
> > > > >
> > > > > The vote will remain open for at least 72 hours (15:00 UTC on
> Sunday,
> > > > > July 24th) and passes if a majority of at least 3 +1 PMC votes are
> > > > > cast.
> > > > >   [ ] +1 approve
> > > > >   [ ] +0 no opinion
> > > > >   [ ] -1 disapprove (and reason why)
> > > > >
> > > > > Thanks!
> > > > > Steve Hamrick shamr...@apache.org
> > > > >
> > > > >
> > > >
>

Re: 2022-08-23 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Active mailing list threads:
- [VOTE] Release Apache Traffic Control 7.0.1-RC0 <
https://lists.apache.org/thread/fy4vrs4zk5y2k99kcznp0z6xcnbjyq9k>

On Tue, Aug 16, 2022 at 9:36 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting
> respond to this email and it's on the agenda.
>

Re: 2022-08-16 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Active mailing list threads:

- [ANNOUNCE] Release Apache Traffic Control 7.0.0 <
https://lists.apache.org/thread/gy4g3dwwxsnwhhkrhtj9lbtqhj7xh18v>

On Tue, Aug 16, 2022 at 9:15 AM Jeremy Mitchell 
wrote:

> Our goal is quarterly releases. 7.0 was the Q2 release. What is the Q3
> release going to be? 7.1, 8.0?
>
> On Tue, Aug 16, 2022 at 9:12 AM Steve Hamrick  wrote:
>
> > Discuss View Profile > DS's TP bug in 7.0.0.
> >
> > On Tue, Aug 9, 2022 at 10:16 AM ocket   wrote:
> >
> > > If you have anything you want to discuss at next week's meeting
> > > respond to this email and it's on the agenda.
> > >
> >
>

Re: [EXTERNAL] Re: 2022-08-02 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

> 3. Using the EPEL Traffic Server RPM is not supported <
https://github.com/apache/trafficcontrol/issues/6871>
> - Evan's working on it

Nono, Evan (trafficserver committer and PMC member eze) is working on
getting the ATS RPM used by the t3c integration tests to support ATS 9.1.x,
different issue <https://github.com/apache/trafficcontrol/issues/7006>

-Zach

On Tue, Aug 9, 2022 at 10:16 AM ocket   wrote:

> 0. Due to scheduling conflicts, this meeting was pushed to 2022-08-09
> 1. Attendance
>     - Stephen Hamrick
> - Zach Hoffman
> - Srijeet Chatterjee
> - Eric Holguin
> - Joshua Zenn
> - Taylor Frey
> - Ashish Paudyal
> 2. Do we want to support Swagger in the TO API?
> - Tabled because the person who was asking about isn't around to
> extoll its virtue
> - Could be very complex, we should announce a depreciation to
> force people to speak up in its defense.
> 3. Using the EPEL Traffic Server RPM is not supported
> - Evan's working on it
> - biggest issue is the /opt/trafficserver installation prefix.
> - #6871 tracks the problem
> 4. ML: 7.0.0 is approved
> - Official release announcement expected today
> 5. ML: TC changelog
> - It's probably better to add tags to change-log lines instead of
> splitting by component, to avoid duplicates
> - a GHA could be written to suggest to people what to use for tags
> - Needs Mailing list decision
>
> On Tue, Aug 9, 2022 at 9:26 AM Zach Hoffman  wrote:
> >
> > Consider discussion:
> > - Do we want to support Swagger in the Traffic Ops API?
> > - Using the EPEL Traffic Server RPM is not supported (
> >
> https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/issues/6871__;!!CQl3mcHX2A!G-CdXfrF3I17BtsU8Med_x_aEME5X6Od2mSugAvD8euQrwHTRbSLdvQ57fq3LZ3NSuHhoIf7qpUj2osFZnMB$
> )
> >
> > Active mailing list threads:
> > - [RESULT][VOTE] Release Apache Traffic Control 7.0.0-RC2 <
> >
> https://urldefense.com/v3/__https://lists.apache.org/thread/oc6t7grh1sk40ck95mtyxmk3f53fdvps__;!!CQl3mcHX2A!G-CdXfrF3I17BtsU8Med_x_aEME5X6Od2mSugAvD8euQrwHTRbSLdvQ57fq3LZ3NSuHhoIf7qpUj2jC-x1VR$
> >
> > - TC change log <
> >
> https://urldefense.com/v3/__https://lists.apache.org/thread/93k7qkr54kjyt43c8y5p686wv0b2t7r6__;!!CQl3mcHX2A!G-CdXfrF3I17BtsU8Med_x_aEME5X6Od2mSugAvD8euQrwHTRbSLdvQ57fq3LZ3NSuHhoIf7qpUj2jsyLLyr$
> >
> >
> > -ach
> >
> > On Tue, Jul 26, 2022 at 10:17 AM ocket   wrote:
> >
> > > If you have anything you want to discuss at next week's meeting
> > > respond to this email and it's on the agenda.
> > >
>

Re: 2022-08-02 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussion:
- Do we want to support Swagger in the Traffic Ops API?
- Using the EPEL Traffic Server RPM is not supported (
https://github.com/apache/trafficcontrol/issues/6871)

Active mailing list threads:
- [RESULT][VOTE] Release Apache Traffic Control 7.0.0-RC2 <
https://lists.apache.org/thread/oc6t7grh1sk40ck95mtyxmk3f53fdvps>
- TC change log <
https://lists.apache.org/thread/93k7qkr54kjyt43c8y5p686wv0b2t7r6>

-ach

On Tue, Jul 26, 2022 at 10:17 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting
> respond to this email and it's on the agenda.
>

Re: 2022-07-26 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Active mailing list threads:
* [VOTE] Release Apache Traffic Control 7.0.0-RC2 <
https://lists.apache.org/thread/5h41gc90jbh8knbwxp1q60jnp75g8mcg>

On Tue, Jul 19, 2022 at 10:22 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting
> respond to this email and it's on the agenda.
>

Re: [VOTE] Release Apache Traffic Control 7.0.0-RC2

[Zach Hoffman]

+1, weasel passes, and default and optional components build as expected

-Zach

On Thu, Jul 21, 2022 at 10:44 AM Steve Hamrick  wrote:

> Hello All,
>
> I've prepared a release for 7.0.0-RC2. Changes since RELEASE-6.1.0
>
>
> https://github.com/apache/trafficcontrol/compare/RELEASE-6.1.0...RELEASE-7.0.0-RC2
>
> https://github.com/apache/trafficcontrol/blob/RELEASE-7.0.0-RC2/CHANGELOG.md
>
> The artifacts are available for download at:
>
> https://dist.apache.org/repos/dist/dev/trafficcontrol/7.0.0/RC2
>
> Change since previous RCs
>
>
> https://github.com/apache/trafficcontrol/compare/RELEASE-7.0.0-RC0..RELEASE-7.0.0-RC2
>
> https://github.com/apache/trafficcontrol/compare/RELEASE-7.0.0-RC1..RELEASE-7.0.0-RC2
>
> BLAKE2 checksum:
>
> 64451309b850a3381a18f78a0ed48531c2bb970dc4909d20257eb6686afb94f3e3e114e42439f8c6edf7fee0b08739968628eac7df2dc138cffd34eb7b08b736
>  apache-trafficcontrol-7.0.0.tar.gz
>
>
>
> SHA512 checksum:
>
> 8177d4123c507ccb43e10145931c03f9baa53c790499ebc6912d5d8e768ac953f57c29ec97e92012d05a16f11a7f2e0fadd29595b785e3f565181327b44ba969
>  apache-trafficcontrol-7.0.0.tar.gz
>
>
> This corresponds to git refs:
>
> Hash: ffcd4b26521b711996eaab1b415893251b7c439
> Tag: RELEASE-7.0.0-RC2
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-7.0.0-RC2
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote will remain open for at least 72 hours (15:00 UTC on Sunday,
> July 24th) and passes if a majority of at least 3 +1 PMC votes are
> cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> Steve Hamrick shamr...@apache.org
>

Re: [VOTE] Release Apache Traffic Control 7.0.0-RC1

[Zach Hoffman]

+1

On Wed, Jul 20, 2022 at 2:10 PM Steve Hamrick  wrote:

> Hello All,
>
> I've prepared a release for 7.0.0-RC1. Changes since RELEASE-6.1.0
>
>
> https://github.com/apache/trafficcontrol/compare/RELEASE-6.1.0...RELEASE-7.0.0-RC1
>
> https://github.com/apache/trafficcontrol/blob/RELEASE-7.0.0-RC1/CHANGELOG.md
>
> The artifacts are available for download at:
>
> https://dist.apache.org/repos/dist/dev/trafficcontrol/7.0.0/RC1/
>
> Change since RC0
>
>
> https://github.com/apache/trafficcontrol/compare/RELEASE-7.0.0-RC0..RELEASE-7.0.0-RC1
>
> BLAKE2 checksum:
>
> d0f00fff6abb2fc4c9f750835ac6878fd0a4b8e241a76dcdbaff244c6e100a34824c67721de86dd16f75f06e30421320fcd78c810aca06048049a1cd840b97e1
>  apache-trafficcontrol-7.0.0.tar.gz
>
>
> SHA512 checksum:
>
> 8690aa3984345474f53ebf375f14e5a5a710923c5ac2f763a14aa4192abafdb1913af4dd8fad2e1e68c956b5758a925b1c6bb217c0a2a2ca109510943e4bbe42
>  apache-trafficcontrol-7.0.0.tar.gz
>
>
> This corresponds to git refs:
>
> Hash: 344b0adcf54bcf0789af285d19b06d15525bf923
> Tag: RELEASE-7.0.0-RC1
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-7.0.0-RC1
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote will remain open for at least 72 hours (21:00 UTC on Saturday,
> July 23rd) and passes if a majority of at least 3 +1 PMC votes are
> cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> Steve Hamrick shamr...@apache.org
>

Re: [VOTE] Release Apache Traffic Control 7.0.0-RC0

[Zach Hoffman]

`./pkg -v weasel` fails for me. I removed most `.npm` and `.m2` lines
(otherwise, the file would be 4745 lines):

Error Unknown!
.m2/repository/antlr/antlr/2.7.2/_remote.repositories
Error Unknown!
.m2/repository/antlr/antlr/2.7.2/antlr-2.7.2.pom
Error Unknown!
.m2/repository/antlr/antlr/2.7.2/antlr-2.7.2.pom.sha1
[...]
Error Unknown!
.npm/_cacache/content-v2/sha1/00/8c/3a7fe1e96bd0d84e260ea1fa1783457f79c2
Error Unknown!
.npm/_cacache/content-v2/sha1/02/58/eae4d3d0c0974de1c169188ef0051d1d1988
Error Unknown!
.npm/_cacache/content-v2/sha1/04/e6/926f662895354f3dd015203633b857297e2c
[...]
Error Unknown! dist/build-docs.log
Error Unknown!
dist/build-grove-grovetccfg.log
Error Unknown! dist/build-grove.log
Error Unknown! dist/build-tarball.log
Error Unknown!
dist/build-traffic_monitor.log
Error Unknown! dist/build-traffic_ops.log
Error Unknown! dist/build-traffic_portal.log
Error Unknown! dist/build-traffic_router.log
Error Unknown! dist/build-traffic_stats.log
Error Unknown!
dist/grove-0.2-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/grove-0.2-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/grovetccfg-0.2-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/grovetccfg-0.2-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/tomcat-9.0.43-1.el8.noarch.rpm
Error Unknown!
dist/tomcat-9.0.43-1.el8.src.rpm
Error Unknown!
dist/traffic_monitor-7.0.0-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/traffic_monitor-7.0.0-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/traffic_ops-7.0.0-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/traffic_ops-7.0.0-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/traffic_portal-7.0.0-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/traffic_portal-7.0.0-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/traffic_router-7.0.0-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/traffic_stats-7.0.0-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/traffic_stats-7.0.0-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/trafficcontrol-cache-config-7.0.0-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/trafficcontrol-cache-config-7.0.0-12107.bdb9f929.el8.x86_64.rpm
Error Unknown!
dist/trafficcontrol-health-client-7.0.0-12107.bdb9f929.el8.src.rpm
Error Unknown!
dist/trafficcontrol-health-client-7.0.0-12107.bdb9f929.el8.x86_64.rpm

-Zach

On Tue, Jul 19, 2022 at 12:37 PM Steve Hamrick  wrote:

> Hello All,
>
> I've prepared a release for 7.0.0-RC0. Changes since RELEASE-6.1.0
>
>
> https://github.com/apache/trafficcontrol/compare/RELEASE-6.1.0...RELEASE-7.0.0-RC0
>
> https://github.com/apache/trafficcontrol/blob/RELEASE-7.0.0-RC0/CHANGELOG.md
>
> The artifacts are available for download at:
>
> https://dist.apache.org/repos/dist/dev/trafficcontrol/7.0.0/RC0/
>
> BLAKE2 checksum:
>
> 834f7327434c189f6fa1079d2cd8a238d187d116da0f49f5f82e2e432e0b593eafd20eca90ff614fc20a791fa422f828eee5c38e39e754b479855e14518dcdc1
>  apache-trafficcontrol-7.0.0.tar.gz
>
>
> SHA512 checksum:
>
> 2dc890a119d9d7291e2a7b09de023c5dff09847aa68c025bd5d1c8c0ed2424a971da4e73aa3698c3e70256975055c53f36052324bdab5d8e0e8b67212a11ac81
>  apache-trafficcontrol-7.0.0.tar.gz
>
>
> This corresponds to git refs:
>
> Hash: bdb9f929f4f3b116b4ad5b1b560a25fdd0ed0d96
> Tag: RELEASE-7.0.0-RC0
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-7.0.0-RC0
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote will remain open for at least 72 hours (19:00 UTC on Friday,
> July 19th) and passes if a majority of at least 3 +1 PMC votes are
> cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> Steve Hamrick shamr...@apache.org
>

Re: 2022-06-14 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Active mailing list threads:
• Call for Traffic Portal Enhancements / New Features <
https://lists.apache.org/thread/82g2cstsn0p5gf8b6b56og17owq1837j>

-Zach

On Tue, Jun 7, 2022 at 9:28 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.
>

Re: Call for Traffic Portal Enhancements / New Features

[Zach Hoffman]

Posting from another thread for better organization:

On Tue, Jun 7, 2022 at 10:06 AM Gray, Jonathan
 wrote:

> The data kindof exists.  Servers have Physlocations which have addresses
> of some kind.  Their purpose is presently ambiguous as to if that should be
> used for physical address or mailing address.  Clearing that ambiguity and
> adding lat/long are nice to haves, but that’s really a TO enhancement
> rather than a TP one.  Additionally those physlocation lat/longs wouldn’t
> presently used in a meaningful way since all routing decisions are based on
> the cachegroup.  There are reasons that a cachegroup location might be
> skewed away from the physlocation or serve as an area aggregate.  Today you
> can suboptimally equate physlocation and cachegroup for routing/capacity
> purposes if desired, but that gets pretty far into micromanagement and
> capacity issues.  Analytics I’ve done in the past that were useful were to
> create convex hull polygons of the physlocations associated to a cachegroup
> and check that the areas were reasonable for the tiers as well as to ensure
> the cachegroup lat/long was contained within it or nearby to where it made
> sense.  That’s shown in the past where we’ve had physlocations set wrong on
> hosts due to ambiguous physlocation names.  Although that didn’t affect
> routing just RMA work.
>
> Better visualization around parentage in general would be a definite win.
> Given how we’ve gone from a 1 or 2 tier CDN model with secondary parents
> and MSO to an N-tier model with additional dimensions of permutations
> around topologies as well as capabilities/requirements, as an SRE it’s much
> more difficult to know how traffic ideally should be flowing for diagnostic
> purposes.  That view doesn’t have to be geographic in nature though.  A
> graph/tree would suffice.  From a perspective of self-service though, all
> the topic around parentage is generally too complex for a non-ATC engineer
> and too powerful.  Better visualization around parentage I think benefits
> both user groups.
>
> Jonathan G
>
>
> From: Dave Neuman 
> Date: Tuesday, June 7, 2022 at 9:30 AM
> To: dev@trafficcontrol.apache.org 
> Subject: [EXTERNAL] Re: 2022-06-07 TC Working Group Agenda and Meeting
> Notes
> >>   - Zach proposes/iss working on a geographic Topology builder using
> Cache Group latitude/longitude to map them out
>
> I would suggest incorporating the physical locations of the hosts as well.
> Maybe as a drill down?  Cache groups can be as big as a whole country,
> having the actual locations of the caches could be much more helpful.
>
> Just my $.02
>
> --Dave
>

-Zach

On Mon, Jun 6, 2022 at 9:15 AM Wilson, Amy 
wrote:

> To add some additional color, a new delivery service self-service feature
> really means is 2 things:
>
>   *   simplified view for non-super/advanced users
>   *   eliminate the need to queue [server] updates / CDN snapshot to
> propagate changes - https://github.com/apache/trafficcontrol/issues/6183
>
> ~Amy
>
> From: Wilson, Amy 
> Date: Wednesday, June 1, 2022 at 4:04 PM
> To: dev@trafficcontrol.apache.org 
> Subject: Call for Traffic Portal Enhancements / New Features
> Good afternoon,
>
> I hope this email finds everyone doing well.
>
> Looking to gather enhancements or new features for Traffic Portal.
> Specifically, around User Management, Tenancy, and Delivery Services
> management.
>
> Please provide your detailed ideas/requirements.
>
> Thanks,
> ~Amy
>

2022-06-07 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Active mailing list threads:
• Call for Traffic Portal Enhancements / New Features <
https://lists.apache.org/thread/82g2cstsn0p5gf8b6b56og17owq1837j>

Re: 2022-05-31 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

ATS 9 will likely be in EPEL within the next week <
https://github.com/apache/trafficserver/issues/6855#issuecomment-1136490669>,
but hard-coded `/opt/trafficserver/*` paths are still always used in some
places , so we are
not yet ready for stock ATS

On Tue, May 24, 2022 at 9:41 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.
>

Re: 2022-05-24 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Active mailing list threads:
- Reminder: ApacheCon Asia 2022 CFP closes on May 31st <
https://lists.apache.org/thread/qs2pz0bksvngzbqbn0bcp25tf87ghyvx>
- GSoC Backup Mentor <
https://lists.apache.org/thread/cm0m2v7f3wvqkyo4457ypolm9k9zff2m>
- Blueprint: Cache Config Service <
https://lists.apache.org/thread/7wsffkd52r21dmwkjxyl0cnqnhdjgm99>

-Zach


On Tue, May 17, 2022 at 9:43 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.
>

Re: 2022-05-10 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- As of this last week, we have C++ code scanning alerts. What other static
analysis should we add?

Active mailing list threads:
- Blueprint: Cache Config Service <
https://lists.apache.org/thread/7wsffkd52r21dmwkjxyl0cnqnhdjgm99>

-Zach

On Tue, May 3, 2022 at 10:16 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.
>

Re: 2022-05-03 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

>From Evan Zelkowitz of Traffic Server:
If anyone has any CDN-esque talks, the ATS spring summit (which is still
online for this go around) is having their call for topics:
https://cwiki.apache.org/confluence/display/TS/Spring+2022+Summit#Spring2022Summit-CallforTopics

On Tue, May 3, 2022 at 9:21 AM Zach Hoffman  wrote:

> Consider discussing:
>
> - ATS 9 EPEL packages are in the works <
> https://lists.apache.org/thread/k8qh7mk7g4gp44pomfxjlq5blkops2hb>. What
> is required for us to switch to them?
> - As of last week, we have Java code scanning alerts. What other languages
> should we add?
>
> -Zach
>
> On Tue, Apr 26, 2022 at 9:42 AM ocket   wrote:
>
>> If you have anything you want to discuss at next week's meeting,
>> respond to this email and it's on the agenda.
>>
>

Re: 2022-05-03 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

- ATS 9 EPEL packages are in the works <
https://lists.apache.org/thread/k8qh7mk7g4gp44pomfxjlq5blkops2hb>. What is
required for us to switch to them?
- As of last week, we have Java code scanning alerts. What other languages
should we add?

-Zach

On Tue, Apr 26, 2022 at 9:42 AM ocket   wrote:

> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.
>

Re: 2022-04-12 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Active mailing list threads:
• supported API versions


On Tue, Apr 5, 2022 at 10:13 AM ocket   wrote:
>
> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.

Re: supported API versions

[Zach Hoffman]

How about at the top of
https://traffic-control-cdn.readthedocs.io/en/latest/api/ ? And we
could link to it from wherever makes sense to

-Zach

On Thu, Apr 7, 2022 at 9:52 AM Jeremy Mitchell  wrote:
>
> Is there a place I'm unaware of that shows which API versions are supported
> for a given TC release? something like this:
>
> TC 6.1.x:
> - API 4.x unstable
> - API 3.x stable
> - API 2.x deprecated
>
> i think i can dig thru the api documentation to figure this out but didn't
> feel like digging. anyhow, maybe if we don't have this, it could go here?
> although that doesn't seem quite right:
> https://github.com/apache/trafficcontrol/security/policy
>
> Jeremy

Re: 2022-04-05 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- What languages do we not yet have code scanning alerts for?
- GitHub Actions do not run on PRs generated by GitHub Actions

On Tue, Mar 29, 2022 at 10:01 AM ocket   wrote:
>
> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.

Re: 2022-03-29 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

- Since the Docker hub now uses rate limiting, we should take
advantage of the GitHub Container Registry to speed up our CI.
Example: https://github.com/apache/trafficcontrol/pull/6699
- Do we want to be notified of wiki edits in #traffic-control-commits?

-Zach

On Tue, Mar 22, 2022 at 9:28 AM ocket   wrote:
>
> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.

Re: ATC 6.x + Rocky

[Zach Hoffman]

Backported to the 6.1.x branch in
<https://github.com/apache/trafficcontrol/commit/cfb321ec2a>

-Zach


On Tue, Mar 15, 2022 at 10:20 AM Zach Hoffman  wrote:
>
> Let's backport Rocky to 6.1.x
>
> -Zach
>
> On Tue, Mar 15, 2022 at 10:16 AM ocket   wrote:
> >
> > CiaB is explicitly not meant to be a real production deployment option
> > - if that's the *only* thing that's broken I don't think it warrants
> > backports. But I would imagine there are other issues as well.
> >
> > On Tue, Mar 15, 2022 at 10:14 AM Eric Friedrich  wrote:
> > >
> > > Hey-
> > >  Thoughts on backporting the Rocky Linux fixes to the 6.x branch?
> > > Currently CIAB is broken on that branch and it is our current "stable"
> > > release
> > >
> > > --Eric

Re: ATC 6.x + Rocky

[Zach Hoffman]

Let's backport Rocky to 6.1.x

-Zach

On Tue, Mar 15, 2022 at 10:16 AM ocket   wrote:
>
> CiaB is explicitly not meant to be a real production deployment option
> - if that's the *only* thing that's broken I don't think it warrants
> backports. But I would imagine there are other issues as well.
>
> On Tue, Mar 15, 2022 at 10:14 AM Eric Friedrich  wrote:
> >
> > Hey-
> >  Thoughts on backporting the Rocky Linux fixes to the 6.x branch?
> > Currently CIAB is broken on that branch and it is our current "stable"
> > release
> >
> > --Eric

Re: [EXTERNAL] 2022-03-01 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Today is the first time we have a new collaborator for March from our
new policy to assign the GitHub Triage role for a month to any
contributor who has had 2 Issue-closing Pull Requests merged within
the last 31 days .

On Tue, Mar 1, 2022 at 9:20 AM Frey, Taylor
 wrote:
>
> Blueprints - Any outstanding or accepted?
>
> From: ocket  
> Date: Tuesday, February 22, 2022 at 9:21 AM
> To: dev@trafficcontrol.apache.org 
> Subject: [EXTERNAL] 2022-03-01 TC Working Group Agenda and Meeting Notes
> If you have anything you want to discuss at next week's meeting, respond to
> this email and it's on the agenda.

Re: 2022-03-01 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Dependabot used to be enabled for our repo

but is now disabled.
* Should we enable security alerts on the repo for dependabot (visible
only to committers)
?
* Should we re-enable dependabot security updates (dependabot creates
a PR to update a dependency it notices a vulnerability for)?re-

On Tue, Feb 22, 2022 at 9:20 AM ocket   wrote:
>
> If you have anything you want to discuss at next week's meeting, respond to
> this email and it's on the agenda.

Fwd: [ACTION REQUIRED] Time to create GSoC ideas

[Zach Hoffman]

Anyone have a Google Summer of Code idea to submit for Apache Traffic Control?

To see ideas already submitted (includes 2022 and past years):
https://issues.apache.org/jira/browse/COMDEV-438?jql=project=COMDEV+AND+component=%22GSoC%2FMentoring+ideas%22

-Zach

-- Forwarded message -
From: Maxim Solodovnik 
Date: Tue, Feb 15, 2022 at 9:32 PM
Subject: [ACTION REQUIRED] Time to create GSoC ideas
To: mentors 


Hello mentors,

As you may know GSoC 2022 is coming :)
I'm creating application on behalf of ASF

It's time to collect GSoc ideas!
As usual the process is described here [1]

There are changes in rules this year I would like to highlight:
  1) NOT only students can apply
so from now on "GSoC contributor" should be 18+, and should be
"beginner contributor" [2]
  2) there will be 2 types of projects this year ~175 hour (medium) and 350
hour (large)
  NOTE: there is an option to extend the standard 12 week coding time
frame to a maximum of 22 weeks
3) we will provide scoring for GSoC contributors to Google for automatic
conflict resolution

Please add "*full-time*" label to the JIRA for 350 hour project OR "
*part-time*" label for 175 hours project

I'll update my scripts so this information will be available in Ideas list:
[3]

Thanks in advance!


[1] https://community.apache.org/gsoc.html#prospective-asf-mentors-read-this
[2]
https://groups.google.com/g/google-summer-of-code-mentors-list/c/TRqoysISSo8/m/4pnYQo9tBAAJ?utm_medium=email&utm_source=footer
[3] https://s.apache.org/gsoc2022ideas

Re: 2022-02-08 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- Java 17 support in TR?
- Go 1.18 is late

Active mailing list threads:
- CVE-2022-23206: Apache Traffic Control: Server-Side Request Forgery
in Traffic Ops endpoint POST /user/login/oauth

- Google Summer of Code 2022


On Tue, Feb 8, 2022 at 9:15 AM Jeremy Mitchell  wrote:
>
> We have 19 tech debt issue with no indication of the impact associated with
> each:
> https://github.com/apache/trafficcontrol/issues?q=is%3Aopen+is%3Aissue+label%3A%22tech+debt%22++-label%3A%22high+impact%22+-label%3A%22medium+impact%22+-label%3A%22low+impact%22
>
> Maybe we can add high, med, low impact as a team to each.
>
> On Tue, Feb 8, 2022 at 9:11 AM Jeremy Mitchell 
> wrote:
>
> > Now that 6.1.0 is official, do we want to start thinking about our next
> > official release planned for April 1 (start of Q2)? Are we thinking this
> > will be 6.2.x or 7.0.x?
> >
> > On Tue, Feb 1, 2022 at 9:36 AM ocket   wrote:
> >
> >> If you have anything you want to discuss at next week's meeting,
> >> respond to this email and it's on the agenda.
> >>
> >

CVE-2022-23206: Apache Traffic Control: Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth

[Zach Hoffman]

Description:

In Apache Traffic Control Traffic Ops prior to 6.1.0 or 5.1.6, an unprivileged 
user who can reach Traffic Ops over HTTPS can send a specially-crafted POST 
request to /user/login/oauth to scan a port of a server that Traffic Ops can 
reach.

Mitigation:

6.0.x user should upgrade to 6.1.0.
5.1.x users should upgrade to 5.1.6 or 6.1.0.

Credit:

Apache Traffic Control would like to thank walkerxiong of SecCoder Security Lab 
for reporting this issue.

CVE-2022-23206: Apache Traffic Control: Server-Side Request Forgery in Traffic Ops endpoint POST /user/login/oauth

[Zach Hoffman]

Description:

In Apache Traffic Control Traffic Ops prior to 6.1.0 or 5.1.6, an unprivileged 
user who can reach Traffic Ops over HTTPS can send a specially-crafted POST 
request to /user/login/oauth to scan a port of a server that Traffic Ops can 
reach.

Mitigation:

6.0.x user should upgrade to 6.1.0.
5.1.x users should upgrade to 5.1.6 or 6.1.0.

Credit:

Apache Traffic Control would like to thank walkerxiong of SecCoder Security Lab 
for reporting this issue.

[ANNOUNCE] Release Apache Traffic Control 6.1.0

[Zach Hoffman]

The Apache Traffic Control team is proud to announce the release of
Apache Traffic Control 6.1.0,
which contains various new features and bug fixes.

Apache Traffic Control allows you to build a large scale content
delivery network using open source.
Built around Apache Traffic Server as the caching software, Traffic
Control implements all the core
functions of a modern CDN.

More details regarding Apache Traffic Control can be found at:

https://trafficcontrol.apache.org/

The release artifacts, along with release notes, can be found here:

https://trafficcontrol.apache.org/releases/


Thanks!

The Apache Traffic Control Team

Re: [VOTE] Release Apache Traffic Control 6.1.0-RC2

[Zach Hoffman]

Calling this vote with 6 +1s (3 binding), and 0 -1s.

+===+===+===+===+===+
| Voter | +1| +0| -1|Binding|
+===+===+===+===+===+
| Jeremy Mitchell   | +1|   |   | x |
+---+---+---+---+---+
| Rawlin Peters | +1|   |   | x |
+---+---+---+---+---+
| Srijeet Chatterjee| +1|   |   |   |
+---+---+---+---+---+
| Zach Hoffman  | +1|   |   | x |
+---+---+---+---+---+
| Eric Holguin  | +1|   |   |   |
+---+---+---+---+---+
| Steve Hamrick | +1|   |   |   |
+---+---+---+---+---+

Thanks to all who voted! I'll prepare the 6.1.0 release shortly.

-Zach

On Tue, 2022-02-01 at 22:25 +, Holguin, Eric wrote:
> +1
> 
> From: Zach Hoffman 
> Date: Monday, January 31, 2022 at 2:51 PM
> To: dev@trafficcontrol.apache.org 
> Subject: [EXTERNAL] [VOTE] Release Apache Traffic Control 6.1.0-RC2
> I've prepared a release for 6.1.0-RC2. Changes since RELEASE-6.0.2:
> 
> 
> https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC2
> 
> 
> https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC2/CHANGELOG.md
> 
> 
> The artifacts are available for download at:
> 
> https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC2/
> 
> 
> BLAKE2 checksum:
> 35b73bea81f6550aeecb8e5a0e8776089b557fea135ffdd1c6bc022d3625e34941c834d55114cf7de594578ba4bbe1103d17ae9d3efc3b92ed52279d2c5b14e7
>   apache-trafficcontrol-6.1.0.tar.gz
> 
> SHA512 checksum:
> be4cb2d99462cd92bb771705853381b8c6fd466d97ebbf273cc401e26629a56019838ba4a9993504780f5994f5005ae5f04d27587664ea3fe5113f816d6e1424
>   apache-trafficcontrol-6.1.0.tar.gz
> 
> This corresponds to git refs:
> 
> Hash: f8041b3b5d616003b32d7c0dc160f5f9621e5366
> Tag: RELEASE-6.1.0-RC2
> 
> Which can be verified with the following command:
> 
> $ git tag -v RELEASE-6.1.0-RC2
> 
> All code signing keys are available here:
> 
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
> 
> 
> Make sure you refresh from a key server to get all relevant signatures.
> 
> The vote is open until 22:00 UTC on Thursday, February 3 and passes if a 
> majority of at least 3 +1 PMC votes are cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
> 
> -Zach

Re: 2022-02-01 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

John Rushford switched the t3c integration tests to Rocky Linux 8 in
<https://github.com/apache/trafficcontrol/pull/6530> (merged). The
rest of the repo is migrated from CentOS 8 to Rocky Linux 8 in
<https://github.com/apache/trafficcontrol/pull/6535>.

-Zach

On Tue, Feb 1, 2022 at 12:23 PM Eric Friedrich  wrote:
>
> Rocky makes sense to me as the next step after Centos8
>
> --Eric
>
> On Tue, Feb 1, 2022 at 1:20 PM ocket   wrote:
> >
> > Hey, that sounds great to me. As far as I'm concerned, this is all the
> > discussion necessary to move forward. I'm just saying I can't demand
> > that our project support any particular OS on my own without talking
> > about it with the list.
> >
> > To be clear, I was definitely never going to suggest Alma - not the
> > least because I couldn't remember the name - or anything else. Rocky
> > seems like the right choice. And by "going to 7 does sound like moving
> > backwards" I didn't mean to drop support for CentOS 7, just that
> > testing on only CentOS 7 instead of updating our CentOS 8 images to
> > Rocky seemed like the wrong call. I don't think we need to drop
> > support for that even after being comfortable with Rocky, until it
> > hits EoL and/or becomes an inconvenience to support.
> >
> > On Tue, Feb 1, 2022 at 10:33 AM Dave Neuman  wrote:
> > >
> > > +1 to retaining support for 7 until we are good with Rocky.  Now *that* is
> > > something that we can decide as a community.
> > >
> > > On Tue, Feb 1, 2022 at 10:31 AM Rawlin Peters  wrote:
> > >
> > > > We should probably retain support for CentOS 7 until such a time that
> > > > we're comfortable with Rocky going forward. I do think Rocky is the
> > > > future (at least for Comcast that seems to be the case). It's really
> > > > Rocky vs Alma, and if someone wants to add support for Alma in
> > > > addition to Rocky and can maintain that support, they should be free
> > > > to do so.
> > > >
> > > > - Rawlin
> > > >
> > > > On Tue, Feb 1, 2022 at 10:21 AM ocket   wrote:
> > > > >
> > > > > Yeah, going to 7 does sound like moving backwards - we don't want to
> > > > > do that, we want to move to whatever is going to be supported now that
> > > > > CentOS 8 no longer works. The issue is that we need to know that Rocky
> > > > > Linux is what the ATC project will support if we're going to use it
> > > > > moving forward, and the working group does not have the authority to
> > > > > make that call.
> > > > >
> > > > > On Tue, Feb 1, 2022 at 9:39 AM Dave Neuman  wrote:
> > > > > >
> > > > > > - Need mailing list confirmation that moving to Rocky is the plan,
> > > > > > then our CI can be converted to Rocky Linux
> > > > > >
> > > > > > Do we though?  Can't we just put in support for Rocky and if folks 
> > > > > > want
> > > > > > support for other things they could add it?
> > > > > > Seems like going to 7 is going backwards for what reason?
> > > > > >
> > > > > > On Tue, Feb 1, 2022 at 9:35 AM ocket   
> > > > > > wrote:
> > > > > >
> > > > > > > 1. Attendance
> > > > > > > - Stephen Hamrick
> > > > > > > - Zach Hoffman
> > > > > > > - Eric Holguin
> > > > > > > - Matt Jackson
> > > > > > > - Srijeet Chatterjee
> > > > > > > - Taylor Frey
> > > > > > > 2. CentOS 8 Docker image no longer works
> > > > > > > - Should we make a workaround or switch to e.g. Rocky Linux ?
> > > > > > > - Probably depends on overall project direction, but that
> > > > conversation
> > > > > > > takes longer than fixing our CI
> > > > > > > - Issue #6343 needs to be fixed before we could downgrade to only
> > > > > > > testing on CentOS 7
> > > > > > > - Need mailing list confirmation that moving to Rocky is the plan,
> > > > > > > then our CI can be converted to Rocky Linux
> > > > > > > 3. ML: ATCv6.1.0-RC2 needs votes
> > > > > > > - Currently has 2 PMC +1s
> > > > > > > 4. ML: Summer of Code 2022
> > > > > > >
> > > > > > > On Tue, Feb 1, 2022 at 9:21 AM Zach Hoffman 
> > > > wrote:
> > > > > > > >
> > > > > > > > Consider discussing:
> > > > > > > > - CentOS 8 no longer works, which breaks our CI. Time to move to
> > > > Rocky
> > > > > > > Linux?
> > > > > > > >
> > > > > > > > Active mailing list threads:
> > > > > > > > - Release Apache Traffic Control 6.1.0-RC2
> > > > > > > > <https://lists.apache.org/thread/soqqndn7ggzrzjx5s81t7c09yzovll6h>
> > > > > > > >
> > > > > > > > On Tue, Jan 25, 2022 at 9:44 AM ocket  
> > > > wrote:
> > > > > > > > >
> > > > > > > > > If you have anything you want to discuss at next week's 
> > > > > > > > > meeting,
> > > > > > > > > respond to this email and it's on the agenda.
> > > > > > >
> > > >

Re: [EXTERNAL] Re: [VOTE] Release Apache Traffic Control 6.1.0-RC2

[Zach Hoffman]

+1

On Tue, Feb 1, 2022 at 9:37 AM Chatterjee, Srijeet
 wrote:
>
> +1
>
> On 2/1/22, 9:14 AM, "Rawlin Peters"  wrote:
>
> +1
>
> On Tue, Feb 1, 2022 at 9:10 AM Jeremy Mitchell  
> wrote:
> >
> > +1
> >
> > On Mon, Jan 31, 2022 at 2:51 PM Zach Hoffman  
> wrote:
> >
> > > I've prepared a release for 6.1.0-RC2. Changes since RELEASE-6.0.2:
> > >
> > >
> > > 
> https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC2__;!!CQl3mcHX2A!R0XdVsfAfoM4YVpxxhH49Vrpwv9N0bQEgoEC-4WNbvidWADVxb5hQhmlhXXfweTcFcN7Am2v$
> > >
> > > 
> https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC2/CHANGELOG.md__;!!CQl3mcHX2A!R0XdVsfAfoM4YVpxxhH49Vrpwv9N0bQEgoEC-4WNbvidWADVxb5hQhmlhXXfweTcFZRCOeY1$
> > >
> > > The artifacts are available for download at:
> > >
> > > 
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC2/__;!!CQl3mcHX2A!R0XdVsfAfoM4YVpxxhH49Vrpwv9N0bQEgoEC-4WNbvidWADVxb5hQhmlhXXfweTcFfMRJ1uE$
> > >
> > > BLAKE2 checksum:
> > > 
> 35b73bea81f6550aeecb8e5a0e8776089b557fea135ffdd1c6bc022d3625e34941c834d55114cf7de594578ba4bbe1103d17ae9d3efc3b92ed52279d2c5b14e7
> > > apache-trafficcontrol-6.1.0.tar.gz
> > >
> > > SHA512 checksum:
> > > 
> be4cb2d99462cd92bb771705853381b8c6fd466d97ebbf273cc401e26629a56019838ba4a9993504780f5994f5005ae5f04d27587664ea3fe5113f816d6e1424
> > > apache-trafficcontrol-6.1.0.tar.gz
> > >
> > > This corresponds to git refs:
> > >
> > > Hash: f8041b3b5d616003b32d7c0dc160f5f9621e5366
> > > Tag: RELEASE-6.1.0-RC2
> > >
> > > Which can be verified with the following command:
> > >
> > > $ git tag -v RELEASE-6.1.0-RC2
> > >
> > > All code signing keys are available here:
> > >
> > > 
> https://urldefense.com/v3/__https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS__;!!CQl3mcHX2A!R0XdVsfAfoM4YVpxxhH49Vrpwv9N0bQEgoEC-4WNbvidWADVxb5hQhmlhXXfweTcFak_CSAJ$
> > >
> > > Make sure you refresh from a key server to get all relevant 
> signatures.
> > >
> > > The vote is open until 22:00 UTC on Thursday, February 3 and passes 
> if a
> > > majority of at least 3 +1 PMC votes are cast.
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> > > -Zach
> > >
>

Re: 2022-02-01 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Yeah, since CentOS 8 is already EOL as of end of 2021, we're now
missing a platform. So we can just change all CentOS 8 to Rocky Linux
and it won't mean dropping support for any non-EOL platform.

The only question is whether we want to retain CentOS 7 support. From
my testing, Rocky Linux really is a drop-in replacement for CentOS 8,
so if we add a `BASE_IMAGE` build arg, similar to our existing
`RHEL_VERSION` build arg, we can get images `FROM
${BASE_IMAGE}:${RHEL_VERSION}`, which could be either
`rockylinux/rockylinux:8` (default) or `centos:7` without making
additional changes to our Dockerfile logic.

If we don't retain CentOS 7 support in our Dockerfiles, we should
probably remove CentOS 7 as a build target, since that target would go
untested.

-Zach

On Tue, Feb 1, 2022 at 9:39 AM Dave Neuman  wrote:
>
> - Need mailing list confirmation that moving to Rocky is the plan,
> then our CI can be converted to Rocky Linux
>
> Do we though?  Can't we just put in support for Rocky and if folks want
> support for other things they could add it?
> Seems like going to 7 is going backwards for what reason?
>
> On Tue, Feb 1, 2022 at 9:35 AM ocket   wrote:
>
> > 1. Attendance
> > - Stephen Hamrick
> > - Zach Hoffman
> > - Eric Holguin
> > - Matt Jackson
> > - Srijeet Chatterjee
> > - Taylor Frey
> > 2. CentOS 8 Docker image no longer works
> > - Should we make a workaround or switch to e.g. Rocky Linux ?
> > - Probably depends on overall project direction, but that conversation
> > takes longer than fixing our CI
> > - Issue #6343 needs to be fixed before we could downgrade to only
> > testing on CentOS 7
> > - Need mailing list confirmation that moving to Rocky is the plan,
> > then our CI can be converted to Rocky Linux
> > 3. ML: ATCv6.1.0-RC2 needs votes
> > - Currently has 2 PMC +1s
> > 4. ML: Summer of Code 2022
> >
> > On Tue, Feb 1, 2022 at 9:21 AM Zach Hoffman  wrote:
> > >
> > > Consider discussing:
> > > - CentOS 8 no longer works, which breaks our CI. Time to move to Rocky
> > Linux?
> > >
> > > Active mailing list threads:
> > > - Release Apache Traffic Control 6.1.0-RC2
> > > <https://lists.apache.org/thread/soqqndn7ggzrzjx5s81t7c09yzovll6h>
> > >
> > > On Tue, Jan 25, 2022 at 9:44 AM ocket   wrote:
> > > >
> > > > If you have anything you want to discuss at next week's meeting,
> > > > respond to this email and it's on the agenda.
> >

Google Summer of Code 2022

[Zach Hoffman]

It's time to start thinking about Google Summer of Code 2022!

Info about what Google Summer of Code is: https://community.apache.org/gsoc.html

ASF gets accepted for GSoC every year as an umbrella organization and
will have a limited number of slots to allocate among Apache projects.
To participate in GSoC, Traffic Control will need to
- Submit at least 1 proposal
- Get ATC community members to volunteer to mentor these proposals. As
an example from last year, GSoC 2021 requested that each project
provide 2 mentors for each selected proposal

If you are interested in being a mentor, see this page
 and
subscribe to ment...@community.apache.org.

Any contributor who participates in Google Summer of Code 2022 for an
ATC proposal will get a stipend for participation, which varies in
amount by where the student lives
.
This part is funded entirely by Google.

ASF ideas/proposals from 2021: https://s.apache.org/gsoc2021ideas
See the GSoC 2021 Successful Projects for the ASF to see what
contribution effort ASF was capable of fostering laster year

ASF ideas/proposals for GSoC 2021: https://s.apache.org/gsoc2021ideas

Submit proposals to the Community Development. To see Jira proposals
submitted last year:
:

Anyone interested?


-Zach

Re: 2022-02-01 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- CentOS 8 no longer works, which breaks our CI. Time to move to Rocky Linux?

Active mailing list threads:
- Release Apache Traffic Control 6.1.0-RC2


On Tue, Jan 25, 2022 at 9:44 AM ocket   wrote:
>
> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.

[VOTE] Release Apache Traffic Control 6.1.0-RC2

[Zach Hoffman]

I've prepared a release for 6.1.0-RC2. Changes since RELEASE-6.0.2:


https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC2

https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC2/CHANGELOG.md

The artifacts are available for download at:

https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC2/

BLAKE2 checksum:
35b73bea81f6550aeecb8e5a0e8776089b557fea135ffdd1c6bc022d3625e34941c834d55114cf7de594578ba4bbe1103d17ae9d3efc3b92ed52279d2c5b14e7
  apache-trafficcontrol-6.1.0.tar.gz

SHA512 checksum:
be4cb2d99462cd92bb771705853381b8c6fd466d97ebbf273cc401e26629a56019838ba4a9993504780f5994f5005ae5f04d27587664ea3fe5113f816d6e1424
  apache-trafficcontrol-6.1.0.tar.gz

This corresponds to git refs:

Hash: f8041b3b5d616003b32d7c0dc160f5f9621e5366
Tag: RELEASE-6.1.0-RC2

Which can be verified with the following command:

$ git tag -v RELEASE-6.1.0-RC2

All code signing keys are available here:

https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS

Make sure you refresh from a key server to get all relevant signatures.

The vote is open until 22:00 UTC on Thursday, February 3 and passes if a 
majority of at least 3 +1 PMC votes are cast.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-Zach

Re: Slack Invite request

[Zach Hoffman]

Invite sent!

-Zach

On Tue, Jan 25, 2022 at 3:25 PM Chirag Patel
 wrote:

> Will someone please invite me to the ASF Slack so I can join the
> #traffic-control channel?
>
> Thanks,
>
> Chirag Patel
>
> Principal Software Architect
>
> m: +1.215.896.7037
>
>
>
> [image: signature_969109539]
>
>
>

Re: 2022-01-25 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:

- Time to revisit Google Summer of Code 2022?

Mailing list threads from the past week:
- [RESULT][VOTE] Release Apache Traffic Control 6.1.0-RC1

- [VOTE] Release Apache Traffic Control 5.1.6-RC0

- [VOTE] Release Apache Traffic Control 6.1.0-RC1

- change log entry improvement



-Zach

On Tue, Jan 18, 2022 at 10:15 AM ocket   wrote:
>
> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.

[RESULT][VOTE] Release Apache Traffic Control 6.1.0-RC1

[Zach Hoffman]

Voting for ATC 6.1.0 Release Candidate 1 has closed. 6.1.0 RC1 fails with 0 +1 
votes and 0 -1 votes.

+-++++
| PMC member  | +1 | +0 | -1 |
+-++++
| covener ||||
+-++++
| dangogh ||||
+-++++
| dewrich ||||
+-++++
| dgelinas||||
+-++++
| elsloo  ||||
+-++++
| friede  ||||
+-++++
| hbeatty ||||
+-++++
| jvd ||||
+-++++
| mitchell852 ||||
+-++++
| mtorluemke  ||||
+-++++
| neuman  ||||
+-++++
| ocket   ||||
+-++++
| rawlin  ||||
+-++++
| rob ||||
+-++++
| smalenfant  ||||
+-++++
| sorber  ||||
+-++++
| zrhoffman   ||||
+-++++
| zwoop   ||||
+-++++

Voting results can be found here: 


I will cut another 6.1.0 release candidate early next week.

-Zach

[VOTE] Release Apache Traffic Control 6.1.0-RC1

[Zach Hoffman]

I've prepared a release for 6.1.0-RC1. Changes since RELEASE-6.0.2:


https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC1

https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC1/CHANGELOG.md

The artifacts are available for download at:

https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC1/

BLAKE2 checksum:
65fd72e198801d36312d3781d2ced0143a2c490c174b21d9e3388e665da82142e7d9a6de57b8b190c5a0e4e67b77cc706f9a4ad892f88aa9dfa071cce8f5de8b
  apache-trafficcontrol-6.1.0.tar.gz

SHA512 checksum:
3abd479f91efc7f05e1fcc21c63a6c27c9978d46a4103cc0cf9a8a22a48961d116d8b6db4da98b286197404d4b1dc988a759227b1f3a4f75bf6e64985544fa2e
  apache-trafficcontrol-6.1.0.tar.gz

This corresponds to git refs:

Hash: d93e9ad967bf93dc398099294dc185dfa3d5669c
Tag: RELEASE-6.1.0-RC1

Which can be verified with the following command:

$ git tag -v RELEASE-6.1.0-RC1

All code signing keys are available here:

https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS

Make sure you refresh from a key server to get all relevant signatures.

The vote is open until 22:00 UTC on Monday, January 24 and passes if a majority 
of at least 3 +1 PMC votes are cast.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-Zach

Re: [VOTE] Release Apache Traffic Control 6.1.0-RC0

[Zach Hoffman]

+1

On Tue, Jan 18, 2022 at 3:51 PM Zach Hoffman  wrote:
>
> I've prepared a release for 6.1.0-RC0. Changes since RELEASE-6.0.2:
>
> 
> https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC0
> 
> https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC0/CHANGELOG.md
>
> The artifacts are available for download at:
>
> https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC0/
>
> BLAKE2 checksum:
> b3dc6fb675514f22992252aef2c96b2edf7fbba263a250a48a5adba5eb4c264b811b74bcb735081377e8a210eb3df085ae0bfbadf45d01255852c8eb7821e2ba
>   apache-trafficcontrol-6.1.0.tar.gz
>
> SHA512 checksum:
> f3f6b88bcadcb317ad46ed080c3643d528664dcf33f34c68c7fc6b5b2758292d0824caba387381df127083ad71146d75f0d9ad6cf1db291f8ae5835148cb980d
>   apache-trafficcontrol-6.1.0.tar.gz
>
> This corresponds to git refs:
>
> Hash: e4ca62a440b42a0f9bd8f2f3c4cf1453f3ebc331
> Tag: RELEASE-6.1.0-RC0
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-6.1.0-RC0
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote is open until 23:00 UTC on Friday, January 21 and passes if a 
> majority of at least 3 +1 PMC votes are cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> -Zach

Re: [VOTE] Release Apache Traffic Control 5.1.6-RC0

[Zach Hoffman]

+1

On Tue, Jan 18, 2022 at 11:07 PM ocket   wrote:
>
> Hello All,
>
> I've prepared a release for 5.1.6-RC0. Changes since RELEASE-5.1.5:
>
> https://github.com/apache/trafficcontrol/compare/RELEASE-5.1.5...RELEASE-5.1.6-RC0
> https://github.com/apache/trafficcontrol/blob/RELEASE-5.1.6-RC0/CHANGELOG.md
>
> The artifacts are available for download at:
>
> https://dist.apache.org/repos/dist/dev/trafficcontrol/5.1.6/RC0/
>
> SHA512 checksum:
> fc8ec80a591d496adf98dbf641d5d88a94a80015045e865c741b129d1e18cb001cdf499c324ace37b563b7af8de9cdb70c1e33d70865f15e63d2f1a4dde4dc0d
>
> This corresponds to git refs:
>
> Hash: e4d38dbd57b1ee9143db19f9201a83b36f68aae7
> Tag: RELEASE-5.1.6-RC0
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-5.1.6-RC0
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote is open until 06:06:00 UTC on Saturday, January 22 and passes
> if a majority of at least 3 +1 PMC votes are cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thanks!
> ocket ocket8...@gmail.com

[VOTE] Release Apache Traffic Control 6.1.0-RC0

[Zach Hoffman]

I've prepared a release for 6.1.0-RC0. Changes since RELEASE-6.0.2:


https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.2...RELEASE-6.1.0-RC0

https://github.com/apache/trafficcontrol/blob/RELEASE-6.1.0-RC0/CHANGELOG.md

The artifacts are available for download at:

https://dist.apache.org/repos/dist/dev/trafficcontrol/6.1.0/RC0/

BLAKE2 checksum:
b3dc6fb675514f22992252aef2c96b2edf7fbba263a250a48a5adba5eb4c264b811b74bcb735081377e8a210eb3df085ae0bfbadf45d01255852c8eb7821e2ba
  apache-trafficcontrol-6.1.0.tar.gz

SHA512 checksum:
f3f6b88bcadcb317ad46ed080c3643d528664dcf33f34c68c7fc6b5b2758292d0824caba387381df127083ad71146d75f0d9ad6cf1db291f8ae5835148cb980d
  apache-trafficcontrol-6.1.0.tar.gz

This corresponds to git refs:

Hash: e4ca62a440b42a0f9bd8f2f3c4cf1453f3ebc331
Tag: RELEASE-6.1.0-RC0

Which can be verified with the following command:

$ git tag -v RELEASE-6.1.0-RC0

All code signing keys are available here:

https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS

Make sure you refresh from a key server to get all relevant signatures.

The vote is open until 23:00 UTC on Friday, January 21 and passes if a majority 
of at least 3 +1 PMC votes are cast.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-Zach

Re: 2022-01-18 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

- 6.1.0 RC0 to be open for voting today

active mailing list threads:
- Layered Profiles Blueprint


-Zach

On Tue, Jan 18, 2022 at 9:15 AM Jeremy Mitchell  wrote:
>
> Maybe we can put some impact and effort labels on the following tech debt
> items:
>
> https://github.com/apache/trafficcontrol/issues?q=is%3Aopen+is%3Aissue+label%3A%22tech+debt%22++-label%3A%22high+impact%22+-label%3A%22medium+impact%22+-label%3A%22low+impact%22
>
> On Tue, Jan 18, 2022 at 9:14 AM Jeremy Mitchell 
> wrote:
>
> > Status of 6.1
> >
> > On Tue, Jan 11, 2022 at 9:43 AM ocket   wrote:
> >
> >> If you have anything you want to discuss at next week's meeting,
> >> respond to this email and it's on the agenda.
> >>
> >

Re: 2022-01-11 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- Internet Bug Bounty Invite - Apache Software Foundation


Active mailing list threads:
- 6.1.0 Planning


On Tue, Jan 4, 2022 at 12:24 PM ocket   wrote:
>
> If you have anything you want to discuss at next week's meeting,
> respond to this email and it's on the agenda.

Re: [EXTERNAL] Re: 6.1.0 Planning

[Zach Hoffman]

Right, API v4 would only become stable if we have an unstable API v5,
which we yet do not.

-Zach

On Mon, Jan 10, 2022 at 1:02 PM Jeremy Mitchell  wrote:
>
> @jonathan - the in progress "layered server profiles
> <https://github.com/apache/trafficcontrol/blob/master/blueprints/layered-profile-server.md>"
> requires 4.0 remain unstable if i recall correctly, therefore, TC 6.1 will
> still have an unstable API 4.0. maybe our next release for march is 7.0
> with a stable api 4.0 and an unstable 5.x?
>
> On Thu, Jan 6, 2022 at 11:01 AM Gray, Jonathan
>  wrote:
>
> > With 6.1.0 should API 4.0 be considered stable or is there still
> > outstanding work in flight?
> >
> > Jonathan G
> >
> > From: Zach Hoffman 
> > Date: Thursday, January 6, 2022 at 10:09 AM
> > To: dev@trafficcontrol.apache.org 
> > Subject: [EXTERNAL] Re: 6.1.0 Planning
> > If there's anything anyone else wants included in 6.1.0, let's try to
> > get it in before the expected 6.1.0 release branch cut date
> > 2021-01-11.
> >
> > -Zach
> >
> > On Thu, Jan 6, 2022 at 10:06 AM Zach Hoffman  wrote:
> > >
> > > In the 2021-01-04 TC working group, we went through open issues and
> > > PRs and put together the 6.1.0 milestone
> > > <
> > https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/milestone/19__;!!CQl3mcHX2A!XEggSAgJjuxCs_cjtUY4Lqa1Y4wdsC-fw0IpB_qsl1glGMFx4QvrrCSgGY9GPoDpAgs6$
> > >:
> > > - Replace github.com/dgrijalva/jwt-go with
> > github.com/lestrrat-go/jwx/jwt
> > > - Create a secure parameter read permission to be able to see the
> > > values of secure parameters
> > > - Remove postgresql13-devel package dependency from Traffic Ops rpm
> > > - Revert automatic log rotation Log4J configuration
> > >
> > > -Zach
> > >
> > > On Thu, Jan 6, 2022 at 10:04 AM Eric Friedrich 
> > wrote:
> > > >
> > > > Sounds good, Thanks Zach.
> > > >
> > > > How's the state of master? Are we feeling good that its ready to cut a
> > > > release off of?
> > > >
> > > > On Thu, Jan 6, 2022 at 11:16 AM Jeremy Mitchell 
> > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman 
> > wrote:
> > > > >
> > > > > > Planning to cut the 6.1.0 release branch from master on Tuesday,
> > January
> > > > > > 11.
> > > > > >
> > > > > > -Zach
> > > > > >
> >

Re: 6.1.0 Planning

[Zach Hoffman]

If there's anything anyone else wants included in 6.1.0, let's try to
get it in before the expected 6.1.0 release branch cut date
2021-01-11.

-Zach

On Thu, Jan 6, 2022 at 10:06 AM Zach Hoffman  wrote:
>
> In the 2021-01-04 TC working group, we went through open issues and
> PRs and put together the 6.1.0 milestone
> <https://github.com/apache/trafficcontrol/milestone/19>:
> - Replace github.com/dgrijalva/jwt-go with github.com/lestrrat-go/jwx/jwt
> - Create a secure parameter read permission to be able to see the
> values of secure parameters
> - Remove postgresql13-devel package dependency from Traffic Ops rpm
> - Revert automatic log rotation Log4J configuration
>
> -Zach
>
> On Thu, Jan 6, 2022 at 10:04 AM Eric Friedrich  wrote:
> >
> > Sounds good, Thanks Zach.
> >
> > How's the state of master? Are we feeling good that its ready to cut a
> > release off of?
> >
> > On Thu, Jan 6, 2022 at 11:16 AM Jeremy Mitchell  
> > wrote:
> > >
> > > +1
> > >
> > > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman  wrote:
> > >
> > > > Planning to cut the 6.1.0 release branch from master on Tuesday, January
> > > > 11.
> > > >
> > > > -Zach
> > > >

Re: 6.1.0 Planning

[Zach Hoffman]

In the 2021-01-04 TC working group, we went through open issues and
PRs and put together the 6.1.0 milestone
<https://github.com/apache/trafficcontrol/milestone/19>:
- Replace github.com/dgrijalva/jwt-go with github.com/lestrrat-go/jwx/jwt
- Create a secure parameter read permission to be able to see the
values of secure parameters
- Remove postgresql13-devel package dependency from Traffic Ops rpm
- Revert automatic log rotation Log4J configuration

-Zach

On Thu, Jan 6, 2022 at 10:04 AM Eric Friedrich  wrote:
>
> Sounds good, Thanks Zach.
>
> How's the state of master? Are we feeling good that its ready to cut a
> release off of?
>
> On Thu, Jan 6, 2022 at 11:16 AM Jeremy Mitchell  wrote:
> >
> > +1
> >
> > On Thu, Jan 6, 2022 at 9:13 AM Zach Hoffman  wrote:
> >
> > > Planning to cut the 6.1.0 release branch from master on Tuesday, January
> > > 11.
> > >
> > > -Zach
> > >

6.1.0 Planning

[Zach Hoffman]

Planning to cut the 6.1.0 release branch from master on Tuesday, January 11.

-Zach

Re: 2022-01-04 TC Working Group Agenda and Meeting Notes

[Zach Hoffman]

Consider discussing:
- Any insights from GopherCon 2021?
- 1 month until Go 1.18 is released and we get generics
- GHA for Collaborator status is in review


Mailing list activity since last WG meeting:
- New committer: Srijeet Chatterjee

- Layered Profiles Blueprint

- ATC 6.0.2 
and 5.1.5 
released

On Tue, Jan 4, 2022 at 9:26 AM Taylor Frey  wrote:
>
> Automatic log rotation as a default setting in Log4J for TR
>
> On Tue, Jan 4, 2022 at 9:18 AM Jeremy Mitchell 
> wrote:
>
> > as a new quarter is upon us, is it time to consider getting 6.1 ready?
> >
> > On Tue, Dec 14, 2021 at 10:23 AM ocket   wrote:
> >
> > > If you have anything you want to discuss at next week's meeting,
> > > respond to this email and it's on the agenda.
> > >
> >

New committer: Srijeet Chatterjee

[Zach Hoffman]

The Project Management Committee (PMC) for Apache Traffic Control has
invited Srijeet Chatterjee to become a committer, and we are pleased
to announce that he has accepted!

Since April 2020, Srijeet has authored 84 merged Pull Requests, fixing
46 Issues across various ATC components. In addition to contributing
to numerous projects in the last 21 months, Sijeet implemented
If-Modified-Since and If-Unmodified-Since header support in Traffic
ops, and, more recenly, blueprinted and implemented CDN Locks before
presenting it at ApacheCon@Home 2021.

Being a committer enables easier contribution to the project since
there is no need to go via the patch submission process. This should
enable better productivity.

-Zach

[ANNOUNCE] Release Apache Traffic Control 6.0.2

[Zach Hoffman]

The Apache Traffic Control team is proud to announce the release of
Apache Traffic Control 6.0.2, which updates the log4j dependency in
Traffic Router to version 2.17.0.

Apache Traffic Control allows you to build a large scale content
delivery network using open source. Built around Apache Traffic Server
as the caching software, Traffic Control implements all the core
functions of a modern CDN.

More details regarding Apache Traffic Control can be found at:
https://trafficcontrol.apache.org/

The release artifacts, along with release notes, can be found here:
https://trafficcontrol.apache.org/releases/

Thanks!
The Apache Traffic Control Team

Re: [EXTERNAL] Re: [VOTE] Release Apache Traffic Control 6.0.2-RC2

[Zach Hoffman]

Calling the vote with 8 +1 votes (5 binding) and 0 -1 votes.

Thanks to everyone who voted! I will prepare the release shortly.

-Zach

On Tue, Dec 21, 2021 at 12:01 PM Stephen Hamrick  wrote:
>
> +1
>
> On Tue, Dec 21, 2021 at 11:18 AM Chatterjee, Srijeet
>  wrote:
>
> > +1
> >
> > --Srijeet
> >
> > On 12/21/21, 10:54 AM, "Zach Hoffman"  wrote:
> >
> > +1
> >
> > On Tue, Dec 21, 2021 at 10:51 AM Rawlin Peters 
> > wrote:
> > >
> > > +1
> > >
> > > On Tue, Dec 21, 2021 at 9:15 AM Eric Friedrich 
> > wrote:
> > > >
> > > > +1
> > > > Verified signatures, hashes and that I can build via pkg
> > > >
> > > > On Tue, Dec 21, 2021 at 11:14 AM Jeremy Mitchell <
> > mitchell...@gmail.com> wrote:
> > > > >
> >     > > > +1
> > > > >
> > > > > On Mon, Dec 20, 2021 at 2:48 PM ocket  
> > wrote:
> > > > >
> > > > > > Note that the 23rd is a Thursday
> > > > > >
> > > > > > On Mon, Dec 20, 2021 at 11:33 AM Zach Hoffman <
> > zrhoff...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > I've prepared a release for 6.0.2-RC2. Changes since
> > RELEASE-6.0.1:
> > > > > > >
> > > > > > >
> > > > > >
> > https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.1...RELEASE-6.0.2-RC2__;!!CQl3mcHX2A!TJLP9rfe8CyyaMd4Iy8iBN7bhnqTGBo87mY2YMW7ijpG3HAUc3Al0jTtFAEDQ5sVIZ35ziq2$
> > > > > > >
> > > > > >
> > https://urldefense.com/v3/__https://github.com/apache/trafficcontrol/blob/RELEASE-6.0.2-RC2/CHANGELOG.md__;!!CQl3mcHX2A!TJLP9rfe8CyyaMd4Iy8iBN7bhnqTGBo87mY2YMW7ijpG3HAUc3Al0jTtFAEDQ5sVISApxEeu$
> > > > > > >
> > > > > > > The artifacts are available for download at:
> > > > > > >
> > > > > > >
> > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/trafficcontrol/6.0.2/RC2/__;!!CQl3mcHX2A!TJLP9rfe8CyyaMd4Iy8iBN7bhnqTGBo87mY2YMW7ijpG3HAUc3Al0jTtFAEDQ5sVIbUlwchv$
> > > > > > >
> > > > > > > BLAKE2 checksum:
> > > > > > >
> > > > > >
> > 80cbac152f2dd37f5f874bafc5ce1d9c554ad78ce64e31fbb341db489ca22b4e5fe01e9dd35faaf9a2809f6636c6bac668963a142a71043535a0efd479ef
> > > > > > >  apache-trafficcontrol-6.0.2.tar.gz
> > > > > > >
> > > > > > > SHA512 checksum:
> > > > > > >
> > > > > >
> > de0abe5670f0a8a80ab12c73688f9a111794190d208d3190b6961934c0499ddb398f7fc45cd99d330c9f807e80c8a22cec385dbd60dd6498cc7b44831794452a
> > > > > > >  apache-trafficcontrol-6.0.2.tar.gz
> > > > > > >
> > > > > > > This corresponds to git refs:
> > > > > > >
> > > > > > > Hash: d33bf4189911f8631d0583b28c9e70151ca82535
> > > > > > > Tag: RELEASE-6.0.2-RC2
> > > > > > >
> > > > > > > Which can be verified with the following command:
> > > > > > >
> > > > > > > $ git tag -v RELEASE-6.0.2-RC2
> > > > > > >
> > > > > > > All code signing keys are available here:
> > > > > > >
> > > > > > >
> > https://urldefense.com/v3/__https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS__;!!CQl3mcHX2A!TJLP9rfe8CyyaMd4Iy8iBN7bhnqTGBo87mY2YMW7ijpG3HAUc3Al0jTtFAEDQ5sVIYEP4h6B$
> > > > > > >
> > > > > > > Make sure you refresh from a key server to get all relevant
> > signatures.
> > > > > > >
> > > > > > > The vote is open until 19:00 UTC on Wednesday, December 23
> > and passes
> > > > > > > if a majority of at least 3 +1 PMC votes are cast.
> > > > > > > [ ] +1 approve
> > > > > > > [ ] +0 no opinion
> > > > > > > [ ] -1 disapprove (and reason why)
> > > > > > >
> > > > > > > -Zach
> > > > > >
> >
> >

Re: [VOTE] Release Apache Traffic Control 6.0.2-RC2

[Zach Hoffman]

+1

On Tue, Dec 21, 2021 at 10:51 AM Rawlin Peters  wrote:
>
> +1
>
> On Tue, Dec 21, 2021 at 9:15 AM Eric Friedrich  wrote:
> >
> > +1
> > Verified signatures, hashes and that I can build via pkg
> >
> > On Tue, Dec 21, 2021 at 11:14 AM Jeremy Mitchell  
> > wrote:
> > >
> > > +1
> > >
> > > On Mon, Dec 20, 2021 at 2:48 PM ocket   wrote:
> > >
> > > > Note that the 23rd is a Thursday
> > > >
> > > > On Mon, Dec 20, 2021 at 11:33 AM Zach Hoffman 
> > > > wrote:
> > > > >
> > > > > I've prepared a release for 6.0.2-RC2. Changes since RELEASE-6.0.1:
> > > > >
> > > > >
> > > > https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.1...RELEASE-6.0.2-RC2
> > > > >
> > > > https://github.com/apache/trafficcontrol/blob/RELEASE-6.0.2-RC2/CHANGELOG.md
> > > > >
> > > > > The artifacts are available for download at:
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/trafficcontrol/6.0.2/RC2/
> > > > >
> > > > > BLAKE2 checksum:
> > > > >
> > > > 80cbac152f2dd37f5f874bafc5ce1d9c554ad78ce64e31fbb341db489ca22b4e5fe01e9dd35faaf9a2809f6636c6bac668963a142a71043535a0efd479ef
> > > > >  apache-trafficcontrol-6.0.2.tar.gz
> > > > >
> > > > > SHA512 checksum:
> > > > >
> > > > de0abe5670f0a8a80ab12c73688f9a111794190d208d3190b6961934c0499ddb398f7fc45cd99d330c9f807e80c8a22cec385dbd60dd6498cc7b44831794452a
> > > > >  apache-trafficcontrol-6.0.2.tar.gz
> > > > >
> > > > > This corresponds to git refs:
> > > > >
> > > > > Hash: d33bf4189911f8631d0583b28c9e70151ca82535
> > > > > Tag: RELEASE-6.0.2-RC2
> > > > >
> > > > > Which can be verified with the following command:
> > > > >
> > > > > $ git tag -v RELEASE-6.0.2-RC2
> > > > >
> > > > > All code signing keys are available here:
> > > > >
> > > > > https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
> > > > >
> > > > > Make sure you refresh from a key server to get all relevant 
> > > > > signatures.
> > > > >
> > > > > The vote is open until 19:00 UTC on Wednesday, December 23 and passes
> > > > > if a majority of at least 3 +1 PMC votes are cast.
> > > > > [ ] +1 approve
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 disapprove (and reason why)
> > > > >
> > > > > -Zach
> > > >

Re: [VOTE] Release Apache Traffic Control 5.1.5-RC0

[Zach Hoffman]

+1
Tested Traffic Router with the backports, it works as expected.

-Zach

On Tue, Dec 21, 2021 at 10:49 AM Rawlin Peters  wrote:
>
> +1
>
> On Tue, Dec 21, 2021 at 9:14 AM Jeremy Mitchell  wrote:
> >
> > +1
> >
> > On Mon, Dec 20, 2021 at 2:47 PM ocket   wrote:
> >
> > > And actually the 23rd is a Thursday.
> > >

[VOTE] Release Apache Traffic Control 6.0.2-RC2

[Zach Hoffman]

I've prepared a release for 6.0.2-RC2. Changes since RELEASE-6.0.1:


https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.1...RELEASE-6.0.2-RC2
https://github.com/apache/trafficcontrol/blob/RELEASE-6.0.2-RC2/CHANGELOG.md

The artifacts are available for download at:

https://dist.apache.org/repos/dist/dev/trafficcontrol/6.0.2/RC2/

BLAKE2 checksum:
80cbac152f2dd37f5f874bafc5ce1d9c554ad78ce64e31fbb341db489ca22b4e5fe01e9dd35faaf9a2809f6636c6bac668963a142a71043535a0efd479ef
 apache-trafficcontrol-6.0.2.tar.gz

SHA512 checksum:
de0abe5670f0a8a80ab12c73688f9a111794190d208d3190b6961934c0499ddb398f7fc45cd99d330c9f807e80c8a22cec385dbd60dd6498cc7b44831794452a
 apache-trafficcontrol-6.0.2.tar.gz

This corresponds to git refs:

Hash: d33bf4189911f8631d0583b28c9e70151ca82535
Tag: RELEASE-6.0.2-RC2

Which can be verified with the following command:

$ git tag -v RELEASE-6.0.2-RC2

All code signing keys are available here:

https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS

Make sure you refresh from a key server to get all relevant signatures.

The vote is open until 19:00 UTC on Wednesday, December 23 and passes
if a majority of at least 3 +1 PMC votes are cast.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-Zach

Re: [VOTE] Release Apache Traffic Control 6.0.2-RC1

[Zach Hoffman]

Sorry, this info is incorrect. Sending out RC2 shortly.

-Zach

On Mon, Dec 20, 2021 at 9:20 AM Zach Hoffman  wrote:
>
> I've prepared a release for 6.0.2-RC1. Changes since RELEASE-6.0.1:
>
> 
> https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.1...RELEASE-6.0.2-RC1
> 
> https://github.com/apache/trafficcontrol/blob/RELEASE-6.0.2-RC1/CHANGELOG.md
>
> The artifacts are available for download at:
>
> https://dist.apache.org/repos/dist/dev/trafficcontrol/6.0.2/RC1/
>
> BLAKE2 checksum:
> 4ac2bc3aed03bc26cd46480926dbb2ebd8e62148d71a032b7903888c0718f7a44690ebc46b1e163d905e9ee58a452f03bc23301ed62153ad31269a5fa605f02c
>  apache-trafficcontrol-6.0.2.tar.gz
>
> SHA512 checksum:
> a4b0c6ace6d01714aa7fa849dd35da49aa9c5f16aab7c28a834060fe5bf36fe7cb3869d639b59f6d57c0f9021f84280e8bbb759f906ff12afe77615eeb6007c2
>  apache-trafficcontrol-6.0.2.tar.gz
>
> This corresponds to git refs:
>
> Hash: 007107c699c7425c91d2d1a6f5b9928b7f3b2b9f
> Tag: RELEASE-6.0.2-RC1
>
> Which can be verified with the following command:
>
> $ git tag -v RELEASE-6.0.2-RC1
>
> All code signing keys are available here:
>
> https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS
>
> Make sure you refresh from a key server to get all relevant signatures.
>
> The vote is open until 16:20 UTC on Thursday, December 23 and passes
> if a majority of at least 3 +1 PMC votes are cast.
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> -Zach

[VOTE] Release Apache Traffic Control 6.0.2-RC1

[Zach Hoffman]

I've prepared a release for 6.0.2-RC1. Changes since RELEASE-6.0.1:


https://github.com/apache/trafficcontrol/compare/RELEASE-6.0.1...RELEASE-6.0.2-RC1
https://github.com/apache/trafficcontrol/blob/RELEASE-6.0.2-RC1/CHANGELOG.md

The artifacts are available for download at:

https://dist.apache.org/repos/dist/dev/trafficcontrol/6.0.2/RC1/

BLAKE2 checksum:
4ac2bc3aed03bc26cd46480926dbb2ebd8e62148d71a032b7903888c0718f7a44690ebc46b1e163d905e9ee58a452f03bc23301ed62153ad31269a5fa605f02c
 apache-trafficcontrol-6.0.2.tar.gz

SHA512 checksum:
a4b0c6ace6d01714aa7fa849dd35da49aa9c5f16aab7c28a834060fe5bf36fe7cb3869d639b59f6d57c0f9021f84280e8bbb759f906ff12afe77615eeb6007c2
 apache-trafficcontrol-6.0.2.tar.gz

This corresponds to git refs:

Hash: 007107c699c7425c91d2d1a6f5b9928b7f3b2b9f
Tag: RELEASE-6.0.2-RC1

Which can be verified with the following command:

$ git tag -v RELEASE-6.0.2-RC1

All code signing keys are available here:

https://dist.apache.org/repos/dist/release/trafficcontrol/KEYS

Make sure you refresh from a key server to get all relevant signatures.

The vote is open until 16:20 UTC on Thursday, December 23 and passes
if a majority of at least 3 +1 PMC votes are cast.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

-Zach