2.0 planned features

[David Neuman]

Hey All, 

Since the Traffic Control 1.6.0 Release Candidate has been cut, I think now is a good time to start the conversation about what will be included in 2.0.  My hope is that we can get our arms around everything that is planned to be included and make sure we have it properly tracked in Github.  Below I started a list of what I know of that is planned for the Traffic Control 2.0 release.  Please feel free to add anything I may have missed or anything you are planning to include that is not already on this list.

Traffic Router: https://github.com/Comcast/traffic_control/issues?q=is%3Aopen+is%3Aissue+label%3A%22Traffic+Router%22+milestone%3A2.0.0

  - HTTPS Support for HTTP* DSs

  - HTTP redirection to HTTPS for DSs configured to use HTTPS or HTTP/HTTPS

  - Issue #1404: Improved logging

  - Issue #1449:  Traffic Router fetches invalid czfile/rgbfile to its db directory

Traffic Monitor: https://github.com/Comcast/traffic_control/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0.0+label%3A%22Traffic+Monitor%22

  - We are currently working on a golang re-write of Traffic Monitor.  I dont think it will be ready for 2.0, but I will update as we get closer to complete.

  - 

Traffic Stats: https://github.com/Comcast/traffic_control/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0.0+label%3A%22Traffic+Stats%22

  - Issue #1458 - Traffic Stats exits when it cannot reach influxDb servers

Traffic Ops: https://github.com/Comcast/traffic_control/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0.0+label%3A%22Traffic+Ops%22

  - Support for configuring HTTP* DSs to use HTTPS

  - Conversion from MySQL to PostgresSQL

  - Add 'Geolimit Redirect URL' parameter in Delivery service

  - Add ability to copy url_sig_keys from one deliveryservice to another

  - Error when creating SSL keys for DS when keys were originally pasted and not generated

Traffic Vault: https://github.com/Comcast/traffic_control/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.0.0+label%3A%22Traffic+Vault%22

  - Enable Riak Search to make it easier to get all SSL certs for a host, deliveryservice, or CDN.

[Steve Malenfant]

Dave,

I see a lot of good stuff related to HTTPS here. 1 issue that prevented me from moving ahead is related to running origin on different port than 80 (regression mostly due to parent.config origin separation at the edge). I've got something that half tested so far and not in production yet which is https://github.com/Comcast/traffic_control/issues/1203

There is also a few things related to Multi-site origin like https://github.com/Comcast/traffic_control/issues/1349 as well.

I planning on contributing the fix for both, but they might require extensive testing on other users of Traffic Control.

Steve

[David Neuman]

Thanks, Steve.  I added both of those issues to the 2.0 milestone and assigned to you.

--
You received this message because you are subscribed to the Google Groups "traffic_control-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to traffic_control-d...@googlegroups.com.
To post to this group, send email to traffic_con...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/traffic_control-discuss/adebe7a0-beec-4411-9f26-5767480f6111%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jackie Heitzer]

I think the main focus of Traffic Control 2.0 should be the conversion from MySQL to PostgreSQL.  This release will include alot of breaking changes and we want  to have the ability to regression test thoroughly and roll back easily if necessary.  I recommend renaming the current release 1.7 and holding off on the conversion of MySQL to PostgreSQL until 2.0.

Thanks

Jackie

To view this discussion on the web visit https://groups.google.com/d/msgid/traffic_control-discuss/CAMuiy1P63rz%2BEV35BiPopzL-d2tNYKmYQ7HvQfqAs6cTp5mXpA%40mail.gmail.com.

[David Neuman]

Any idea when you guys plan on being ready with the Postgres migration?  Trying to figure out if we should try to do that before we do another release or after...

[David Neuman]

All, 

After talking with Jan (project chair) we decided that it is best to have the next feature release of Traffic Control be 1.7.0.  We will then have a release shortly after with only the Postgres migration called 2.0.  

I am going to move all of the non Postgres related issues from the 2.0 milestone to the 1.7.0 milestone.  I have outlined which features I know to be in this release above, but if you want more information I encourage you to check out the 1.7.0 milestone in Github.  If there is something you were hoping to see get included which is not in this email or github, lets work together to get it in the plan.

Please let me know if you have any questions.

Thanks,
Dave

[Eric Friedrich (efriedri)]

Thanks Dave-

  What is the target date for 1.7? We may have some features we’d like to add into the list

—Eric

To view this discussion on the web visit https://groups.google.com/d/msgid/traffic_control-discuss/CAMuiy1OGzjzSB0argsw1Shb%2BwJmo0R5QnKEYgLxTQ1mGjE-zLQ%40mail.gmail.com.

[David Neuman]

Ah, I forgot to mention that part!  We are planning on creating our first release candidate on 8/31/2016.

To view this discussion on the web visit https://groups.google.com/d/msgid/traffic_control-discuss/B03B0F30-CA55-46D7-AC2A-B2997BDE3A02%40cisco.com.

[Eric Friedrich (efriedri)]

Ok Great. 

We’ll hopefully be able to contribute the following in that timeframe:

- Components verified on Centos 7.2 (not sure how much dev work is in this one)

- Very basic content prepositioning support (email to come on this in the next week or so, expect a WIP PR too)

I’m not sure if these will make the cut for 1.7 but we are planning for them to be complete by the end of August

—Eric

To view this discussion on the web visit https://groups.google.com/d/msgid/traffic_control-discuss/CAMuiy1MjA0jD6pbwdmbcijCx-wnB%3D3Xq4LKCX4f-vOVHZAxUtA%40mail.gmail.com.

[Dan Kirkwood]

Hi Dave,

I'd also like to add the capability to build rpms using docker.   Initial work is complete:  https://github.com/Comcast/traffic_control/pull/1657 . Jeremy (mitchell852) has already assigned to himself,  but more eyeballs and comments are welcome...

Also planning on updating the docker runtime that Rob created to work with 1.6.0.

-dan

[David Neuman]

Sweet, sounds good Dan.  I think we should start a new thread on Docker support (maybe once the PR is ready) and see if we can get others to help with the testing.

--

You received this message because you are subscribed to the Google Groups "traffic_control-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to traffic_control-d...@googlegroups.com.
To post to this group, send email to traffic_con...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/traffic_control-discuss/0bf166cf-7d97-4fed-9cc6-31bbc025f97b%40googlegroups.com.