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

[Dan Kirkwood]

-1 -- I neglected to remove the reference to an rpm on the build
server in the traffic_ops installation doc.   That won't go over well
with the IPMC.

Otherwise,  I checked:
- signature -- issue with that
+ tarball is correctly named and extracts correct structure
+ md5 and sha512 checksums good
+ builds from source extracted from tarball
+ rpm for traffic_ops installs on clean machine

-dan

On Thu, Jun 15, 2017 at 1:41 PM, Dan Kirkwood  wrote:
> I checked the signature,  but didn't get Eric's key from the gpg
> refresh.   He's looking into that now..
>
> Meanwhile,  I'm going to build and install fresh.
>
> btw,  Eric -- the Changes section above should be:
>> Changes since 1.8.1:
>> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1...RELEASE-2.0.0-RC5
>
> -dan
>
> On Thu, Jun 15, 2017 at 12:30 PM, Eric Friedrich (efriedri)
>  wrote:
>> Hello All,
>>
>> I've prepared the next candidate release for incubator-trafficcontrol v2.0.0 
>> (RC5)
>>
>> Changes since 1.8.0:
>> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC5
>>
>> This corresponds to git:
>> Hash: b64848e38a09ee372c9a21a3652ea210962ccffa
>> Tag: RELEASE-2.0.0-RC5
>>
>> Which can be verified with the following:git tag -v RELEASE-2.0.0-RC5
>>
>> 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/RC5
>>
>> Docs are available here: https://trafficcontrol.apache.org/docs/2.0.x/
>>
>>
>> The vote will remain open until Thursday, June 20, 2017.
>>
>> This RC fixes some comments from the IPMC made about 1.8.1 and also some 
>> minor bugs in the post install.
>>
>> Thanks,
>> Eric Friedrich

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

[Dan Kirkwood]

I checked the signature,  but didn't get Eric's key from the gpg
refresh.   He's looking into that now..

Meanwhile,  I'm going to build and install fresh.

btw,  Eric -- the Changes section above should be:
> Changes since 1.8.1:
> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1...RELEASE-2.0.0-RC5

-dan

On Thu, Jun 15, 2017 at 12:30 PM, Eric Friedrich (efriedri)
 wrote:
> Hello All,
>
> I've prepared the next candidate release for incubator-trafficcontrol v2.0.0 
> (RC5)
>
> Changes since 1.8.0:
> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.8.1-RC0...RELEASE-2.0.0-RC5
>
> This corresponds to git:
> Hash: b64848e38a09ee372c9a21a3652ea210962ccffa
> Tag: RELEASE-2.0.0-RC5
>
> Which can be verified with the following:git tag -v RELEASE-2.0.0-RC5
>
> 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/RC5
>
> Docs are available here: https://trafficcontrol.apache.org/docs/2.0.x/
>
>
> The vote will remain open until Thursday, June 20, 2017.
>
> This RC fixes some comments from the IPMC made about 1.8.1 and also some 
> minor bugs in the post install.
>
> Thanks,
> Eric Friedrich

[VOTE] Release Apache Traffic Control 2.0.0-incubating (RC5)

[Eric Friedrich (efriedri)]

Hello All,

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

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

This corresponds to git:
Hash: b64848e38a09ee372c9a21a3652ea210962ccffa
Tag: RELEASE-2.0.0-RC5

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

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/RC5

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


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

This RC fixes some comments from the IPMC made about 1.8.1 and also some minor 
bugs in the post install.

Thanks,
Eric Friedrich

Re: Project Management - Shared Dashboards

[Durfey, Ryan]

Thanks for the feedback. I see the issue now.  I shared with the “Traffic 
Control” project so if you didn’t have a formal role assignment, you couldn’t 
see them.  I have updated to share = “Everyone”.

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


From: Hank Beatty 
Reply-To: "dev@trafficcontrol.incubator.apache.org" 

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

Subject: Re: Project Management - Shared Dashboards

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.com:
cdn_supp...@comcast.com>

Re: Component Naming Standards - Project Management

[Chris Lemmons]

I concur, as long as the github switch is happening in the fairly near
future. The team has consensus on the switch, but have we let Apache
Infrastructure know?

On Mon, Jun 12, 2017 at 7:55 AM, Gelinas, Derek 
wrote:

> +1
>
> On Jun 12, 2017, at 9:54 AM, Dave Neuman  a...@apache.org>> wrote:
>
> To be honest, I would hold off on that for now since we should be moving to
> full github soon.
> Once we move to full github we can slice and dice things up.
>
> On Sun, Jun 11, 2017 at 8:25 AM, Durfey, Ryan  mailto:ryan_dur...@comcast.com>>
> wrote:
>
> I wanted to start organizing the Jira issues and the first thing I need to
> do is ensure components are assigned to each issue.  The list looks pretty
> good, but I wanted to confirm a few before organizing?
>
>
>  1.  Should we subdivide components like this?  If yes, are all of these
> valid?
> *   Traffic Ops
> *   Traffic Ops API
> *   Traffic Ops ORT
> *   Traffic Ops Client
>  2.  Should we have a component that relates back to Traffic Server to
> indicate work that crosses over like "Traffic Server Related"?
>  3.  Do we need generic components like these?
> *   Documentation
> *   Release
> *   All
>  4.  All of these look good, any mods suggested?
> *   Traffic Analytics
> *   Traffic Logs
> *   Traffic Monitor
> *   Traffic Monitor (golang)
> *   Traffic Ops
> *   Traffic Portal
> *   Traffic Router
> *   Traffic Stats
> *   Traffic Vault
>
>
> Ryan Durfey
> Sr. Product Manager - CDN | Comcast Technology Solutions
> 1899 Wynkoop Ste. 550 | Denver, CO 8020
> M | 303-524-5099
> ryan_dur...@comcast.com ryan_dur...@comcast.com>
> CDN Support (24x7): 866-405-2993 or cdn_supp...@comcast.com cdn_supp...@comcast.com> cdn_supp...@comcast.com>
>
>
>

Re: Project Management - Shared Dashboards

[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

[Chris Lemmons]

Ok, if we're going to bite the bullet and break all the traffic ops client
imports, here's my vote:

traffic_ops/clients/go-to/*.go
traffic_ops/clients/py-to/*.py

This is because the last part of the name of the end directory is, by
convention, the name of the library in go. I'll skip the long rant about
precisely how much I do or don't like it, but it means you'll use it like
this:

import `
github.com/apache/incubator-trafficcontrol/traffic_ops/clients/go-to`
func foo() {
  to.DoThings()
}

Half the time I see the import overriden as "to" anyway. Note, we'd need to
update the package line to be "package to" in the folder.
golang.org/x/tools/cmd/gorename may be of use for the transition.

On Thu, Jun 15, 2017 at 9:16 AM, Hank Beatty  wrote:

> 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: Project Management - Shared Dashboards

[Durfey, Ryan]

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

[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: Traffic Ops - Reorganize the client directory

[Dave Neuman]

How about we leave all of the golang stuff in the client directory and then
add a "python_client" directory (or whatever you want to call it)?
That way we don't break everyone using the client and we still get the
python client in there.

On Thu, Jun 15, 2017 at 8:42 AM, Dan Kirkwood  wrote:

> +1 as well,  but should `golang` be `go` instead?
>
> I have the beginnings of a usable set of bash functions as well..
> Should that go in as well? :-)
>
> On Wed, Jun 14, 2017 at 9:37 PM, Mark Torluemke 
> wrote:
> > Also +1 to having more TO clients, and classifying them into
> > language-specific directories. Other suggestions welcome, though.
> >
> > For instance, longer term, should we target a "Traffic Control" client,
> > with sub-modules for each component? Should the code for these clients
> live
> > in the language-specific networks (PyPI, CPAN, etc)?
> >
> > On Wed, Jun 14, 2017 at 3:11 PM, Dewayne Richardson 
> > wrote:
> >
> >> +1 (as long as you don't break anything!, lol).  I think this will be
> >> valuable because I've already seen 2 different groups out side of ours
> (at
> >> Comcast) that are reinventing that wheel over and over.  We should have
> >> several clients in different languages to open the door to more Traffic
> Ops
> >> access.
> >>
> >> On Wed, Jun 14, 2017 at 9:35 AM, Scrimo, Robert (Contractor) <
> >> robert_scr...@comcast.com> 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
> >> >
> >> >
> >>
>

Project Management - Shared Dashboards

[Durfey, Ryan]

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.com