15:00:40 #startmeeting Infrastructure (2019-12-05) 15:00:40 Meeting started Thu Dec 5 15:00:40 2019 UTC. 15:00:40 This meeting is logged and archived in a public location. 15:00:40 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:40 The meeting name has been set to 'infrastructure_(2019-12-05)' 15:00:41 #meetingname infrastructure 15:00:41 The meeting name has been set to 'infrastructure' 15:00:41 #chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs 15:00:41 Current chairs: abompard bowlofeggs cverna mizdebsk mkonecny nirik pingou relrod smooge tflink 15:00:41 #info Agenda is at: https://board.net/p/fedora-infra 15:00:41 #topic aloha 15:00:48 * pingou says: hi 15:00:53 morning 15:00:54 hello 15:01:29 morning all 15:01:43 nirik, will be a bit late 15:01:49 #topic Next chair 15:01:49 #info magic eight ball says: 15:01:49 #info 2019-12-05 -smooge 15:01:49 #info 2019-12-12 -nirik 15:01:49 #info 2019-12-19 - ?? 15:01:50 #info 2019-12-26 - NO MEETING 15:01:52 #info 2020-01-02 - NO MEETING 15:01:54 #info 2020-01-09 - ?? 15:02:39 * cverna waves 15:03:10 * relrod waves 15:03:10 .hello2 15:03:11 lgriffin: lgriffin 'Leigh Griffin' 15:03:28 Howdy all 15:03:30 we need someone to do the 12-19 meeting 15:03:33 I will be out then 15:03:49 i can do it 15:04:52 mizdebsk++ 15:05:15 no cookies :( 15:05:30 mizdebsk++ thanks 15:05:30 smooge: Karma for mizdebsk changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:05:50 #topic New folks introductions 15:05:50 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 15:05:50 #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted 15:06:09 .hello zlopez 15:06:10 mkonecny: zlopez 'Michal Konečný' 15:06:39 do we have any new people? if not we can move on 15:07:10 #topic announcements and information 15:07:11 #info No meetings coming up due to various holidays. Many Fedora people will be on time-off til parts of january 15:07:11 #info work in progress in improving the script syncing assignee and CC from dist-git to bugzilla 15:07:11 #info work done on improving the error messages sent by fedscm-admin when processing scm requests 15:07:11 #info builder reinstalls/uprgades to f31 continuing. Should be done before holiday break - kevin 15:07:12 #info ops folks are trying a 30min ticket triage every day at 19UTC in #fedora-admin 15:07:57 morning 15:10:18 any other announcements for this week? 15:12:58 #topic Oncall 15:12:58 #info https://fedoraproject.org/wiki/Infrastructure/Oncall 15:12:58 #info smooge is on call 2019-11-28->2019-12-05 15:12:58 #info kevin is oncall 2019-12-05 -> 2019-12-12 15:12:58 ??? is oncall 2019-12-12 -> 2019-12-19 15:12:59 NOONE is oncall 2019-12-19 -> 2020-01-02 15:13:01 ??? is oncall 2019-01-02 -> 2019-01-09 15:13:33 .takoncallus 15:13:38 .takeoncallus 15:13:49 #info On-call summary: mirrorlist outages still happening.. most other pings have been on 'do my ticket' tpes 15:13:49 .oncall 15:13:49 smooge is oncall. My normal hours are 13:00 UTC to 21:00 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:13:51 never remember the right one. ;) 15:13:59 nirik: it's on the board 15:14:09 .oncalltakeus 15:14:09 pingou: Error: You don't have the alias.add capability. If you think that you should have this capability, be sure that you are identified before trying again. The 'whoami' command can tell you if you're identified. 15:14:09 .oncalltakeus 15:14:20 .oncalltakeus 15:14:20 nirik: Kneel before zod! 15:14:25 .oncall 15:14:25 nirik is oncall. My normal hours are 13:00 UTC to 21:00 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:14:29 working :) 15:14:36 yeah 15:14:46 so who volunteers to take over next week? 15:15:42 I can take next week 15:16:34 in december i can take any week too 15:17:21 cverna said it first so I will put him there 15:17:51 #info cverna is oncall 2019-12-12 -> 2019-12-19 15:17:51 #info NOONE is oncall 2019-12-19 -> 2020-01-02 15:18:09 #topic Monitoring discussion 15:18:09 #info https://nagios.fedoraproject.org/nagios 15:18:09 #info Go over existing out items and fix 15:19:35 * nirik is having firefox issues. ;( 15:19:42 osbs-master01.stg.phx2.fedoraproject.org is up now should I restart the nrpe service ? 15:19:49 proxy11 is due to a problem with podman not killing processes cleanly so one will keep running locking port 81 or 82 until kill -9 is send 15:20:02 cverna, check the firewall allows is 15:20:11 I am not sure at all why buildvmhost-aarch64-01 is showing down. The machine is up and seems fine. 15:20:34 cverna, openshift things do weird things with firewalls so it may not allow it 15:21:12 smooge: oh right, checking that now 15:23:21 ok, that was firewall, I think I fixed it. 15:23:41 the swap low thing smooge filed a bug on 15:23:43 any other items for this or do we need to go to the next topic? 15:23:57 yeah.. it is an interesting kernel bug 15:24:13 odcs Check for fedmsg-hub-3 proc just needs removed... 15:24:19 that one moved to fedora-messaging I think? 15:24:47 planet I am not sure of, it's updating, but not sending fedmsgs. ;( 15:25:41 is it one where someone set it up for fedora-messaging but because it isn't in PHX2 amqp doesn't work? 15:27:02 ok next itme 15:27:05 #topic Tickets discussion 15:27:05 #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket 15:27:34 no, it's in phx2... 15:27:49 isn't planet on people? 15:28:10 oh yes, I thought you meant odcs 15:30:15 ok for tickets we are doing a daily 30 minute standup in #fedora-admin to go over tickets needing to be itemized and to assign out any tickets so they are getting worked on 15:30:52 #info Fedora CoreOS Team requests 15:30:52 #link https://hackmd.io/5uB7hOJKSjGUt65iLgPnbA#Existing-requests-for-Fedora-Infra 15:33:46 #topic ResultsDB Ownership Going Forward 15:33:46 #link https://pagure.io/fedora-infrastructure/issue/8415 15:34:02 not sure who is running this question 15:34:22 tflink was asking. 15:34:40 I think we need to bring it to the CPE team/applicaations folks... 15:34:47 yep 15:34:48 unless the CI people would take it 15:35:33 either way works for me 15:36:24 I would be -1 for the CPE team :) 15:36:27 we've upgraded the instance to F31 so it'll be OK at least until the move but I think that the HW running that VM is due to be retired 15:36:52 internally it's run on openshift, so moving to this sounds like a good idea 15:36:59 in my mind, resultsdb is more gating than CI so it made sense for the folks doing the gating to be responsible for it. don't know if that's CPE or CI 15:37:06 tflink: do you know who will be taking the lead on this internally? 15:37:36 pingou: the internal deployments have been another group. it was pnt devops at one point 15:37:51 would be nice to piggy back on them 15:37:52 they're the ones who handled the "port" to openshift 15:38:34 I'll take point on this 15:38:48 thanks pingou! 15:39:13 it would be good to decide even if we run it but ci 'owns' it upstream... 15:39:14 tflink: this is as much about the maintenance of the deployed instance as well as development right? 15:39:14 can we approch the Factory 2.0 team since they own greenwave, that might be a logical choice 15:39:37 cverna: might be an option too... yeah. 15:40:34 pingou: at a minimum, it's about the deployed instance. I honestly don't know if jskladan is planning to keep up with development 15:40:34 #topic backlog discussion 15:40:34 #info go over our backlog and discuss and determine priority 15:40:34 #link https://pagure.io/fedora-infrastructure/issue/8178 15:40:34 #info topic: provision new aarch64 builders 15:40:49 I'll reach out to Aleksandra, Ralph and Luiz and see with them 15:41:39 I'll ping Josef for the dev question 15:41:48 pingou: thanks 15:41:51 pingou++ 15:41:51 tflink: Karma for pingou changed to 8 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:42:29 so we have 7 aarch64 vmhosts going. We are waiting for cables ot bring up replacements in qa and cloud 15:43:01 yeah, I am going to move more buildvm's to them in the coming days 15:43:16 any other backlog for today? 15:43:27 this has taken a lot longer than we hoped... but hardware... ;( 15:43:39 #topic Community Fires Team [pingou?] 15:45:12 ok i am not sure if I am on a netsplit or nothing to be said.. so I am going to move to openfloor 15:45:25 #topic Open Floor 15:45:39 ok if I am netsplit.. zodbot is still with me 15:45:40 * tflink has one hopefully quick thing for openfloor 15:45:51 go tflink 15:46:01 smooge: no, you are fine... people are just quiet today. ;) 15:46:03 for https://pagure.io/fedora-infrastructure/issue/8438 I was hoping for some clarification on what you all would prefer 15:46:20 sorry smooge was watching another window for a minute :( 15:46:23 Just one quick note from me, I'm out next week for moving, so if anyone needs anything urgent from me, ping me by tomorrow, otherwise file tickets and assign them to me as needed ;) 15:46:27 tflink: well, I am not sure. ;) 15:46:28 sharing certs, consolidating instances etc. 15:47:08 perhaps someone knows the fedora-messaging setup there and could tell us? 15:47:12 relrod: good luck with the moving 15:47:17 * tflink is asking the folks who are responsible for the ci pipleline jenkins instance what they would prefer as well 15:47:19 if it's not easy to share, happy to issue new ones 15:47:46 I suspect that it comes down to more of that there are different people responsible for the different instances 15:48:55 cverna / pingou ^ any thoughts? 15:49:06 cverna: thanks. I suspect very cramped legs after hours and hours of driving ;) 15:49:11 relrod: yeah, safe travels and hope the move goes well. :) 15:51:21 * cverna checks the ticket 15:51:42 nirik: iirc, we'll still have to regenerate the certs once we've put in place the sending restrictions, right? 15:52:09 if so, with the current setup it doesn't make much difference 15:52:18 and we can just take the path of least resistance 15:52:38 AFAIK, the two instances will be sending out messages on pretty much the same topics 15:52:42 uh, I have no idea on that 15:53:20 ok I think several of us have 0 idea on amqp needs and when things need to be regenerated etc 15:54:17 I expect we will have to expire the current ones and generate new ones 15:54:54 that will be a pain. 15:55:21 ok, so I guess lets just go ahead and issue certs for this now and consolidate later if we can. 15:55:24 a bit, but we don't have so many out of our hands 15:55:50 ok coming up to the top of the hour. can we move the amqp needs to #fedora-admin? 15:56:06 or we can just issue certs and close this :) 15:56:09 alright then 15:56:28 anything else for today? 15:56:36 thank you all for coming this week 15:57:09 #endmeeting