Traffic Control 1.2.0 Release
Release Notes for Traffic Control 1.2.0
- CDN_Name has become a top level attribute in the new 'cdn' table
- New API endpoint 'cdns' to expose the 'cdn' table data
- New Misc->CDNs UI to support the new 'cdn' table
- Configurable Mojo secret can now be stored in the /opt/traffic_ops/app/conf/cdn.conf file
- traffic_stats has been refactored into one binary
- Additional bug fixes
Upgrading
If upgrading Traffic Monitor from 1.1.1 to 1.2.0, make a backup of /opt/traffic_monitor/conf/traffic_monitor_config.js, erase 1.1.1, then install 1.2.0. Once 1.2.0 is installed, copy the prior config back in place and start tomcat.
Known Issues
There is a bug introduced with the concept of the "ALL" CDN that breaks the legacy redis graphs.
Changes with Traffic Control 1.2.0
#131 - diff tool with parameters missing entries
#556 - Error in Genfiles for OFFLINE mid
#562 - Join on ID instead of parameter name since that can be duplicated.
#565 - Missed some variable renames.
#572 - Combine ts_daily_summary into write_traffic_stats
#577 - More changes for traffic_stats
#578 - Update init script and default log level
#580 - handle case where CDN is null for a profile
#582 - Try CentOS init instead of Debian init
#583 - Fix logging and startup
#584 - Missed one time format change
#585 - Switch from ID to name:configfile for the param key when deciding uniqueness
#589 - Fix traffic_stats init script startup
#590 - MySQL does not use a standard time format
#594 - Web UI Unexpected RuntimeException
#598 - Setting server in PRE_PROD causes Traffic Monitor exceptions
#604 - Use retention policy from config instead of hard coded value
#628 - Update all versions to 1.2.0 due to breaking changes.
#630 - Reverts Federation mapping changes targeted for the next release.
#633 - cdn.conf validation checks for secrets instead of shared_secret
#635 - Sql cherrypicks 1 2 0