15:02:00 #startmeeting RDO meeting - 2017-09-13 15:02:01 Meeting started Wed Sep 13 15:02:00 2017 UTC. The chair is chandankumar. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:02:01 The meeting name has been set to 'rdo_meeting_-_2017-09-13' 15:02:02 Meeting started Wed Sep 13 15:02:00 2017 UTC and is due to finish in 60 minutes. The chair is chandankumar. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:05 The meeting name has been set to 'rdo_meeting___2017_09_13' 15:02:12 #topic Roll Call 15:02:14 o/ 15:02:15 \o/ 15:02:16 o/ 15:02:24 #chair number80 jruzicka 15:02:24 Current chairs: chandankumar jruzicka number80 15:02:24 Current chairs: chandankumar jruzicka number80 15:02:30 o/ 15:02:37 #chair apevec 15:02:37 Current chairs: apevec chandankumar jruzicka number80 15:02:38 Current chairs: apevec chandankumar jruzicka number80 15:02:42 o/ 15:02:49 #chair jpena 15:02:49 Current chairs: apevec chandankumar jpena jruzicka number80 15:02:50 Current chairs: apevec chandankumar jpena jruzicka number80 15:03:07 Feel free to add your agenda here : https://etherpad.openstack.org/p/RDO-Meeting 15:03:48 snecklifter: PagliaccisCloud rdo meeting time if you are around. 15:03:56 i'm here 15:03:59 o/ 15:04:05 #chair PagliaccisCloud snecklifter 15:04:05 Current chairs: PagliaccisCloud apevec chandankumar jpena jruzicka number80 snecklifter 15:04:06 Current chairs: PagliaccisCloud apevec chandankumar jpena jruzicka number80 snecklifter 15:04:59 So starting with first topic 15:05:17 #topic dropping patches repositories 15:05:22 jruzicka: go ahead 15:05:35 actually, it was from me 15:05:46 number80: please go ahead 15:05:47 Well, I just noticed that they are not used anymore 15:06:05 that's by RDO def, we don't carry patches :) 15:06:08 so either we use them, or decide to try something else 15:06:18 but sometimes we do need a patch 15:06:32 Yeah, if we just didn't have patches, it would be perfect 15:06:36 for blockers/security issues 15:06:46 but as we have them, we need to consolidate how we handle them 15:07:25 And also we never discussed about EOLing open reviews 15:07:45 * number80 can't use the user-specific views of gerrit since they are accumulating 15:08:00 by design, they can't be closed 15:08:20 patches reviews for EOL branches can be abandoned? 15:08:40 I think so 15:08:53 but I wouldn't do that without checking with everyone else 15:08:57 number80: https://github.com/openstack/horizon/blob/master/tools/abandon_old_reviews.sh 15:09:01 with current SF implementation, reviews stay open as long as we need to build the RPM with the patch 15:09:06 if we are talking about old reviews then 15:09:13 chandankumar: not a tooling problem, but a policy one 15:09:26 these reviews are designed to be opened 15:09:30 never merged 15:10:06 so I guess from discussion, I can elaborate two proposals 15:10:17 A: create patches branches on-demand 15:10:47 B: as part of EOL process, abandon open patches reviews for EOL branches 15:10:55 abandoning old review could be part of EOL checklist, we had template card for that: https://trello.com/c/fV69VODx/165-rdo-release-eol 15:11:02 *nods* 15:11:13 A: +1 B: +1 (my personal take) 15:11:27 +1 both 15:11:43 +1 +1 15:12:20 PagliaccisCloud, snecklifter: even if you're new, you're allowed to express yourselves (or ask questions if you're unsure) :o) 15:12:46 :D 15:13:28 I thought we could pull patches into specs from upstream, what am I missing? 15:13:42 lots, probably 15:14:21 snecklifter: well, flepied came with this idea of using gerrit open reviews to track downstream patches 15:14:35 Pros: easy rebase, we keep history and run CI on them 15:15:04 and we even had rdopkg support to manage them nicely (some commands were removed recently) 15:15:21 Yes, have used and I like it 15:15:59 so we're just trying to see if we should keep using them, and just create repo/branches on-demand 15:16:28 and also what to do with accumulating reviews on EOL branches 15:16:29 +1 to that idea, I'm all for simplification which is what this feels like to me 15:16:49 ok then 15:17:05 #agreed create patches branches on-demand 15:17:15 #agreed abandon patches open reviews for EOL branches 15:17:27 #action number80 document that where it fits ^ 15:17:38 * number80 is done with that topic 15:17:44 number80: thanks :-) 15:17:57 Any question with this topic, if not moving ahead. 15:18:08 nope 15:18:31 #topic Fedora worker cleanup in RDO Trunk 15:18:42 that's mine 15:18:42 i hope it is jpena's topic :-) 15:19:12 The Fedora Rawhide worker in RDO Trunk has been mostly unmaintained for too long, and as a result most packages are failing to build 15:19:30 that explains all the py3 reviews :) 15:19:34 I've started working on it, trying to get it consistent asap 15:20:06 I'm using https://review.rdoproject.org/r/#/q/topic:fedora-cleanup as a general topic for reviews related to this effort. So far I've found a few mistakes in the specs 15:20:09 jpena: is this anything I can help out with? 15:20:40 snecklifter: sure, check https://trunk-primary.rdoproject.org/f25/report.html , see if there's any failing spec you can fix 15:20:54 jpena: will do, cheers 15:21:08 besides spec issues, we have two more general problems: 15:21:11 jpena: adding it to office hour for getting more help 15:21:26 1- We don't have openstack-macros in Fedora (should we add it?) 15:21:41 Absolutely 15:22:10 2- eventlet 0.21.0 in Fedora is known to create problems for OpenStack: https://github.com/eventlet/eventlet/issues/401 15:23:06 jpena: yeah, I was looking at that this morning, pinning to 0.20.0 as workaround 15:23:20 I can propose openstack-macros in Fedora, but I'm happy to leave it for someone else if there's any volunteer :) 15:24:16 jpena: I'll propose it tomorrow 15:24:28 nice, thanks! 15:24:28 * snecklifter is UK-based 15:24:41 #action snecklifter to propose openstack-macros for fedora 15:24:52 jpena, I'd add openstack-macros in trunk 15:24:59 it's openstack project 15:25:10 so I'd undo 15:25:17 proposing it in fedora 15:25:36 #undo 15:25:36 Removing item from minutes: ACTION by chandankumar at 15:24:41 : snecklifter to propose openstack-macros for fedora 15:25:38 I can get behind not doing it also :) 15:25:38 Removing item from minutes: #action snecklifter to propose openstack-macros for fedora 15:25:38 apevec: iirc, I added support for that in DLRN (because the source repo is the whole github.com/openstack/rpm-packaging) 15:25:59 I'll check that, then 15:26:00 jpena, yeah, we could test on it sourcing pkg directly from rpm-packaging 15:27:18 #action jpena to check inclusion of openstack-macros in RDO Trunk 15:27:51 that's it for me 15:28:42 I think once cleanup is done, we can start porting/enabling python3 packages/ 15:28:43 ? 15:29:17 snecklifter: macros are specific case in Fedora, you need approval from FPC 15:29:35 chandankumar, let's get it FTBFS-clean first 15:29:36 number80: ah ok 15:29:43 apevec: ack! 15:29:45 after that we can discuss adding CI 15:30:02 Well, do not start py3 work until we know *how* we will support python3 15:30:14 number80, in Fedora we know 15:30:27 that's prep for next rhel 15:30:29 this is not just adding lines to spec files, it impacts build system too dependending tech 15:30:36 for rhel7, it's different story 15:30:49 and currently we are not doing it 15:30:51 apevec: yeah, for clients, most work is already done, I was thinking about services and other stuff 15:30:53 on el7 15:31:28 Well, what happens if EL8 is not released before upstream drops py2 ? 15:31:39 That's the part worrying me 15:31:57 don't worry about that, py2 will stay 15:31:59 FWIW SUSE is shipping queens with py3 15:32:03 ok 15:32:10 (discussed with suse yesterday in regards to rpm-packaging) 15:32:27 software factory has Python35-SCL listed 15:32:28 dmsimard: SUSE has their own agenda on py3 15:32:32 dmsimard, not all services actually work with py3, this is still work in progress 15:32:50 just highlighting what they told me their plan was :) 15:32:53 RDO has to support RHEL too 15:33:05 RHEL has no py3 support as of today 15:33:33 chandankumar, right, that works for zuul with limited set of deps, 15:33:39 b/c you need to SCLized and rebuild them all 15:34:04 either way, this is off topic, 15:34:12 Yeah long topic too 15:34:13 Fedora cleanup is first step as a prep 15:34:18 *nods* 15:34:38 Any questions for this topic if not moving to next topic 15:35:10 #topic Using the CentOS extras Ansible 15:35:17 dmsimard: please go ahead :-) 15:35:40 A review caught my attention recently, we upgraded from ansible 2.3.1 to 2.3.2 15:35:47 and it looked like it was *required* 15:35:56 yes, for ceph 15:35:58 so that means we won't be rolling with the ansible provided by rhel/centos extras ? 15:36:10 ceph actually requires >= 2.3.1 15:36:23 so we could avoid pushing 2.3.2 to release 15:36:26 rdo-trunk created openstack/manila-ui-distgit pike-rdo: Update to 2.10.2 https://review.rdoproject.org/r/9469 15:36:29 now that 7.4 is released 15:36:59 it was not clear when 7.4 will be released, so we pushed latest 2.3.2 we had in CBS 15:37:10 to unblock ceph ansible 15:37:56 ok, ideally we would try really hard to use the extras version :) 15:38:23 ansible in Extras could be rebased more frequently (different update policy than baseos) 15:38:31 so testing 2.3.2 in advance is also good 15:38:41 * Duck :-) 15:38:56 Yeah, I guess we can even provide both 15:39:00 2.3.1 is -release 15:39:05 2.3.2 in -testing 15:39:10 yep 15:39:23 (it will require manual tweaking but doable) 15:39:45 why tweaking? 15:39:56 we just don't push 2.3.2 to openstack-release 15:40:06 and 2.3.1 comes from centos extras 15:40:30 it was released today http://mirror.centos.org/centos/7/extras/x86_64/Packages/ansible-2.3.1.0-3.el7.noarch.rpm 15:43:13 ok 15:43:53 Any questions on this topic, if not moving ahead. 15:44:15 dmsimard: Thanks :-) 15:44:26 #topic rdopkg is now in Fedora 25+ and EPEL 7 15:44:34 jruzicka: please go ahead 15:44:42 just a quick announcement 15:45:23 rdopkg is now available from official Fedora 25+ and EPEL 7 repos so you can get it 15:45:34 **sweet** 15:45:35 by just: dnf install rdopkg 15:45:40 jruzicka: so no need to use your copr repo any more? I guess we need to update the website docs 15:45:51 this is good news 15:46:04 yes, the copr repo is now obsolete 15:46:19 great. 15:46:23 I'll use it for testing/bleeding edge builds 15:46:33 jruzicka, which NVR is in f25 ? I still got last update from copr 15:46:39 jruzicka: yeah, update the doc before doing this then :-) 15:46:55 rdopkg docs updates are in review, I'll go through website 15:47:04 ah so I got bleeding version :) 15:47:15 me too 15:47:17 #action jruzicka to update website 15:47:21 dnf info rdopkg --refresh 15:47:25 rdo-trunk created openstack/manila-distgit pike-rdo: Update to 5.0.1 https://review.rdoproject.org/r/9470 15:47:44 you want to disable the copr by 15:47:48 dnf copr disable jruzicka/rdopkg 15:48:23 Name : rdopkg 15:48:24 Arch : noarch 15:48:24 Epoch : 0 15:48:24 Version : 0.45.0 15:48:24 Release : 4.fc25 15:48:25 Size : 69 k 15:48:26 Repo : updates 15:48:31 -4 is Fedora 15:48:36 -3 is last copr version 15:48:51 I'll leave the Fedora version ahead for the time of transition 15:48:58 ack 15:49:30 Finally, CI scripts should also be updated not to use the copr repo. 15:49:47 I assume DLRN will follow shortly after, right jpena? ;) 15:49:57 yep, that's the plan 15:50:01 jruzicka, iirc CI is mostly pip installing rdopkg... 15:50:31 even better ;) 15:50:39 well that's 15:51:18 *that's it 15:51:21 jruzicka: thanks :-) 15:51:32 Moving to next topic 15:51:40 #topic chair for next meeting 15:51:54 Any volunteer up to chair for next meeting? 15:53:12 allright, I'll do it. 15:53:25 #action jruzicka to chair for next meeting 15:53:29 jruzicka: thanks :-) 15:53:43 we still have 7 mins, time to go for open discussion 15:53:50 #topic Open discussion 15:53:54 back to the patches branch 15:54:01 I need dmsimard's time to work on Ansible roles :-) 15:54:04 sorry for missing that, I got lost in codes 15:54:16 so we're keeping the reviews? 15:54:18 I expect a lot of people are rather buried in stuff at the PTG, too. 15:54:37 allright, I'll discuss post-meeting ;) 15:54:39 Also, the network here is *terrible* 15:55:41 All I read on twitter is about the trains and their horns 15:55:52 The trains are indeed very loud. 15:56:03 I think one of them runs through my room. 15:57:45 rbowen: i think near the interview room, there is a long dinning space. 15:58:52 ok well if there is nothing else, small announcement from me 15:59:12 In a blow for RDO project diversity, I have taken a job with Red Hat 15:59:20 ! 15:59:35 Congratulations. And also, curse you for ruining my metrics! ;-) 15:59:36 welcome :-) 15:59:41 snecklifter: congrats :-) Welcome to Red Hat :-) 15:59:44 rbowen: yes, I know, sorry 15:59:49 hehe 15:59:53 snecklifter, congrats :D 15:59:53 snecklifter: I'd say "oh, no" and "oh, yes!" at the same time :) 16:00:00 welcome ;) 16:00:08 thanks all, starting in 3 weeks 16:00:24 where will you be located? 16:00:27 UK 16:01:06 a bit far for me. if you come to other event like DevConf, FOSDEM… 16:01:10 I thought nice to end the meeting on a positive note :) 16:01:15 very very far far from my location :-) 16:01:25 Duck: yes and I can't swim like a duck can 16:01:30 times up 16:01:34 #endmeeting