You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2018/07/24 16:37:53 UTC

[GitHub] jhg03a opened a new issue #2578: Change how Traffic Router gets its connectivity to TrafficOps

jhg03a opened a new issue #2578: Change how Traffic Router gets its connectivity to TrafficOps
URL: https://github.com/apache/trafficcontrol/issues/2578
 
 
   Currently we store credentials in the traffic router's traffic_ops.properties file.  I'd like to see us add a new parameter to traffic_ops.properties for the TO API base URL similar to the rest of the TC components store that relationship.
   
   Today, Traffic Router knows where to find TO by reading a field in the CRConfig generated by the url a user was using when performing a snapshot.  That CRConfig is handed off to Traffic Router by way of Traffic Monitor.  By storing the URL in the TR configs directly: you prevent connectivity issues derived from firewalls/dns-name differences at the client/TO relationship, reduce reliance on TM, and appear more consistent with the rest of Traffic Control.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services