[00:26:56] 10serviceops, 10Operations, 10Performance-Team, 10Patch-For-Review, 10Sustainability (Incident Prevention): Reduce read pressure on memcached servers by adding a machine-local Memcache instance - https://phabricator.wikimedia.org/T244340 (10Krinkle) [10:43:10] yoyo - we're looking into solving the issue of routing in the API gateway atm and it's looking clear that the Proper way to solve the problem is to route using a control plane rather than config. Would our future xDS system be the right place for storing them in your opinions? We can probably hack a stopgap out of lua and chewing gum for the time being [10:43:31] seems like it's a reasonable idea given that there'll already be lots of info about the services themselves but just wanted to be sure [10:54:42] (erk, apologies for silent friday question :)) [11:04:11] <_joe_> hnowlan: oh no prob :P [11:04:30] <_joe_> I assume silent friday means async communications, but I'm happy to talk you through this [11:05:00] <_joe_> I'm not sure how an XDS would remove the need for lua :) [11:05:28] <_joe_> but to be clear, I hope to work on xDS next quarter, or to drive that work :) [12:28:45] not remove it per se but at least simplify our routing logic. The thing that's really messing me up is the fact that we can't dynamically change the host header easily without all kinds of gross hacks *or* lots of extremely explicit config per-vhost [12:29:43] both of which the Envoy looks make it look like are the Wrong Way https://www.envoyproxy.io/learn/routing-configuration [12:46:09] <_joe_> so what I did is template the hell out of the config, for now [12:50:36] yeah that's what I have kinda hacked together. Only thing is unless we do some kind of semi-smart setting of the host header, we're gonna end up with config entries for every site+language combo [12:51:09] one lazy option would be to simply do the management on the appserver level but that kinda completely defeats the point of having routing on the gateway at all [13:29:10] <_joe_> uhm I remembered that routing allowed pattern matching [13:29:15] <_joe_> was I wrong? [13:42:37] it does, and path rewriting is very easy. but rewriting hosts is quite awkward