Re: General TC Cleanup

2018-04-30 Thread Hank Beatty 
I was considering adding a News page that would have a link in the top menu (HOME INFO DOCS ISSUES NEWS ...) when I was 
release manager.


Other projects put the news on the main page: https://httpd.apache.org/

Regardless, I think we should move it to the our apache.org site instead of 
GitHub.

- Hank

On 03/21/2018 12:54 PM, Dewayne Richardson wrote:

As we get more visibility as we become an Apache project, I've been taking
a fresh eye at Github project so that we can tidy up a bit to present
ourselves well.  I highly recommend that each of you do as well so that we
can get more eyeballs on the matter.

One nit that I've noticed is the

Github README.md News
https://github.com/apache/incubator-trafficcontrol#news

This section always seems to get overlooked with each TC release.  The
question I have is do we think the "News" section is still valuable (it's
was only used to point out releases), or is there a better location we
should be directing from our Github project that is more Apache facing so
that we're making changes in one place?

I've created this PR as my suggestion to the change.  Please provide
feedback and suggestions on the appropriate location for our "Traffic
Control News".

https://github.com/apache/incubator-trafficcontrol/pull/2011

-Dew

Re: [VOTE] Release Apache Traffic Control (incubating) 2.2.0-RC2

2018-03-08 Thread Hank Beatty 

+1

Lab Testing:

- Docker build - Could not figure out how to get all components to build at once
- build/build.sh on CentOS 6 - all components built successfully
- Upgraded Traffic Monitor (2.2.0.d7e588 -> 2.2.0.6ea850)
  - Could pull up UI and it connects to all cache servers
- Upgraded Traffic Router (2.2.0.d7e588 -> 2.2.0.6ea850)
  - Could connect to : and crs/stats looked correct
- Upgraded Traffic Stats (2.2.0.d7e588 -> 2.2.0.6ea850) CentOS 6
- Upgraded Traffic Ops ORT
  - mid cache "report" and "badass" mode seem to work correctly
  - edge cache "report" and "badass" mode seem to work correctly
- Tested DNS DS and works correctly

On 03/05/2018 01:25 PM, Robert Butts wrote:

Hello All,

I've prepared a release for v2.2.0-RC2

The vote is open for at least 72 hours and passes if a majority of at least
3 +1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.1.0:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-2.1.0...RELEASE-2.2.0-RC2

This corresponds to git:
  Hash: 6ea85056a1a69973be4a74b82d602df29f21f42d
  Tag: RELEASE-2.2.0-RC2

Which can be verified with the following: git tag -v RELEASE-2.2.0-RC2

My code signing key is available here:
http://keys.gnupg.net/pks/lookup?search=0xFDD04F7F=vindex

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha1 checksums are provided here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.2.0/RC2


Thanks!

Re: [VOTE] Traffic Control graduation to TLP

2018-03-01 Thread Hank Beatty 

+1

On 03/01/2018 10:41 AM, Dave Neuman wrote:

  Hey All,

After a great discussion amongst the Apache Traffic Control PPMC, reviewing
the graduation checklist[1], updating the podling status page[2], and
updating the project website to ensure the whimsy podling website checks
pass[3], I would like to call a vote for Apache Traffic Control graduating
to a top level project.

Apache Traffic Control entered the incubator on July 12, 2016.  Since then
we have announced 4 releases, nominated 4 new committers, organized 3
summits, had almost 8,000 commits from 63 different contributors, and --
most importantly -- we have grown and diversified our community.  Apache
Traffic Control is a healthy project that is already acting like an Apache
top level project, so we should take the next step.

If we agree that we should graduate to a top level project, the next steps
will be to pick the initial PMC chair for the TLP and draft a Resolution
for the PPMC and IPMC to vote upon.

Please take a minute to vote on wheter or not Traffic Control should
graduate to a Top Level Project by responding with one of the following:

[ ] +1 Apache Traffic Control should graduate.
[ ] +0 No opinion
[ ] -1 Apache Traffic Control should not graduate (please provide the
reason)

The VOTE will be opened for at least the next 72 hours.  Per Apache
guidelines[4] I will also be notifying the incubator mailing list that a
community vote is under way.

Thanks,
Dave


[1]
https://incubator.apache.org/guides/graduation.html#graduation_check_list
[2] http://incubator.apache.org/projects/trafficcontrol.html
[3] https://whimsy.apache.org/pods/project/trafficcontrol
[4]
https://incubator.apache.org/guides/graduation.html#community_graduation_vote

Re: [ANNOUNCE] Release Apache Traffic Control 2.1.0 (Incubating)

2018-01-22 Thread Hank Beatty 



On 01/22/2018 10:01 AM, sebb wrote:

On 22 January 2018 at 14:48, Hank Beatty <hbea...@apache.org> wrote:

The Apache Traffic Control team is proud to announce the release of Apache
Traffic Control 2.1.0 (incubating).

More details regarding Apache Traffic Control can be found at:

http://trafficcontrol.incubator.apache.org/

The release artifacts can be downloaded here:

https://www.apache.org/dyn/closer.cgi/incubator/trafficcontrol/2.1.0-incubating/


It would be better to point to

http://trafficcontrol.incubator.apache.org/downloads/index.html

which has links for KEYS etc.


I have updated our notes to reflect this change. Future ANNOUNCE emails
will have this update.



However the MD5 and SHA512 links are broken (page uses the wrong
extensions), and the page still refers to 2.0.0


The release notes can be found here:

http://trafficcontrol.incubator.apache.org/downloads/index.html


But these relate to 2.0.0 as noted above


The web page doesn't seem to have updated yet. Do you know how long
it usually takes for that to happen once a commit has been completed?

The new page has the corrections that you mention.




Thanks!
The Apache Traffic Control Team


Apache Traffic Control is an effort undergoing Incubation at The Apache
Software Foundation (ASF), sponsored by the Incubator. Incubation is
required of all newly accepted projects until a further review indicates
that the infrastructure, communications, and decision making process have
stabilized in a manner consistent with other successful ASF projects. While
incubation status is not necessarily a reflection of the completeness or
stability of the code, it does indicate that the project has yet to be fully
endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Release Apache Traffic Control 2.1.0 (Incubating)

2018-01-22 Thread Hank Beatty 

The Apache Traffic Control team is proud to announce the release of Apache 
Traffic Control 2.1.0 (incubating).

More details regarding Apache Traffic Control can be found at:

http://trafficcontrol.incubator.apache.org/

The release artifacts can be downloaded here:

https://www.apache.org/dyn/closer.cgi/incubator/trafficcontrol/2.1.0-incubating/

The release notes can be found here:

http://trafficcontrol.incubator.apache.org/downloads/index.html

Thanks!
The Apache Traffic Control Team


Apache Traffic Control is an effort undergoing Incubation at The Apache Software Foundation (ASF), sponsored by the 
Incubator. Incubation is required of all newly accepted projects until a further review indicates that the 
infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful 
ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it 
does indicate that the project has yet to be fully endorsed by the ASF.

[RESULT][VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC3

2018-01-22 Thread Hank Beatty 

Thanks to all who voted!

The release has PASSED with the following IPMC votes:

+1 Phil Sorber (binding)
+1 Justin Mclean (binding)
+1 Leif Hedstrom (binding)

I will proceed to publish the release and send ANNOUNCE.

On behalf of the Apache Traffic Control podling, thank you!

Regards,
Hank Beatty hbea...@apache.org

On 01/20/2018 11:40 AM, sebb wrote:

AFAIK the normal way to announce this is to send a message with the
subject starting:

[RESULT][VOTE] ...

Also the votes should be tallied.

See for example:

https://lists.apache.org/thread.html/95689e3c01a601a6c5ff8873785d8728c2eb2f95b040a9fbcb159d7f@%3Cgeneral.incubator.apache.org%3E


On 19 January 2018 at 13:47, Hank Beatty <hbea...@apache.org> wrote:

Hello,

It would appear RC3 has passed the IPMC vote. I'll do the release today.

Regards,
Hank

On 2018-01-17 17:01, Phil Sorber <sor...@apache.org> wrote:

+1 (binding). After having fought with docker for a bit I was able to
build
packages. Sig and hashes check out as well. We should work on getting all
our GPG keys signed by each other next summit, but that is not a show
stopper in my opinion.

Thanks!

On Tue, Jan 16, 2018 at 11:45 AM Leif Hedstrom <zw...@apache.org> wrote:


+1 (binding). Tested the build, RPMs successfully built, and double
checked the RAT report.

Cheers

%u2014 Leif


On Jan 10, 2018, at 18:04, Justin Mclean <jus...@classsoftware.com>

wrote:


Hi,

+1 (binding)

I checked:
- incubating in name
- hashes and signatures good
- DISCLAIMER exists
- LICENSE good and NOTICE OK (see below)
- no unexpected binary files
- All ALv2 source files have ASF headers

For the NOTICE don%u2019t forget to update the year to be the current
one and

there%u2019s no need to list information about the fonts inside it.


Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org






-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC3

2018-01-19 Thread Hank Beatty 

Hello,

It would appear RC3 has passed the IPMC vote. I'll do the release today.

Regards,
Hank

On 2018-01-17 17:01, Phil Sorber  wrote:
> +1 (binding). After having fought with docker for a bit I was able to build
> packages. Sig and hashes check out as well. We should work on getting all
> our GPG keys signed by each other next summit, but that is not a show
> stopper in my opinion.
>
> Thanks!
>
> On Tue, Jan 16, 2018 at 11:45 AM Leif Hedstrom  wrote:
>
> > +1 (binding). Tested the build, RPMs successfully built, and double
> > checked the RAT report.
> >
> > Cheers
> >
> > %u2014 Leif
> >
> > > On Jan 10, 2018, at 18:04, Justin Mclean 
> > wrote:
> > >
> > > Hi,
> > >
> > > +1 (binding)
> > >
> > > I checked:
> > > - incubating in name
> > > - hashes and signatures good
> > > - DISCLAIMER exists
> > > - LICENSE good and NOTICE OK (see below)
> > > - no unexpected binary files
> > > - All ALv2 source files have ASF headers
> > >
> > > For the NOTICE don%u2019t forget to update the year to be the current one 
and
> > there%u2019s no need to list information about the fonts inside it.
> > >
> > > Thanks,
> > > Justin
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC3

2018-01-08 Thread Hank Beatty 

Hello Incubator PMC,

I believe we have fixed all issues related to the vote thread found here:

https://lists.apache.org/thread.html/743bd8a999a375e9500485d778a753e5adfcc39e4b2bc42948aa4846@%3Cgeneral.incubator.apache.org%3E

We kindly request a review and vote on this RC3 version.

Regards,
Hank Beatty hbea...@apache.org

On 01/02/2018 09:39 AM, Hank Beatty wrote:

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 2.1.0-incubating. We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/49182efa73361f66590441b27988010317266a6de06a8f11706a7b4f@%3Cdev.trafficcontrol.apache.org%3E 



The previous approved releases and release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

This release once approved will also be at this location.

The proposed download page is here:

http://trafficcontrol.apache.org/downloads/index-new.html

The git tag for the repository is "RELEASE-2.1.0-RC3":

https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-2.1.0-RC3

The source distribution is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC3/

Build instructions are included in the BUILD.md file which is included
in the source artifact.

Artifacts have been signed with the hbea...@apache.org key listed in:

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

Please review and vote:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Hank Beatty hbea...@apache.org

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2018-01-08 Thread Hank Beatty 



On 01/08/2018 03:25 AM, Henk P. Penning wrote:


Hi Dan,

   regarding

     https://www.apache.org/dist/incubator/trafficcontrol/2.0.0-incubating/

   Please use extension .md5 instead of .md5sum ;
   this is required :

     http://www.apache.org/dev/release-distribution#sigs-and-sums

   Also, use extension .sha512 for a SHA-512 checksum file.


   Thank, regards,

   Henk Penning


   _
Henk P. Penning, ICT-beta R Uithof MG-403    _/ \_
Faculty of Science, Utrecht University    T +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/


Hello Henk,

The above files have been renamed and the new download page has been updated.

http://trafficcontrol.apache.org/downloads/index-new.html

Thanks,
Hank

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2018-01-08 Thread Hank Beatty 



On 12/29/2017 04:36 AM, Henk P. Penning wrote:


   +1 :-) ; don't forget to update your download page ;
   see also the points below [Regarding your website].



Hello Henk,

All of the changes mentioned below have been corrected on the new proposed 
download page located here:

http://trafficcontrol.apache.org/downloads/index-new.html

I'm working on removing the 1.8.1 links now.

Thanks,
Hank




On Thu, Dec 28, 2017 at 3:34 AM, Henk P. Penning <penn...@uu.nl> wrote:

On Thu, 7 Dec 2017, Hank Beatty wrote:


Date: Thu, 7 Dec 2017 17:17:59 +0100
From: Hank Beatty <hbea...@apache.org>
To: gene...@incubator.apache.org
Cc: dev@trafficcontrol.incubator.apache.org
Subject: Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2




On 12/06/2017 04:14 AM, Henk P. Penning wrote:





https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC2/




    Please rename
  apache-trafficcontrol-2.1.0-incubating.tar.gz.sha




I have renamed the file.



  Some more points ; in dist/incubator/trafficcontrol/

  PGP key c4b33c804587a8f0 [Dan Kirkwood <dang...@apache.org>] signed

    1.8.0-incubating/trafficcontrol-incubating-1.8.0.tar.gz.asc
    1.8.1-incubating/trafficcontrol-incubating-1.8.1.tar.gz.asc

  ... but this key expired on 2017-11-08.

  Please, either

    -- remove 1.8.0-incubating and 1.8.1-incubating
   from dist/incubator/trafficcontrol/
    -- fix (resign) key c4b33c804587a8f0 ;
    -- replace the .asc's

  See https://checker.apache.org/projs/incubator.html
  For help, see https://checker.apache.org/doc/README.html#prob-sigexp

  Note that 1.8.0-incubating and 1.8.1-incubating must be
  removed from dist/incubator/trafficcontrol/ when development
  on those branches has stopped (replaced by 2.x).
  [ http://www.apache.org/legal/release-policy.html#when-to-archive ]

  Regarding your website :

    https://trafficcontrol.incubator.apache.org/downloads/index.html

  Under "MD5 SHA512 PGP" you point to the mirrors, but sigs and
  checksums aren't on the mirrors ; please refer to [note the https]

    https://www.apache.org/dist/incubator/trafficcontrol/

  Please note that all your stuff in automatically archived at

    https://archive.apache.org/dist/incubator/trafficcontrol/

  Thanks ; regard,

  Henk Penning -- apache.org infrastructure ; mirrors

   _
Henk P. Penning, ICT-beta R Uithof MG-403    _/ \_
Faculty of Science, Utrecht University    T +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

[VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC3

2018-01-02 Thread Hank Beatty 

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 2.1.0-incubating. We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/49182efa73361f66590441b27988010317266a6de06a8f11706a7b4f@%3Cdev.trafficcontrol.apache.org%3E

The previous approved releases and release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

This release once approved will also be at this location.

The proposed download page is here:

http://trafficcontrol.apache.org/downloads/index-new.html

The git tag for the repository is "RELEASE-2.1.0-RC3":

https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-2.1.0-RC3

The source distribution is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC3/

Build instructions are included in the BUILD.md file which is included
in the source artifact.

Artifacts have been signed with the hbea...@apache.org key listed in:

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

Please review and vote:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,
Hank Beatty hbea...@apache.org

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC3

2018-01-02 Thread Hank Beatty 

Hello,

This vote has passed with +6. Putting together the IPMC email now.

Thanks everyone.

Hank

On 12/20/2017 05:14 PM, Dave Neuman wrote:

+1

On Wed, Dec 20, 2017 at 8:33 AM, Hank Beatty <hbea...@apache.org> wrote:


Hello All,

I've prepared a release for v2.1.0-RC3

The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/
2.0.x...RELEASE-2.1.0-RC3

This corresponds to git:
   Hash: 1dcd512f7e2b4898b090837cd3f260e453896e32
   Tag: RELEASE-2.1.0-RC3

Which can be verified with the following: git tag -v RELEASE-2.1.0-RC3

My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x920152B94E0CC77C

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC3

The new proposed download page can be found here:

https://trafficcontrol.incubator.apache.org/downloads/index-new.html

Thanks!

[VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC3

2017-12-20 Thread Hank Beatty 

Hello All,

I've prepared a release for v2.1.0-RC3

The vote is open for at least 72 hours and passes if a majority of at least 3 
+1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/2.0.x...RELEASE-2.1.0-RC3

This corresponds to git:
  Hash: 1dcd512f7e2b4898b090837cd3f260e453896e32
  Tag: RELEASE-2.1.0-RC3

Which can be verified with the following: git tag -v RELEASE-2.1.0-RC3

My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x920152B94E0CC77C

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC3

The new proposed download page can be found here:

https://trafficcontrol.incubator.apache.org/downloads/index-new.html

Thanks!

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-12-07 Thread Hank Beatty 



On 12/06/2017 04:14 AM, Henk P. Penning wrote:

On Tue, 5 Dec 2017, Hank Beatty wrote:


Date: Tue, 5 Dec 2017 17:49:03 +0100
From: Hank Beatty <hbea...@apache.org>
To: gene...@incubator.apache.org
Cc: dev@trafficcontrol.incubator.apache.org
Subject: Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 2.1.0-incubating. We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/a180ba5e90ed0e10972f647b444d039d7fee17a79fbab3b673999556@%3Cdev.trafficcontrol.apache.org%3E 



The previous approved releases and release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

This release once approved will also be at this location.

The proposed download page is here:

file:///media/repos/incubator-trafficcontrol-website/downloads/index-new.html

The git tag for the repository is "RELEASE-2.1.0-RC2":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-2.1.0-RC2


Hi,


The source distribution is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC2/


   Please rename

     apache-trafficcontrol-2.1.0-incubating.tar.gz.sha

   to

     apache-trafficcontrol-2.1.0-incubating.tar.gz.sha512

   Reference :

     http://www.apache.org/dev/release-distribution#sigs-and-sums

   Regards,

   Henk Penning


I have renamed the file.




Build instructions are included in the BUILD.md file which is included
in the source artifact.

Artifacts have been signed with the "hbea...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

Hank Beatty <hbea...@apache.org>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




   _
Henk P. Penning, ICT-beta R Uithof HFG-406   _/ \_
Faculty of Science, Utrecht University    T +31 30 253 4106 / \_/ \
Budapestlaan 6, 3584CD Utrecht, NL    F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-12-07 Thread Hank Beatty 



On 12/05/2017 06:31 PM, sebb wrote:

On 5 December 2017 at 16:49, Hank Beatty <hbea...@apache.org> wrote:

Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 2.1.0-incubating. We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/a180ba5e90ed0e10972f647b444d039d7fee17a79fbab3b673999556@%3Cdev.trafficcontrol.apache.org%3E

The previous approved releases and release notes (along with links to
artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

This release once approved will also be at this location.

The proposed download page is here:

file:///media/repos/incubator-trafficcontrol-website/downloads/index-new.html


Rather difficult to reach this from here ... so cannot comment.
But the existing download page has some problems - see below.


Here is the corrected link:

https://trafficcontrol.incubator.apache.org/downloads/index-new.html

I believe all of the issues mentioned below have been corrected on this new 
page.




The git tag for the repository is "RELEASE-2.1.0-RC2":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-2.1.0-RC2

The source distribution is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC2/

Build instructions are included in the BUILD.md file which is included
in the source artifact.

Artifacts have been signed with the "hbea...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS


Better to use the canonical location

https://www.apache.org/dist/incubator/trafficcontrol/KEYS


The 2 KEYS files mentioned here don't seem to match. My key isn't currently in the second one, but understand what you 
are saying.




Note also that the download page must also use the same host
(www.apache.org) for the sigs and hashes.
These are deliberately not provided to 3rd party mirrors.
Only the release archives should be linked from the 3rd party mirrors.


Please review and vote:

[ ] +1 Approve the release
[ ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

Hank Beatty <hbea...@apache.org>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-11-15 Thread Hank Beatty 

Yes, of course. How does Friday 11/17 or Monday 20/17 sound?

On 11/14/2017 04:09 PM, Dave Neuman wrote:

Hey Hank,
It looks like you have the votes you need to pass, but can you leave it
open a little longer for those of us that haven't gotten a chance to test
yet?

Thanks,
Dave

On Tue, Nov 14, 2017 at 12:47 PM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:


I’m +1 as well

Checked out:
- signatures/checksums (Hank is your key signed yet?)
- licenses
- build

—Eric



On Nov 14, 2017, at 2:36 PM, Nir Sopher  wrote:

+1
We were able to build traffic-control, install and connect OPs,

Portal-V2,

Monitor (Golang), Router and Stats.
Also got a redirect.
Note that I missed the last commit ("Change cdn.name to cdn.domain_name

in

DeliveryServiceInfoForDomainList"), but as far as I see it could not

break

the installation.
Nir

On Tue, Nov 14, 2017 at 8:10 PM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:


Thanks Matt-
  I found another LEGAL ticket (https://issues.apache.org/
jira/browse/LEGAL-330) based on a Google version of the PATENTS file

this

time.

Looks like things are OK to use then.

—Eric

On Nov 14, 2017, at 12:50 PM, Mills, Matthew > wrote:

FYI, Go itself has the same file

https://github.com/golang/go/blob/master/PATENTS


On 11/14/17, 10:36:43 AM, "Eric Friedrich (efriedri)" <

efrie...@cisco.com>

wrote:

   I’ve been going through licensing for the 2.1 release and found this
file:
   ./traffic_stats/vendor/golang.org/x/net/PATENTS

   This looks like it places some of the same restrictions that caused

the

whole Facebook React.js and rocksDb controversy a few months ago.
   Fun reading here: https://issues.apache.org/jira/browse/LEGAL-303
   There’s some in depth discussion of the detailed Facebook license, I
can’t even begin to speculate how that compares to this Google

conditional

patent grant.

   We can see what the IPMC/Legal thinks or maybe just remove the code?

   —Eric

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-11-15 Thread Hank Beatty 
Yes. Steve Malenfant signed it. Unfortunately, it looks like he is not in the "circle of trust" in the KEYS file. Does 
that matter?


On 11/14/2017 02:47 PM, Eric Friedrich (efriedri) wrote:

I’m +1 as well

Checked out:
- signatures/checksums (Hank is your key signed yet?)
- licenses
- build

—Eric



On Nov 14, 2017, at 2:36 PM, Nir Sopher  wrote:

+1
We were able to build traffic-control, install and connect OPs, Portal-V2,
Monitor (Golang), Router and Stats.
Also got a redirect.
Note that I missed the last commit ("Change cdn.name to cdn.domain_name in
DeliveryServiceInfoForDomainList"), but as far as I see it could not break
the installation.
Nir

On Tue, Nov 14, 2017 at 8:10 PM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:


Thanks Matt-
  I found another LEGAL ticket (https://issues.apache.org/
jira/browse/LEGAL-330) based on a Google version of the PATENTS file this
time.

Looks like things are OK to use then.

—Eric

On Nov 14, 2017, at 12:50 PM, Mills, Matthew > wrote:

FYI, Go itself has the same file

https://github.com/golang/go/blob/master/PATENTS


On 11/14/17, 10:36:43 AM, "Eric Friedrich (efriedri)" 
wrote:

   I’ve been going through licensing for the 2.1 release and found this
file:
   ./traffic_stats/vendor/golang.org/x/net/PATENTS

   This looks like it places some of the same restrictions that caused the
whole Facebook React.js and rocksDb controversy a few months ago.
   Fun reading here: https://issues.apache.org/jira/browse/LEGAL-303
   There’s some in depth discussion of the detailed Facebook license, I
can’t even begin to speculate how that compares to this Google conditional
patent grant.

   We can see what the IPMC/Legal thinks or maybe just remove the code?

   —Eric

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-11-13 Thread Hank Beatty 
Now that everyone has had the weekend to review RC2 we should be ready to cut the release. I didn't see any -1. I'm 
going to take that as acceptance and move forward.


Regards,
Hank

:) Just kidding.

On 11/10/2017 03:30 PM, Dewayne Richardson wrote:

Nice work 72 hours on a Friday!

On Fri, Nov 10, 2017 at 11:21 AM, Hank Beatty <hbea...@apache.org> wrote:


Hello All,

I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/
2.0.x...RELEASE-2.1.0-RC2

This corresponds to git:
   Hash: cac666ef7f0626ea8180e976b07fa841d53f755f
   Tag: RELEASE-2.1.0-RC2

Which can be verified with the following: git tag -v RELEASE-2.1.0-RC1

My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x920152B94E0CC77C

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC2


Thanks!

[VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC2

2017-11-10 Thread Hank Beatty 

Hello All,

I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority of at least 3 
+1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/2.0.x...RELEASE-2.1.0-RC2

This corresponds to git:
  Hash: cac666ef7f0626ea8180e976b07fa841d53f755f
  Tag: RELEASE-2.1.0-RC2

Which can be verified with the following: git tag -v RELEASE-2.1.0-RC1

My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x920152B94E0CC77C

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC2


Thanks!

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

2017-10-27 Thread Hank Beatty 

This vote has failed. There will be a new RC when the issues have been resolved.

Thanks,
Hank

On 10/23/2017 04:01 PM, Hank Beatty wrote:

Hello All,

I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority of at least 3 
+1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/2.0.x...RELEASE-2.1.0-RC1

This corresponds to git:
  Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206
  Tag: RELEASE-2.1.0-RC1

Which can be verified with the following: git tag -v RELEASE-2.1.0-RC1

My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x582D3F6E79270895

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC1

Thanks!

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

2017-10-27 Thread Hank Beatty 

There are 41 pages of PRs that do not have milestones.

On 10/26/2017 02:24 PM, Dave Neuman wrote:

Yeah, every PR should have a milestone

On Thu, Oct 26, 2017 at 11:42 AM, Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:


Do PRs/issues that don’t have a milestone assigned still end up in this
changelog? I know theres a bunch more that went into 2.1 that isn’t in this
list.

Should we make sure that every PR/Issue is assigned a milestone before its
merged?


On Oct 26, 2017, at 12:52 PM, Hank Beatty <hbea...@gmail.com> wrote:

Thanks Phil this is very nice.

Both of these scripts use the "milestones" to generate the changelog.

Currently there are 21 issues associated with the 2.1.0 milestone.


Here is the output of the one in TC:

Changes with Traffic Control 2.1.0
  #878 - [TC-488] Docs - Multi Site Origin not up to date
  #879 - [TC-490] mso.qstring_handling parameter is checked but not

documented

  #880 - [TC-489] Multi Site Origin - Invalid default values for multiple

config params

  #901 - [TC-377] Default profiles for EDGE and MID are missing after

initial install

  #906 - [TC-327] ConfigFiles.pm detects blank as not null and tries to

gen files GH #1090

  #909 - [TC-301] creating https delivery service and not setting to

active still looks for cert. Github Issue #1086

  #912 - [TC-169] TR download the RGB file continuously when the same RGB

file on server

  #915 - [TC-116] remap.config order is different on master (postgres)

than it is on 1.8.

  #980 - [TC-552] Global parameters may be duplicated when seeds.sql is

run

  #988 - [TC-514] ORT: Change Traffic Ops hostname in middle of ORT run
  #1001 - [TC-408] Documentation for creating ssl keys is missing a field.
  #1090 - [TC-518] ToCDUCheck and ToCHRCheck: Value formatted as float

instead of int

  #1115 - [TC-429] - TP - removes map due to license incompatibility
  #1118 - POST /api/1.2/deliveryserviceserver doesn't update header

rewrite, regex remap and cacheurl

  #1167 - [BACKPORT][TC-518] ToCDUCheck and ToCHRCheck: Value formatted

as float instead of int #1090

  #1168 - [BACKPORT][TC-514] ORT: Change Traffic Ops hostname in middle

of ORT run

  #1195 - [Issue-1189] - Backport to 2.1.x - delivery service tenancy is

forced on creation and update if use_tenancy is on

  #1375 - BACKPORT - fix docs for Deliveryservice/sslkeys/generate and

deliveryservice/ssl…

  #1386 - Traffic Portal V2 main menu has two rows labeled "Tenants"


On 10/26/2017 11:55 AM, Phil Sorber wrote:

I believe this one has had a little more love recently and does things

like

only include merged pull requests, etc.
https://github.com/apache/trafficserver/blob/master/tools/changelog.pl
On Thu, Oct 26, 2017 at 9:52 AM Phil Sorber <sor...@apache.org> wrote:

You guys mean like this?


https://github.com/apache/incubator-trafficcontrol/blob/

master/misc/changelog.pl


On Thu, Oct 26, 2017 at 8:39 AM Hank Beatty <hbea...@apache.org>

wrote:



I was thinking of starting with something like this:
https://github.com/skywinder/github-changelog-generator#

output-example.

I will also look at the github-changes that Steve mentions.

Hank

On 10/26/2017 08:48 AM, Steve Malenfant wrote:

Do we have a sample from a script that would create a change log

based

on

pull request only? I tried `github-changes` yesterday but it seemed

to

work

only with the older releases (<1.8). Although I haven't spent much

time

on

it.

We should probably only list the high level changes such as new

features,

improvements, important fixes and breaking changes (relates to

operations

action required).

Few things we should note as well :
- How to upgrade from pre-2.0 releases
- What are the upgrade procedures (run postinstall for example)
- Profiles locations (not included in 2.x basic install anymore)

I'm sure some of those are documented already, might just requires
references.

Steve



On Wed, Oct 25, 2017 at 8:06 AM, Hank Beatty <hbea...@apache.org>

wrote:



Hello Steve,

The release notes are still being worked on. I am also looking for
suggestions on how the release notes should be formatted, and how

they

might be auto-generated. If you have any, please let me know.

Regards,
Hank

On 10/24/2017 07:26 AM, Steve Malenfant wrote:


Is there any Release Notes associated with this release? 1,337

changes and

the link above will only display 250 of them.

Steve

On Mon, Oct 23, 2017 at 4:01 PM, Hank Beatty <hbea...@apache.org>

wrote:


Hello All,


I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority

of at

least 3 +1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/
2.0.x...RELEASE-2.1.0-RC1

This corresponds to git:
Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206

<(505)%20927-1206>

<(505)%20927-1206>

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

2017-10-26 Thread Hank Beatty 
Not currently. We either need to use a different script to generate the changelog or go back and modify all of the 
PRs/commits to have the 2.1.0 milestone.


Give me until tomorrow because I would like to look at the other one that I 
presented.

Hank

On 10/26/2017 01:42 PM, Eric Friedrich (efriedri) wrote:

Do PRs/issues that don’t have a milestone assigned still end up in this 
changelog? I know theres a bunch more that went into 2.1 that isn’t in this 
list.

Should we make sure that every PR/Issue is assigned a milestone before its 
merged?


On Oct 26, 2017, at 12:52 PM, Hank Beatty <hbea...@gmail.com> wrote:

Thanks Phil this is very nice.

Both of these scripts use the "milestones" to generate the changelog. Currently 
there are 21 issues associated with the 2.1.0 milestone.

Here is the output of the one in TC:

Changes with Traffic Control 2.1.0
  #878 - [TC-488] Docs - Multi Site Origin not up to date
  #879 - [TC-490] mso.qstring_handling parameter is checked but not documented
  #880 - [TC-489] Multi Site Origin - Invalid default values for multiple 
config params
  #901 - [TC-377] Default profiles for EDGE and MID are missing after initial 
install
  #906 - [TC-327] ConfigFiles.pm detects blank as not null and tries to gen 
files GH #1090
  #909 - [TC-301] creating https delivery service and not setting to active 
still looks for cert. Github Issue #1086
  #912 - [TC-169] TR download the RGB file continuously when the same RGB file 
on server
  #915 - [TC-116] remap.config order is different on master (postgres) than it 
is on 1.8.
  #980 - [TC-552] Global parameters may be duplicated when seeds.sql is run
  #988 - [TC-514] ORT: Change Traffic Ops hostname in middle of ORT run
  #1001 - [TC-408] Documentation for creating ssl keys is missing a field.
  #1090 - [TC-518] ToCDUCheck and ToCHRCheck: Value formatted as float instead 
of int
  #1115 - [TC-429] - TP - removes map due to license incompatibility
  #1118 - POST /api/1.2/deliveryserviceserver doesn't update header rewrite, 
regex remap and cacheurl
  #1167 - [BACKPORT][TC-518] ToCDUCheck and ToCHRCheck: Value formatted as 
float instead of int #1090
  #1168 - [BACKPORT][TC-514] ORT: Change Traffic Ops hostname in middle of ORT 
run
  #1195 - [Issue-1189] - Backport to 2.1.x - delivery service tenancy is forced 
on creation and update if use_tenancy is on
  #1375 - BACKPORT - fix docs for Deliveryservice/sslkeys/generate and 
deliveryservice/ssl…
  #1386 - Traffic Portal V2 main menu has two rows labeled "Tenants"


On 10/26/2017 11:55 AM, Phil Sorber wrote:

I believe this one has had a little more love recently and does things like
only include merged pull requests, etc.
https://github.com/apache/trafficserver/blob/master/tools/changelog.pl
On Thu, Oct 26, 2017 at 9:52 AM Phil Sorber <sor...@apache.org> wrote:

You guys mean like this?


https://github.com/apache/incubator-trafficcontrol/blob/master/misc/changelog.pl

On Thu, Oct 26, 2017 at 8:39 AM Hank Beatty <hbea...@apache.org> wrote:


I was thinking of starting with something like this:
https://github.com/skywinder/github-changelog-generator#output-example.
I will also look at the github-changes that Steve mentions.

Hank

On 10/26/2017 08:48 AM, Steve Malenfant wrote:

Do we have a sample from a script that would create a change log based

on

pull request only? I tried `github-changes` yesterday but it seemed to

work

only with the older releases (<1.8). Although I haven't spent much time

on

it.

We should probably only list the high level changes such as new

features,

improvements, important fixes and breaking changes (relates to

operations

action required).

Few things we should note as well :
- How to upgrade from pre-2.0 releases
- What are the upgrade procedures (run postinstall for example)
- Profiles locations (not included in 2.x basic install anymore)

I'm sure some of those are documented already, might just requires
references.

Steve



On Wed, Oct 25, 2017 at 8:06 AM, Hank Beatty <hbea...@apache.org>

wrote:



Hello Steve,

The release notes are still being worked on. I am also looking for
suggestions on how the release notes should be formatted, and how they
might be auto-generated. If you have any, please let me know.

Regards,
Hank

On 10/24/2017 07:26 AM, Steve Malenfant wrote:


Is there any Release Notes associated with this release? 1,337

changes and

the link above will only display 250 of them.

Steve

On Mon, Oct 23, 2017 at 4:01 PM, Hank Beatty <hbea...@apache.org>

wrote:


Hello All,


I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/
2.0.x...RELEASE-2.1.0-RC1

This corresponds to git:
Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206 <

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

2017-10-26 Thread Hank Beatty 

Thanks Phil this is very nice.

Both of these scripts use the "milestones" to generate the changelog. Currently there are 21 issues associated with the 
2.1.0 milestone.


Here is the output of the one in TC:

Changes with Traffic Control 2.1.0
  #878 - [TC-488] Docs - Multi Site Origin not up to date
  #879 - [TC-490] mso.qstring_handling parameter is checked but not documented
  #880 - [TC-489] Multi Site Origin - Invalid default values for multiple 
config params
  #901 - [TC-377] Default profiles for EDGE and MID are missing after initial 
install
  #906 - [TC-327] ConfigFiles.pm detects blank as not null and tries to gen 
files GH #1090
  #909 - [TC-301] creating https delivery service and not setting to active 
still looks for cert. Github Issue #1086
  #912 - [TC-169] TR download the RGB file continuously when the same RGB file 
on server
  #915 - [TC-116] remap.config order is different on master (postgres) than it 
is on 1.8.
  #980 - [TC-552] Global parameters may be duplicated when seeds.sql is run
  #988 - [TC-514] ORT: Change Traffic Ops hostname in middle of ORT run
  #1001 - [TC-408] Documentation for creating ssl keys is missing a field.
  #1090 - [TC-518] ToCDUCheck and ToCHRCheck: Value formatted as float instead 
of int
  #1115 - [TC-429] - TP - removes map due to license incompatibility
  #1118 - POST /api/1.2/deliveryserviceserver doesn't update header rewrite, 
regex remap and cacheurl
  #1167 - [BACKPORT][TC-518] ToCDUCheck and ToCHRCheck: Value formatted as 
float instead of int #1090
  #1168 - [BACKPORT][TC-514] ORT: Change Traffic Ops hostname in middle of ORT 
run
  #1195 - [Issue-1189] - Backport to 2.1.x - delivery service tenancy is forced 
on creation and update if use_tenancy is on
  #1375 - BACKPORT - fix docs for Deliveryservice/sslkeys/generate and 
deliveryservice/ssl…
  #1386 - Traffic Portal V2 main menu has two rows labeled "Tenants"


On 10/26/2017 11:55 AM, Phil Sorber wrote:

I believe this one has had a little more love recently and does things like
only include merged pull requests, etc.

https://github.com/apache/trafficserver/blob/master/tools/changelog.pl

On Thu, Oct 26, 2017 at 9:52 AM Phil Sorber <sor...@apache.org> wrote:


You guys mean like this?


https://github.com/apache/incubator-trafficcontrol/blob/master/misc/changelog.pl

On Thu, Oct 26, 2017 at 8:39 AM Hank Beatty <hbea...@apache.org> wrote:


I was thinking of starting with something like this:
https://github.com/skywinder/github-changelog-generator#output-example.
I will also look at the github-changes that Steve mentions.

Hank

On 10/26/2017 08:48 AM, Steve Malenfant wrote:

Do we have a sample from a script that would create a change log based

on

pull request only? I tried `github-changes` yesterday but it seemed to

work

only with the older releases (<1.8). Although I haven't spent much time

on

it.

We should probably only list the high level changes such as new

features,

improvements, important fixes and breaking changes (relates to

operations

action required).

Few things we should note as well :
- How to upgrade from pre-2.0 releases
- What are the upgrade procedures (run postinstall for example)
- Profiles locations (not included in 2.x basic install anymore)

I'm sure some of those are documented already, might just requires
references.

Steve



On Wed, Oct 25, 2017 at 8:06 AM, Hank Beatty <hbea...@apache.org>

wrote:



Hello Steve,

The release notes are still being worked on. I am also looking for
suggestions on how the release notes should be formatted, and how they
might be auto-generated. If you have any, please let me know.

Regards,
Hank

On 10/24/2017 07:26 AM, Steve Malenfant wrote:


Is there any Release Notes associated with this release? 1,337

changes and

the link above will only display 250 of them.

Steve

On Mon, Oct 23, 2017 at 4:01 PM, Hank Beatty <hbea...@apache.org>

wrote:


Hello All,


I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/
2.0.x...RELEASE-2.1.0-RC1

This corresponds to git:
Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206 <(505)%20927-1206>

<(505)%20927-1206>

<(505)%20927-1206>
Tag: RELEASE-2.1.0-RC1

Which can be verified with the following: git tag -v

RELEASE-2.1.0-RC1


My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x582D3F6E79270895

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

signatures.


The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcont
rol/2.1.0/RC1

Thanks!

Re: [VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

2017-10-25 Thread Hank Beatty 

Hello Steve,

The release notes are still being worked on. I am also looking for 
suggestions on how the release notes should be formatted, and how they 
might be auto-generated. If you have any, please let me know.


Regards,
Hank

On 10/24/2017 07:26 AM, Steve Malenfant wrote:

Is there any Release Notes associated with this release? 1,337 changes and
the link above will only display 250 of them.

Steve

On Mon, Oct 23, 2017 at 4:01 PM, Hank Beatty <hbea...@apache.org> wrote:


Hello All,

I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority of at
least 3 +1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/
2.0.x...RELEASE-2.1.0-RC1

This corresponds to git:
  Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206 <(505)%20927-1206>
  Tag: RELEASE-2.1.0-RC1

Which can be verified with the following: git tag -v RELEASE-2.1.0-RC1

My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x582D3F6E79270895

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC1

Thanks!

[VOTE] Release Apache Traffic Control (incubating) 2.1.0-RC1

2017-10-23 Thread Hank Beatty 

Hello All,

I've prepared a release for v2.1.0-RC1

The vote is open for at least 72 hours and passes if a majority of at least 3 
+1 PPMC votes are cast.

[ ] +1 Approve the release

[ ] -1 Do not release this package because ...

Changes since 2.0.0:
https://github.com/apache/incubator-trafficcontrol/compare/2.0.x...RELEASE-2.1.0-RC1

This corresponds to git:
 Hash:6ea2ca86d07c16a3b3ca419dd56b975059271206
 Tag: RELEASE-2.1.0-RC1

Which can be verified with the following: git tag -v RELEASE-2.1.0-RC1

My code signing key is available here:
https://pgp.mit.edu/pks/lookup?op=get=0x582D3F6E79270895

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.1.0/RC1

Thanks!

2.1 Release Update

2017-08-16 Thread Hank Beatty 

Hello Everyone,

I have finished my first pass of the open bugs that could possibly apply 
to 2.1. We have reduced the count from 110 to 80! There are some of 
these that already have PRs open. I plan on starting to go through these 
today. If anyone has time to test/review another's PR and merge to 
master I would greatly appreciate it.


Thank you all for your help.

Regards,
Hank

Bug query I've been using:

https://issues.apache.org/jira/browse/TC-44?jql=project%20%3D%20TC%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20in%20(EMPTY%2C%201.7.0%2C%201.8.0%2C%201.9.0%2C%202.0.0%2C%202.1.0)%20ORDER%20BY%20key%20ASC

Fwd: [jira] [Created] (TC-187) Update delivery service makes SSL keys invalid

2017-08-10 Thread Hank Beatty 
It looks like this one is ready to be merged. Can someone please take a 
look at this PR https://github.com/apache/incubator-trafficcontrol/pull/360?


Thanks,
Hank



 Forwarded Message 
Subject: 	[jira] [Created] (TC-187) Update delivery service makes SSL 
keys invalid

Date:   Tue, 14 Mar 2017 06:27:41 + (UTC)
From:   Zhilin Huang (JIRA) 
Reply-To:   dev@trafficcontrol.incubator.apache.org
To: iss...@trafficcontrol.incubator.apache.org



Zhilin Huang created TC-187:
---

 Summary: Update delivery service makes SSL keys invalid
 Key: TC-187
 URL: https://issues.apache.org/jira/browse/TC-187
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops
Reporter: Zhilin Huang
Assignee: Zhilin Huang


Modify xml-id or subdomain in a https delivery service will make existing SSL 
keys invalid.

And there is problem to generate keys if using "http and https" together with 1 
host_regex, and 1 path_regex.

BTW, the certificate returned by RESTful API is not consistent with that GUI.



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

Fwd: [jira] [Created] (TC-157) Failed to restart tomcat in Traffic Router when failed to get SSL keys

2017-08-10 Thread Hank Beatty 
There is a PR 
(https://github.com/apache/incubator-trafficcontrol/pull/294) open for 
this one. Can someone review and merge and backport if acceptable?


Thanks,
Hank



 Forwarded Message 
Subject: 	[jira] [Created] (TC-157) Failed to restart tomcat in Traffic 
Router when failed to get SSL keys

Date:   Mon, 20 Feb 2017 08:37:44 + (UTC)
From:   Zhilin Huang (JIRA) 
Reply-To:   dev@trafficcontrol.incubator.apache.org
To: iss...@trafficcontrol.incubator.apache.org



Zhilin Huang created TC-157:
---

 Summary: Failed to restart tomcat in Traffic Router when failed to 
get SSL keys
 Key: TC-157
 URL: https://issues.apache.org/jira/browse/TC-157
 Project: Traffic Control
  Issue Type: Bug
Reporter: Zhilin Huang
Assignee: Zhilin Huang


Stopping tomcat failed with the following log:

WARN  2017-02-17T09:00:05.939 [main] 
com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesPublisher
 - Detected destroy setting running to false
INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.secure.CertificatesClient - 
Interrupted while pausing for check of traffic ops config
INFO  2017-02-17T09:00:05.943 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - POSTing: 
https://192.168.122.181/api/1.1/user/login; timeout is 15000
INFO  2017-02-17T09:00:06.005 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - GETing: 
https://192.168.122.181/api/1.2/cdns/name/kabletown_cdn/sslkeys.jso
n; timeout is 15000
WARN  2017-02-17T09:00:06.040 [pool-2-thread-1] 
com.comcast.cdn.traffic_control.traffic_router.core.util.Fetcher - Failed Http 
Request to https://192.168.122.181/api/1.2/cdns/name/kabletown_
cdn/sslkeys.json Status 400



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

Fwd: [jira] [Created] (TC-151) Delivery Service XML IDs should be limited to lower-case letters

2017-08-10 Thread Hank Beatty 
Does anyone know if this has been fixed? If not, are we planning in 
fixing it for 2.1?


Thanks,
Hank



 Forwarded Message 
Subject: 	[jira] [Created] (TC-151) Delivery Service XML IDs should be 
limited to lower-case letters

Date:   Thu, 16 Feb 2017 08:10:41 + (UTC)
From:   Oren Shemesh (JIRA) 
Reply-To:   dev@trafficcontrol.incubator.apache.org
To: iss...@trafficcontrol.incubator.apache.org



Oren Shemesh created TC-151:
---

 Summary: Delivery Service XML IDs should be limited to lower-case 
letters
 Key: TC-151
 URL: https://issues.apache.org/jira/browse/TC-151
 Project: Traffic Control
  Issue Type: Bug
  Components: Traffic Ops
Affects Versions: 1.7.0
Reporter: Oren Shemesh
Priority: Minor


The DNS system is case-insensitive. Since a delivery service XML ID is used as 
part of the FQDN of the cache being redirected to, two different DSs cannot 
differ only by case.
This leads to the conclusion that it is best if we limit the XML IDs of 
delivery services to be lower-case only.
This would achieve the following:
1. Make domain names used by TC 'conventional' (i.e. lower-case only)
2. Remove the possibility of a case-conflict between DSs
3. Currently, Traffic Router does not behave correctly when a DS XML ID 
contains upper case letters. Limiting to lower-case would prevent the need to 
fix this :-)

Current problems with TR behaviour, when an XML ID contains opper-case letter 
are:
1. The TR sends a redirect to a host FQDN which contains a lower-case version 
of the DS XML ID
2. The TR does not resolve the lower-case version of the host FQDN.

Here is an example to demo current bug in TR. DS XML ID is opencachehub-DT, TR 
redirects to opencachehub-dt, and then refused to resolve the cache name using 
this DS (a lot of irrelevant data was removed fro this text):


$ curl -L -s -D - 
http://tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com/video01.mp4 -v
* Connected to tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com 
(54.244.152.242) port 80 (#0)

GET /video01.mp4 HTTP/1.1
Host: tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com
Accept: */*


< HTTP/1.1 302 Moved Temporarily
< Location: 
http://p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com/video01.mp4
< Content-Length: 0

<
* Connection #0 to host tr.opencachehub-DT.stage-cdn.tc-stage.cqloud.com left 
intact
* Issue another request to this URL: 
'http://p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com/video01.mp4'
* getaddrinfo(3) failed for 
p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com:80
* Couldn't resolve host 
'p39-edge-lab.opencachehub-dt.stage-cdn.tc-stage.cqloud.com'




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

Fwd: [jira] [Updated] (TC-118) Traffic Ops should get it's name from some confioguration when generating CrConfig

2017-08-10 Thread Hank Beatty 
Does anyone know if this has been fixed? If not, are we planning in 
fixing it for 2.1?


Thanks,
Hank



 Forwarded Message 
Subject: 	[jira] [Updated] (TC-118) Traffic Ops should get it's name 
from some confioguration when generating CrConfig

Date:   Wed, 14 Jun 2017 19:00:01 + (UTC)
From:   Ryan Durfey (JIRA) 
Reply-To:   dev@trafficcontrol.incubator.apache.org
To: iss...@trafficcontrol.incubator.apache.org



 [ 
https://issues.apache.org/jira/browse/TC-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ryan Durfey updated TC-118:
---
Labels: configuration crconfig  (was: )


Traffic Ops should get it's name from some confioguration when generating 
CrConfig
--

Key: TC-118
URL: https://issues.apache.org/jira/browse/TC-118
Project: Traffic Control
 Issue Type: Bug
 Components: Traffic Ops
   Affects Versions: 1.7.0
   Reporter: Oren Shemesh
   Priority: Minor
 Labels: configuration, crconfig

The code that generates the CrConfig has a problem when creating the "stat" 
section.
It fills values for that section, such as "tm_host", based on the HTTP headers 
found in the request that triggered the CrConfig snapshot:
Here is a snippet from traffic_ops/app/lib/UI/Topology.pm:
$data_obj->{'stats'}->{'tm_path'}= $self->req->url->path->{'path'};
$data_obj->{'stats'}->{'tm_host'}= $self->req->headers->host;
I find this to be a problem for two reasons:
This code assumes that it is being run from the context of an HTTP transaction, which to me sounds like contaminating the logic of actually creating the CrConfig with details from the upper layer which currently uses this logic. 
For example, if one would want to run this code from a different path (Maybe in a unit test), it would be a problem.

If the traffic ops is accessed through a NAT, then the host name known to the 
HTTP client issuing the 'Snapshot CrConfig' request is not necessarily the same 
as the traffic ops host name known to the other components of the system, e.g. 
the traffic router that uses this information.
(This is how I found out about this problem - we are experimenting with 
deploying TC in the cloud (Amazon EC2) and the host name visible to the outside 
world is not the same as the host names used internally)
I believe that tm_host should come from the database (Currently there is no 
entry from the traffic ops itself, but such an entry can be created for this 
purpose), or from cdn.conf.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Starting the 2.1 Branch for Next Release of TC

2017-08-01 Thread Hank Beatty 

Hello All,

How does getting all the changes in this week and I'll cut the 2.1 
branch first thing Monday morning (8/7/17 6AM Eastern)?


Thanks,
Hank

On 07/31/2017 03:58 PM, Dave Neuman wrote:

Hey Hank,
Are you still planning on cutting a release sometime this week?
I have a few PRs that I was planning on merging and wanted to see if I have
some time.

Thanks,
Dave

On Tue, Jul 18, 2017 at 2:46 PM, Nir Sopher <n...@qwilt.com> wrote:


Hi Hank,
With guidance and review by Jeremy, we are working on the first phase of
tenancy for version 2.1.
Tenants were already introduced to the TC database, and next to get in are
the tenancy based access control enforcement - for users as well as
delivery services.
We expect it to be fully in master within 2 weeks.
Thanks,
Nir


On Tue, Jul 18, 2017 at 3:33 PM, Hank Beatty <hbea...@apache.org> wrote:


Good Morning,

I am very excited to be the Release Manager for the 2.1 version of TC.

We are getting ready to start the 2.1 branch of TC. We would like to do
this in the next 2 weeks.

Are there any know issues that would prevent this from happening?

Are there any features that can be wrapped up and go into this version?

Any other comments or suggestions?

Thanks,
Hank

Re: 2.1 RM

2017-07-17 Thread Hank Beatty 

Hi Dave,

I would like to volunteer.

Thanks,
Hank

On 07/05/2017 03:38 PM, Dave Neuman wrote:

Hey All,
Now that 2.0 has officially passed the project and IPMC vote (YAY!), it's
time to start thinking about 2.1.  I don't think we have identified a
release manager for the 2.1 release yet, would anyone like to volunteer?

Thanks,
Dave

Re: Project Management - Shared Dashboards

2017-06-15 Thread Hank Beatty 

I'm unable to access these.

Traffic Ops: private filters
Traffic Ops API: private filters
Traffic Router: private filters
Traffic Monitor: private filters
Traffic Portal: private filters
Traffic Stats: don't have access
Traffic Analytics: private filters

Also, don't these become unusable once we go back to github.com or did I 
misunderstand and we are still using JIRA?


Thanks,
Hank

On 06/15/2017 11:31 AM, Durfey, Ryan wrote:

These should all be available to anyone in our project.
Traffic Ops 
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12331420
Traffic Ops API 
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12331414
Traffic Router 
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12331415
Traffic Monitor 
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12331416
Traffic Portal 
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12331417
Traffic Stats 
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12331418
Traffic Analytics 
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12331419


Ryan DurfeyM | 303-524-5099
CDN Support (24x7): 866-405-2993 or 
cdn_supp...@comcast.com


From: Dave Neuman 
Reply-To: "dev@trafficcontrol.incubator.apache.org" 

Date: Thursday, June 15, 2017 at 11:11 AM
To: "dev@trafficcontrol.incubator.apache.org" 

Subject: Re: Project Management - Shared Dashboards

Links?

On Thu, Jun 15, 2017 at 8:42 AM, Durfey, Ryan 
>
wrote:

I created shared dashboards for the open issues of each major component.
Please let me know if you think of any other dashboards that might be
helpful.

Ryan Durfey
Sr. Product Manager - CDN | Comcast Technology Solutions
1899 Wynkoop Ste. 550 | Denver, CO 8020
M | 303-524-5099
ryan_dur...@comcast.com
CDN Support (24x7): 866-405-2993 or 
cdn_supp...@comcast.commailto:cdn_supp...@comcast.com>>

Re: Traffic Ops - Reorganize the client directory

2017-06-15 Thread Hank Beatty 

I started a Traffic Control Client in python.

You can find it here:

https://github.com/hbeatty/traffic-control-python

Still needs a lot of work!

Thanks,
Hank

On 06/14/2017 11:35 AM, Scrimo, Robert (Contractor) wrote:

All,

I would like to add a Python Traffic Ops Client to the 
‘apache/incubator-trafficcontrol’ repository but while I am in there I should 
probably re-organize the golang client that resides in there too.  This will 
most definitely break other code dependent on its current location, which is 
the root of the client directory.  I am proposing to move the golang code to a 
newly created ‘golang’ directory and add a ‘python’ directory for my Python 
client.  I will fix any references to code using the client from within the 
‘incubator-trafficcontrol’ repository.  If anyone has any 
insight/objections/comments about this please respond.  I will take your 
silence as approval...

Thank you,
-Robert

Re: [VOTE] Release Apache Traffic Control 2.0.0-incubating (RC4)

2017-06-08 Thread Hank Beatty 
I just realized it is our cdn.conf that doesn't have the secrets in it 
not the default. Still don't think it should error. I'll fix it and 
submit the PR.


On 06/08/2017 11:30 AM, Dan Kirkwood wrote:

not that I'm aware of...  please do file an issue for it,  though and
attach that to the PR.

thanks!  Dan

On Thu, Jun 8, 2017 at 9:18 AM, Hank Beatty <hbea...@apache.org> wrote:

postinstall might still be broken:

Password for database server admin:
Re-Enter Password for database server admin:
Download Maxmind Database? [yes]:
Download Maxmind Database?: yes
===/opt/traffic_ops/app/conf/cdn.conf===
Generate a new secret? [yes]:
Generate a new secret?: yes
Number of secrets to keep? [10]:
Number of secrets to keep?: 10
Can't use an undefined value as an ARRAY reference at
/opt/traffic_ops/install/bin/_postinstall line 211,  line 13.

And I've already started looking into it...

It is trying to load the secrets from the cdn.conf file. The initial
cdn.conf file doesn't have any secrets. I can fix the _postinstall to
correct this and do a PR.

Unless someone else has already fixed it or it needs to be done a different
way.

Thanks,
Hank

On 06/05/2017 02:16 PM, Eric Friedrich (efriedri) wrote:


Hello All,

I've prepared the next candidate release for incubator-trafficcontrol
v2.0.0 (RC4)

Changes since 1.8.0:

https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC4<https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC3>

This corresponds to git:
Hash: 795ea3adf2003dd27523b6b9ff4691f23d41ce30
Tag: RELEASE-2.0.0-RC4

Which can be verified with the following:git tag -v RELEASE-2.0.0-RC4

My code signing key is available here:
http://pgp.mit.edu/pks/lookup?op=get=0xF2200BAB9AB7BDD5

and here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), and md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.0.0/RC4


The vote will remain open until Thursday, June 8, 2017.

This RC fixes some packaging issues in RC2 and RC3, there are no other
changes. The git tag hash is the same, but due to changes in the tarball the
release signatures HAVE changes.

Thanks,
Eric Friedrich

Re: [VOTE] Release Apache Traffic Control 2.0.0-incubating (RC4)

2017-06-08 Thread Hank Beatty 

postinstall might still be broken:

Password for database server admin:
Re-Enter Password for database server admin:
Download Maxmind Database? [yes]:
Download Maxmind Database?: yes
===/opt/traffic_ops/app/conf/cdn.conf===
Generate a new secret? [yes]:
Generate a new secret?: yes
Number of secrets to keep? [10]:
Number of secrets to keep?: 10
Can't use an undefined value as an ARRAY reference at 
/opt/traffic_ops/install/bin/_postinstall line 211,  line 13.


And I've already started looking into it...

It is trying to load the secrets from the cdn.conf file. The initial 
cdn.conf file doesn't have any secrets. I can fix the _postinstall to 
correct this and do a PR.


Unless someone else has already fixed it or it needs to be done a 
different way.


Thanks,
Hank

On 06/05/2017 02:16 PM, Eric Friedrich (efriedri) wrote:

Hello All,

I've prepared the next candidate release for incubator-trafficcontrol v2.0.0 
(RC4)

Changes since 1.8.0:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC4

This corresponds to git:
Hash: 795ea3adf2003dd27523b6b9ff4691f23d41ce30
Tag: RELEASE-2.0.0-RC4

Which can be verified with the following:git tag -v RELEASE-2.0.0-RC4

My code signing key is available here:
http://pgp.mit.edu/pks/lookup?op=get=0xF2200BAB9AB7BDD5

and here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), and md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.0.0/RC4


The vote will remain open until Thursday, June 8, 2017.

This RC fixes some packaging issues in RC2 and RC3, there are no other changes. 
The git tag hash is the same, but due to changes in the tarball the release 
signatures HAVE changes.

Thanks,
Eric Friedrich

Re: [VOTE] Release Apache Traffic Control 2.0.0-incubating (RC4)

2017-06-07 Thread Hank Beatty 
Do we care if the documentation is up to date before we cut a release? 
Especially since this requires postgresql 9.6 and that is not mentioned 
on the install page.


http://trafficcontrol.apache.org/docs/2.0.x/admin/traffic_ops_install.html

On 06/05/2017 02:16 PM, Eric Friedrich (efriedri) wrote:

Hello All,

I've prepared the next candidate release for incubator-trafficcontrol v2.0.0 
(RC4)

Changes since 1.8.0:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC4

This corresponds to git:
Hash: 795ea3adf2003dd27523b6b9ff4691f23d41ce30
Tag: RELEASE-2.0.0-RC4

Which can be verified with the following:git tag -v RELEASE-2.0.0-RC4

My code signing key is available here:
http://pgp.mit.edu/pks/lookup?op=get=0xF2200BAB9AB7BDD5

and here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), and md5 and sha512 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/2.0.0/RC4


The vote will remain open until Thursday, June 8, 2017.

This RC fixes some packaging issues in RC2 and RC3, there are no other changes. 
The git tag hash is the same, but due to changes in the tarball the release 
signatures HAVE changes.

Thanks,
Eric Friedrich

Re: [VOTE] Move Traffic Control to full GitHub

2017-05-19 Thread Hank Beatty 

+1

On 05/18/2017 04:32 PM, Jan van Doorn wrote:

In
https://lists.apache.org/thread.html/5bdb9b073343f49c1d5b85147eb9d260bf7ad15d61384929993c7e1d@%3Cdev.trafficcontrol.apache.org%3E
Dave
mentioned that we can now move to "full" GitHub. Some more information in
that thread if you are not familiar. I would like to call an official vote
on that.

This vote will be open for at least 72 hours.

  [ ] +1 Move Traffic Control to use full GitHub
  [ ]  0 No opinion
  [ ] -1 Do not Move Traffic Control to use full GitHub because...

Rgds,
JvD

Re: [VOTE] Adding a CHANGELOG.md file

2017-05-17 Thread Hank Beatty 
-1 for a manual changelog - doing a compare between branches/commits in 
github is relatively simple.


+1 for a scripted changelog - 
https://github.com/skywinder/github-changelog-generator - There is even 
a list of alternatives: 
https://github.com/skywinder/Github-Changelog-Generator/wiki/Alternatives


On 05/17/2017 12:52 PM, Phil Sorber wrote:

Here is a link to an example script generated CHANGES file from Jira:

https://raw.githubusercontent.com/apache/trafficserver/6.0.x/CHANGES

On Wed, May 17, 2017 at 10:48 AM Phil Sorber  wrote:


The script can be updated to do Jira. ATS used a Jira version before they
went to github. You can also separate out easily. In fact, we did it more
easily with Jira than with github, since those categories are mutually
exclusive in Jira and labels in github are not. You could also have a
developer run the script regularly, or have CI do it.

To Eric's comment, if you can make that indication in Jira/GitHub then you
can transition that to the script. For example, a "Changelog" label in
github that would mean to have it included.

On Wed, May 17, 2017 at 10:37 AM Eric Friedrich (efriedri) <
efrie...@cisco.com> wrote:


What about a compromise where developer chooses whether or not a
feature/important fix is worth mentioning in the release notes. This would
be at feature granularity not individual commit.

Then at release build time, a script gathers from JIRA/Github API all
fixes that were committed in that release and checks that into repo.

—Eric


On May 17, 2017, at 12:18 PM, Phil Sorber  wrote:

Don't we have a script that can generate this? ATS had this for a long

time

and it became a huge hassle. It caused merge conflicts all the time,

that

while easy to address, were a huge nuisance. It also ended up out of

date

often.

On Wed, May 17, 2017 at 10:11 AM Gelinas, Derek <

derek_geli...@comcast.com>

wrote:


+1 for sure. It'll also give us a way to scan the notes and see what

needs

documenting and what doesn't yet have it.


On May 17, 2017, at 11:44 AM, Dave Neuman  wrote:

Hey All,
One thing we discussed at the meetup was the addition of a

CHANGELOG.md

file to the project.   This file will contain changes that are made to

the

project including bug fixes and new features. (e.g.
https://github.com/influxdata/influxdb/blob/master/CHANGELOG.md).

Adding

this file means that we will now require each PR to contain an update

to

the CHANGELOG.md file, and our documentation will need to be updated
accordingly.
I thought it would be good to open a vote for adding this file, and

if it

passes, I will update the documentation and add a CHANGELOG.md file.

Thanks,
Dave

Re: Moving Traffic Control the "full" github

2017-05-17 Thread Hank Beatty 

+1

On 05/17/2017 10:51 AM, Dave Neuman wrote:

While at ApaceCon, a few of us attended a talk about navigating the
incubator where we were informed that "full" Github is now available for
podlings.  This gives us the ability to use github issues, to use github
wiki, to assign PRs, to add tags to PRs, and the "merge PR" button among
other things.  It sounds like the process would take our repo down for a
short period - minutes not hours - but the URL shouldn't change.  I know we
just got all of our issues moved to Jira, but we would need to move them
over to github as well.

Since the apache way is to have a discussion before a vote, I thought I
would start the discussion on this topic now and if we feel like this is
worth pursuing, we start a vote.  Sothoughts?


Thanks,
Dave

Re: Edge Server throughput measure

2017-05-17 Thread Hank Beatty 

If you are looking for a load testing tool you might try http://locust.io

On 05/11/2017 11:22 AM, Burak Sarp wrote:

  blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px 
#715FFA solid !important; padding-left:1ex !important; background-color:white 
!important; }
Hi all,
Is there any way to measure throughput of edge server ?I mean how to create 
efficient load on edge servers?
ThanksSarp
Sent from Yahoo Mail for iPhone

Re: Access Control Model

2017-02-22 Thread Hank Beatty 

Hi Naama,

I like the idea of making Access Control hierarchical.

I came up with some questions I thought we might think about:

1. Do the tenants become the equivalent of the "groups" we are using today?

2. In your example, can there be children of 'Company C'?

3. Some of the APIs currently allow for 'token' authentication but, the 
UI portion was never implemented (AFAIK). I would like to see the 
'token' authentication added so that scripts don't have to be run with 
user/pass.


4. I would like to see more than a single "root" user (perhaps a group 
that one could assign users).


Thanks,
Hank

On 02/21/2017 03:32 PM, Naama Shoresh wrote:

Hi,

We've been considering the subject of authorization within TO, and have
phrased a concept we'd like to share and get some feedback about.
You can find it in the wiki
,
and also written below, for ease of use.
Your comments and insights are most welcome.

=

The access control model concept is constructed of two dimensions:
capabilities & data.
1. CapabilitiesCheck if a user is allowed to perform an operation

APIs are grouped to roles, and each user is assigned a set of roles which
implies his allowed APIs.

Example:

API  | Role
-+-
GET  /ds/:id | ds-read
POST /ds/create  | ds-write
POST /ds/:id/update  | ds-write
POST /profile/:id/update | profile-write

The  access is checked at the entry point. A user Joe which has the roles
ds-read & ds-write is allowed to operate the following APIs:  /ds/:id,
/ds/create and /ds/:id/update.
2. DataCheck if a user is allowed to access a specific set of data.

Here is where the concept of *tenants* is introduced:

Every "resource" in the  database is assigned  (delivery-services, servers,
etc..) to  a tenant. A tenant is an organization in TC. It can be either a
content-provider or an ISP. Tenants are hierarchical, where  the parent is
conceptually assigned a super-set of all the resources of  its children.

Each user belongs to one or more tenants. Only the tenant's resources are
available for the tenant's users.

* Note: for simplicitly, the example below refers to a single tenant per
user.

Example:

Tenant table:

ID  | Tenant-name | Parent-ID
+-+---
1   | company A   | -
2   | company B   | 1 // a child of company A
3   | company C   | 1 // another child of company A
4   | company D   | -
5   | company E   | -

DS table:

DS-Name| ... | Tenant
-+
cp-a-vod   | ... | 1
cp-a-linear| ... | 1
cp-b-vod   | ... | 2
cp-e-linear| ... | 4

Users table:

Username   | ... | Tenant
---+-+
Joe| ... | 1
Jack   | ... | 2
John   | ... | 4

The user Joe will be allowed to access DSs of company A, company B &
company C, namely: cp-1-vod, cp-a-linear & cp-b-vod.
The user Jack will be allowed to access DS of company B, namely: cp-b-vod.
The user John will be allowed to access DS of company D, namely:
cp-e-linear.

Note: There will be a special "root" user that will be allowed to access
all resources.
Access Control Serice

The  authorization (access-control) functionality is contained within a new
service(s). The first APIs this service will expose are something along
these lines:

1. Check if a user is allowed to perform an operation.
Input: A user and an API route
Output: A boolean answer allowed/rejected

2. Check if a user is allowed to access a resource of a certain tenant
Input: A user and a tenant
Output: A boolean answer allowed/rejected



This is a simplified description. It doesn't handle the issue of
interaction between tenants, such as assigning a delivery-service to a CDN,
which will be discussed separately.

This email only aims to present the concepts.

Thanks,
Naama

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC11)

2017-02-18 Thread Hank Beatty 

+1

Looks like only licenses were changed.

On 02/17/2017 03:07 PM, Dan Kirkwood wrote:

Hello All,

I've prepared another release for v1.8.0 (RC11).   I apologize for the
confusion on RC10 -- we had a glitch in our tagging process.  RC11 is
identical to RC10,  but we decided to redo the process to ensure the
integrity of the release.   The source tarballs are identical in
content -- only dates changed, but the checksums will be different.

Changes since 1.7.0:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC11

This corresponds to git:
  Hash: 14ef03fd251b6306e67627c935f9111efb0284af
  Tag: RELEASE-1.8.0-RC11

Which can be verified with the following:git tag -v RELEASE-1.8.0-RC11

My code signing key is available here:
http://keys.gnupg.net/pks/lookup?search=0x4587A8F0=vindex

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), and md5 and sha1 checksums are provided here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC11

(from RC10): This RC has only LICENSE file changes to eliminate 3rd
party URLs and
a small addition to NOTICE to cover binary font files.

The vote will remain open until the evening of Monday, Feb 20, 2017 to
allow a full 72 hour vetting period.

Thanks!
Dan

Re: [VOTE] Release Apache Traffic Control 1.8.0-incubating (RC10)

2017-02-16 Thread Hank Beatty 

+1

On 02/16/2017 01:50 PM, Dan Kirkwood wrote:

Hello All,

I've prepared another release for v1.8.0 (RC10)

Changes since 1.7.0:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC10

This corresponds to git:
  Hash: 14ef03fd251b6306e67627c935f9111efb0284af
  Tag: RELEASE-1.8.0-RC10

Which can be verified with the following:git tag -v RELEASE-1.8.0-RC10

My code signing key is available here:
http://keys.gnupg.net/pks/lookup?search=0x4587A8F0=vindex

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), and md5 and sha1 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC10

This RC has only LICENSE file changes to eliminate 3rd party URLs and
a small addition to NOTICE to cover binary font files.

Since the changes are license-related only,   we'd like to keep the
voting period very short.   Please vote by end-of-day today (Thursday,
 Feb 16).  If this is not enough time for you to examine the RC,
please respond and we can extend the vote.


Thanks!

Re: [VOTE] incubator-trafficcontrol-1.8.0-RC8

2017-01-20 Thread Hank Beatty 

On 01/19/2017 02:22 PM, Dave Neuman wrote:

It also appears the issue I brought up about Traffic Ops not working with
Riak 2.1.4 hasn't been addressed.

We agreed, I think on email but maybe on slack, that we would document the
Riak issue in release notes and fix it in the next release. Do you think
you are ok with that solution?

Thanks,
Dave
​


Yeah. I'll fix it on my side.

+1

Re: [VOTE] incubator-trafficcontrol-1.8.0-RC8

2017-01-20 Thread Hank Beatty 

On 01/19/2017 02:58 PM, Dan Kirkwood wrote:

Thanks,   Hank..I don't think the double-license or double-use
will have any impact,  but thanks for pointing those out.I'll get
that fixed in master.   Still -1?

-dan



That was just an FYI.

Re: [VOTE] incubator-trafficcontrol-1.8.0-RC8

2017-01-19 Thread Hank Beatty 

* traffic_ops/app/lib/Schema/Result/SteeringView.pm
  * License is in twice
  * use strict and use warnings is also in twice

It also appears the issue I brought up about Traffic Ops not working 
with Riak 2.1.4 hasn't been addressed.


-1

On 01/13/2017 03:57 PM, Dan Kirkwood wrote:

Hello All,

I've prepared another release for v1.8.0 (RC7)

Changes since 1.7.0:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC8

This corresponds to git:
  Hash:597e7795c48ab65fe57175642973481b9dc020e6
  Tag: RELEASE-1.8.0-RC8

Which can be verified with the following:git tag -v RELEASE-1.8.0-RC8

My code signing key is available here:
http://keys.gnupg.net/pks/lookup?search=0x4587A8F0=vindex

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

The source .tar.gz file, pgp signature (.asc signed with my key from
above), and md5 and sha1 checksums are provided here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC8

More Apache License compliance changes are included in this RC as well
as one critical regression from 1.7:
https://issues.apache.org/jira/browse/TC-97

The vote will remain open until Wednesday,  Jan 18, 2017.

Thanks!