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

-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 +

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

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: >

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

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:

Re: Project Management - Shared Dashboards

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

Re: Component Naming Standards - Project Management

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

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

Re: Traffic Ops - Reorganize the client directory

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

Re: Project Management - Shared Dashboards

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

Re: Traffic Ops - Reorganize the client directory

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

Re: Traffic Ops - Reorganize the client directory

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

Project Management - Shared Dashboards

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