[VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Eric Friedrich
Hello Incubator PMC,

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


Changes since 1.8.1:

https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1...RELEASE-2.0.0-RC6


This corresponds to git:

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

Hash: 85d14ebe2a4ac71236f86f70349481d2b3dc784b

Tag: RELEASE-2.0.0-RC6

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


My code signing key is available from the following locations:

http://pgp.mit.edu/pks/lookup?op=get&search=0xF2200BAB9AB7BDD5

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


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.0.0/RC6


Docs are available here: https://trafficcontrol.apache.org/docs/2.0.x/


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


This vote will be open for at least 72 hours. Please review and vote:

[ ] +1 Approve the release

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


We’ve taken IPMC feedback to change following since the recent 1.8.1 vote:

- Modify release artifact filename to
apache-trafficcontrol-2.0.0-incubating.tar.gz

- Fix font licenses in LICENSE and NOTICE


Thanks,

Eric Friedrich <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

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

Eric Friedrich (efriedri)
Hi Incubator PMC-
  In the past 5 days our vote thread has not yet received any feedback. Could I please request that you consider reviewing and voting on the below release candidate?

Thanks,
Eric

> On Jun 21, 2017, at 5:05 PM, Eric Friedrich <[hidden email]> wrote:
>
> Hello Incubator PMC,
>
> The Apache Traffic Control community has voted on and approved a proposal
> to release Apache Traffic Control 2.0.0. We now kindly request that the
> Incubator PMC members review and vote on this incubator release.
>
>
> Changes since 1.8.1:
>
> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1...RELEASE-2.0.0-RC6
>
>
> This corresponds to git:
>
> Repo: https://github.com/apache/incubator-trafficcontrol
>
> Hash: 85d14ebe2a4ac71236f86f70349481d2b3dc784b
>
> Tag: RELEASE-2.0.0-RC6
>
> Which can be verified with the following:    git tag -v RELEASE-2.0.0-RC6
>
>
> My code signing key is available from the following locations:
>
> http://pgp.mit.edu/pks/lookup?op=get&search=0xF2200BAB9AB7BDD5
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
>
> 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.0.0/RC6
>
>
> Docs are available here: https://trafficcontrol.apache.org/docs/2.0.x/
>
>
> Build instructions are included in the BUILD.md file which is included in
> the source artifact.
>
>
> This vote will be open for at least 72 hours. Please review and vote:
>
> [ ] +1 Approve the release
>
> [ ] -1 Don't approve the release (please provide specific comments)
>
>
> We’ve taken IPMC feedback to change following since the recent 1.8.1 vote:
>
> - Modify release artifact filename to
> apache-trafficcontrol-2.0.0-incubating.tar.gz
>
> - Fix font licenses in LICENSE and NOTICE
>
>
> Thanks,
>
> Eric Friedrich <[hidden email]>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

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

Justin Mclean
Hi,

>  In the past 5 days our vote thread has not yet received any feedback. Could I please request that you consider reviewing and voting on the below release candidate?

I can take a look at your release.

Out of interest is there any reason why you mentors (who are also IPMC members) have not voted on this release?

Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

John D. Ament-2
In reply to this post by Eric Friedrich
Hi Eric,

I see that a lot changed in the project as a part of this release.
Specifically I'm concerned about the over eager rat excludes.

- The Apache License v2 is not a software only license.  It also applies to
documentation, etc.  So feel free to add the header to .md files
- Minified files should include proper license headers
- Copyright dates should be ranges, so 2016-2017 or 2016,2017 are both
fine.

I'll continue to dig into the release tarball if you can comment on these
items (I'm not asking you to cut a new release, I'm asking for you to
comment on these only)

John

On Wed, Jun 21, 2017 at 5:05 PM Eric Friedrich <[hidden email]> wrote:

> Hello Incubator PMC,
>
> The Apache Traffic Control community has voted on and approved a proposal
> to release Apache Traffic Control 2.0.0. We now kindly request that the
> Incubator PMC members review and vote on this incubator release.
>
>
> Changes since 1.8.1:
>
>
> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1...RELEASE-2.0.0-RC6
>
>
> This corresponds to git:
>
> Repo: https://github.com/apache/incubator-trafficcontrol
>
> Hash: 85d14ebe2a4ac71236f86f70349481d2b3dc784b
>
> Tag: RELEASE-2.0.0-RC6
>
> Which can be verified with the following:    git tag -v RELEASE-2.0.0-RC6
>
>
> My code signing key is available from the following locations:
>
> http://pgp.mit.edu/pks/lookup?op=get&search=0xF2200BAB9AB7BDD5
>
> https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS
>
>
> 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.0.0/RC6
>
>
> Docs are available here: https://trafficcontrol.apache.org/docs/2.0.x/
>
>
> Build instructions are included in the BUILD.md file which is included in
> the source artifact.
>
>
> This vote will be open for at least 72 hours. Please review and vote:
>
> [ ] +1 Approve the release
>
> [ ] -1 Don't approve the release (please provide specific comments)
>
>
> We’ve taken IPMC feedback to change following since the recent 1.8.1 vote:
>
> - Modify release artifact filename to
> apache-trafficcontrol-2.0.0-incubating.tar.gz
>
> - Fix font licenses in LICENSE and NOTICE
>
>
> Thanks,
>
> Eric Friedrich <[hidden email]>
>
Reply | Threaded
Open this post in threaded view
|

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

Justin Mclean
In reply to this post by Justin Mclean
Hi,

+0 binding as I can’t build from source and no instructions provided.

I will change to +1 when I can compile/ you raise a JIRA to add instructions on how to build.

I checked:
- signatures and hashes good
- DISCLAIMER exists
- LICENSE good
- NOTICE OK . You can remove the information about the fonts in there it’s not needed.
- No unexpected binary files
- All source files have headers (there's a few script files and other files that could also have headers)
- can't build from source

when running the build.sh script it eventually fails with this error

cp: ./build/*.spec: No such file or directory
Could not copy spec files: 1
traffic_stats failed:
The following subdirectories had errors:
   traffic_monitor
   traffic_monitor_golang
   traffic_ops
   traffic_portal
   traffic_router
   traffic_stats

Has perhaps something not been included in the release or is my environment not set up correctly?

It would be nice to include the build instructions in the build itself. I believe this has come up before. By providing a URL it means that the content of that URL may change for future releases and people would be unable to build this release. In fact the URL in the documentation is incorrect [1] and currently 404s which is less than helpful.

There a few file still copyright comcast I assume these need to be removed? [2][3][4][5][6]

Thanks,
Justin

1. http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
2. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
3. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
4. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/github.com/jheitz200/test_helper/http.go
6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/github.com/jheitz200/test_helper/test.go



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

John D. Ament-2
On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean <[hidden email]>
wrote:

> Hi,
>
> +0 binding as I can’t build from source and no instructions provided.
>

I struggled with this a bit as well.  The BUILD.md indicates:

See the build instructions at ./docs/source/development/building.rst or at
http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html

That URL doesn't work, but the rst file indicates running pkg does the
build.

However, when I run pkg, I get the following:

~/Desktop/apache-trafficcontrol-2.0.0-incubating
☺  ./pkg



Building traffic_portal_build.
Building traffic_router_build.
Building traffic_monitor_build.
Building source.
Building traffic_ops_build.
Building traffic_stats_build.
Failed to build traffic_portal_build.


>
> I will change to +1 when I can compile/ you raise a JIRA to add
> instructions on how to build.
>
> I checked:
> - signatures and hashes good
> - DISCLAIMER exists
> - LICENSE good
> - NOTICE OK . You can remove the information about the fonts in there it’s
> not needed.
> - No unexpected binary files
> - All source files have headers (there's a few script files and other
> files that could also have headers)
> - can't build from source
>
> when running the build.sh script it eventually fails with this error
>
> cp: ./build/*.spec: No such file or directory
> Could not copy spec files: 1
> traffic_stats failed:
> The following subdirectories had errors:
>    traffic_monitor
>    traffic_monitor_golang
>    traffic_ops
>    traffic_portal
>    traffic_router
>    traffic_stats
>
> Has perhaps something not been included in the release or is my
> environment not set up correctly?
>
> It would be nice to include the build instructions in the build itself. I
> believe this has come up before. By providing a URL it means that the
> content of that URL may change for future releases and people would be
> unable to build this release. In fact the URL in the documentation is
> incorrect [1] and currently 404s which is less than helpful.
>
> There a few file still copyright comcast I assume these need to be
> removed? [2][3][4][5][6]
>
> Thanks,
> Justin
>
> 1.
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> 2. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
> 3.
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
> 4.
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> github.com/jheitz200/test_helper/http.go
> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> github.com/jheitz200/test_helper/test.go
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

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

Dan Kirkwood-2
Thanks John and Justin..    Eric's out for a few days,  but I can work
on getting some of these things addressed.

The build instructions will be put in place once the release is done
-- catch-22..  but I should be able to add a reference to the local
rst file as well.   Would Jira issues for the copyright and build
instruction issues be sufficient?  Or would you prefer to see another
RC to address those?

The `./pkg` is the simplest way to build.   If you give that a `-v`,
it will spill all the output to stdout so you can see where it's
erroring out.   We are able to build it,  so not sure where the issue
lies with building the traffic_portal.

-dan

On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament <[hidden email]> wrote:

> On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean <[hidden email]>
> wrote:
>
>> Hi,
>>
>> +0 binding as I can’t build from source and no instructions provided.
>>
>
> I struggled with this a bit as well.  The BUILD.md indicates:
>
> See the build instructions at ./docs/source/development/building.rst or at
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>
> That URL doesn't work, but the rst file indicates running pkg does the
> build.
>
> However, when I run pkg, I get the following:
>
> ~/Desktop/apache-trafficcontrol-2.0.0-incubating
> ☺  ./pkg
>
>
>
> Building traffic_portal_build.
> Building traffic_router_build.
> Building traffic_monitor_build.
> Building source.
> Building traffic_ops_build.
> Building traffic_stats_build.
> Failed to build traffic_portal_build.
>
>
>>
>> I will change to +1 when I can compile/ you raise a JIRA to add
>> instructions on how to build.
>>
>> I checked:
>> - signatures and hashes good
>> - DISCLAIMER exists
>> - LICENSE good
>> - NOTICE OK . You can remove the information about the fonts in there it’s
>> not needed.
>> - No unexpected binary files
>> - All source files have headers (there's a few script files and other
>> files that could also have headers)
>> - can't build from source
>>
>> when running the build.sh script it eventually fails with this error
>>
>> cp: ./build/*.spec: No such file or directory
>> Could not copy spec files: 1
>> traffic_stats failed:
>> The following subdirectories had errors:
>>    traffic_monitor
>>    traffic_monitor_golang
>>    traffic_ops
>>    traffic_portal
>>    traffic_router
>>    traffic_stats
>>
>> Has perhaps something not been included in the release or is my
>> environment not set up correctly?
>>
>> It would be nice to include the build instructions in the build itself. I
>> believe this has come up before. By providing a URL it means that the
>> content of that URL may change for future releases and people would be
>> unable to build this release. In fact the URL in the documentation is
>> incorrect [1] and currently 404s which is less than helpful.
>>
>> There a few file still copyright comcast I assume these need to be
>> removed? [2][3][4][5][6]
>>
>> Thanks,
>> Justin
>>
>> 1.
>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>> 2. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
>> 3.
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
>> 4.
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
>> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> github.com/jheitz200/test_helper/http.go
>> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> github.com/jheitz200/test_helper/test.go
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

John D. Ament-2
On Wed, Jun 28, 2017 at 3:26 PM Dan Kirkwood <[hidden email]> wrote:

> Thanks John and Justin..    Eric's out for a few days,  but I can work
> on getting some of these things addressed.
>
> The build instructions will be put in place once the release is done
> -- catch-22..  but I should be able to add a reference to the local
> rst file as well.   Would Jira issues for the copyright and build
> instruction issues be sufficient?  Or would you prefer to see another
> RC to address those?
>
> The `./pkg` is the simplest way to build.   If you give that a `-v`,
> it will spill all the output to stdout so you can see where it's
> erroring out.   We are able to build it,  so not sure where the issue
> lies with building the traffic_portal.
>

Is there a log to look at the failure?

Either way I'm fine with releasing as is, so +1.


>
> -dan
>
> On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament <[hidden email]>
> wrote:
> > On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean <[hidden email]>
> > wrote:
> >
> >> Hi,
> >>
> >> +0 binding as I can’t build from source and no instructions provided.
> >>
> >
> > I struggled with this a bit as well.  The BUILD.md indicates:
> >
> > See the build instructions at ./docs/source/development/building.rst or
> at
> >
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> >
> > That URL doesn't work, but the rst file indicates running pkg does the
> > build.
> >
> > However, when I run pkg, I get the following:
> >
> > ~/Desktop/apache-trafficcontrol-2.0.0-incubating
> > ☺  ./pkg
> >
> >
> >
> > Building traffic_portal_build.
> > Building traffic_router_build.
> > Building traffic_monitor_build.
> > Building source.
> > Building traffic_ops_build.
> > Building traffic_stats_build.
> > Failed to build traffic_portal_build.
> >
> >
> >>
> >> I will change to +1 when I can compile/ you raise a JIRA to add
> >> instructions on how to build.
> >>
> >> I checked:
> >> - signatures and hashes good
> >> - DISCLAIMER exists
> >> - LICENSE good
> >> - NOTICE OK . You can remove the information about the fonts in there
> it’s
> >> not needed.
> >> - No unexpected binary files
> >> - All source files have headers (there's a few script files and other
> >> files that could also have headers)
> >> - can't build from source
> >>
> >> when running the build.sh script it eventually fails with this error
> >>
> >> cp: ./build/*.spec: No such file or directory
> >> Could not copy spec files: 1
> >> traffic_stats failed:
> >> The following subdirectories had errors:
> >>    traffic_monitor
> >>    traffic_monitor_golang
> >>    traffic_ops
> >>    traffic_portal
> >>    traffic_router
> >>    traffic_stats
> >>
> >> Has perhaps something not been included in the release or is my
> >> environment not set up correctly?
> >>
> >> It would be nice to include the build instructions in the build itself.
> I
> >> believe this has come up before. By providing a URL it means that the
> >> content of that URL may change for future releases and people would be
> >> unable to build this release. In fact the URL in the documentation is
> >> incorrect [1] and currently 404s which is less than helpful.
> >>
> >> There a few file still copyright comcast I assume these need to be
> >> removed? [2][3][4][5][6]
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1.
> >>
> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> >> 2.
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
> >> 3.
> >>
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
> >> 4.
> >>
> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
> >> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> >> github.com/jheitz200/test_helper/http.go
> >> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> >> github.com/jheitz200/test_helper/test.go
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

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

Dan Kirkwood-2
unfortunately,  no log  -- -v is the only way to get it.  That's
something I'd like to have,  so I'll put in a Jira issue for that as
well.

On Wed, Jun 28, 2017 at 1:28 PM, John D. Ament <[hidden email]> wrote:

> On Wed, Jun 28, 2017 at 3:26 PM Dan Kirkwood <[hidden email]> wrote:
>
>> Thanks John and Justin..    Eric's out for a few days,  but I can work
>> on getting some of these things addressed.
>>
>> The build instructions will be put in place once the release is done
>> -- catch-22..  but I should be able to add a reference to the local
>> rst file as well.   Would Jira issues for the copyright and build
>> instruction issues be sufficient?  Or would you prefer to see another
>> RC to address those?
>>
>> The `./pkg` is the simplest way to build.   If you give that a `-v`,
>> it will spill all the output to stdout so you can see where it's
>> erroring out.   We are able to build it,  so not sure where the issue
>> lies with building the traffic_portal.
>>
>
> Is there a log to look at the failure?
>
> Either way I'm fine with releasing as is, so +1.
>
>
>>
>> -dan
>>
>> On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament <[hidden email]>
>> wrote:
>> > On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean <[hidden email]>
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> +0 binding as I can’t build from source and no instructions provided.
>> >>
>> >
>> > I struggled with this a bit as well.  The BUILD.md indicates:
>> >
>> > See the build instructions at ./docs/source/development/building.rst or
>> at
>> >
>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>> >
>> > That URL doesn't work, but the rst file indicates running pkg does the
>> > build.
>> >
>> > However, when I run pkg, I get the following:
>> >
>> > ~/Desktop/apache-trafficcontrol-2.0.0-incubating
>> > ☺  ./pkg
>> >
>> >
>> >
>> > Building traffic_portal_build.
>> > Building traffic_router_build.
>> > Building traffic_monitor_build.
>> > Building source.
>> > Building traffic_ops_build.
>> > Building traffic_stats_build.
>> > Failed to build traffic_portal_build.
>> >
>> >
>> >>
>> >> I will change to +1 when I can compile/ you raise a JIRA to add
>> >> instructions on how to build.
>> >>
>> >> I checked:
>> >> - signatures and hashes good
>> >> - DISCLAIMER exists
>> >> - LICENSE good
>> >> - NOTICE OK . You can remove the information about the fonts in there
>> it’s
>> >> not needed.
>> >> - No unexpected binary files
>> >> - All source files have headers (there's a few script files and other
>> >> files that could also have headers)
>> >> - can't build from source
>> >>
>> >> when running the build.sh script it eventually fails with this error
>> >>
>> >> cp: ./build/*.spec: No such file or directory
>> >> Could not copy spec files: 1
>> >> traffic_stats failed:
>> >> The following subdirectories had errors:
>> >>    traffic_monitor
>> >>    traffic_monitor_golang
>> >>    traffic_ops
>> >>    traffic_portal
>> >>    traffic_router
>> >>    traffic_stats
>> >>
>> >> Has perhaps something not been included in the release or is my
>> >> environment not set up correctly?
>> >>
>> >> It would be nice to include the build instructions in the build itself.
>> I
>> >> believe this has come up before. By providing a URL it means that the
>> >> content of that URL may change for future releases and people would be
>> >> unable to build this release. In fact the URL in the documentation is
>> >> incorrect [1] and currently 404s which is less than helpful.
>> >>
>> >> There a few file still copyright comcast I assume these need to be
>> >> removed? [2][3][4][5][6]
>> >>
>> >> Thanks,
>> >> Justin
>> >>
>> >> 1.
>> >>
>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>> >> 2.
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
>> >> 3.
>> >>
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
>> >> 4.
>> >>
>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
>> >> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> >> github.com/jheitz200/test_helper/http.go
>> >> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>> >> github.com/jheitz200/test_helper/test.go
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [hidden email]
>> >> For additional commands, e-mail: [hidden email]
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

Dan Kirkwood-2
actually,   I take that back..   the "dist" directory contains all the
rpm artifacts and a log file for each of the components.

I think ./pkg needs to point that out,  and perhaps even display the
contents of that directory.   Filing an issue for that..

-dan

On Wed, Jun 28, 2017 at 1:30 PM, Dan Kirkwood <[hidden email]> wrote:

> unfortunately,  no log  -- -v is the only way to get it.  That's
> something I'd like to have,  so I'll put in a Jira issue for that as
> well.
>
> On Wed, Jun 28, 2017 at 1:28 PM, John D. Ament <[hidden email]> wrote:
>> On Wed, Jun 28, 2017 at 3:26 PM Dan Kirkwood <[hidden email]> wrote:
>>
>>> Thanks John and Justin..    Eric's out for a few days,  but I can work
>>> on getting some of these things addressed.
>>>
>>> The build instructions will be put in place once the release is done
>>> -- catch-22..  but I should be able to add a reference to the local
>>> rst file as well.   Would Jira issues for the copyright and build
>>> instruction issues be sufficient?  Or would you prefer to see another
>>> RC to address those?
>>>
>>> The `./pkg` is the simplest way to build.   If you give that a `-v`,
>>> it will spill all the output to stdout so you can see where it's
>>> erroring out.   We are able to build it,  so not sure where the issue
>>> lies with building the traffic_portal.
>>>
>>
>> Is there a log to look at the failure?
>>
>> Either way I'm fine with releasing as is, so +1.
>>
>>
>>>
>>> -dan
>>>
>>> On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament <[hidden email]>
>>> wrote:
>>> > On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean <[hidden email]>
>>> > wrote:
>>> >
>>> >> Hi,
>>> >>
>>> >> +0 binding as I can’t build from source and no instructions provided.
>>> >>
>>> >
>>> > I struggled with this a bit as well.  The BUILD.md indicates:
>>> >
>>> > See the build instructions at ./docs/source/development/building.rst or
>>> at
>>> >
>>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>>> >
>>> > That URL doesn't work, but the rst file indicates running pkg does the
>>> > build.
>>> >
>>> > However, when I run pkg, I get the following:
>>> >
>>> > ~/Desktop/apache-trafficcontrol-2.0.0-incubating
>>> > ☺  ./pkg
>>> >
>>> >
>>> >
>>> > Building traffic_portal_build.
>>> > Building traffic_router_build.
>>> > Building traffic_monitor_build.
>>> > Building source.
>>> > Building traffic_ops_build.
>>> > Building traffic_stats_build.
>>> > Failed to build traffic_portal_build.
>>> >
>>> >
>>> >>
>>> >> I will change to +1 when I can compile/ you raise a JIRA to add
>>> >> instructions on how to build.
>>> >>
>>> >> I checked:
>>> >> - signatures and hashes good
>>> >> - DISCLAIMER exists
>>> >> - LICENSE good
>>> >> - NOTICE OK . You can remove the information about the fonts in there
>>> it’s
>>> >> not needed.
>>> >> - No unexpected binary files
>>> >> - All source files have headers (there's a few script files and other
>>> >> files that could also have headers)
>>> >> - can't build from source
>>> >>
>>> >> when running the build.sh script it eventually fails with this error
>>> >>
>>> >> cp: ./build/*.spec: No such file or directory
>>> >> Could not copy spec files: 1
>>> >> traffic_stats failed:
>>> >> The following subdirectories had errors:
>>> >>    traffic_monitor
>>> >>    traffic_monitor_golang
>>> >>    traffic_ops
>>> >>    traffic_portal
>>> >>    traffic_router
>>> >>    traffic_stats
>>> >>
>>> >> Has perhaps something not been included in the release or is my
>>> >> environment not set up correctly?
>>> >>
>>> >> It would be nice to include the build instructions in the build itself.
>>> I
>>> >> believe this has come up before. By providing a URL it means that the
>>> >> content of that URL may change for future releases and people would be
>>> >> unable to build this release. In fact the URL in the documentation is
>>> >> incorrect [1] and currently 404s which is less than helpful.
>>> >>
>>> >> There a few file still copyright comcast I assume these need to be
>>> >> removed? [2][3][4][5][6]
>>> >>
>>> >> Thanks,
>>> >> Justin
>>> >>
>>> >> 1.
>>> >>
>>> http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
>>> >> 2.
>>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
>>> >> 3.
>>> >>
>>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
>>> >> 4.
>>> >>
>>> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
>>> >> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>>> >> github.com/jheitz200/test_helper/http.go
>>> >> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
>>> >> github.com/jheitz200/test_helper/test.go
>>> >>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: [hidden email]
>>> >> For additional commands, e-mail: [hidden email]
>>> >>
>>> >>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

David Neuman
In reply to this post by Dan Kirkwood-2
If you run `./pkg -v` it should give you/us enough output to figure out why
the build is failing.

On Wed, Jun 28, 2017 at 1:30 PM, Dan Kirkwood <[hidden email]> wrote:

> unfortunately,  no log  -- -v is the only way to get it.  That's
> something I'd like to have,  so I'll put in a Jira issue for that as
> well.
>
> On Wed, Jun 28, 2017 at 1:28 PM, John D. Ament <[hidden email]>
> wrote:
> > On Wed, Jun 28, 2017 at 3:26 PM Dan Kirkwood <[hidden email]> wrote:
> >
> >> Thanks John and Justin..    Eric's out for a few days,  but I can work
> >> on getting some of these things addressed.
> >>
> >> The build instructions will be put in place once the release is done
> >> -- catch-22..  but I should be able to add a reference to the local
> >> rst file as well.   Would Jira issues for the copyright and build
> >> instruction issues be sufficient?  Or would you prefer to see another
> >> RC to address those?
> >>
> >> The `./pkg` is the simplest way to build.   If you give that a `-v`,
> >> it will spill all the output to stdout so you can see where it's
> >> erroring out.   We are able to build it,  so not sure where the issue
> >> lies with building the traffic_portal.
> >>
> >
> > Is there a log to look at the failure?
> >
> > Either way I'm fine with releasing as is, so +1.
> >
> >
> >>
> >> -dan
> >>
> >> On Tue, Jun 27, 2017 at 6:59 PM, John D. Ament <[hidden email]>
> >> wrote:
> >> > On Tue, Jun 27, 2017 at 8:56 PM Justin Mclean <
> [hidden email]>
> >> > wrote:
> >> >
> >> >> Hi,
> >> >>
> >> >> +0 binding as I can’t build from source and no instructions provided.
> >> >>
> >> >
> >> > I struggled with this a bit as well.  The BUILD.md indicates:
> >> >
> >> > See the build instructions at ./docs/source/development/building.rst
> or
> >> at
> >> >
> >> http://trafficcontrol.incubator.apache.org/docs/
> latest/development/building.html
> >> >
> >> > That URL doesn't work, but the rst file indicates running pkg does the
> >> > build.
> >> >
> >> > However, when I run pkg, I get the following:
> >> >
> >> > ~/Desktop/apache-trafficcontrol-2.0.0-incubating
> >> > ☺  ./pkg
> >> >
> >> >
> >> >
> >> > Building traffic_portal_build.
> >> > Building traffic_router_build.
> >> > Building traffic_monitor_build.
> >> > Building source.
> >> > Building traffic_ops_build.
> >> > Building traffic_stats_build.
> >> > Failed to build traffic_portal_build.
> >> >
> >> >
> >> >>
> >> >> I will change to +1 when I can compile/ you raise a JIRA to add
> >> >> instructions on how to build.
> >> >>
> >> >> I checked:
> >> >> - signatures and hashes good
> >> >> - DISCLAIMER exists
> >> >> - LICENSE good
> >> >> - NOTICE OK . You can remove the information about the fonts in there
> >> it’s
> >> >> not needed.
> >> >> - No unexpected binary files
> >> >> - All source files have headers (there's a few script files and other
> >> >> files that could also have headers)
> >> >> - can't build from source
> >> >>
> >> >> when running the build.sh script it eventually fails with this error
> >> >>
> >> >> cp: ./build/*.spec: No such file or directory
> >> >> Could not copy spec files: 1
> >> >> traffic_stats failed:
> >> >> The following subdirectories had errors:
> >> >>    traffic_monitor
> >> >>    traffic_monitor_golang
> >> >>    traffic_ops
> >> >>    traffic_portal
> >> >>    traffic_router
> >> >>    traffic_stats
> >> >>
> >> >> Has perhaps something not been included in the release or is my
> >> >> environment not set up correctly?
> >> >>
> >> >> It would be nice to include the build instructions in the build
> itself.
> >> I
> >> >> believe this has come up before. By providing a URL it means that the
> >> >> content of that URL may change for future releases and people would
> be
> >> >> unable to build this release. In fact the URL in the documentation is
> >> >> incorrect [1] and currently 404s which is less than helpful.
> >> >>
> >> >> There a few file still copyright comcast I assume these need to be
> >> >> removed? [2][3][4][5][6]
> >> >>
> >> >> Thanks,
> >> >> Justin
> >> >>
> >> >> 1.
> >> >>
> >> http://trafficcontrol.incubator.apache.org/docs/
> latest/development/building.html
> >> >> 2.
> >> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/
> api/1.1/cdn.t
> >> >> 3.
> >> >>
> >> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/
> delivery_service_resources.go
> >> >> 4.
> >> >>
> >> ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/
> install/lib/WebDep.pm
> >> >> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> >> >> github.com/jheitz200/test_helper/http.go
> >> >> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/
> >> >> github.com/jheitz200/test_helper/test.go
> >> >>
> >> >>
> >> >>
> >> >> ------------------------------------------------------------
> ---------
> >> >> To unsubscribe, e-mail: [hidden email]
> >> >> For additional commands, e-mail: [hidden email]
> >> >>
> >> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

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

Dan Kirkwood-2
In reply to this post by Justin Mclean
Justin,  the build instructions are there in BUILD.md,  which
references the above non-existent link (it will exist once we release)
and the rst file local to the source tree:
docs/source/development/building.rst

Those few copyright issues did slip by us -- filing an issue to get
that corrected for the next release.

thanks.. Dan

On Tue, Jun 27, 2017 at 6:56 PM, Justin Mclean <[hidden email]> wrote:

> Hi,
>
> +0 binding as I can’t build from source and no instructions provided.
>
> I will change to +1 when I can compile/ you raise a JIRA to add instructions on how to build.
>
> I checked:
> - signatures and hashes good
> - DISCLAIMER exists
> - LICENSE good
> - NOTICE OK . You can remove the information about the fonts in there it’s not needed.
> - No unexpected binary files
> - All source files have headers (there's a few script files and other files that could also have headers)
> - can't build from source
>
> when running the build.sh script it eventually fails with this error
>
> cp: ./build/*.spec: No such file or directory
> Could not copy spec files: 1
> traffic_stats failed:
> The following subdirectories had errors:
>    traffic_monitor
>    traffic_monitor_golang
>    traffic_ops
>    traffic_portal
>    traffic_router
>    traffic_stats
>
> Has perhaps something not been included in the release or is my environment not set up correctly?
>
> It would be nice to include the build instructions in the build itself. I believe this has come up before. By providing a URL it means that the content of that URL may change for future releases and people would be unable to build this release. In fact the URL in the documentation is incorrect [1] and currently 404s which is less than helpful.
>
> There a few file still copyright comcast I assume these need to be removed? [2][3][4][5][6]
>
> Thanks,
> Justin
>
> 1. http://trafficcontrol.incubator.apache.org/docs/latest/development/building.html
> 2. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/app/t/api/1.1/cdn.t
> 3. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/client/delivery_service_resources.go
> 4. ./apache-trafficcontrol-2.0.0-incubating/traffic_ops/install/lib/WebDep.pm
> 5. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/github.com/jheitz200/test_helper/http.go
> 6. ./apache-trafficcontrol-2.0.0-incubating/traffic_stats/vendor/github.com/jheitz200/test_helper/test.go
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

Justin Mclean
In reply to this post by Dan Kirkwood-2
Hi,

> The build instructions will be put in place once the release is done
> -- catch-22.

Yep another reason for including them in the release IMO.

> Would Jira issues for the copyright and build instruction issues be sufficient?  

Yes. Changing my vote to +1 binding.

Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

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

Phil Sorber
Checksums match.

GPG sig verifies, but is untrusted:
$ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
gpg: assuming signed data in `apache-trafficcontrol-2.0.0-incubating.tar.gz'
gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
9AB7BDD5
gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
[hidden email]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the
owner.
Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5

No signatures:
$ gpg --list-sigs 9AB7BDD5
pub   4096R/9AB7BDD5 2017-04-25
uid                  Eric Friedrich (CODE SIGNING KEY) <[hidden email]>
sig 3        9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
[hidden email]>
sub   4096R/F445ABB1 2017-04-25
sig          9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
[hidden email]>

I won't -1 on that, but we should try to have every RM make sure their keys
are trusted. I've already spoken with Eric about this.

Build also works, with one caveat. You have to set selinux to unenforcing,
otherwise you fail from permissions errors. You can do this with
`setenforce 0` as root. I won't -1 for this either, but we should add that
to the build documentation.

-rw-r--r--. 1 phil phil  51M Jun 30 15:12
traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 910K Jun 30 15:10
traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 858K Jun 30 15:10
traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil  22K Jun 30 15:10
traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil  21K Jun 30 15:10
traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 142K Jun 30 15:12
traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil  17M Jun 30 15:12
traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 417K Jun 30 15:11
traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm

+1 binding.

Thanks!

On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <[hidden email]>
wrote:

> Hi,
>
> > The build instructions will be put in place once the release is done
> > -- catch-22.
>
> Yep another reason for including them in the release IMO.
>
> > Would Jira issues for the copyright and build instruction issues be
> sufficient?
>
> Yes. Changing my vote to +1 binding.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re:[RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Eric Friedrich (efriedri)
Dear IPMC Community,

I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of Apache Traffic Control (Incubating) for release as “Apache Traffic Control (incubating) 2.0.0"

The vote has passed with:
- three binding "+1" votes
- no "0" votes
- no "-1" votes

The votes were (https://lists.apache.org/thread.html/c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%3Cgeneral.incubator.apache.org%3E<https://lists.apache.org/thread.html/c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@<general.incubator.apache.org>>):
- +1, Justin Mclean (binding)
- +1, John D. Ament (binding)
- +1, Phil Sorber (binding)

Thank you, for your support!

—Eric

On Jun 30, 2017, at 5:27 PM, Phil Sorber <[hidden email]<mailto:[hidden email]>> wrote:

Checksums match.

GPG sig verifies, but is untrusted:
$ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
gpg: assuming signed data in `apache-trafficcontrol-2.0.0-incubating.tar.gz'
gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
9AB7BDD5
gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
[hidden email]<mailto:[hidden email]>>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the
owner.
Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5

No signatures:
$ gpg --list-sigs 9AB7BDD5
pub   4096R/9AB7BDD5 2017-04-25
uid                  Eric Friedrich (CODE SIGNING KEY) <[hidden email]<mailto:[hidden email]>>
sig 3        9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
[hidden email]<mailto:[hidden email]>>
sub   4096R/F445ABB1 2017-04-25
sig          9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
[hidden email]<mailto:[hidden email]>>

I won't -1 on that, but we should try to have every RM make sure their keys
are trusted. I've already spoken with Eric about this.

Build also works, with one caveat. You have to set selinux to unenforcing,
otherwise you fail from permissions errors. You can do this with
`setenforce 0` as root. I won't -1 for this either, but we should add that
to the build documentation.

-rw-r--r--. 1 phil phil  51M Jun 30 15:12
traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 910K Jun 30 15:10
traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 858K Jun 30 15:10
traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil  22K Jun 30 15:10
traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil  21K Jun 30 15:10
traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 142K Jun 30 15:12
traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil  17M Jun 30 15:12
traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
-rw-r--r--. 1 phil phil 417K Jun 30 15:11
traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
-rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm

+1 binding.

Thanks!

On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <[hidden email]<mailto:[hidden email]>>
wrote:

Hi,

The build instructions will be put in place once the release is done
-- catch-22.

Yep another reason for including them in the release IMO.

Would Jira issues for the copyright and build instruction issues be
sufficient?

Yes. Changing my vote to +1 binding.

Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]<mailto:[hidden email]>
For additional commands, e-mail: [hidden email]<mailto:[hidden email]>



Reply | Threaded
Open this post in threaded view
|

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Dave Neuman
+1 However....
We need to add a release note suggesting that traffic stats works best with
influxdb version < 1.3.x.  As of 1.3.x InfluxDB now returns a 400 response
when the client attempts to write points that are outside of the retention
policy.  When this happens, Traffic Stats seems to hold on to the "old"
points and attempts to write them again on the next POST.  This causes what
is essentially a memory leak in Traffic Stats since it continues to hold
onto and tries to write stats that are outside of the retention policy.
This may or may not affect a user, depending upon which stats they are
trying to write to influxdb.  For example, we write the wrap_count to
influxdb, this is a stat that does not often change within 24 hours, so we
see the memory leak with stats not written on each poll of traffic stats.

In versions < 1.3.x InfluxDB would still not write the point, but it would
accept the write request and just drop the points outside of the retention
policy on the floor.

This is fixed here:
https://github.com/apache/incubator-trafficcontrol/pull/1289 and will be in
the next release of traffic control.

Also, we should note that you need to set selinux to "unenforcing" in order
to get the build to work, otherwise you fail on permissions erros.  You can
do this with
`setenforce 0` as root.


Thanks,
Dave

On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
[hidden email]> wrote:

> Dear IPMC Community,
>
> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of
> Apache Traffic Control (Incubating) for release as “Apache Traffic Control
> (incubating) 2.0.0"
>
> The vote has passed with:
> - three binding "+1" votes
> - no "0" votes
> - no "-1" votes
>
> The votes were (https://lists.apache.org/thread.html/
> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
> 3Cgeneral.incubator.apache.org%3E<https://lists.apache.org/thread.html/
> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@<ge
> neral.incubator.apache.org>>):
> - +1, Justin Mclean (binding)
> - +1, John D. Ament (binding)
> - +1, Phil Sorber (binding)
>
> Thank you, for your support!
>
> —Eric
>
> On Jun 30, 2017, at 5:27 PM, Phil Sorber <[hidden email]<mailto:sorb
> [hidden email]>> wrote:
>
> Checksums match.
>
> GPG sig verifies, but is untrusted:
> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
> incubating.tar.gz'
> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
> 9AB7BDD5
> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
> [hidden email]<mailto:[hidden email]>>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:          There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5
>
> No signatures:
> $ gpg --list-sigs 9AB7BDD5
> pub   4096R/9AB7BDD5 2017-04-25
> uid                  Eric Friedrich (CODE SIGNING KEY) <[hidden email]
> <mailto:[hidden email]>>
> sig 3        9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> [hidden email]<mailto:[hidden email]>>
> sub   4096R/F445ABB1 2017-04-25
> sig          9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> [hidden email]<mailto:[hidden email]>>
>
> I won't -1 on that, but we should try to have every RM make sure their keys
> are trusted. I've already spoken with Eric about this.
>
> Build also works, with one caveat. You have to set selinux to unenforcing,
> otherwise you fail from permissions errors. You can do this with
> `setenforce 0` as root. I won't -1 for this either, but we should add that
> to the build documentation.
>
> -rw-r--r--. 1 phil phil  51M Jun 30 15:12
> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil  22K Jun 30 15:10
> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil  21K Jun 30 15:10
> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil  17M Jun 30 15:12
> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>
> +1 binding.
>
> Thanks!
>
> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <[hidden email]<
> mailto:[hidden email]>>
> wrote:
>
> Hi,
>
> The build instructions will be put in place once the release is done
> -- catch-22.
>
> Yep another reason for including them in the release IMO.
>
> Would Jira issues for the copyright and build instruction issues be
> sufficient?
>
> Yes. Changing my vote to +1 binding.
>
> Thanks,
> Justin
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]<mailto:
> [hidden email]>
> For additional commands, e-mail: [hidden email]<mailto:
> [hidden email]>
>
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Dan Kirkwood-2
Dave,  did you mean for this to be for 2.1.0 RC2?    You replied to
the wrong email..

-dan

On Mon, Nov 20, 2017 at 11:13 AM, Dave Neuman <[hidden email]> wrote:

> +1 However....
> We need to add a release note suggesting that traffic stats works best with
> influxdb version < 1.3.x.  As of 1.3.x InfluxDB now returns a 400 response
> when the client attempts to write points that are outside of the retention
> policy.  When this happens, Traffic Stats seems to hold on to the "old"
> points and attempts to write them again on the next POST.  This causes what
> is essentially a memory leak in Traffic Stats since it continues to hold
> onto and tries to write stats that are outside of the retention policy.
> This may or may not affect a user, depending upon which stats they are
> trying to write to influxdb.  For example, we write the wrap_count to
> influxdb, this is a stat that does not often change within 24 hours, so we
> see the memory leak with stats not written on each poll of traffic stats.
>
> In versions < 1.3.x InfluxDB would still not write the point, but it would
> accept the write request and just drop the points outside of the retention
> policy on the floor.
>
> This is fixed here:
> https://github.com/apache/incubator-trafficcontrol/pull/1289 and will be in
> the next release of traffic control.
>
> Also, we should note that you need to set selinux to "unenforcing" in order
> to get the build to work, otherwise you fail on permissions erros.  You can
> do this with
> `setenforce 0` as root.
>
>
> Thanks,
> Dave
>
> On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
> [hidden email]> wrote:
>
>> Dear IPMC Community,
>>
>> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6 of
>> Apache Traffic Control (Incubating) for release as “Apache Traffic Control
>> (incubating) 2.0.0"
>>
>> The vote has passed with:
>> - three binding "+1" votes
>> - no "0" votes
>> - no "-1" votes
>>
>> The votes were (https://lists.apache.org/thread.html/
>> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
>> 3Cgeneral.incubator.apache.org%3E<https://lists.apache.org/thread.html/
>> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@<ge
>> neral.incubator.apache.org>>):
>> - +1, Justin Mclean (binding)
>> - +1, John D. Ament (binding)
>> - +1, Phil Sorber (binding)
>>
>> Thank you, for your support!
>>
>> —Eric
>>
>> On Jun 30, 2017, at 5:27 PM, Phil Sorber <[hidden email]<mailto:sorb
>> [hidden email]>> wrote:
>>
>> Checksums match.
>>
>> GPG sig verifies, but is untrusted:
>> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
>> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
>> incubating.tar.gz'
>> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
>> 9AB7BDD5
>> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
>> [hidden email]<mailto:[hidden email]>>"
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg:          There is no indication that the signature belongs to the
>> owner.
>> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7 BDD5
>>
>> No signatures:
>> $ gpg --list-sigs 9AB7BDD5
>> pub   4096R/9AB7BDD5 2017-04-25
>> uid                  Eric Friedrich (CODE SIGNING KEY) <[hidden email]
>> <mailto:[hidden email]>>
>> sig 3        9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
>> [hidden email]<mailto:[hidden email]>>
>> sub   4096R/F445ABB1 2017-04-25
>> sig          9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
>> [hidden email]<mailto:[hidden email]>>
>>
>> I won't -1 on that, but we should try to have every RM make sure their keys
>> are trusted. I've already spoken with Eric about this.
>>
>> Build also works, with one caveat. You have to set selinux to unenforcing,
>> otherwise you fail from permissions errors. You can do this with
>> `setenforce 0` as root. I won't -1 for this either, but we should add that
>> to the build documentation.
>>
>> -rw-r--r--. 1 phil phil  51M Jun 30 15:12
>> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
>> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil  22K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil  21K Jun 30 15:10
>> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
>> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil  17M Jun 30 15:12
>> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
>> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
>> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
>>
>> +1 binding.
>>
>> Thanks!
>>
>> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <[hidden email]<
>> mailto:[hidden email]>>
>> wrote:
>>
>> Hi,
>>
>> The build instructions will be put in place once the release is done
>> -- catch-22.
>>
>> Yep another reason for including them in the release IMO.
>>
>> Would Jira issues for the copyright and build instruction issues be
>> sufficient?
>>
>> Yes. Changing my vote to +1 binding.
>>
>> Thanks,
>> Justin
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]<mailto:
>> [hidden email]>
>> For additional commands, e-mail: [hidden email]<mailto:
>> [hidden email]>
>>
>>
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [RESULT] [VOTE] Release Apache Traffic Control 2.0.0 incubating (RC6)

Dave Neuman
Oops. I did reply to the wrong email! Sorry.

On Mon, Nov 20, 2017 at 12:47 Dan Kirkwood <[hidden email]> wrote:

> Dave,  did you mean for this to be for 2.1.0 RC2?    You replied to
> the wrong email..
>
> -dan
>
> On Mon, Nov 20, 2017 at 11:13 AM, Dave Neuman <[hidden email]> wrote:
> > +1 However....
> > We need to add a release note suggesting that traffic stats works best
> with
> > influxdb version < 1.3.x.  As of 1.3.x InfluxDB now returns a 400
> response
> > when the client attempts to write points that are outside of the
> retention
> > policy.  When this happens, Traffic Stats seems to hold on to the "old"
> > points and attempts to write them again on the next POST.  This causes
> what
> > is essentially a memory leak in Traffic Stats since it continues to hold
> > onto and tries to write stats that are outside of the retention policy.
> > This may or may not affect a user, depending upon which stats they are
> > trying to write to influxdb.  For example, we write the wrap_count to
> > influxdb, this is a stat that does not often change within 24 hours, so
> we
> > see the memory leak with stats not written on each poll of traffic stats.
> >
> > In versions < 1.3.x InfluxDB would still not write the point, but it
> would
> > accept the write request and just drop the points outside of the
> retention
> > policy on the floor.
> >
> > This is fixed here:
> > https://github.com/apache/incubator-trafficcontrol/pull/1289 and will
> be in
> > the next release of traffic control.
> >
> > Also, we should note that you need to set selinux to "unenforcing" in
> order
> > to get the build to work, otherwise you fail on permissions erros.  You
> can
> > do this with
> > `setenforce 0` as root.
> >
> >
> > Thanks,
> > Dave
> >
> > On Thu, Jul 6, 2017 at 3:26 PM, Eric Friedrich (efriedri) <
> > [hidden email]> wrote:
> >
> >> Dear IPMC Community,
> >>
> >> I am pleased to announce that the Incubator PMC has approved 2.0.0-RC6
> of
> >> Apache Traffic Control (Incubating) for release as “Apache Traffic
> Control
> >> (incubating) 2.0.0"
> >>
> >> The vote has passed with:
> >> - three binding "+1" votes
> >> - no "0" votes
> >> - no "-1" votes
> >>
> >> The votes were (https://lists.apache.org/thread.html/
> >> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@%
> >> 3Cgeneral.incubator.apache.org%3E<https://lists.apache.org/thread.html/
> >> c44716e02d175b78def5d1a219474e6f5c397120e33d64208158511e@<ge
> >> neral.incubator.apache.org>>):
> >> - +1, Justin Mclean (binding)
> >> - +1, John D. Ament (binding)
> >> - +1, Phil Sorber (binding)
> >>
> >> Thank you, for your support!
> >>
> >> —Eric
> >>
> >> On Jun 30, 2017, at 5:27 PM, Phil Sorber <[hidden email]<mailto:sorb
> >> [hidden email]>> wrote:
> >>
> >> Checksums match.
> >>
> >> GPG sig verifies, but is untrusted:
> >> $ gpg --verify apache-trafficcontrol-2.0.0-incubating.tar.gz.asc
> >> gpg: assuming signed data in `apache-trafficcontrol-2.0.0-
> >> incubating.tar.gz'
> >> gpg: Signature made Fri 16 Jun 2017 10:25:33 AM MDT using RSA key ID
> >> 9AB7BDD5
> >> gpg: Good signature from "Eric Friedrich (CODE SIGNING KEY) <
> >> [hidden email]<mailto:[hidden email]>>"
> >> gpg: WARNING: This key is not certified with a trusted signature!
> >> gpg:          There is no indication that the signature belongs to the
> >> owner.
> >> Primary key fingerprint: C3ED F3D4 C5EE F3E5 5932  3FF8 F220 0BAB 9AB7
> BDD5
> >>
> >> No signatures:
> >> $ gpg --list-sigs 9AB7BDD5
> >> pub   4096R/9AB7BDD5 2017-04-25
> >> uid                  Eric Friedrich (CODE SIGNING KEY) <
> [hidden email]
> >> <mailto:[hidden email]>>
> >> sig 3        9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> >> [hidden email]<mailto:[hidden email]>>
> >> sub   4096R/F445ABB1 2017-04-25
> >> sig          9AB7BDD5 2017-04-25  Eric Friedrich (CODE SIGNING KEY) <
> >> [hidden email]<mailto:[hidden email]>>
> >>
> >> I won't -1 on that, but we should try to have every RM make sure their
> keys
> >> are trusted. I've already spoken with Eric about this.
> >>
> >> Build also works, with one caveat. You have to set selinux to
> unenforcing,
> >> otherwise you fail from permissions errors. You can do this with
> >> `setenforce 0` as root. I won't -1 for this either, but we should add
> that
> >> to the build documentation.
> >>
> >> -rw-r--r--. 1 phil phil  51M Jun 30 15:12
> >> traffic_monitor-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 910K Jun 30 15:10
> >> traffic_ops-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 858K Jun 30 15:10
> >> traffic_ops-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil  22K Jun 30 15:10
> >> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil  21K Jun 30 15:10
> >> traffic_ops_ort-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 142K Jun 30 15:12
> >> traffic_portal-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 3.6M Jun 30 15:12
> >> traffic_portal-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil  17M Jun 30 15:12
> >> traffic_router-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >> -rw-r--r--. 1 phil phil 417K Jun 30 15:11
> >> traffic_stats-2.0.0-5668.85d14ebe.el7.src.rpm
> >> -rw-r--r--. 1 phil phil 5.0M Jun 30 15:11
> >> traffic_stats-2.0.0-5668.85d14ebe.el7.x86_64.rpm
> >>
> >> +1 binding.
> >>
> >> Thanks!
> >>
> >> On Wed, Jun 28, 2017 at 5:20 PM Justin Mclean <[hidden email]
> <
> >> mailto:[hidden email]>>
> >> wrote:
> >>
> >> Hi,
> >>
> >> The build instructions will be put in place once the release is done
> >> -- catch-22.
> >>
> >> Yep another reason for including them in the release IMO.
> >>
> >> Would Jira issues for the copyright and build instruction issues be
> >> sufficient?
> >>
> >> Yes. Changing my vote to +1 binding.
> >>
> >> Thanks,
> >> Justin
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> <mailto:
> >> [hidden email]>
> >> For additional commands, e-mail: [hidden email]
> <mailto:
> >> [hidden email]>
> >>
> >>
> >>
> >>
>