15:01:04 #startmeeting RELENG (2020-05-26) 15:01:04 Meeting started Tue May 26 15:01:04 2020 UTC. 15:01:04 This meeting is logged and archived in a public location. 15:01:04 The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:04 The meeting name has been set to 'releng_(2020-05-26)' 15:01:04 #meetingname releng 15:01:04 The meeting name has been set to 'releng' 15:01:04 #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec 15:01:04 Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz 15:01:04 #topic init process 15:01:13 รณ/ 15:01:27 I should rename this channel to #fedora-releng-meeting :D 15:01:40 morning. 15:01:50 * nirik is somewhat here, but also busy with the new datacenter stuff 15:01:53 morning pingou and nirik again :) 15:02:11 * mboddu also might cut this meeting short, but we will see 15:02:29 * sharkcz is here 15:03:03 Since pingou is here 15:03:07 #topic #9467 Testing compose from a side tag, possible? 15:03:14 #link https://pagure.io/releng/issue/9467 15:03:45 pingou: So, these side tags are created from main buildroot tags, right? 15:04:11 I supose so 15:04:29 otherwise we wouldn't have the newRepo task issue :) 15:04:35 Yes :) 15:05:15 I guess we cannot run the composes from buildroot tags and IIRC from my convo with Dennis Gilmore when I joined, it will compose with buildroot stuff in it 15:05:55 what's preventing this? 15:06:13 would odcs help? 15:06:16 ^ this is from recollecting from a conversation I had while working from his basement, so I dont remember the exact reasons 15:06:27 arf :( 15:06:54 we could probibly make it work... but I don't have any time to devote right now. 15:07:09 pingou: We can use odcs, but as far as I remember, there are some reasons why we cannot run composes out of buildroot tags 15:07:35 nirik: Is there any reason why we cannot run composes from buildroot tags? 15:07:46 That you can remember 15:08:33 I can do the work, but can we do it or not is my question. 15:08:37 well, this is a side tag right? 15:08:42 yes 15:08:59 so the things built in it are tagged there... 15:09:10 nirik: yes, but it is also a buildroot tag 15:09:11 so couldn't we do a pungi run with f33 + f33-side-whatever ? 15:09:30 well, inheritence might blow up if we can't do -no-inherit 15:09:48 I'm not sure how pungi will see it there. 15:10:09 We can just do f33-side-whatever with inheritance set to true in pungi configs 15:10:26 I guess it should work 15:11:31 If its do-able, my next question is, self serviceable and how can we achieve it? 15:12:02 We can leave it in the hands of maintainers, but they can run it whenever they wish, which might be bad 15:12:24 mboddu: considering the colo move, let's do baby step 15:12:38 I definitely don't think we should worry about self service here 15:12:39 fix this one request, and potentially table the long term solution for this for later 15:12:40 right now 15:12:44 +1 15:12:44 pingou: Agreed, its going to be post colo move 15:13:06 mboddu: could be a good idea to discuss this with Aoife as a pitch for an initiative 15:13:13 also, adamw said he was going to do something with openqa, so we should try not and duplicate efforts here. 15:13:33 didn't he say openqa works on composes ? 15:14:06 yes, but he got tired of waiting for releng to make on demand/test composes, so he implemented it himself in openqa... 15:14:16 updates testing does that for example. 15:14:43 ok 15:15:46 anyhow, if we can easily do a test compose I'm all for it. 15:16:06 just another rawhide with that tag added on the side. 15:16:24 another tag on the side? :) 15:16:29 and some salad maybe? 15:16:36 * pingou stops derailing 15:18:38 the side tag on the side. 15:18:40 :) 15:44:35 I am back 15:44:37 No idea what happened 15:45:00 it happens :) 15:46:27 So, we will try it with the python39 side tag and we will see if anyone else needs it and doing a self service if needed and check with adamw before replicating the work 15:46:36 nirik, pingou : ^ is that okay? 15:47:44 +1 15:48:09 Okay 15:48:47 sure. 15:50:12 #info we will try running the compose with the python39 side tag and we will see if anyone else needs it and doing a self service if needed and check with adamw before replicating the work 15:50:19 * mboddu updated the ticket 15:50:55 #topic Open Floor 15:51:22 Sorry for my laptop issues, with the time we got, I had to jump to open floor 15:52:37 no worries, it happens 15:53:02 pingou: I got a question on https://pagure.io/fedora-infra/ansible/pull-request/73#c-8478226057f4f388675184534448910b77fe7829-31 15:53:28 shoot 15:53:30 Is it just running uuid on the box and adding to private repo and adding it to the ansible? 15:54:03 adding uuid to private repo and adding that variable to ansible role?* 15:54:03 mboddu: nah 15:54:15 Okay.... 15:54:36 * pingou looks for an example 15:54:37 I couldn't find any docs on it 15:54:50 Thanks pingou 15:54:51 you're only listening or also publishing? 15:55:30 mboddu: this is the doc: https://fedora-infra-docs.readthedocs.io/en/latest/dev-guide/messaging.html 15:55:46 pingou: Just listening 15:56:08 so you need to create an user and a queue 15:56:20 both of which can be done via roles in the playbook 15:56:35 Okay 15:56:58 https://pagure.io/fedora-infra/ansible/blob/master/f/playbooks/openshift-apps/bodhi.yml#_31-39 15:57:02 I will go through the docs and if I need anything I will ping pingou :D 15:57:18 in this case they've put the queue_name in a variable but that's up to you 15:58:23 pingou: I was looking at https://pagure.io/fedora-infra/ansible/blob/master/f/roles/bodhi2/base/templates/fedora-messaging.toml.j2#_33 15:58:35 mboddu: and now you have one more comment :) 15:59:08 yeah, they've used a variable (not in the private repo btw) 15:59:13 pingou: I know I shouldn't have asked you :P 15:59:27 Thanks pingou 15:59:36 Thats all I got 15:59:43 mboddu: check the backcave playbook 15:59:43 Oh btw, today is F30 EOL 15:59:49 pingou: Sure 15:59:49 since it also just consumes 16:00:11 (but it covers 3 different hosts using 3 different queues) 16:00:14 RIP F30 16:01:16 pingou: Okay, thanks for the info 16:01:27 Thanks guys for joining 16:01:40 And sorry for my laptop issues 16:02:11 We went past time, so closing the meeting and we can continue in #fedora-releng if I missed anything 16:02:14 np, it was a bit strange, because you didn't leave IRC :-) 16:02:14 #endmeeting