14:01:12 #startmeeting Infrastructure (2018-06-21) 14:01:12 Meeting started Thu Jun 21 14:01:12 2018 UTC. 14:01:12 This meeting is logged and archived in a public location. 14:01:12 The chair is smooge. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:12 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:01:12 The meeting name has been set to 'infrastructure_(2018-06-21)' 14:01:12 #meetingname infrastructure 14:01:12 The meeting name has been set to 'infrastructure' 14:01:12 #topic aloha 14:01:12 #chair nirik pingou puiterwijk relrod smooge tflink threebean 14:01:13 Current chairs: nirik pingou puiterwijk relrod smooge tflink threebean 14:01:29 good morning everyone. 14:01:35 * relrod waves 14:01:39 morning 14:01:45 Morning 14:01:52 I can make these now with the new time :) 14:01:53 morning 14:01:58 morning 14:02:03 morning 14:02:03 .hello2 14:02:05 creaked: creaked 'Will Chellman' 14:02:36 .hello 14:02:36 puffi: (hello ) -- Alias for "hellomynameis $1". 14:02:38 .hello mohanboddu 14:02:39 mboddu: mohanboddu 'Mohan Boddu' 14:02:45 .hello puffi 14:02:47 puffi: puffi 'Brian O'Regan' 14:02:48 .hello2 14:02:50 pingou: pingou 'Pierre-YvesChibon' 14:03:38 hi everyone 14:04:11 #topic New folks introductions 14:04:11 #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves 14:04:23 Are there any new people here today? 14:05:04 I'm new but I haven't sent my introduction to the mailing list, so I'll hold off until next week. 14:05:28 hi mklvr 14:05:47 will look forward to your intro 14:05:48 Hi mklvr 14:05:51 any others? 14:06:22 #topic announcements and information 14:06:22 #info bowlofeggs is on PTO 14:06:22 #info tflink is on extended PTO 14:06:22 #info most systems have been moved off of iscsi and cisco ucs boxes 14:06:23 #info planning to deploy new OSBS in prod next week (wish me luck) - cverna 14:07:02 * threebean waves 14:07:14 cverna: good luck :) 14:07:23 threebean: thanks 14:07:42 cverna: Is that the one with flatpak support? 14:08:19 mboddu: not yet, but that's the first step to enbale flatpak support and multi arch 14:08:21 * vgolwala waves 14:08:23 any other announcements? 14:08:56 cverna: Okay, good luck :) 14:09:49 ok next up 14:09:52 #topic Oncall 14:09:52 #info Relrod is on call from 2018-06-20->2018-06-26 14:09:52 #info Smooge is on call from 2018-06-27->2018-07-05 14:09:52 #info ?? is on call from 2018-07-06->2018-07-12 14:10:24 I expect it will be Kevin taking the ?? 14:10:36 yeah, I can take that block 14:10:55 I was thinking also about mass update schedule... 14:11:04 I don't mind taking a block at one point 14:11:31 perhaps july 2nd/3rd... 14:12:23 I will be around then and will be available for the 4th in case of problems 14:12:27 pingou, cool 14:12:39 nirik, I will put that as the next topic 14:12:51 #topic Next Update Schedule 14:13:05 #info RHEL-6.10 is out and will affect FAS and some other services 14:13:26 smooge: just FAS. That's the only RHEL6 production service we still have to the best of my knowledge 14:13:33 fedorapeople? 14:13:39 #info It has been 25-40 days since the last update 14:13:49 #link https://fedoraproject.org/wiki/Infrastructure/RHEL6_hosts 14:14:03 pingou: that's RHEL7 14:14:07 cool 14:14:41 nice list :) 14:15:49 anyhow, I think 2nd and 3rd? or we could do next week. 14:15:55 nirik, I was thinking of updating fas01.stg next week and see if it borked stuff 14:16:04 2nd/3rd sounds good 14:16:26 #info koji01 will be moved off of iscsi during outage 14:17:03 what are we doing about cloud this time around 14:17:13 threebean, you are up for the next topic.. 14:17:18 yeah :) 14:17:33 * threebean grabs a coffee 14:17:42 relrod, well I am going to say you are going to rebuild it on the new hardware 14:18:06 I am also saying it with a mwahahahahaha 14:18:09 well, I hope we can have newcloud up by then... but you know... 14:18:18 we can play it by ear 14:18:23 I think next week should be newcloud week 14:18:35 with all hands on it 14:19:19 newcloud week ++ 14:20:07 well, we have all read the mythical man month (and if you haven't you should)... that said, it could help to have more folks working on parts or discussing. 14:20:50 nirik, I figure that adding 3 new people to a late project would be great. But I rooted for IBM management in that story 14:20:58 9 women having a baby in 1 month ? team effort 14:21:22 right 14:21:41 * FrostyX takes a note about reading that book 14:21:55 actually what I was figuring was that the people who are not cloud experts work as interference to the experts 14:22:19 so while I might not be working on cloud directly.. I am keeping people from bugging you relrod and puiterwijk 14:23:06 and that other people know that you have your heads down trying to figure out the evil mechanations of RHOS 13 14:23:46 but yeah.. my all hands would not be useful 14:23:59 ok any other ways I can derail this? 14:24:24 we will get there someday... 14:25:23 #topic Ursa-major? https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/LPCRSNGLPC2M3ZX6DPXSADWDAGWUAQPD/#LPCRSNGLPC2M3ZX6DPXSADWDAGWUAQPD - threebean 14:25:51 yes, ok. 14:26:20 this came up on the list previously, I just wanted to raise it again so it didn't die there. 14:27:00 I won't reintroduce the stuff I tried to explain on the list... but I think the modularity-wg people want/need the problem to be solved on the Fedora side of things. 14:27:19 they keep bringing it up. :p 14:28:00 do folks here have any gut feelings about it from the list? objections? different ways to approach it? 14:28:05 so this was pretty much the first time I heard of this thing 14:28:53 * nirik hasn't really pondered it too much. 14:29:13 does that mean a rpm that buildrequires a module could also require a module at install time? 14:29:37 well, no. :/ it's just a buildtime availability thing. 14:30:06 there would be some releng-blessed set of modules that are always available and present in the f30 build tag. 14:30:31 but runtime is another story. 14:31:18 at build time - normal old rpms would just declare normal rpm buildtime deps. those would just get fulfilled by rpms from the blessed set of modules. normal old rpms don't get a new way to declare a buildtime dep on "a module" per se. 14:32:01 .. but - that's the way we implemented internally. the problem its trying to solve is: how do we modularize things over time that are still needed as buildtime deps for core pieces? 14:32:15 it sounds like this is f30+ territory? 14:32:27 heh, not f29, for sure. 14:32:44 yeah, I think there's advantage to doing the same thing in fedora as internally... 14:33:52 agreed.. because i think we have at least a similar need from the discussions on devel today.. and reinventing the wheel for our maybe slightly different need would be poor 14:34:28 threebean: So, if I am understanding it correctly, rpms that cannot be modularized (bare rpms) still be in f30-build and the modular rpms that are needed at build time will be tagged into a inherited buildroot tag, is that right? 14:34:41 * linuxmodder lurks 14:34:42 that's right, yeah. 14:35:03 the modular rpms (needed as deps) get their tag added to the tag inheritance for f30-build. 14:35:35 so, f30-build is full of lots of usual stuff, but also gets a handful of new modular tags added to its inheritance chain. 14:35:54 threebean: Ahh, okay, understood 14:36:02 the module tags change with every new build of different module streams, so the tool watches for this and swaps out old inherited tags with new inherited tags. 14:36:27 releng maintains the config of which module streams should be watched for. 14:37:59 ok anything else or questions for threebean? 14:38:33 can anyone recommend a next step for this? 14:39:02 smooge: I think I have more questions regarding this, but I dont want to stall the meeting for this 14:39:03 I'd say let it simmer for now, but then later this year we could look at starting to roll it in stg? 14:39:17 or some solution 14:39:25 we could talk about it at flock (for those there) 14:39:26 what nirik said was my idea 14:39:41 +1, wfm. :) 14:40:09 threebean: ^ be ready to answer more questions at flock :P 14:40:38 smooge: if we are low on time, some of my topics could bump to next week. 14:40:49 aww.. I won't be there this year :/ we can jit.si during flock hours :) 14:41:40 threebean: sure, we can jit.si but not during flock hours :) 14:41:46 Anyway, thanks for the info threebean 14:42:05 yeah, thanks threebean! 14:42:10 thanks threebean. 14:42:12 thanks all :) 14:42:23 I am goint ot do tickets next and then we will do the other topics as time allowed 14:42:27 #topic Tickets discussion 14:42:27 #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket 14:42:41 .ticket 7040 14:42:43 smooge: Issue #7040: co-maintainer of cbootimage - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/7040 14:42:45 .hello2 14:42:47 x3mboy: x3mboy 'Eduard Lucena' 14:42:53 .ticket 7043 14:42:55 smooge: Issue #7043: RFE: discussion.fp.o use your fp.o alias - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/7043 14:43:04 that is the right ticket 14:43:49 so, yeah, I don't think we can use fedoraproject.org aliases in a place where email will be sent/used with them 14:43:54 I agree with misc on that 14:44:25 perhaps there is some way to override tho? a pref? 14:44:34 puiterwijk: ^ any thoughts? 14:45:16 Let me check the ticket... 14:45:36 Also, since when are new tickets part of the meeting? I haven't even had time to read that ticket yet... 14:46:20 sorry, I just thought this one would be good to discuss... 14:46:25 we can punt it 14:46:36 the others I tagged are old 14:46:39 Well, as Michael said, without CLA+1 there's no alias we have. 14:47:05 While I can make Ipsilon know about that, that means that when you get added to a group, it changes 14:47:30 yeah. ;( 14:47:31 So... if people want this, I can make it happen, but a preference is difficult at this point in time 14:47:58 So the best I can do is "provide @fp.o email if CLA+1, FAS email otherwise" 14:48:15 it then gets hard to know where you'll receive notifs 14:48:21 and yeah, I suspect some people don't want that way either 14:48:32 wontfix +1 14:48:40 wontfix +1 14:48:44 defer +1 14:48:57 Since when we get CAIAPI, I can add a preference for this to that.... 14:48:59 could ipsilon ask the user ? (with code, down the road, etc) 14:49:07 ah, or yeah, caiapi 14:49:19 nirik: down the road, Ipsilon might be able to. I have an RFE that comes down to this. 14:49:32 this kind of thing would also affect things like bugzilla soon. 14:49:36 But I've not had time to work on Ipsilon for a while, unfortunately. I need to get back to that stuff.... 14:49:52 So, that's whyI vote defer 14:49:55 so, lets close the ticket and say we can't do it now, but we will try and implement it down the road. 14:50:07 sounds good to me 14:50:09 +1 14:50:16 Well, maybe keep it open for now so I remember to look when I get to that? 14:50:23 I'll take the ticket... 14:50:54 I suppose. I don't like infra tickets sitting there forever... 14:51:38 Right, but as with the other one, I don't have a tracker for CAIA yet... 14:51:42 I can take it when I get to that 14:51:47 ok 14:52:32 @puiterwijk - is there a repo for CAIAPI? 14:52:42 aikidouke: no, not yet. 14:53:00 Or it looks like there is actually. Hum 14:53:04 I have done more than I thought I had 14:53:11 .ticket 6470 14:53:13 smooge: Issue #6470: Regenerate infra dist-repos regularly - fedora-infrastructure - Pagure - https://pagure.io/fedora-infrastructure/issue/6470 14:53:26 ok - ty, havent had time to catch up with you on that yet, just thinking about avatars, etc.. 14:54:04 * nirik sees we are low on time, should we punt the rest to next week? 14:54:32 ok will do so 14:55:16 relrod, we will put your discussion next week if that is ok 14:55:32 * relrod nods 14:55:35 #topic Open Floor 14:55:49 Hi team! 14:55:50 I started to look at loopabull earlier this week 14:56:02 turns out it's actually actively being used by releng for one task 14:56:13 yeah.. 14:56:15 I was looking for someone in the infre team that would want to be interviewed for the Fedora Podcast 14:56:39 I'd like to gather nirik and mboddu to see if we could merge playbooks into one repo 14:56:48 or see how we'd like to proceed 14:57:12 pingou: oh? what task? I don't think we saw anything at the hackfest? 14:57:26 * x3mboy is thinking that everyone is thinking in Flock 14:57:35 @x3mboy - I hear @bowlofeggs can be quite verbose, but I don't see that he is here today 14:57:49 nirik: https://pagure.io/releng-automation/blob/master/f/ansible/include/release-containers.yml 14:57:54 nirik: We use it for layered container build and release 14:58:22 nirik: mboddu said he manually updates that playbook so it's not as automated as it should but we can always fix this later 14:58:23 aikidouke, cool! I can catch him in another time 14:58:31 If everyone else agreed, of course 14:58:45 puiterwijk, pingou nirik ^^ 14:58:53 pingou: nothing's actually running in loopabull right now 14:59:00 aikidouke / x3mboy: bowlofeggs is on vacation for the next 3 weeks. ;) when do you need someone? 14:59:01 mboddu: you aren't. 14:59:37 nirik: I am talking about the repo 14:59:39 nirik, Well 3 week works perfectly because I already have 3 episode recorded, that means 6 weeks covered 14:59:46 sorry, puiterwijk ^^ 14:59:56 mboddu: right. Just not the actual deployed system 15:00:03 x3mboy: sure, feel free to drop him an email... but don't expect a quick answer. ;) 15:00:16 ah... I see. 15:00:16 puiterwijk: the config points to that repo though 15:00:25 https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/loopabull/defaults/main.yml 15:01:05 that being said, the routing_keys that should trigger https://pagure.io/releng-automation/blob/master/f/ansible/org.fedoraproject.prod.releng.twoweek.complete.yml 15:01:08 is not in the config 15:01:17 nirik, cool! I will! 15:01:22 Thanks 15:01:39 mboddu: so changes are that the playbook may work but isn't being triggered by loopabull 15:02:23 ok we are overtime. I am not sure if there is a meeting waiting for us. can we move this to #fedora-admin? 15:02:30 sure 15:02:53 pingou: Okay 15:03:02 thanks smooge! 15:03:02 The loopabull conversation will be in #fedora-admin 15:03:06 Thank you all for coming today 15:03:11 See you in a weeks time 15:03:12 thanks smooge 15:03:13 thanks smooge 15:03:15 #endmeeting