17:01:47 #startmeeting RELENG (2017-11-16) 17:01:47 Meeting started Thu Nov 16 17:01:47 2017 UTC. The chair is mboddu. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 17:01:47 The meeting name has been set to 'releng_(2017-11-16)' 17:01:47 #meetingname releng 17:01:47 #chair dgilmore nirik tyll sharkcz masta pbrobinson pingou puiterwijk maxamillion mboddu Kellin 17:01:47 The meeting name has been set to 'releng' 17:01:47 Current chairs: Kellin dgilmore masta maxamillion mboddu nirik pbrobinson pingou puiterwijk sharkcz tyll 17:01:47 #topic init process 17:02:09 morning 17:02:21 howdy 17:02:27 .hello kellin 17:02:28 Kellin: kellin 'None' 17:02:49 .hello2 17:02:50 dustymabe: dustymabe 'Dusty Mabe' 17:03:12 * mboddu hopes this meeting will be short and sweet 17:05:26 Okay, lets get started 17:05:45 #topic #7113 proposal to run bodhi updates pungi composes with `--no-label` 17:05:58 dustymabe: puiterwijk was working on it, any update from him yet? 17:06:45 Can we delay discussing this until we have test results? 17:07:05 yep 17:07:14 i'm +1 17:07:46 puiterwijk: sure 17:08:33 #info We are still waiting on the test results. 17:09:13 #topic #7100 new koji tags for atomic host 17:09:21 #link https://pagure.io/releng/issue/7100 17:09:34 mboddu: this was was approved last meeting. we just need to do the work now that freezes are over 17:09:39 Last week we decided on https://pagure.io/releng/issue/7100#comment-478272 17:09:49 mboddu: let's work together to make that happen before next meeting 17:10:00 dustymabe: Yes, I just wanted to know when we can collaborate and work on it? 17:10:16 mboddu: later today? 17:10:44 dustymabe: Not today 17:11:02 ok. i can create specific tickets for specific work items if you like 17:11:25 i don't think it's too crazy, should be able to communicate the needs through tickets 17:11:30 dustymabe: Off the topic, but this reminded me about the doc and we can meet today afternoon to discuss about it 17:11:43 mboddu: +1 17:12:49 nirik, puiterwijk : If I create the tags tomorrow, can you able to get the permissions done by EOD tomorrow? 17:13:46 mboddu: what permissions? I have no idea, I did not follow that ticket 17:14:58 basically permissions to tag stuff into *atomic* koji tags 17:15:02 puiterwijk: Its just another permission to allow certain people to tag/untag packages from the newly created tags. "we request a new "atomic" koji permission. This permission will have the appropriate policy to allow people with this permission to add/remove packages from these tags." 17:15:30 mboddu: you know you can just do that while creating the tag, right? 17:15:40 Just create the tag with --permission=atomic and that's it 17:15:48 (and create an "atomic" permission in koji) 17:16:04 might need some hub rules to restrict things... 17:16:28 nirik: like?? 17:17:01 puiterwijk: Yes, but I dont think "atomic" permission exists? 17:17:05 nirik: I don't think so? 17:17:14 mboddu: just create it? That's in the koji api... 17:17:17 * nirik looks at the ticket 17:17:28 nirik: as long as we make sure that all tags require permission=atomic, that should be it? 17:17:49 yeah, looks like. ok. 17:17:57 the only remaining question I have from the ticket is: do people care above f27-atomichost-installer vs f27-atomic-installer ? 17:18:00 puiterwijk: Okay, I will take a look at it, if I need any help I will contact you guys 17:18:10 I'd like to use 'atomichost' in case we want to do this for workstation also 17:18:55 dustymabe: I care that the two words are run together; I'm assuming atomic-host won't work because - is separating other words? 17:19:28 Kellin: doesn't really matter to me 17:19:54 basically I was tryhing to separate it like -- 17:20:12 dustymabe: are the other things eg: f27-Workstation-installer? 17:20:12 so this would be the tag for f27, atomichost, installer 17:20:20 ehh 17:20:24 I think making it such that you could add workstation later makes sense. Otherwise I don't care what colour the bikeshed is 17:20:28 the other one would be f27-atomicworkstation-installer 17:20:39 but I don't care about adding another dash 17:20:45 f27-atomic-host-installer 17:20:50 dustymabe: I'm thinking of people parsing that later 17:20:50 f27-atomic-workstation-installer 17:21:07 Kellin: parsing it in their head? or in a script? 17:21:11 dustymabe: a script 17:21:25 not sure why they would need to 17:21:38 but this is a new area for me 17:21:51 dustymabe: I agree with Kevin, having something that we can add later makes sense. 17:21:57 can we put colons in there? 17:22:04 Kellin: nope 17:22:05 no 17:22:23 what other valid separators could we use 17:22:24 so i don't care as long as it is one of these two 17:22:35 f27-atomic-host-installer, f27-atomichost-installer 17:23:19 ⚛ ? :) 17:23:56 "How's that said?" - "The variant formerly known as Atomic" 17:23:58 nirik: I see the emoji as a flower 17:24:10 nice. 17:24:13 it's supposed to be a 'atom' cloud 17:24:20 i'm sure ausil would love that 17:24:51 anyhow, atomichost seems fine to me. 17:24:55 nirik: Ohhh, right, now I can see it :) 17:25:08 as far as I know the only place this will be used is in a pungi config 17:25:15 i'm not really sure what would need to parse it 17:26:17 dustymabe: I dont think parsing is a problem, just pick one and can you update the ticket with what you picked? 17:26:27 sure 17:26:34 Kellin: which one do you prefer? 17:26:39 atomic-host 17:26:51 k 17:26:53 thanks 17:26:57 parse rule can just be read-tofirst, read from back, accept center 17:26:59 easy enough 17:27:45 dustymabe: Can you also add the list of users who should have the "atomic" permissions? 17:28:36 mboddu: i can try 17:28:37 thanks 17:28:50 dustymabe: thanks 17:29:39 #info mboddu will work on creating the tags and adding permissions tomorrow, Nov 17th 2017 and dustymabe will work on the configs. 17:29:55 Okay, moving on 17:30:06 #topic Alternate Architecture Updates 17:30:20 sharkcz: Are you around? Any update? 17:34:28 * nirik guesses not 17:34:32 So, I guess he is not around 17:35:28 holiday there I think 17:35:28 #topic Open Floor 17:35:43 I have quick question 17:35:56 #info f27 release went out this week. Thanks to everyone who put in long hours and hard work to make it happen! 17:36:17 I suspect most of the USA folks will not be here next week... we should cancel next weeks meeting. ;) 17:36:23 nirik: With RHEL7.4 availability on multi arch? Is there anything we have to do on epel7? 17:36:35 nirik: Sure, I will do that 17:37:14 we have the new aarch64 rhel 7.4 synced. we need to switch koji to use it for epel7... 17:38:18 nirik: Who has to do it and when can we do it? 17:38:30 I can do it, or you can if you want... anytime. 17:38:42 Do it *now*! 17:38:51 nirik: I want to do it, but can you tell me how? 17:39:33 puiterwijk: Why are you soo excited? Do you need anything? 17:39:35 * mboddu thinking 17:39:56 hum, I was thinking it was just editing the external repos... 17:39:57 mboddu: no. But just get it over with, as it's a simple enough thing to do. 17:40:08 nirik: I think you'll need to delete and re-add 17:40:12 but thats not per arch... so it might be easier to just setup synlinks on our end 17:40:28 * dustymabe steps away 17:40:34 bb in a few 17:40:40 at least I don't think so 17:41:54 anyhow, there's a ticket on it, so we should just update it when we decide how to implement it. 17:42:21 I think it's going to need to be links tho to the existing names 17:44:03 nirik: thanks, I will keep an eye on it 17:44:52 #info We have the new aarch64 rhel 7.4 synced. we need to switch koji to use it for epel7 and we are thinking on how to implement it. 17:45:00 Thats all I have 17:45:06 Anybody got anything else? 17:45:55 * mboddu counting from 10 to 1 17:47:02 Okay, thanks guys for joining 17:47:21 I will cancel next weekss meeting 17:47:26 weeks' 17:47:38 #endmeeting