Traffic Ops 2.0 - Upcoming Features

26 views
Skip to first unread message

Dewayne Richardson

unread,
Jun 1, 2016, 3:15:21 PM6/1/16
to traffic_control-discuss
We are in the initial planning stages of TO 2.0, where the biggest change will be the TO database migration from MySQL to PostgreSQL.  This will include code changes to the 1.x code base and documentation to support Postgres as well as any automated scripts (if necessary). The existing TO 1.x features that exist today will stay intact (barring bug fixes), including the UI, and API. 

Therefore, Traffic Control 1.6 will be the last Traffic Ops with MySQL release.  

Reasoning
Traffic Control's ultimate goal is to become an Apache project, which requires that the Traffic Control software stack be truly Open Source and license free.  MySQL is currently a barrier to that goal.

Operational Impact
We anticipate automation to help with the database conversion from MySQL to Postgres, which will be fully documented when completed.

Please keep questions and concerns focused to this group thread so that the information stays public and accessible.

Jan van Doorn

unread,
Jun 3, 2016, 11:24:21 AM6/3/16
to traffic_control-discuss
Just to add some background, this is a change from the plans I proposed before.  

Proposal is now to first move the existing perl/mojo/jquery TO app to the Postgres database, and change nothing else, and call that Traffic Ops 2.0.  Then when we move to an Angular.JS main Traffic Ops UI, we call that TO 3.0. The transition from 2.0 to 3.0 can be a set of incremental changes this way. 

The 3.0 plan doesn't really change a lot. We will have a reverse proxy that is the 'single entry point' into the app, that maps all requests to the appropriate (micro) service. And a set of (micro) services that handle the database REST-CRUD operations, Traffic Stats and Traffic Vault access, etc. 

Please let us know if you see any issues with this change in plan.

Rgds,
JvD

Jay Li

unread,
Jun 13, 2016, 8:46:44 AM6/13/16
to traffic_control-discuss
The migration plan looks good. Will the Postgress be a separated micro-service in TO2.0?

thanks
Jay

j...@knutsel.com

unread,
Jun 13, 2016, 11:38:56 AM6/13/16
to traffic_control-discuss

Thanks. I think in 2.0 we just run Postgres as we run MySQL - a direct database connection from the Mojolicious app. 


Rgds,

JvD


On Wednesday, June 1, 2016 at 1:15:21 PM UTC-6, Dewayne Richardson wrote:

Eric Friedrich

unread,
Jul 6, 2016, 11:45:41 AM7/6/16
to traffic_control-discuss
In which release is support for Centos7 planned? 
Reply all
Reply to author
Forward
0 new messages