15:01:47 <apevec> #startmeeting RDO packaging meeting (2015-02-18)
15:01:47 <zodbot> Meeting started Wed Feb 18 15:01:47 2015 UTC.  The chair is apevec. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:47 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:47 <ihrachyshka> o/
15:01:49 <panda> o/~
15:01:55 <apevec> #chair number80
15:01:55 <zodbot> Current chairs: apevec number80
15:02:00 <gchamoul> o/
15:02:03 <apevec> #topic roll-call
15:02:15 <apevec> #info agenda at https://etherpad.openstack.org/p/RDO-Packaging
15:02:21 <number80> o/
15:02:22 <apevec> o/
15:02:32 <ihrachyshka> roll call ?
15:02:32 <ryansb> o/
15:02:33 <rbowen> o/
15:02:51 <eggmaster> o/
15:03:18 <rbowen> Is alphacc here?
15:03:25 <ihrachyshka> o/
15:03:50 <apevec> rbowen, nick is here :)
15:04:04 <jruzicka> o/
15:04:29 <jruzicka> I'll be alternating between RL in unpredictable intervals, so I'm semi-present :)
15:04:49 <apevec> #topic RDO update CI status
15:05:00 * eggmaster nods
15:05:03 <apevec> eggmaster, so we should have cbs source working now?
15:05:23 <apevec> also, jruzicka has rdopkg topic changes done
15:05:23 <ihrachyshka> I get a weird failure just now for neutron update for juno. is it expected to work now?
15:05:34 <eggmaster> apevec: yes, it is working. phase1 is being triggered off internal and external (new) rdo-update events
15:05:38 <apevec> ihrachyshka, not quite hence the topic
15:05:50 <eggmaster> Just need to pull a change over to the phase1 script and it should legit pass/fail afaict
15:06:30 <apevec> eggmaster, ok, let's get this cleared today
15:06:37 <eggmaster> #info rdo-update internal and external events are now triggering phase1, should have legit results shortly after meeting
15:06:50 <apevec> next step would be to try CI 2.0 jobs
15:06:59 <eggmaster> #info eggmaster will retrigger queued recent updates to send them through phase1
15:07:06 <eggmaster> yes
15:07:19 <eggmaster> jruzicka: when will we have a new package with that change in it?
15:07:21 <apevec> eggmaster, but that should be all the same just need to configure them to trigger on topic
15:07:35 <apevec> jruzicka, yeah, anything else you want in 0.25 ?
15:07:45 <apevec> if not, just push the release please
15:07:46 <rbowen> What's the URL that we're using now for the CI status page?
15:07:58 <rbowen> I have several here, and I'm getting confused. Can we get one into the minutes?
15:08:01 <apevec> rbowen, RDO update CI is still internal
15:08:16 <apevec> but we have public daily jobs against production repo at
15:08:28 <apevec> https://prod-rdojenkins.rhcloud.com/
15:08:39 <apevec> #action jruzicka to push rdopkg 0.25
15:08:58 <rbowen> Ok. The one over at centos.org was the one I was unsure about. Thanks.
15:08:58 <apevec> #action apevec to move pending updates from internal gerrit to gerrithub rdo-update.git
15:09:25 <apevec> eggmaster, ^ so you can configure rdo update job to trigger on gerrithub only
15:09:48 <apevec> rbowen, ci.centos is work in progress, Wes was looking at it afaik
15:09:55 <apevec> but no jobs there yet
15:10:56 <apevec> anything else for updates CI ?
15:11:17 <eggmaster> not from me.
15:11:18 <rbowen> Thank you.
15:11:25 <apevec> tl;dr eggmaster and I hope to have post a good news later today!
15:11:37 <apevec> ok, next
15:11:39 <apevec> #topic Kilo Packstack/OPM status
15:11:50 * gchamoul is running ... ;-)
15:11:57 <apevec> gchamoul, so we'll declare current Delorean OPM hopeless
15:12:09 <gchamoul> yes
15:12:16 <gchamoul> unfortunately ...
15:12:27 <apevec> #info current Delorean openstack-puppet-modules is building from all puppet modules master branches
15:12:38 <apevec> #info which does not work with Packstack
15:13:06 <apevec> #action apevec is modifying build_rpm_opm.sh to build from redhat-openstack/OPM master branch
15:13:10 <gchamoul> as Martin told ... packstack need a compliant composition layer to work against OPM master (master for all modules)
15:13:26 <gchamoul> s/need/needs/
15:14:03 <apevec> gchamoul, can you tl;dr "composition layer" was non-puppet initiated ?
15:14:16 <apevec> just as info
15:14:50 <gchamoul> apevec: we can use just use master for all puppet openstack modules ... and be sticked to the commits we used for packstack with opm for the rest
15:15:33 <apevec> interesting idea, but let's try with redhat-openstack/OPM master first
15:16:17 <gchamoul> apevec: that's our problem ... all puppetlabs-* modules that we use ...
15:17:34 <apevec> gchamoul, and they all don't maintain proper backward compatibility?
15:18:06 <gchamoul> apevec: they are moving faster ...
15:18:39 <gchamoul> and are maintained out the puppet-openstack community
15:18:49 <gchamoul> s/out/out of/
15:19:31 <gchamoul> apevec I think we need a packstack branch for delorean ...
15:20:10 <apevec> that might be confusing, but let's keep it as an option
15:20:48 <apevec> I like use master for all puppet openstack modules/pin the rest more
15:20:56 <gchamoul> apevec: we will have all the patches we will be able to backport afterwards ..
15:21:24 <apevec> gchamoul, yeah, but let's first restrict # of trunks to chase
15:21:41 <apevec> we don't track linux kernel trunk for example
15:22:30 <apevec> ok, I think we have way forward now: 1. redhat-openstack/OPM master
15:22:59 <gchamoul> so how can I manage to send patches to pk without to break pk master which sticks to opm/master-patches
15:22:59 <apevec> 2.  master for all puppet openstack modules/pin the rest
15:23:19 <apevec> gchamoul, pk ?
15:23:25 <gchamoul> pk=packstack
15:23:51 <apevec> opm/master-patches not opm/master ?
15:24:28 <apevec> gchamoul, what about creating packstack kilo branch early?
15:24:40 <apevec> and keep that working with opm/master
15:24:57 <gchamoul> apevec: opm/master-branch contains all the patches we includes in the RPM
15:25:25 <gchamoul> apevec: to make testing much easier for us
15:25:27 <apevec> packstack master would be then for tracking all puppet modules' master branches
15:25:42 <gchamoul> apevec: we could do this
15:26:05 <apevec> let's do this then
15:26:15 <apevec> #action gchamoul to create packstack kilo branch
15:26:47 <gchamoul> #action gchamoul to create packstack/opm kilo branches
15:27:25 <Rodrigo_US> does anyone know if staypuft is already stable for production use?
15:28:07 <number80> Rodrigo_US: please wait few minutes, we're having a meeting running :)
15:28:46 <apevec> gchamoul, looking now at opm repo, trying to understand master vs master-patches
15:29:16 <jruzicka> eggmaster, apevec: I was considering adding `rdopkg build` but that's rather big change so I'll release 0.25 with current fixes ASAP
15:29:17 <apevec> gchamoul, master is for updating upstream modules only?
15:29:17 <gchamoul> apevec: master-patches, f22-patches and f21-patches
15:29:27 <apevec> jruzicka, ack
15:29:54 <apevec> gchamoul, yeah, I -patches is clear, just trying to understand why we need patches at all
15:30:05 <eggmaster> jruzicka: +1
15:30:05 <number80> +1
15:30:13 <apevec> gchamoul, so stuff in -patches is what is not merged in upstream puppet modules yet?
15:30:30 <apevec> gchamoul, and you don't want to push that to master branch?
15:30:51 <gchamoul> apevec: to include patches which are still on review and are needed for packaging and testing
15:30:52 <apevec> i.e. master is clean  upstream collection
15:30:55 <apevec> is that right?
15:31:00 <gchamoul> apevec: yep
15:31:09 <apevec> ok, makes sense
15:31:25 <apevec> so we really want opm/master-patches
15:31:39 <apevec> with packstack/master (kilo soon)
15:32:02 <apevec> and packstack new master will be chasing all puppet master branches
15:32:32 <gchamoul> packstack/master will be used for kilo and will play with opm master with all puppet master branches
15:32:39 <Rodrigo_US> number80, ok
15:32:44 <gchamoul> apevec: exactly
15:32:50 <apevec> ok, I'll modify my action then:
15:33:04 <apevec> #action apevec will modify build_rpm_opm.sh to build from redhat-openstack/OPM master-patches
15:33:09 <gchamoul> apevec: yes no need to modify delorean for that
15:33:41 <apevec> gchamoul, still need to, openstack-puppet-modules is a special case
15:33:53 <gchamoul> apevec: dprince needs to stick to OPM master with all puppet master for Tripleo-puppet-elements devs
15:34:17 <apevec> gchamoul, right, this will be a separate Delorean instance
15:34:41 <apevec> it will use rdoinfo from my branch
15:34:46 <gchamoul> ack
15:35:44 <apevec> do we have anyone from triplelo here?
15:36:09 <apevec> derekh, ^ FYI - I can give you tl;dr later so there aren't surprises for you :)
15:36:50 <apevec> slagle, ^ btw how is instack with delorean going?
15:37:14 <apevec> ok, I'll ping them after the meeting
15:37:21 <apevec> #topic EL6 Juno status
15:37:29 <derekh> apevec, ok
15:38:15 <apevec> last week we had ACTION: alphacc will post EL6 Juno Nova spec on the mailing list
15:38:19 * number80 started working on clients
15:38:31 <apevec> #info number80 started working on clients
15:38:53 <apevec> I think alphacc was about to post first spec but I didn't see it yet
15:39:18 <number80> same
15:39:54 <apevec> next step will be to create rpm-juno branch in openstack-packages/nova so that we can review spec changes in gerrithub
15:40:53 <apevec> number80, ok, we can followup with alphacc
15:41:03 <number80> ack
15:41:06 <apevec> #topic open floor
15:41:18 <apevec> any other topic which missed agenda?
15:41:52 <eggmaster> apevec: I'm wondering if there are any known delorean instances building pkgs for rhel(epel) or centos. Or if there any plans/dreams for same.
15:42:13 <apevec> I know rdo-management folks plan one
15:42:19 <number80> \o/
15:42:40 <apevec> I'll try el7 with my forked rdoinfo for opm
15:42:56 <apevec> patches to support centos7 builder were merged in delorean
15:43:09 <apevec> it's just that current instance is f20
15:43:27 <apevec> derekh was looking at running multiple builders in the same instance
15:43:47 <apevec> it's all in docker containers so it should work
15:44:08 <apevec> derekh, ^ there was just one patch missing for multiple builders right?
15:44:19 <apevec> or was that merged in the meantime?
15:45:20 <apevec> btw trunk.rdoproject.org is now pointing to the old Delorean instance
15:45:47 <eggmaster> apevec: great, thanks for that info/status.
15:45:59 <apevec> it has been moved to http://104.130.230.24/f21/report.html
15:46:03 <derekh> apevec, it should now be merged checking
15:46:27 <rbowen> http://trunk.rdoproject.org/ is a Fedora test page. So we still need that DNS record updated, right?
15:46:28 <apevec> rbowen, I've ticket to change IP for  trunk.rdoproject.org
15:46:32 <rbowen> oh, ok. Good.
15:46:52 <derekh> apevec, yup, merged https://review.gerrithub.io/#/c/215887/
15:47:00 <apevec> derekh, cool
15:47:03 <apevec> rbowen, it was http://trunk.rdoproject.org/repos/
15:47:14 <number80> apevec: when will we import Kilo into dist-git ? milestone 1 ?
15:47:30 <apevec> derekh, could you in the meantime setup redirect on OS1 instance?
15:47:37 <apevec> derekh, IT takes ages to change DNS...
15:47:46 <derekh> apevec, yup willdo
15:48:01 <apevec> number80, for RC was my thinking
15:48:11 <apevec> number80, I want clean CI results before import
15:48:18 <apevec> number80, also we need to start sorting new deps
15:48:32 <apevec> we'll need few fedora reviews, I'll start the list...
15:48:37 <rbowen> apevec: Then we should probably put some kind of more welcoming and descriptive landing page there too.
15:48:45 <rbowen> Once the change has been made, that is.
15:48:52 <number80> apevec: makes sense, I'll probably only let new projects going in F23 branch then
15:49:08 <apevec> rbowen, please provide index.html and email to me and derekh
15:49:14 <rbowen> Will do.
15:49:28 <rbowen> #action rbowen will provide index.html landing page for trunk.rdoproject.org
15:50:35 <apevec> number80, ack - but they might have new deps so we'll probably need to start updating oslos
15:50:49 <number80> ok
15:50:57 <number80> I'll monitor them, then
15:50:59 <eggmaster> brb
15:51:25 <apevec> number80, if you have a list, let's put it on etherpad
15:51:35 <apevec> https://etherpad.openstack.org/p/RDO-Trunk
15:51:39 <number80> apevec: atm, only barbican & rally (soon)
15:51:41 <apevec> or separate?
15:51:46 <apevec> rally, nice
15:51:56 <number80> small list so let's have it in the same page
15:51:58 <apevec> eggmaster, will that use tempest-lib ?
15:52:45 <apevec> rbowen, for trunk landing page, important URLs are:
15:52:57 <apevec> * list of latest builds http://trunk.rdoproject.org/repos/report.html
15:53:17 <apevec> * latest (untested!) delorean repo http://trunk.rdoproject.org/repos/current/
15:53:31 <rbowen> ok. Thanks.
15:54:12 <apevec> actually on new instance it's <distro>/ instead of repos/
15:54:27 <apevec> currently distro is only f21
15:54:33 <apevec> centos7 coming soon
15:55:11 <apevec> anything else?
15:55:42 <apevec> if not, thanks everybody!
15:55:45 <apevec> #endmeeting