[GitHub] [trafficserver] mlibbey commented on issue #8557: Dynamic origin server selection with REST API in ATS

[GitBox <gi...@apache.org>]

mlibbey commented on issue #8557:
URL: https://github.com/apache/trafficserver/issues/8557#issuecomment-996030060


   I don't think there is an opt of the box feature that does exactly this.
   
   - it might be possible to do a lua plugin script. Like fetch the api (ts.fetch?), parse the json, and then set the IP (like ts.server_request.server_addr.set_addr?)
   - I believe the concept would fit into a parent selection strategy plugin. https://docs.trafficserver.apache.org/admin-guide/files/strategies.yaml.en.html is for strategies, but, I'm struggling to find docs around that.
   - different track... either strategy.yaml/parent.config can do various selection strategies -- round robin; consistent hash; etc. Could imagine requirement tweaks to have the app periodically update one of those files as appropriate. (but, couldn't do that on a per-request basis)
   - or https://docs.trafficserver.apache.org/admin-guide/files/records.config.en.html#proxy-config-srv-enabled ... makes ATS us SRV records instead of A/AAAA, which then allows for weighted round robin across the records.
   - or have the app act as a small DNS server (instead of json). Have it set the record's ttl to 0 sec, and ATS's resolv.conf to use it.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org