The use case behind this question probably deserves a longer dev@ email. I will oversimplify: we are extending TC to support multiple IPv4 (or multiple IPv6) addresses per edge cache (across 1 or more NICs).
Assume all addresses are reachable from the TM. —Eric > On Mar 28, 2018, at 11:37 AM, Robert Butts <robert.o.bu...@gmail.com> wrote: > > When you say different interfaces, do you mean IPv4 versus IPv6? Or > something else? > > If you mean IPv4 vs IPv6, we have a PR for that from Dylan Volz > https://github.com/apache/incubator-trafficcontrol/pull/1627 > > I'm hoping to get to it early next week, just haven't found the time to > review and test it yet. > > Or did you mean something else by "interface"? Linux network interfaces? > Ports? > > > On Wed, Mar 28, 2018 at 12:02 AM, Neil Hao (nbaoping) <nbaop...@cisco.com> > wrote: > >> Hi, >> >> Currently, we poll exact one URL request to each cache server for one >> interface, but now we’d like to add multiple interfaces support, therefore, >> we need multiple requests to query each interface of the cache server, I >> check the code of Traffic Monitor, it seems we don’t support this kind of >> polling, right? >> >> I figure out different ways to support this: >> 1) The first way: change the ‘Urls’ field in the HttpPollerConfig from >> ‘map[string]PollConfig’ to ‘map[string][]PollConfig’, so that we can have >> multiple polling config to query the multiple interfaces info. >> >> 2) The second way: Change the ‘URL’ field in the PollConfig from ‘string’ >> to ‘[]string’. >> >> No matter which way, it seems it will bring a little big change to the >> current polling model. I’m not sure if I’m on the right direction, would >> you guys have suggestions for this? >> >> Thanks, >> Neil >>
