18:01:36 #startmeeting Fedora Infrastructure Ops Daily Standup Meeting 18:01:36 Meeting started Tue Jul 5 18:01:36 2022 UTC. 18:01:36 This meeting is logged and archived in a public location. 18:01:36 The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:01:36 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:01:36 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:36 #chair mboddu nirik mobrien nb 18:01:36 Current chairs: mboddu mobrien nb nirik 18:01:36 #meetingname fedora_infrastructure_ops_daily_standup_meeting 18:01:36 #info meeting is 30 minutes MAX. At the end of 30, its stops 18:01:36 #info agenda is at https://board.net/p/fedora-infra-daily 18:01:36 The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting' 18:01:37 #info reminder: speak up if you want to work on a ticket! 18:01:50 anyone around today for a standup? 18:02:04 phsmoura: Error: Can't start another meeting, one is in progress. 18:02:05 yo 18:02:09 .hi 18:02:11 aheath1992: aheath1992 'Andrew Heath' 18:02:22 #chair nirik mobrien aheath1992 smooge 18:02:23 phsmoura: sorry, already started one... you can take over if you like tho. ;) 18:02:31 hello 18:02:48 oh sorry now I saw it 18:03:46 go ahead 18:04:05 #topic Tickets needing review 18:04:05 #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1 18:04:27 .ticket 10800 18:04:29 nirik: Issue #10800: Request for an r-maint-sig group - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10800 18:04:36 low low ops? 18:05:07 +1 18:05:36 thats it for infra... a few releng ones: 18:05:48 .releng 10872 18:05:49 nirik: Issue #10872: F37: Self contained change: Officially suport Raspberry Pi 4 - releng - Pagure.io - https://pagure.io/releng/issue/10872 18:06:03 I think we can just close this one, I don't think there's any impact? 18:06:26 That one, I saw it and seems no releng action is need 18:06:42 +1 18:07:14 .releng 10874 18:07:15 nirik: Issue #10874: rust-print_bytes repo has wrong ownership - releng - Pagure.io - https://pagure.io/releng/issue/10874 18:07:22 I can delete that branch I guess... 18:09:43 ok, done and I will just close it 18:10:14 .releng 10875 18:10:15 nirik: Issue #10875: zlib downgraded in rawhide 1.2.12-2.fc37 -> 1.2.11-31.fc36 - releng - Pagure.io - https://pagure.io/releng/issue/10875 18:10:29 this was deliberate, so I guess we can close it? 18:11:17 thats it for tickets. 18:11:22 theres another one 18:11:37 oh, did I miss one? 18:11:46 .releng 10870 18:11:47 phsmoura: Issue #10870: F37 Self contained change: LXQt 1.1 - no releng actions needed - releng - Pagure.io - https://pagure.io/releng/issue/10870 18:12:07 like the 1st one 18:12:32 ah right, yeah, close and thank them for the ticket. 18:12:38 you got it? or want me to? 18:12:58 sure, I can post a comment there and close it 18:13:24 thanks 18:13:34 #topic Upcoming plans / discussion 18:13:58 I'm hoping to start on builder refreshes this week... but been trying to just catch up this morning. ;) 18:14:09 i have a question about 18:14:12 aheath1992: you had questions on splunk? 18:14:16 .ticket 10120 18:14:17 aheath1992: Issue #10120: Investigate forwarding centralised logs to splunk - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10120 18:14:32 yes, where are we in the state of this project? 18:15:08 yeah, good question. :) 18:15:36 So, I asked about this, was told we should first get us access then we can look at getting the data input... but not sure what happened. Let me look... 18:15:58 So i have access as part of RHIT 18:16:17 and work closely with the team that manages Splunk 18:16:32 ah ha. cool! 18:16:40 I have an internal ticket I think. 18:17:32 So I have no problem with working and getting the green light for us to do this and get a Splunk role setup to ingest logs 18:17:48 so, they added mobrien and us to have access to query it... then said "Then we can move on to ingesting data for you to the splunk platform once you figure out what you would like to see. Please update the ticket with your findings." 18:18:01 but then the ticket was closed... 18:18:13 so, I guess we should restart the conversation? 18:18:30 we already send all our logs to a central log host (log01) via rsyslog 18:18:53 so I would hope it would just be something like having log01 send also to some ingestion point for splunk? 18:19:11 yep and I believe the splunk team has some ansible automation for setting up systems 18:19:55 yeah, then of course, we should: make things log less junk (kojid is really bad about this, but I am sure there are others) and generate some nice reports for things that stand out 18:20:15 So who all has access on the Fedora side I can start an email thread with what we want to see monitored and get the correct tickets added 18:20:19 we used to have epylog to do this, but alas... it never made the jump to python3. ;( 18:21:04 You can include me and mobrien and phsmoura on internal threads. 18:21:35 and thanks for driving this! :) 18:21:44 Ack, sounds good, no problem 18:22:11 That's all i had 18:22:20 cool. 18:22:25 Anything else today? 18:22:34 nothing from me 18:23:05 ok, thanks for coming everyone! 18:23:08 #endmeeting