Hi, In order to further improve the simplicity and robustness of the control path for provisioning infrastructure and delivery services, we are currently considering ways to streamline management and operations.
Currently, when applying changes in traffic-control that require the synchronization between the traffic-router and traffic-servers, the user should be conscious to do so in a certain order. Otherwise, "black holes" may be created. Furthermore, in some of the scenarios the user have to wait and verify that the configuration reached all traffic server before he may apply it to the traffic-router. We have noticed that TC-3.0 is planned to include a "Config State Machine", probably dealing with the issue thoroughly. We have no further information about this bullet and would appreciate any additional info. We would like to start investing in making TC operations more streamline, robust and user-friendly. The main use-cases we would like to address at this point are: 1. Assign servers to a Delivery-Service. For this operation, the configuration must first be applied to the added traffic servers, propagate, and only then applied to the traffic-router. 2. Remove servers assignment to a Delivery-Service. For this operation, the configuration must first be applied to the traffic-router, and only then to the traffic-servers. 3. Add a new delivery service. This is practically a private case of servers assignment to a delivery-service. 4. Delete a delivery service. This is practically a private case of servers assignment removal from a delivery-service. 5. Update settings that must be applied together on the traffic servers and the router. We would like to simplify the procedure, allowing the deployment of new configuration in a single operation, instead of doing it step by step. One solution can be based on the insight that deploying such configuration changes may be done by initially updating the traffic server with added functionality (e.g remap-rule), then updating the router, and lastly, removing old functionality from the traffic servers. Such a solution can be orchestrated by traffic-ops, probably without complicating other components. Other solutions may provide more flexibility, but would probably involve adding complexity to other components such as traffic-router. We would be glad to hear the community's thoughts on the matter, so we can take this further. Thanks, Nir
