I would like to propose a new method for ATS config file generation, in which a single definition file for each CDN which will contain all the information required for any server within that CDN to generate its own configs, rather than requesting them from traffic ops. This would be a version-controlled json file that, when generated, would be stored in a new table in the traffic ops database as a blob type. This will satisfy high-availability requirements and allow several versions of the configuration to be retained for rollback, as well as “freezing” the config at that moment in time. Combined with cache support coming in 2.1, this file would only need be generated once per traffic ops server instance. Instead of queueing servers to update their configurations, the configuration would be snapshotted similar to the crconfig file and downloaded by each cache according to their set interval checks – rather than performing a syncds and checking that the server has been queued for update, the version number would simply be checked and compared against the currently active version on the cache itself. Should a difference be found the server would request the definition file and begin generating configuration files for itself using the data in the definition file.
I would like feedback from the community regarding this proposal, and any suggestions or comments you may have. Thanks! Derek Derek Gelinas IPCDN Engineering derek_geli...@cable.comcast.com<mailto:derek_geli...@cable.comcast.com> 603.812.5379
