15:02:31 #startmeeting RELENG (2020-06-23) 15:02:31 Meeting started Tue Jun 23 15:02:31 2020 UTC. 15:02:31 This meeting is logged and archived in a public location. 15:02:31 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:31 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:31 The meeting name has been set to 'releng_(2020-06-23)' 15:02:32 #meetingname releng 15:02:32 The meeting name has been set to 'releng' 15:02:32 #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec 15:02:32 Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz 15:02:32 #topic init process 15:03:07 morning 15:03:25 I started the meeting in #fedora-mktg and thinking why no one has showed up... 15:03:58 ha 15:07:28 it happens :D 15:08:43 Sorry, got a call from parents 15:09:30 #topic #9459 Provide installed_pkgs.log for builds 15:09:38 #link https://pagure.io/releng/issue/9459 15:10:16 I'm not sure what is needed here. 15:10:39 Currently there is a way, but its not straight forward 15:11:11 Can we ask koji folks to fix it? Maybe its a config change or bug as they are going to root.log? 15:11:26 fix what? 15:11:47 perhaps ask the reporter of the koji command gets them what they need? 15:12:10 ah, you mean going to the wrong log? 15:12:48 sure, we could file a koji bug on it and see what they say 15:13:56 Okay 15:14:19 I'm ok either way... see if the reporter is ok, then file koji bug if they arent? 15:14:59 #info mboddu will the ask the reporter if the current non-direct way is okay, if not we will file a ticket with koji 15:16:40 BTW, that koji list-buildroot call now takes 1.5 seconds 15:19:58 nirik: Cool 15:20:11 #topic #9451 rework koji channels / policy 15:20:16 #link https://pagure.io/releng/issue/9451 15:20:32 nirik: Do you think we should look at it now or later? 15:21:27 I think this would be a nice gain for the community 15:21:39 I also would like to freeze the world while the move is ongoing :) 15:21:40 well... 15:21:57 I made the channels as best I could in the new dc... 15:22:18 I think it would be best to wait until we have all the builders back online 15:22:22 does koji-ansible handle the creation of channels? 15:22:51 * pingou checks https://github.com/ktdreyer/koji-ansible 15:22:56 I don't know. ;) we should find that out... and how much of our config we could move to that 15:23:29 yeah, it does... 15:23:31 I'd love that :) 15:23:33 cool! 15:23:38 but we still need to tweak it likely in hub policy 15:24:05 nirik: in the koji_host right? 15:24:22 It seems like its not, you can assign builders to channels but not create one 15:24:22 yeah 15:24:44 "If you specify channels that do not yet exist, Ansible will create them." 15:25:02 Oh, sorry, I missed that 15:25:14 yeah, I did too at first glance. ;) 15:25:17 nice :) 15:25:29 I'll even dare a: fancy! 15:26:41 anyhow, the hard part is the policy stuff in the hub to make sure it sends things to the right channels. 15:26:42 So, going back to the topic, we will wait until the full move is done and then look at this issue? 15:27:04 wait 15:27:14 (post-move) 15:27:29 yeah, lets wait. 15:27:46 it will be more clear what hosts we have and we will have more time to look 15:29:39 #info We will wait until the full DC move is done and we will come back to this issue again. Maybe we will look at using koji-ansible module. 15:31:15 * mboddu looking for the infra dc move hackmd.io 15:32:45 #topic Open Floor 15:32:50 I got couple of topic here 15:33:01 1. DC move update? 15:33:28 nirik: Do you think everything will be setup by Jul 22nd? We got a mass rebuild to run on that date? 15:33:57 well, all builders should be yes, thats the plan. 15:34:36 All the hardware is moved and should be racked by end of day... but we now need to go thru and add things to the right vlans, reinstall, etc. 15:34:56 Yeah, thats my 2nd question 15:35:02 When do you think it will be done? 15:35:05 pri is builders, then bring up redundent vm's (02), then last staging 15:35:06 End of next week? 15:35:12 I am not sure. 15:35:26 it really depends on how much trouble hardware gets us. 15:35:46 Oh, in that case, we never will complete it :P 15:35:57 We always have problems with hardware :D 15:36:04 mboddu: don't be optimistic :D 15:36:08 everyone does. it's just the way it works 15:36:59 haha :) 15:37:31 I have one more update for the end of the meeting 15:37:36 Anybody got anything else? 15:39:47 nope 15:39:52 Okay... 15:39:53 #info mboddu will be on PTO on Jun 25th to Jun 28th, with very limited access to my work laptop. 15:40:28 Please ping jednorozec or nirik for any help that is needed 15:40:44 (And leave me alone... :D) 15:41:12 ha. :) cool. Glad you are taking some time away... 15:42:14 I am just kidding, I might be able to check on things during the night, but during morning hours I wont be available 15:42:27 And nirik, you should take some as well 15:43:35 yeah, after the dc move is finally over... 15:44:27 Cool 15:44:42 If nothing else, I will close the meeting for today 15:44:53 mboddu: enjoy the time off 15:45:01 we won't tell you if things burn :) 15:45:03 Thanks pingou 15:45:20 pingou: Haha :) 15:47:24 I can check on things in the evening/night, but I wont have access to the laptop in the morning 15:47:34 Anyway, thanks everyone for joining 15:47:39 #endmeeting