15:01:32 <smooge> #startmeeting Infrastructure (2019-01-17)
15:01:32 <zodbot> Meeting started Thu Jan 17 15:01:32 2019 UTC.
15:01:32 <zodbot> This meeting is logged and archived in a public location.
15:01:32 <zodbot> The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:32 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:32 <zodbot> The meeting name has been set to 'infrastructure_(2019-01-17)'
15:01:33 <smooge> #meetingname infrastructure
15:01:33 <smooge> #topic aloha
15:01:33 <smooge> #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mkonecny
15:01:33 <zodbot> The meeting name has been set to 'infrastructure'
15:01:33 <zodbot> Current chairs: cverna mkonecny nirik pingou puiterwijk relrod smooge tflink threebean
15:01:38 <smooge> wa1em, meeting time
15:01:42 * cyberworm54 is here
15:01:45 <suanand> hi
15:01:50 <wa1em> smooge, thanks
15:01:55 <wa1em> .hello2 linuxmodder
15:01:56 <zodbot> wa1em: Sorry, but you don't exist
15:02:01 <nirik> morning. oh so morning.
15:02:03 <wa1em> .hello2 linux-modder
15:02:04 <zodbot> wa1em: Sorry, but you don't exist
15:02:14 <wa1em> whatever zodbot :P
15:03:05 <creaked> .hello2
15:03:06 <zodbot> creaked: creaked 'Will Chellman' <creaked@gmail.com>
15:03:15 <mkonecny> .hello2 zlopez
15:03:16 <pingou> ó/
15:03:16 <zodbot> mkonecny: Sorry, but you don't exist
15:03:24 <mkonecny> .hello zlopez
15:03:26 <zodbot> mkonecny: zlopez 'Michal Konečný' <michal.konecny@packetseekers.eu>
15:03:37 <wa1em> .hello2
15:03:38 <zodbot> wa1em: Sorry, but you don't exist
15:03:45 <smooge> wa1em, .hello2 doesn't take an argument
15:03:53 <smooge> .hello2
15:03:54 <zodbot> smooge: smooge 'Stephen J Smoogen' <smooge@gmail.com>
15:04:04 <linuxmodder> .hello2
15:04:05 <zodbot> linuxmodder: linuxmodder 'Corey W Sheldon' <sheldon.corey@gmail.com>
15:04:10 * cverna waves
15:04:12 <linuxmodder> there we go ... ggesh
15:04:21 <cyberworm54> :)
15:04:38 <smooge> for all the amount of time people take to get that working.. people could just say smooge: smooge
15:05:02 <linuxmodder> okay nerd :P
15:05:35 * smooge is at -9 Humour Points at the moment
15:05:45 <nirik> but we want to make the bots dance to our will....
15:05:56 <linuxmodder> lol
15:05:57 <mkonecny> smooge: I thought minimum is 1
15:06:14 <linuxmodder> he found a bug that allows - karma :P
15:06:42 <smooge> I use the advanced rules where your humour can go to 0 and you are extremely grumpy.. at -10 you go OP
15:06:51 <smooge> #topic New folks introductions
15:06:51 <smooge> #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves
15:06:51 <smooge> #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
15:08:37 <smooge> ok quiet week
15:09:25 <smooge> #topic announcements and information
15:09:25 <smooge> #info Anitya (release-monitoring.org) 0.14.0 deployed on production
15:09:25 <smooge> #info devconf is happening from 2019-01-25 -> 2019-01-27
15:09:25 <smooge> #info outage at PHX2 colocation around 2019-02-02
15:09:25 <smooge> #info cleanup of sysadmin groups
15:09:50 <cverna> I think there is a new version of bodhi in stg
15:10:13 <mkonecny> #info Anitya 0.14.1 was released and deployed on staging - should fix few issues
15:10:46 <cverna> #info bodhi 3.13.0 beta has been deployed to staging: https://bodhi.stg.fedoraproject.org/docs/user/release_notes.html
15:10:50 <cverna> bowlofeggs: ^^
15:11:12 <bowlofeggs> .hello2
15:11:13 <zodbot> bowlofeggs: bowlofeggs 'Randy Barlow' <rbarlow@redhat.com>
15:11:14 <bowlofeggs> (sorry i'm late)
15:11:22 <bowlofeggs> and thanks for adding that to the notes - i'd forgotten!
15:12:12 <cverna> just wanted to make sure I did not say something wrong :)
15:12:23 <bowlofeggs> yeah it's correct
15:12:32 <bowlofeggs> i'm hoping to try out fedora_messaging with it
15:12:38 <bowlofeggs> it's currently still deployed to use fedmsg though
15:12:47 <bowlofeggs> i need to read up on how to get it to use the new lib
15:12:57 <bowlofeggs> i imagine there are configuration thingies to do
15:13:07 <bowlofeggs> but supposedly that version should work with it
15:13:29 <bowlofeggs> this miiiight be the last feature release before bodhi 4
15:13:31 <bowlofeggs> i'm not sure
15:13:36 <bowlofeggs> bodhi 4 has a long way to go
15:13:57 <mkonecny> bowlofeggs: Look at https://github.com/release-monitoring/anitya/pull/570 it's written by jcline
15:14:11 <bowlofeggs> and so i'm weighing the options of holding features for a long time vs. backporting patches (which will likely become increasingly divergent as bodhi 4 keeps removing and chaging thigns)
15:14:53 <bowlofeggs> mkonecny: yeah i have a similar patch in 3.13.0, but i need to read more about how to configure the deployed bodhi to actually use it
15:15:01 <bowlofeggs> bodhi 3.13.0 supports both fedmsg and fedora_messaging
15:17:27 <smooge> sounds ogod. anything else?
15:17:28 <mkonecny> bowloffegs: In Anitya, there is legacy_messaging option in configuration and you also need config for fedora-messaging
15:20:55 <smooge> #topic Oncall
15:20:55 <smooge> #info relrod is on call from 2019-01-10 -> 2019-01-17
15:20:55 <smooge> #info ??? is on call from 2019-01-17 -> 2019-01-24
15:20:55 <smooge> #info ??? is on call from 2019-01-24 -> 2019-01-31
15:20:56 <smooge> #info Summary of last week: (from relrod )
15:22:25 <nirik> we kinda timed that poorly... as everyone except relrod is going to be traveling this coming week. ;) oh well.
15:22:46 <smooge> and relrod has classes
15:23:07 <nirik> true.
15:23:11 <bowlofeggs> it seems like it would be hard for anyone to be on call next week
15:23:16 <nirik> well, I can take it...
15:23:16 <smooge> I am thinking we will just change oncall to 'No one is oncall this week. Please open a ticket'
15:23:22 <pingou> +1
15:23:22 <bowlofeggs> unless relrod can do it twice in a row?
15:23:26 <nirik> and people can open tickets... yeah
15:23:31 <abompard> .hello2
15:23:31 <bowlofeggs> smooge: +1
15:23:31 <chris787> O/
15:23:31 <zodbot> abompard: abompard 'Aurelien Bompard' <aurelien@bompard.org>
15:23:34 <abompard> surry I'm late
15:23:42 <pingou> thrice even, on the 24th DevConf hasn't even started
15:23:46 <bowlofeggs> abompard can be on call, as punishment for being late
15:23:56 <pingou> he's also traveling ;-)
15:24:01 <bowlofeggs> pingou: oh yeah, that's true
15:24:07 <bowlofeggs> both weeks are gonna be tough to cover
15:24:08 <abompard> I'm totally able to answer "Please open a ticket" to everybody.
15:24:31 <bowlofeggs> yeah let's just put a message about how nobody is oncall and make infra turn to mad max
15:24:33 <bowlofeggs> anarchy!
15:24:43 <linuxmodder> I'm +1 on the open tricket verbage tbh
15:24:49 <bowlofeggs> whoever has the most oil wins
15:24:52 <mkonecny> I'm +1 for mad Max
15:24:55 <relrod_cld> Ok just got home from class (haven't gone inside yet)
15:25:08 <relrod_cld> I can be on call for the next few weeks in between classes. That's fine
15:25:24 <smooge> zodbot: alias add oncall "echo No one is oncall this week and most people are afk. Do not expect pings to be seen and open a ticket at https://pagure.io/fedora-infrastructure/issues"
15:25:24 <zodbot> smooge: Kneel before zod!
15:25:52 <relrod_cld> smooge: I'll take it. I'll just put a note that responses might be delayed.
15:26:26 <pingou> smooge++
15:26:29 <pingou> zod++
15:26:44 <smooge> relrod, I would prefer this. You can still look for oncalls over time but I want people to have appropriate expectations
15:27:05 <smooge> versus people pinging you at 3am or 9pm
15:27:15 <smooge> or 2 minutes before an exam
15:27:57 <linuxmodder> smooge,  something to be said for that last one especially
15:28:09 <relrod> It should be fine. But either way.
15:28:23 <smooge> #info no-one is on call from 2019-01-17 -> 2019-01-24 relrod half-duty
15:28:24 <smooge> #info no-one is on call from 2019-01-24 -> 2019-01-31 relrod half duty
15:28:39 <relrod> I'm happy to take it, and just add in a note that says "relrod on call but might be available intermittently; file ticket if no response"
15:29:02 <smooge> #topic Monitoring discussion
15:29:02 <smooge> #info https://nagios.fedoraproject.org/nagios
15:29:02 <smooge> #info Go over existing out items and fix
15:31:03 <nirik> there's a few machines with dropped disks...
15:31:22 <relrod> I am calling them in as we speak.
15:31:35 <smooge> yay!
15:31:36 <nirik> proxy03 needs redoing...
15:31:49 <smooge> I need to move proxy03 over to virthost-cc-rdu02
15:33:52 <smooge> #topic Tickets discussion
15:33:52 <smooge> #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
15:35:45 <smooge> There are curently 109 open tickets
15:36:49 <suanand> smooge: had a request for deploying transtats in Prod.. (when it will be feasible?)
15:36:56 <suanand> .ticket 6459
15:36:58 <zodbot> suanand: Issue #6459: [RFR] transtats - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/6459
15:37:57 <smooge> hmm I don't know. it won't be this week and probably not next week
15:38:08 <suanand> feb first week ?
15:38:33 <nirik> I would think it shouldn't be too hard to roll out in prod
15:38:41 <suanand> or should we wait to finalize on a date?
15:38:53 <suanand> nirik: I agree. thanks!
15:40:34 <smooge> nirik, it probably isn't.. I just have a PILE of things I need to do today/tomorrow and next week is meetings
15:40:52 <smooge> suanand, how about 2019-01-30
15:41:22 <suanand> smooge: I'm so sorry - I m on PTO.. the last week of Jan
15:42:16 <suanand> can we look at it on 4th or 5th of feb?
15:42:34 <smooge> 2019-02-05
15:42:36 <smooge> sounds good
15:42:41 <suanand> sure, time?
15:43:10 <suanand> 1700 UTC ?
15:43:19 <smooge> it is 10:42 my time so no earlier than 15:00 UTC
15:43:20 <suanand> smooge: no resource change..
15:43:59 <suanand> let's fix 1700 UTC on 2019-02-05
15:44:06 <suanand> should I update ticket?
15:45:02 <linuxmodder> smooge,  suanand if you both have no issue with this I'd love to 'shadow' in a workday sense to get back into that realm
15:46:11 <smooge> suanand, yes. I think I set up an invite for you also.
15:46:20 <smooge> linuxmodder, it shouldn't be a problem
15:46:23 <smooge> #topic Apprentice Open office minutes
15:46:24 <smooge> #info A time where apprentices may ask for help or look at problems.
15:46:27 <suanand> You're welcome (but let's have smooge, nirik and puiterwijk around)
15:46:44 <suanand> smooge: great thank you :)
15:47:09 <linuxmodder> suanand,  I have no delusions of being the one to push buttons YET, too green to risk that :P
15:47:32 <suanand> linuxmodder, let's do that ... :)
15:49:39 <smooge> #topic Open Floor
15:49:50 <smooge> ok anything for the open floor today?
15:50:20 <linuxmodder> nfm
15:51:10 <smooge> #info THERE WILL BE NO MEETING NEXT WEEK! NEXT MEETING IS 2019-01-31
15:51:28 <pingou> good catch :)
15:51:41 <smooge> yeah oops
15:52:07 <mkonecny> I have a question, is there a way to monitor output from openshift pod. I want to see if there is any fedmsg message going out
15:52:23 <mkonecny> s/\./?/
15:52:45 <nirik> well, you can get the logs with oc logs
15:53:01 <nirik> but if it doesn't log when it sends fedmsgs, that won't help
15:53:07 <mkonecny> nirik: Yes, but I don't see anything in there
15:53:31 <mkonecny> Not any error, but if I look in datagrepper there is nothing
15:53:58 <mkonecny> Only the fedmsg when I trigger them manually
15:55:01 <mkonecny> It's possible that staging datagrepper isn't catching this topic?
15:55:45 <nirik> it should be catching everything I would think
15:55:59 <smooge> ok can we move this to #fedora-admin?
15:56:15 <mkonecny> Ok
15:56:28 <smooge> or noc? I think its going to need more hands on than meeting time
15:56:29 <smooge> thanks
15:56:50 <mkonecny> Yes, I have nothing against it
15:57:05 <smooge> Thank you all for coming this week. I will hopefully see many of you next week in CZ
15:57:10 <smooge> #endmeeting