15:00:53 <jpena> #startmeeting RDO meeting - 2017-01-18
15:00:54 <zodbot> Meeting started Wed Jan 18 15:00:53 2017 UTC.  The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:54 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:54 <zodbot> The meeting name has been set to 'rdo_meeting_-_2017-01-18'
15:00:54 <openstack> Meeting started Wed Jan 18 15:00:53 2017 UTC and is due to finish in 60 minutes.  The chair is jpena. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:57 <openstack> The meeting name has been set to 'rdo_meeting___2017_01_18'
15:01:11 <jpena> remember to add topics to the agenda: https://etherpad.openstack.org/p/RDO-Meeting
15:01:16 <jpena> #topic roll call
15:01:45 <apevec> o/ at least partially
15:01:47 <jpena> #chair apevec rbowen
15:01:48 <rbowen> o/
15:01:48 <zodbot> Current chairs: apevec jpena rbowen
15:01:48 <openstack> Current chairs: apevec jpena rbowen
15:01:53 <dmsimard> \o I'm here but conflicting with another meeting
15:01:57 <rbowen> I can't figure how it's a week since the last one.
15:01:59 <jpena> #chair dmsimard
15:02:00 <zodbot> Current chairs: apevec dmsimard jpena rbowen
15:02:01 <openstack> Current chairs: apevec dmsimard jpena rbowen
15:02:38 <number80> o/
15:02:47 <trown> o/
15:02:55 <jpena> #chair trown number80
15:02:56 <zodbot> Current chairs: apevec dmsimard jpena number80 rbowen trown
15:02:56 <openstack> Current chairs: apevec dmsimard jpena number80 rbowen trown
15:03:15 <jruzicka> \o
15:03:29 <jpena> #chair jruzicka
15:03:29 <zodbot> Current chairs: apevec dmsimard jpena jruzicka number80 rbowen trown
15:03:29 <openstack> Current chairs: apevec dmsimard jpena jruzicka number80 rbowen trown
15:03:44 <jpena> let's go!
15:03:45 <jpena> #topic Ceph Hammer (EOL) with Mitaka
15:04:01 <jpena> who added this?
15:04:02 <dmsimard> that's mine
15:04:30 <dmsimard> Ceph Hammer is EOL'd since November (although "actual date" has not been updated yet in http://docs.ceph.com/docs/master/releases/ )
15:05:15 <dmsimard> I just wanted to agree and formalize whether or not we're going to be officially shipping or testing jewel against Mitaka
15:05:23 <apevec> yeah, iirc ktdreyer said there will be one more EOL release?
15:05:40 <apevec> dmsimard, we are not shipping it, storage SIG is
15:05:44 <dmsimard> Jewel is known to work with Mitaka but we are not testing it anywhere - not in puppet-openstack-integration, not in TripleO, or anything
15:06:01 <apevec> so it's their decision
15:06:20 <apevec> but we could get involved, there's cry-for-help on centos-devel
15:06:26 <dougbtv> o/
15:07:01 <chandankumar> \o/
15:07:19 <apevec> dmsimard, re. testing - I think upstream puppet ci is not ready to move to Ceph Jewel
15:07:20 <dmsimard> So, we're not going to be testing jewel on Mitaka in our various CI then - just wanted to make that clear.
15:07:25 <dmsimard> mwhahaha, EmilienM: can you ack ^ ?
15:07:26 <apevec> and tripleoci probably the same
15:07:42 <apevec> yeah, we want their acks
15:07:46 <EmilienM> right
15:07:57 <EmilienM> Mitaka puppet CI will never test Jewel
15:08:12 <apevec> alright then it's clear
15:08:12 <dmsimard> trown|mtg, weshay: can you ack ^
15:08:45 <trown|mtg> ya, dont see why we would do that at this point
15:09:07 <dmsimard> ok
15:09:54 <dmsimard> #agreed While Jewel is known to work with RDO Mitaka, RDO does not currently test it and has no plans on testing it until Mitaka is EOL
15:09:57 <dmsimard> fair statement? ^
15:10:09 <dmsimard> er, hang on
15:10:10 <apevec> we just need to "fix" storage sig to keep hammer around
15:10:11 <dmsimard> #undo
15:10:11 <openstack> Removing item from minutes: #agreed While Jewel is known to work with RDO Mitaka, RDO does not currently test it and has no plans on testing it until Mitaka is EOL
15:10:12 <zodbot> Removing item from minutes: AGREED by dmsimard at 15:09:54 : While Jewel is known to work with RDO Mitaka, RDO does not currently test it and has no plans on testing it until Mitaka is EOL
15:10:18 <trown|mtg> ya, that reads to me that we will test it after Mitaka is EOL :P
15:10:55 <leifmadsen> o/
15:11:14 <leifmadsen> +1
15:11:25 <dmsimard> #agreed Ceph Hammer is currently what RDO tests with the Mitaka release. Ceph Hammer is all but EOL. While Jewel is known to work with RDO Mitaka, RDO does not currently test it and has no plans on testing it until Mitaka is EOL.à
15:11:27 <dmsimard> damnit
15:11:29 <dmsimard> #undo
15:11:38 <dmsimard> #agreed Ceph Hammer is currently what RDO tests with the Mitaka release. Ceph Hammer is all but EOL. While Jewel is known to work with RDO Mitaka, RDO does not currently test it and has no plans on testing it until Mitaka is EOL.
15:11:38 <apevec> 3rd lucky
15:11:38 <trown|mtg> haha
15:11:58 <dmsimard> ok we can move on
15:12:01 <apevec> hold on
15:12:18 <apevec> we need action to work with storage sig to ensure ceph hammer is available
15:12:30 <apevec> also updated to that latest EOL release when it happens upstream
15:12:40 <dmsimard> We're not going to get that *here*
15:12:40 <apevec> ktdreyer, ^ is that still planned?
15:14:08 <amoralej|lunch> o/
15:19:25 <EmilienM> we can have a poi job
15:19:32 <apevec> next week is Ocata freeze, we should get them released
15:19:32 <EmilienM> a periodic maybe?
15:19:55 <apevec> EmilienM, can periodic be hacked to run with this additional repo?
15:20:00 <EmilienM> everything is possible in poi :D
15:20:26 <apevec> what about tripleoci ?
15:20:51 <EmilienM> apevec: same
15:20:55 <EmilienM> hack something in tripleo-ci repo
15:20:59 <amoralej> apevec, are we shipping libvirt 2.5.0 ?
15:21:11 <apevec> ah no, that was experimental build, I'll remove it
15:21:22 <apevec> we use base EL7 libvirt
15:21:24 <EmilienM> libvirt-daemon-kvm-2.0.0-10.el7_3.2.x86_64
15:21:32 <EmilienM> amoralej: that's what I have
15:21:36 <apevec> yeah that is base EL7
15:21:47 <apevec> I'll untag 2.5.0 from pending
15:21:49 <amoralej> there is a new 2.5 in -pending, that's why i asked EmilienM
15:21:51 <amoralej> yeah
15:21:57 <EmilienM> oh ok
15:22:04 <EmilienM> we can easily test pending stuff with poi
15:22:11 <EmilienM> we could do it in RDO CI though
15:22:28 <apevec> ok, so who can hack in tripleoci to add common-pending?
15:22:31 <EmilienM> dmsimard already did this process for our promotion pipeline
15:22:38 <EmilienM> apevec: yes kindof
15:22:55 <apevec> yeah, weirdo has passed w/ pending
15:22:58 <apevec> dmsimard, ^ right?
15:23:15 <apevec> actually that was before mariadb update, I tagged 10.1.20 today
15:23:30 <dmsimard> weirdo tested ovs 2.6.1 successfully
15:23:36 <dmsimard> the link to the job is somewhere in that thread
15:23:38 <EmilienM> ship it then
15:23:46 <apevec> dmsimard, I'll untag libvirt 2.5.0 then ask you to rerun it
15:23:46 <dmsimard> there was one failure and it was unrelated, some cinder volume thing iirc
15:23:48 <trown|mtg> I am not sure how relevant the weirdo jobs are for that repo though... seems like every time we push changes there tripleo gets broken
15:23:54 <rdogerrit> mathieu bultel created rdoinfo: Enable ansible-pacemaker module package  https://review.rdoproject.org/r/4351
15:24:05 <apevec> trown|mtg, that's why I'm asking for tripleoci feedback w/ pending
15:24:13 <dmsimard> trown|mtg: I agree, that's why I've asked for help on testing tripleo with it multiple times :(
15:24:21 <EmilienM> trown|mtg: ovs in poi or ovs in tripleo would have same results I think
15:24:46 <dmsimard> Also, I'm going to sound like a broken record and repeat myself but installing from scratch is one thing but upgrading is another thing entirely and worries me
15:24:49 <EmilienM> dmsimard: well, i think it's a 5 lines patch in tripleo-ci
15:25:16 <trown|mtg> hmm, ya I didnt think about testing it with a tripleo-ci review
15:25:22 <trown|mtg> I can take an action for that
15:25:35 <trown|mtg> #action trown submit a review to tripleo-ci to test pending repo
15:26:07 <apevec> excellent, thanks!
15:26:29 <apevec> I'll ping you when pending is cleaned of experimental builds
15:26:29 <trown|mtg> we do need a longer term solution that is easier to integrate into some automation for changes to that repo, but that is the part I don't have cycles to personally work on at the moment
15:26:55 <apevec> trown|mtg, yes. We need something ad-hoc to unblock current updates
15:27:12 <apevec> we'll be adding automation for deps updates, details TBD
15:27:23 <apevec> but number80 is already on it :)
15:28:35 <jpena> next?
15:28:51 <apevec> yes
15:29:12 <jpena> #topic Still looking for talks for CentOS Dojo in Brussels
15:29:14 <rbowen> If 1) you're going to be in Brussels on Friday, February 3rd and 2) you like talking, the CentOS dojo (link in agenda) is still a little short on content.
15:29:48 <rbowen> Talks should be CentOS-centric, rather than OpenStack centric, but that still leaves a lot of topics.
15:30:02 <rbowen> Contact me if you have something in mind.
15:30:05 <rbowen> /EOL
15:31:13 <jpena> #topic Mitaka: Should CI be using KVM from virt sig (>=2.6) ?
15:31:31 <dmsimard> I just came across this so I sneaked it in
15:31:35 <apevec> yes, are we not?
15:31:43 <dmsimard> Newton was the first release to *enforce* KVM >=2.6
15:31:52 <dmsimard> virt sig was not bundled in rdo-release
15:31:53 <jpena> yes, we should. Anything else is asking for trouble with CentOS 7.3
15:31:54 <dmsimard> for mitaka
15:32:14 <dmsimard> ok, I'll update weirdo to use it for Mitaka.
15:32:25 <dmsimard> it was using base OS
15:32:35 <dmsimard> qemu-kvm-1.5.3-126.el7.x86_64
15:32:39 <jpena> I can prepare a PR for the rdo-release rpm
15:33:06 <dmsimard> Implying users might have to ugprade from <2 to >=2.6
15:33:12 <dmsimard> I don't know
15:33:54 <dmsimard> maybe we can communicate on the different MLs that users are encouraged to use >=2.6 with mitaka on 7.3
15:34:02 <dmsimard> without necessarily enforcing it
15:34:26 <rdobot> [sensu] NEW: master.monitoring.rdoproject.org - check-delorean-master-current @ http://tinyurl.com/zqowcwb |#| Build failure on centos7-master/current: tripleo-ui: http://trunk.rdoproject.org/centos7-master/report.html
15:35:01 <dmsimard> I have nightmares about upgrading qemu-kvm in production but that was from experience a while back from icehouse to juno on Ubuntu :)
15:35:11 <apevec> yeah, let's not change rdo-release-mitaka at this point
15:36:21 <dmsimard> ok, that's it for me
15:36:41 <jpena> #action dmsimard to update weirdo to use KVM from virt sig in Mitaka jobs
15:36:52 <jpena> #topic chair for next meeting
15:36:56 <jpena> any volunteer?
15:37:03 <dmsimard> off topic but gfidente can you join #centos-devel to chat about Ceph storage SIG involvment
15:37:09 <chandankumar> chandankumar:
15:37:16 <chandankumar> i will volunteer for the same
15:37:27 <jpena> thanks chandankumar :)
15:37:38 <jpena> #action chandankumar to chair the next meeting
15:37:41 <jpena> #topic open floor
15:37:41 <gfidente> dmsimard ack thanks
15:37:53 <rdogerrit> Jakub Ruzicka proposed rdopkg: patch: refactor to properly handle all cases  https://review.rdoproject.org/r/4291
15:38:01 <jruzicka> need eyes on that ^
15:38:18 <jruzicka> abregman|mtg, it's now noninteractive per your request ^
15:39:01 <jruzicka> much needed `rdopkg patch` fix including unit tests
15:39:59 * number80 is sorry looking for a lost ISP technician and concierge
15:41:26 <rdogerrit> Ken Dreyer proposed rdopkg: guess: handle "VX.Y.Z" Git tags  https://review.rdoproject.org/r/4345
15:42:31 <jpena> if there are no more topics, we can close the meeting (15 minutes more life!)
15:43:26 <jpena> 3
15:43:27 <jpena> 2
15:43:27 <jpena> 1
15:43:34 <jpena> #endmeeting