15:05:48 <apevec> #startmeeting RDO packaging meeting (2015-02-11)
15:05:48 <zodbot> Meeting started Wed Feb 11 15:05:48 2015 UTC.  The chair is apevec. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:05:48 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:05:59 <apevec> #chair number80
15:05:59 <zodbot> Current chairs: apevec number80
15:06:10 <apevec> #topic rollcall
15:06:14 <apevec> o/
15:06:19 <ryansb> \o
15:06:19 <number80> o/
15:06:27 <xaeth> \o
15:06:29 <apevec> #info agenda at https://etherpad.openstack.org/p/RDO-Packaging
15:08:05 <apevec> agenda is boring, almost the same as last week :)
15:08:07 <eggmaster> o/
15:08:14 <rbowen> o/
15:08:31 <apevec> #topic 2014.2.2 updates, status in f22/RDO
15:08:33 <xaeth> can add the openstack-barbican package to the agenda ;)
15:08:46 <xaeth> not that i really have any thing in particular to say about it
15:08:46 <apevec> xaeth, please add in etherpad
15:09:00 <number80> xaeth: anyway welcome :)
15:09:30 <apevec> releated to Juno updates is that F22 was branched yesterday
15:09:54 <apevec> so update process for now is to keep Fedora master Juno and update there first
15:10:00 <apevec> then merge to f22 and build there
15:10:15 <apevec> EL7 builds will come from CentOS CBS Koji
15:10:23 <apevec> number80 and I are handling that
15:10:51 <apevec> We'll start importing Kilo from Delorean to Fedora Rawhide in Kilo RC time frame
15:11:09 <apevec> #info keep Fedora master Juno and update there first, then merge to f22 and build there
15:11:29 <apevec> #info EL7 builds will come from CentOS CBS Koji apevec and hguemar are handling that
15:11:50 <apevec> #info Kilo import from Delorean to Fedora Rawhide in Kilo RC time frame
15:12:09 <apevec> now 2014.2.2 updates status:
15:12:16 <apevec> glance sahara cinder keystone trove heat neutron are done
15:12:35 <apevec> horizon has hit bad deps, mrunge is on it
15:12:45 <apevec> ceilo and nova should be coming today
15:12:57 <apevec> #info ETA to have all 2014.2.2 builds done today
15:13:01 <number80> apevec: should we submit updates through gerrithub ? seems that I'm the only who did that
15:13:15 <number80> or keep using the old CI ?
15:13:22 <apevec> number80, yeah, everybody sould update rdopkg
15:13:27 <number80> ack
15:13:42 <number80> then, I'll push the remaining build I made in CBS
15:13:54 <eggmaster> number80: CI will be triggered from either (old vs gerrithub)
15:13:58 <apevec> #info please update to the latest rdopkg 0.24:  dnf copr enable jruzicka/rdopkg
15:14:29 <apevec> number80, yeah, I'll merge/cleanup updates repo
15:14:39 <eggmaster> It can fail in two ways now ;P juno/f21 doesn't pass right now for anything.
15:14:39 <number80> *nods*
15:15:13 <apevec> packstack/opm update should fix fedora juno
15:15:24 <eggmaster> apevec: oh, sweet.
15:15:41 <apevec> #info packstack/opm update should fix fedora juno issue with kernel 3.18
15:16:06 <apevec> I'm watching it in CI
15:16:22 <apevec> anything else for 2014.2.2 updates?
15:16:49 <number80> nope
15:17:06 <apevec> weshay, eggmaster, once they all pass Phase1, I'll create new rdo testing repo (aka stage) and we'll rely on stage CI instead of Phase2
15:17:12 <apevec> is that ok with you?
15:17:16 <eggmaster> ack
15:17:40 <apevec> ok, next topic
15:17:47 <apevec> #topic Kilo-2 snapshot of http://trunk.rdoproject.org/repos/current/
15:18:09 <apevec> Kilo Packstack/OPM status
15:18:16 <apevec> gchamoul, ^
15:18:48 <apevec> gchamoul, as discussed earlier, we'll abandon OPM from all masters
15:19:03 <apevec> gchamoul, can you confirm that github/opm master is good for Kilo?
15:19:44 <apevec> ok, I'll follow up with Gael later
15:20:06 <apevec> basically steps 2 (CI) and 3 (publishing good K2 snapshot) depend on it
15:20:42 <apevec> CI job is defined but will need to change repo URL from "current" to snapshot URL (TBD)
15:20:55 <apevec> weshay, eggmaster ^ that's job parameter I hope?
15:21:44 <weshay> apevec, ya.. that is a param
15:21:51 <apevec> cool
15:22:21 <apevec> #action apevec to  follow up with gchamoul re. Kilo Packstack/OPM
15:22:47 <apevec> next topic
15:22:57 <apevec> #topic EL6 Juno updates
15:23:34 <apevec> alphacc, ^ any good news, have you found folks to work on this?
15:24:13 <apevec> one more follow up
15:24:22 <apevec> number80, ^ can you take action to follow up that?
15:24:50 <number80> #action follow up with alphacc about Juno/EL6 packages
15:24:56 <apevec> thanks
15:25:19 <apevec> #topic Review Request: openstack-barbican
15:25:20 <number80> I'm only waiting on decision on which python stack to start so I could work on the clients
15:25:32 <apevec> #undo
15:25:32 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x28edc390>
15:25:49 <apevec> number80, which py stack you mean?
15:26:19 <apevec> EL6 has py26 what else?
15:26:26 <apevec> don't tell me you're considering SCL ?
15:26:26 <number80> apevec: they wanted to try the //-installable python27, so I need to sync with folks about it
15:26:29 <apevec> or python27 !
15:26:34 <apevec> no!
15:26:41 <number80> ack
15:26:44 <apevec> that will be unmaintanable
15:26:51 <apevec> you'd have to rebuild ALL python deps
15:27:02 <apevec> instead of just newer ones
15:27:05 <number80> yes, that's what I told them
15:27:08 <apevec> libvirt-pyton comes to mind
15:27:20 * xaeth is trying to avoid that for our internal barbican deploy as well
15:27:40 <apevec> and not sure libvirt in el6 can work with standalone libvirt-python on pypi
15:27:56 <number80> good point
15:28:10 <apevec> ok
15:28:11 * alphacc late, reading.
15:28:34 <apevec> ok, let's keep the topic for alphacc to catch up
15:29:07 <apevec> Juno is still official py26 compatible
15:29:35 <alphacc> so I have almost nova done, I need to import all epel dependencies. Do we have a github branch already ?
15:29:36 <apevec> and for Kilo please do consider moving to EL7
15:30:14 <apevec> alphacc, not yet, I was waiting for .2 Juno rebases to finish before pushing "juno" branch to github/openstack-packages
15:30:39 <apevec> alphacc, and nova is the one of those not done yet :(
15:30:51 <apevec> but should be today
15:31:05 <number80> alphacc: if you need help with dependencies, we could sync up
15:31:08 <alphacc> ok it's good I have more time to finish then ;)
15:31:37 <alphacc> I can drop the spec on the mailing later today.
15:31:39 <number80> since we agree on using base python, I won't wait anymore for the clients
15:33:08 <alphacc> number80: my goal is to be able to do a funcional build with epel enabled and then we can diff.
15:33:10 <apevec> #action alphacc will post EL6 Juno Nova spec on the mailing
15:33:29 <number80> alphacc: ack
15:33:32 <alphacc> thx and sorry for being late.
15:34:08 <apevec> np, thanks for the update
15:34:15 <apevec> and last topic
15:34:28 <apevec> #topic Review Request: openstack-barbican
15:34:43 <apevec> #link https://bugzilla.redhat.com/show_bug.cgi?id=1190269
15:34:46 <number80> review's pending
15:34:50 <apevec> xaeth, thanks for the review
15:34:56 <xaeth> np
15:35:05 <number80> xaeth: are the EL6 bits required ?
15:35:07 <apevec> I've summary in comment 2
15:35:19 <apevec> regarding openstack/fedora mapping
15:35:46 <xaeth> number80, so for our internal deploy we currently needed to be on EL6 due to HSM drivers
15:36:11 <apevec> cool, so this will be an example for EL6 Juno
15:36:19 <xaeth> i went and got it all running on py2.6, and then they pointed out that since they are gonna be running kilo+ they can't promise py2.6 compatability
15:36:20 <number80> xaeth: makes sense :)
15:36:44 <apevec> yeah, kilo removed py26 jobs
15:36:49 <xaeth> ya :(
15:37:08 <xaeth> so right now we are pushing the vendor for el7 support cause i really dont want to find everything i need to add to the py2.7 scl
15:37:36 <number80> xaeth: which vendor ? maybe we could help
15:37:57 <xaeth> umm... you'd think i would know that, but i dont ;)
15:37:59 <apevec> you could suggest vendor to opensource their drivers :)
15:38:08 <xaeth> they are targetting q2
15:38:16 <xaeth> if only apevec
15:38:24 <apevec> yeah I know
15:39:06 <apevec> ok so number80 just to confirm you'll review barbican?
15:39:21 <number80> yes
15:39:39 <apevec> number80, make yourself action for the minutes please :)
15:39:49 <xaeth> i did run the review tool and there were some thing i couldn't address readily
15:39:55 <number80> #action hguemar reviewing openstack-barbican
15:40:19 <xaeth> apevec, i think its a Luna SA from SafeNet
15:41:16 <number80> xaeth: nothing that we can't fix soon :)
15:41:17 <apevec> xaeth, dunno how number80 wants to handle review but you could paste issues in review bz
15:41:47 <apevec> better to have the whole history in bz for posterity
15:42:03 <xaeth> kk
15:42:18 <number80> I'm currently trying to test if the package is working, there are no blockers so far
15:42:22 <xaeth> tbh main reason i couldnt address readily is i havent done the leg work to be an openstack contributor
15:42:38 <apevec> CLA thing?
15:42:45 <xaeth> and reading
15:43:08 <apevec> yeah, it's special little ecosystem
15:43:19 <number80> xaeth: you just have to push the second patch (PBR is a PITA but we have to maintain it until oslo.version is revived)
15:43:22 <ihrachyshka> speaking of community contributors, we have a neutron-gbp package contributed by Rob Kukura (now Cisco) in Fedora, do we want it in RDO/Delorean?
15:43:46 <number80> ihrachyshka: good point, it should be
15:43:53 <apevec> ihrachyshka, it is in RDO Juno already!
15:44:05 <xaeth> number80, kk.. i was actually gonna try and push both patches and the unit files so that was not the spec files problem anymore
15:44:16 <apevec> ihrachyshka, https://trello.com/c/uoullOKB/26-group-based-policy-neutron-addons-an-example-of-public-participation
15:44:17 <ihrachyshka> number80, not that I'm aware of recent developments there, so I'm not sure I'll be able to baby sit it in delorean effectively. but we can try.
15:44:21 <xaeth> they also technically dont have  way to run barbican
15:44:25 <ihrachyshka> apevec, ah, cool. so delorean
15:44:41 <xaeth> their barbican.sh was more of a dev bootstrapper. and in upstream they have a bunch of uwsgi bits
15:44:51 <number80> ihrachyshka: we expect Robert to maintain it or this whole community-based governance would have no meaning
15:44:55 <apevec> ihrachyshka, right, I'll add it to rdoinf and create repos
15:45:00 <xaeth> any suggestions on best approach for an out of the box path on that is very welcome
15:45:19 <ihrachyshka> number80, yeah, I get it. but maybe he is interested in making it delorean aware. you could reach him.
15:45:30 <number80> xaeth: we could discuss this by mail with nkinder and alee
15:45:37 <ihrachyshka> apevec, I don't think we should do this without Rob's approval
15:45:40 <xaeth> kewl
15:45:58 <apevec> ihrachyshka, I'll add him to review rdoinfo PR of course
15:46:07 <apevec> and point to Delorean docs etc
15:46:21 <ihrachyshka> apevec, ok, I leave you clearing this up :D
15:48:21 <apevec> yeah, I'll be The Cleaner
15:48:37 <apevec> "I'm Winston Wolf - I Solve Problems"
15:48:48 <eggmaster> :)
15:49:00 <number80> ^^
15:49:08 <apevec> ok do we need last topic
15:49:15 <apevec> #topic open floor
15:50:15 <ryansb> There's nothing you need from project folk for k-2, right?
15:51:56 <number80> nope
15:52:14 <number80> apevec lost network so he asked me to close the meeting
15:52:24 <number80> thanks for attending and hope to see you next week :)
15:52:28 <number80> #endmeeting