[11:03:04] <gehel>	 lunch!
[11:07:34] <zpapierski>	 ejoseph: I'm back, ping me if you want  to work on plugins
[11:35:38] <dcausse>	 lunch
[11:37:23] <ejoseph>	 zpapierski: i'll be ready in 10mins
[11:51:19] <zpapierski>	 one last thing I need to do and I'm ready as well
[11:52:18] <ejoseph>	 https://code-with-me.jetbrains.com/nK1oG0DdUq9nRcVaUpLXAw#p=IU&fp=77A8BD5467001E5B38035343751D53CDBEF5D03D4812A4A95B41B5A896B7AB95
[14:16:23] <gehel>	 Time to go to hospital, back later
[16:01:26] <Trey314159>	 Office Hours: https://meet.google.com/vgj-bbeb-uyi?authuser=0
[16:10:52] <zpapierski>	 ebernhardson, ejoseph: office hours?
[16:11:08] <zpapierski>	 not very lively today, though
[20:01:57] <ebernhardson>	 alrighty, now i've got all the motivation to start my day :)
[20:02:21] <gehel>	 ebernhardson: I can sympathize
[20:02:44] <gehel>	 if anyone want to jump in a meet to debrief, I'll be around
[20:02:49] <gehel>	 but need a short break first
[20:05:30] <dcausse>	 I'll have to brew more beer than anticipated :/
[20:05:39] <dcausse>	 dinner
[20:18:01] <gehel>	 if anyone wants to debrief the Tech-All meeting, I'll be in meet.google.com/qtg-yyhy-jns for at least the next 15'
[20:18:32] <gehel>	 and feel free to ping me any other time as needed
[21:20:56] <ebernhardson>	 so now my memory is failing me, in OPTIONS_PER_ENV for flink-job.py, which submits the flink jobs, I think we weren't going to have `wdqs-staging`, `wcqs-staging`, ..., but i forget what it should be instead?
[21:31:29] <dcausse>	 ebernhardson: I think that map could either explode by including the job name ("WDQS Streaming Updater"/"WCQS Streaming Updater") in the key, e.g. "staging WCQS Streaming Updater" built using "$env $jobName". Or building a separate map of options (e.g. OPTIONS_PER_JOB) based on the job name with wcqs/wdqs specific options that you would merge with env specific options. 
[21:32:27] <dcausse>	 into other words there won't be a k8s namespace for wcqs
[21:33:27] <dcausse>	 what will vary is the --job-name option, the --env one will remain the same
[21:33:57] <ebernhardson>	 right, the k8s level will still have staging/eqiad/codfw and this has to fit there.  So we would hardcode the job names in some cookbook or whatever? Seems tedious to make them so exact
[21:34:51] <dcausse>	 the script ensures that no job with the same name can be scheduled twice on the same name
[21:35:32] <dcausse>	 I'm fine hardcoding the job name unless you think we can use something different
[21:35:52] <ebernhardson>	 ok, i can't think of anything else. Will setup to vary on the job name and require it to come from the predefined list
[21:36:40] <dcausse>	 it's already kind of hardcoded already in https://grafana-rw.wikimedia.org/d/fdU5Zx-Mk/wdqs-streaming-updater?orgId=1 :/
[21:37:06] <dcausse>	 for the "flink processing latency" series
[21:37:34] <ebernhardson>	 ok, well just continuing the trend then ;)
[21:37:44] <dcausse>	 yes :)
[23:18:28] <ebernhardson>	 ragesoss: wanted to check in on lvs parts, anything i can help with?
[23:20:46] <ragesoss>	 did you mean someone else, ebernhardson?
[23:23:15] <ebernhardson>	 ragesoss: doh, yes. sorry!
[23:23:24] <ebernhardson>	 ryankemper: wanted to check in on lvs parts, anything i can help with?
[23:40:05] <ryankemper>	 ebernhardson: I checked with traffic last night re pybal restarts and they weren’t aware of anything going on that would prevent them, so I’m gonna go ahead and move wcqs into lvs_setup in 30’ or so
[23:53:01] <ebernhardson>	 kk