Recirculating this topic as well. Ryan
On Fri, Sep 1, 2017 at 4:12 PM, Durfey, Ryan <[email protected]<mailto:[email protected]>> wrote: Opening a new thread on Generic Configuration as discussed in our meeting. I drew a sketch (probably inaccurate) to prompt conversation. If you can’t see it in the email there is a link to the wiki below where you can see it. Please keep responses in the email thread (vs. wiki). I will summarize once we conclude debate. Ryan Generic_Configuration https://cwiki.apache.org/confluence/display/TC/Configuration+Management - There is a desire to move to a generic configuration that is stored by Traffic Ops DB that could be interpreted separately for each CDN component or cache type - We are not exactly sure where interpretation gets done but probably in a separate Traffic Ops module before it is pushed out to the component - It could exist on the component, however in the case of edge caches it might not be efficient to operate an interpreter under heavy loads - It would be the responsibility of the Cache or Component development team to write the interpreter of the generic config file - So if you want to use Varnish caches you would be responsible for writing a Varnish interpreter for the generic configuration file - One issue we might experience is that some cache engines may require new configuration parameters that don't exist in prior engines. - In this case we would need to add something upstream. Other engines would need to ignore this parameter, which is probably not a problem so long as we go in knowing they can ignore unrecognized parameters without crashing. [image: https://cwiki.apache.org/confluence/download/attachments/69405446/image2017-9-1%2013%3A46%3A3.png?version=1&modificationDate=1504295163661&api=v2] *Ryan Durfey* Sr. Product Manager - CDN | Comcast Technology Solutions 1899 Wynkoop Ste. 550 | Denver, CO 80202 M | 303-524-5099 <(303)%20524-5099> [email protected]<mailto:[email protected]> CDN Support (24x7): 866-405-2993 <(866)%20405-2993> or [email protected]<mailto:[email protected]>
