15:03:07 #startmeeting RDO meeting - 2018-01-10 15:03:07 Meeting started Wed Jan 10 15:03:07 2018 UTC. The chair is number80. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:07 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:03:07 The meeting name has been set to 'rdo_meeting_-_2018-01-10' 15:03:08 Meeting started Wed Jan 10 15:03:07 2018 UTC and is due to finish in 60 minutes. The chair is number80. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:03:11 The meeting name has been set to 'rdo_meeting___2018_01_10' 15:03:13 #topic roll call 15:03:17 o/ 15:03:18 o/ 15:03:21 o/ 15:03:25 agenda is here: https://etherpad.openstack.org/p/RDO-Meeting 15:03:32 #chair jpena amoralej bcafarel 15:03:32 Current chairs: amoralej bcafarel jpena number80 15:03:32 Current chairs: amoralej bcafarel jpena number80 15:03:37 o/ 15:03:38 o/ 15:03:41 o/ 15:03:46 #chair mfedosin jruzicka mary_grace 15:03:46 Current chairs: amoralej bcafarel jpena jruzicka mary_grace mfedosin number80 15:03:48 Current chairs: amoralej bcafarel jpena jruzicka mary_grace mfedosin number80 15:04:42 Let's start 15:04:59 #topic DLRN Fedora Rawhide builder issues 15:05:01 jpena: ^ 15:05:19 we're having trouble with the Fedora builder for RDO Trunk since a few days ago 15:05:38 TL;DR: since we're running it on CentOS, mock will try to populate the initial buildroot using yum 15:05:59 and that does not work well with some updated packages, that use rich dependencies "(xxx if yyy)" 15:06:31 The only fix I can think of is to separate this builder to its own VM running on Fedora, since there is no way to have dnf on centos (at least I'm not aware of any) 15:06:34 ideas? 15:06:34 jpena: is EPEL enabled for DLRN builders? 15:06:42 number80: usually no 15:07:01 alternative is to get dnf from EPEL and tell mock to use dnf 15:08:18 I haven't found dnf on epel :? 15:08:20 You may just enable EPEL for dnf + deps 15:08:50 that means dnf in the dlrn server 15:09:00 right? 15:09:08 and use it for everything? 15:09:13 or how that works? 15:09:22 let me check, I tried it yesterday but I couldn't get dnf from epel 15:09:23 we could selectively use dnf or yum? 15:10:03 it may have been removed, I'll investigate that after meeting 15:10:31 amoralej: mock allows you to choose default package manager, you may even change the command run in recent mock versions 15:10:39 nice 15:10:43 amoralej: we can choose per-worker, it's a mock option 15:11:15 using a fedora builder sounds as a good solution, anyway 15:11:29 for fedora builders 15:11:31 jpena: even better, CentOS has a specific repo => https://seven.centos.org/2017/10/yum-4-is-available-for-testing/ 15:11:36 oh 15:11:39 * jpena checks 15:12:06 (dnf was removed from EPEL since it was old version and no updates) 15:14:12 number80: it looks like installing yum4 brings a new rpm version, too 15:14:50 I'm not sure if we should use a testing version in the RDO Trunk builder :-/ 15:15:08 jpena: well, just pointing alternatives, a stable fedora builder should be fine 15:15:13 I'd +1 to have a new builder 15:15:29 +1 15:15:58 So does someone disagree with having a new builder? 15:16:17 (let's use lazy consensus here) 15:16:25 cool then :) 15:16:28 jpena we could do redirects from the main builder for fedora repos for the failover case 15:16:35 new rpm version?! whooo 15:16:59 #info jpena will be working on a new DLRN fedora builder 15:17:00 amoralej: yes. Worst case, fedora repos are not that important yet 15:17:12 cyeah 15:17:50 having fedora builder sounds useful anyway. 15:20:20 let's change topic 15:20:44 #topic Move Q3 test day to Feb 8, 9 (conflict with FOSDEM) 15:21:00 o/ 15:21:07 \o 15:21:09 So rbowen asked us if we're okay to move M3 test day to the next week 15:21:12 #chair jschlueter dmsimard 15:21:12 Current chairs: amoralej bcafarel dmsimard jpena jruzicka jschlueter mary_grace mfedosin number80 15:21:13 Current chairs: amoralej bcafarel dmsimard jpena jruzicka jschlueter mary_grace mfedosin number80 15:21:45 sounds good to me 15:21:47 As amoralej and I will be at FOSDEM and CentOS dojo, so we're unlikely to be available 15:22:05 So again, lazy consensus rule, is anyone against it? 15:22:13 +1 15:22:47 there's no force binding it to that specific date, no? so let's do it when we have most testers :) 15:23:13 jruzicka: well, the only reason we set dates is to make sure we won't miss them :) 15:23:40 missing them for sure isn't that much better :) 15:23:48 *nods* 15:24:21 then, let's say we agreed to do that change 15:24:34 #agreed Move M3 test days to Feb 8, 9 15:24:35 \o/ 15:24:48 So the next thing is to decide who'll take the action to announce it? 15:24:51 #chair chandankumar 15:24:51 Current chairs: amoralej bcafarel chandankumar dmsimard jpena jruzicka jschlueter mary_grace mfedosin number80 15:24:53 Current chairs: amoralej bcafarel chandankumar dmsimard jpena jruzicka jschlueter mary_grace mfedosin number80 15:25:01 Sorry, I'm here. 15:25:06 no worries 15:25:12 #chair rbowen 15:25:12 Current chairs: amoralej bcafarel chandankumar dmsimard jpena jruzicka jschlueter mary_grace mfedosin number80 rbowen 15:25:13 Current chairs: amoralej bcafarel chandankumar dmsimard jpena jruzicka jschlueter mary_grace mfedosin number80 rbowen 15:25:32 rbowen: so I guess you'll take the announce action (or maybe mary_grace) ? 15:26:10 go for it, rbowen 15:27:02 Sorry, so many distractions today. 15:27:15 #action rbowen will announce the M3 test days change to Feb 8, 9 15:27:29 Yes, I'll take care of that. :-) 15:27:36 so next topic ^^ 15:27:49 #topic [Octavia] Providing service VM images in RDO 15:27:53 bcafarel: ^ 15:28:08 thanks :) 15:28:20 initial mail sent today: https://lists.rdoproject.org/pipermail/dev/2018-January/008482.html (and thread) 15:28:59 https://lists.rdoproject.org/pipermail/dev/2018-January/008482.html 15:28:59 basically octavia amphora (the service VMs) currently need to be built/updated/uploaded manually by the user 15:29:08 (reposting link for logs) 15:30:16 it would be great to have that image built and provided in the repo, apevec had some nice feedback/questions already 15:30:45 oh yeah, it looks like a lot of work that could be done automatically once as opposed to every user needing to do it manually. 15:31:21 bcafarel: technically, it can be a zuul job we can host 15:31:37 yes, part of the promotion pipeline 15:32:01 that was what I was thinking looking at https://www.rdoproject.org/what/promotion-pipeline/ yes 15:32:02 bcafarel, does puppet-openstack-integration cover octavia? 15:32:22 or in any tripleo scenario? 15:32:58 currently I think none, there is work in progress though 15:33:05 ^ beagles: around? 15:33:54 bcafarel, about distribution, do you plan on including the images in a rpm? 15:34:53 amoralej: if the rpm can be included in the repo, that would be great 15:35:05 i see several advantadges 15:35:16 one is that it provides versioning 15:35:27 we could use creation timestamp 15:35:32 as release or something like that 15:35:33 Seems that Manila is also interested to jump in the bandwagon 15:35:39 (from the mailing list) 15:35:50 and second is that we could use yum repos to distribute 15:36:14 bcafarel, how long takes images to be created and how big are they? 15:36:52 number80: up to this point we've not gotten much traction further downstream b/c of considerations around image maintenance/distribution 15:37:11 but maybe octavia will pioneer here and reduce friction :) 15:37:16 amoralej: on my laptop, ~5min (with "warm" DIB cache) 15:37:30 tbarron: do you mean I opened a can of worms? :) 15:37:47 bcafarel: dunno, we'll see :) 15:38:00 tbarron: yes, having another use case makes it more worthwhile to work on this area 15:38:20 So may I suggest that we continue the discussion on the mailing-list? 15:38:43 (we can have follow-up topic next week) 15:38:53 yes, i think ML is the best option, there are many details to figure out 15:38:59 ack 15:39:09 sounds good yep 15:39:18 #topic rdopkg is now available for testing in F25+ and EPEL7 15:39:25 jruzicka: ^ 15:39:35 someone asked me howto install rdopkg 15:39:45 so when you're on Fedora, it's: 15:39:47 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-b2c3f7fabb 15:39:47 rdopkg install rdopkg 15:39:50 :) 15:40:02 recursive install? 15:40:09 :D 15:40:10 jruzicka: what type of cleanup should we do if we already had it installed via epel? 15:40:10 sry 15:40:18 dnf install rdopkg 15:40:33 recursive instal and self-consciousness are on longer term TODO 15:40:38 any recommendations for cleanup? 15:40:38 lol 15:41:08 #info how to install rdopkg? just dnf/yum it! 15:41:24 EPEL was borked and noone noticed because reasons but there is a working build now 15:41:43 Merged openstack/rsdclient-distgit rpm-master: Fix sphinx-build leftovers removal command https://review.rdoproject.org/r/11252 15:41:48 jruzicka: i hope we should have somehting like pip install -u pip -> rdopkg install -u rdopkg 15:42:15 #info EPEL 7 rdopkg build in testing: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-b2c3f7fabb 15:42:25 feel free to test and +1/-1 to autopush to stable 15:43:07 #info for cleanup, nuke jruzicka/rdopkg copr repo 15:44:00 Thanks jruzicka ! 15:44:05 Next topic 15:44:09 jschlueter, you installed from epel even though pyOpenSSL req isn't met? heh, magic :) 15:44:16 #topic FOSDEM openstack booth volunteers 15:44:26 jruzicka: from way back 15:44:29 rbowen is looking for booth volunteers so please sign up! 15:44:32 https://etherpad.openstack.org/p/fosdem-2018 15:44:35 link ^ 15:44:39 i'll add myself 15:44:40 At the moment, the OpenStack table at FOSDEM is manned by myself and Erwan. That's not going to work out. 15:45:04 It's just an hour, and it's answering questions that tend to be at a very basic level, like What's OpenStack. 15:45:06 I'm not going to FOSDEM this year, sorry :( 15:45:13 I'd help otherwise. 15:45:24 So if you or any of your colleagues will be there, please shame them into participating. 15:45:25 Thanks. 15:45:43 Well, Adrien signed up so we should be enough 15:46:09 Also, dress warmly. 15:46:28 15:46:33 Thanks :) 15:47:04 #topic PTG interviews with Rich 15:47:18 rbowen ^ 15:47:24 Amazingly, it's time for another PTG. I do video interviews at the PTG. You can see examples at http://youtube.com/rdocommunity If you want to talk about your project, watch various mailing lists for signup announcements. 15:47:49 Ideally, interviews are multiple people that represent a particular project, preferably spanning more than one organization. 15:48:09 Topic is "what's new in Queens, and what's coming in Rocky", typically. 15:48:18 amoralej: wondering if anything is stoping https://review.rdoproject.org/r/#/c/11269/ from landing ? 15:48:37 Anyways, there should be a signup sheet as soon as I get confirmation from Erin Disney that they expect to have space for me. 15:48:39 Well, a significant part of the RDO Eng. team will be here, if you want a behind the scene interview with us 15:48:41 chem, we are in a meeting, gimme 10 minutes 15:48:56 number80: That would be great! 15:48:59 rbowen: i will let my presence by tomorrow 15:49:07 Good. 15:49:39 That's all I've got. Hopefully more info next week. 15:49:40 So I guess we're good now 15:49:51 #topic next week meeting chair 15:50:09 since the holiday jumbo-mumbo ended up, so who wants the chair now? 15:50:23 number80: i will take care of that 15:50:27 good 15:50:36 #info chandankumar is chairing next week meeting 15:50:40 Thanks! 15:50:47 #topic open floor 15:51:02 So before we close the meeting, anyone wants to bring another topic? 15:51:15 So last year 2017 in last meeting i have sent a mail related to Add your things which make RDO awesome in year 2017 15:51:23 There's a new newsletter: http://rdoproject.org/newsletter/2018/january/ 15:51:23 Still received no reply 15:51:28 Share it with your friends and family. 15:51:33 #link https://rdo.fsn.ponee.io/thread.html/1e8105a4c9bc869d1d2754f1cf307c7b342abf5b7a89ffcde8f2832c@%3Cdev.lists.rdoproject.org%3E 15:51:44 chandankumar: It was mentioned in the newsletter, too. Hopefully someone will read that. 15:52:02 please take some time, reply to this email so that i can work on drafting blogpost 15:52:09 Ack 15:52:27 that's it from my side. 15:54:18 Ok, thanks! 15:54:30 Well, let's see you next week, ladies and gentlemen! 15:54:33 #endmeeting