15:00:39 #startmeeting Infrastructure (2020-01-30) 15:00:39 Meeting started Thu Jan 30 15:00:39 2020 UTC. 15:00:39 This meeting is logged and archived in a public location. 15:00:39 The chair is cverna. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:39 The meeting name has been set to 'infrastructure_(2020-01-30)' 15:00:39 #meetingname infrastructure 15:00:39 The meeting name has been set to 'infrastructure' 15:00:39 #chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs 15:00:39 Current chairs: abompard bowlofeggs cverna mizdebsk mkonecny nirik pingou relrod smooge tflink 15:00:39 #info Agenda is at: https://board.net/p/fedora-infra 15:00:39 #topic aloha 15:00:47 morning 15:00:48 .hello zlopez 15:00:49 mkonecny: zlopez 'Michal Konečný' 15:00:49 .hello nphilipp 15:00:52 nils: nphilipp 'Nils Philippsen' 15:00:59 hello all 15:02:07 #topic Next chair 15:02:07 #info magic eight ball says: 15:02:08 #info 2020-02-06 - mkonecny 15:02:08 #info 2020-02-13 - ???? 15:02:33 any volunteers for the 02-13 ? 15:03:07 morning 15:03:21 smooge: o/ 15:03:43 ok we can find someone next week :) 15:04:00 #topic New folks introductions 15:04:00 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 15:04:00 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 15:04:16 any new people around ? 15:05:00 i believe there was an introduction on list earlier 15:05:09 but not sure.. been stuck in meetings 15:05:18 I saw one reply to agenda 15:05:57 ok we can reply on the list then :), moving to next topic 15:06:14 #topic announcements and information 15:06:14 #info ops folks are trying a 30min ticket triage every day at 19UTC in #fedora-admin 15:06:14 #info the following people will be AFK for FOSDEM: pingou, mboddu 15:06:14 #info https://xkcd.com/2261/ 15:06:14 #info most of staff has been in Brno at DevConf 15:06:50 * cverna thinks that we should have an xkcd every week :) 15:07:48 Nice idea, but I think it will be better on Open Floor :-) 15:08:01 .hello2 15:08:02 bowlofeggs: bowlofeggs 'Randy Barlow' 15:08:04 any other informations that we would like to share ? 15:08:10 bowlofeggs: o/ 15:08:56 ok moving on 15:09:02 #topic Oncall 15:09:02 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 15:09:02 #info cverna is oncall 2020-01-23 -> 2020-01-30 15:09:02 #info bowlofeggs is oncall 2020-01-30 -> 2020-02-06 15:09:14 #info ???? is oncall 2020-02-06 -> 2020-02-13 15:09:31 put me down for that ??? 15:09:39 ok thanks smooge 15:09:53 i will probably run the meeting also on the 13th 15:10:04 sure 15:10:06 i find that makes for a good bookend 15:10:23 #info Summary of last week: (from current oncall ) 15:10:42 .oncall 15:10:42 cverna is oncall. My normal hours are 0700 UTC to 1600 UTC Monday through Friday. If I do not answer or it is outside those hours, please file a ticket (https://pagure.io/fedora-infrastructure/issues) 15:10:54 huh who was it last week? 15:11:05 It was me :) 15:11:18 bowlofeggs is taking over 15:11:22 oh. dur 15:11:42 I saw a few pings last week but people ended up filing tickets which is nice :) 15:12:19 bodhi composes are failing due to a pungi bug, so I am trying to bruteforce it (pungi fails 9 times out of 10 ) 15:12:47 bug is https://pagure.io/pungi/issue/1335 15:13:18 nothing else on my plate, but I was not online much with devconf + training in Brno 15:14:09 .oncalltakeus 15:14:09 bowlofeggs: Kneel before zod! 15:14:29 #topic Monitoring discussion [nirik] 15:14:29 #info https://nagios.fedoraproject.org/nagios 15:14:29 #info Go over existing out items and fix 15:15:20 I don't see anything new in nagios, so I guess we can move on 15:15:25 the only one I don't understand is 15:15:32 busgateway01.phx2.fedoraproject.org Check datanommer for recent fas messages 15:15:55 I think since we moved fas to openshift the fedmsg have been broken 15:16:04 yeah sorry I meant the next one down 15:16:11 but I think that is probably the same 15:16:28 moving on 15:16:29 ha yes I don't now much about planet 15:17:32 #topic ResultsDB Ownership Going Forward 15:17:33 #link https://pagure.io/fedora-infrastructure/issue/8415 (revist post DevConf) 15:18:25 so I think tflink mentioned that the current host of resultsdb are running out of warranty in march 15:18:55 the plan is to deploy it to our Openshift instance 15:19:03 I'm not sure when they're running out of warranty but I believe they were scheduled to be disposed of during the new datacenter move 15:19:40 tflink: ha ok, that gives us a little more time but still :) 15:19:58 yeah, it would be good to get it figured out sooner than later 15:20:57 the current resultsdb machine should be running F31 so EOL won't be a problem for a while yet 15:21:08 tflink: I think we can move on with using our OpenShift instance to run the service, would you be able to do that ? 15:22:06 I've been explicitly told that I'm not supposed to work on infrastructure things any more 15:22:19 whee 15:22:35 I might be able to help with the migration but It's not something I can be responsible for going forward 15:22:42 so is the rrequest that we are supposed to run it/ 15:22:48 ok thanks for making it clear :) 15:22:58 so is the request that we (CPE) are supposed to run and migrate it? 15:23:12 sorry .. using smaller keyboard than usual 15:23:13 I'm just raising the point that it's a critical part of the release process and it needs to move somewhere 15:23:33 I don't care a whole lot who ends up with it, honestly. CPE made the most logical sense to me 15:23:56 smooge: my thoughts is that we are ok to run it, but we are not taking over the development maintenance etc 15:24:04 AFAIK, pnt devops runs the instances inside the firewall 15:24:34 jskladan has said he's fine with keeping up with code maintenance 15:25:12 tflink: would he be ok to be pinged to help look at outage ? 15:25:17 ok running it and maintaining it are very tied together. it is where these sorts of arrangements fall apart 15:25:46 cverna: you'd have to ask him but he's AFK at the moment 15:26:13 i don't know that we should agree to formally admin it without a team discussion 15:26:29 ok I ll update the ticket, and see if we can find an agreement 15:26:34 bowlofeggs: yes 15:26:38 we don't admin it today, correct? we just provide virtualization hosts for VMs, but don't maintain the VMs themselves? 15:26:49 correct 15:26:57 it's part of taskotron so QA has been responsible for it 15:26:59 we don't provide host 15:27:02 do we ? 15:27:08 we provide the host 15:27:20 ah ok, tho it is in the qa network ? 15:27:48 so moving to openshift would be the same, we provide the host 15:28:01 it is on virthost-comm03 and virthost-commo4 15:28:19 who would do the migration into openshift, and who would be responsible for keeping it running there? 15:28:26 same with taskotron 15:28:41 and which openshift 15:28:54 this is a big project which needs to be scoped out and clarified 15:29:09 bowlofeggs: my idea would be is not us 15:29:10 yeah that too - communshift vs… infrashift? what do we call the one bodhi is in? 15:29:15 taskotron is going away, the only bits that will survive will be resultsdb 15:29:47 cverna: that's my leaning as well 15:30:09 although we could help with the migration since we have the knowledge of our setup 15:31:00 I ll update the ticket and let's see how that goes 15:31:01 all I know is that someone needs to take it on - it can't be any RH folk in QA going forward 15:32:27 ok thanks for the info tflink 15:32:39 np 15:32:49 sorry for dumping this in your lap 15:33:27 np :) 15:33:49 moving to Open Floor 15:34:02 #topic Open Floor 15:34:11 anything to discuss ? 15:37:04 not me 15:37:09 ok closing the meeting in 3 mins 15:37:13 thanks cverna 15:37:24 thanks for running it cverna 15:37:34 thanks all for coming 15:43:15 #endmeeting