Hi All, Planning for a PR on making parent.config's go_direct directive configurable via Delivery service. Right now, go_direct is being hard coded.
Given below is a brief write up on the implementing the same. Assumption: All DS-es sharing an origin server should have same value for go_direct. Implementation: Add a new column 'go_direct' in Deliveryservice table. Its value defaults to False. Delivery service UI (Traffic Ops) and API will be enhanced to support this new column. Conflicts: 1. DS Type HTTP_NO_CACHE and go direct False 2. DS Type HTTP_LIVE and go direct False 3. DS Type DNS_LIVE and go direct False 4. MSO = true and go_direct = true When we have more than 2 DS-es sharing same origin, then updating one particular DS's go_direct value will result in conflict, since all DS-es sharing an origin should have same value for go_direct. Such conflicts should be resolved by deleting and recreating these DS-es with new value for go_direct. This method of deleting and recreating DS-es is preferred over updating all the affected DS-es implicitly. would like your comments on this. Thanks, Vijayanand S
