[10:02:40] <godog>	 hi, I'm reviewing the hosts for codfw row A in T327925 and xhgui is listed there, what do you reckon is the easiest/best action to take ?
[10:02:40] <stashbot>	 T327925: codfw row A switches upgrade - https://phabricator.wikimedia.org/T327925
[10:03:03] <godog>	 I'm thinking probably the easiest is to depool the whole performance.w.o from codfw
[10:14:57] <Krinkle>	 godog: ack, xhgui (the server) is a read only viewer for data in m2 mysql cluster that mw writes to, proxied from webperfX003. Depooling it (from ATS?) and using eqiad SGTM
[10:17:56] <godog>	 Krinkle: *nod* yeah I thought performance.w.o was active/active but it isn't, in the sense that performance.discovery.wmnet (the vhost that frontend caches talk to) is ever pointed to one host only (webperf1003 atm)
[10:18:00] <godog>	 so yeah we don't have to do anything
[10:19:26] <Krinkle>	 godog: hmm that's weird, I don't think it needs to be
[10:20:29] <Krinkle>	 I mean it's fine to have cold standby given tier 2 and low traffic. But wouldn't mind exercising it active active to avoid surprises
[10:20:58] <Krinkle>	 Perhaps we can try that afterwards, if it's easy to pool into it?
[10:21:41] <godog>	 yeah why not, we have to add performance as a conftool record and do some other things but yeah I've done it before
[10:22:03] * godog files task
[10:22:08] <Krinkle>	 Thanks!
[10:22:15] <godog>	 sure np
[10:25:56] <godog>	 {{done}}