15:02:50 <apevec> #startmeeting RDO packaging meeting (2015-03-04)
15:02:50 <zodbot> Meeting started Wed Mar  4 15:02:50 2015 UTC.  The chair is apevec. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:50 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:03:01 <apevec> #chair number80 jruzicka
15:03:01 <zodbot> Current chairs: apevec jruzicka number80
15:03:07 <apevec> #topic roll call
15:03:14 <apevec> \[]
15:03:24 <eggmaster> \o
15:03:28 <thrash> \o
15:03:36 <eggmaster> brb!
15:03:50 <Rodrigo_US> Egyptian[Home], ifconfig phy-br-eth1
15:03:50 <Rodrigo_US> phy-br-eth1: error fetching interface information: Device not found
15:04:20 <number80> o/
15:04:28 <jruzicka> o/
15:04:39 <Rodrigo_US> Egyptian[Home], ifconfig int-br-eth1
15:04:40 <Rodrigo_US> int-br-eth1: error fetching interface information: Device not found
15:04:41 <alphacc> hi all
15:04:42 <Egyptian[Home]> \o
15:05:08 <xaeth> o/
15:05:12 <jruzicka> Rodrigo_US, we have a meeting here now, please wait until it's over.
15:06:06 <apevec> any Packstack folks, jpena, gchamoul ?
15:06:15 <gchamoul> o/
15:06:36 <apevec> ok, let's start
15:06:45 <apevec> #topic review action items
15:07:01 <apevec> ...from last week: http://meetbot.fedoraproject.org/rdo/2015-02-25/rdo.2015-02-25-15.03.html
15:07:47 <apevec> 1. I'm still following up w/ eggmaster re. RDO update CI, we're debugging last item (voting)
15:08:08 <eggmaster> ack
15:08:11 <gchamoul> apevec: jpena is on his way !
15:08:18 <jpena> I'm in
15:08:23 <apevec> 2. OPM spec changes in Delorean were merged, we're now building from master-patches
15:08:44 <apevec> 3. puppet-keystone was fixed upstream, and will be included in next OPM master-patches rebase
15:08:46 <apevec> jpena, right?
15:09:04 <jpena> apevec: right, that patch did not merge, but a different one did
15:09:05 <apevec> any other issues left w/ puppet modules for Kilo?
15:09:19 <jpena> apevec: we have a few patches under review
15:10:07 <jpena> https://review.openstack.org/160845 and https://review.openstack.org/159548
15:10:39 <jpena> once both are ready, we should have a working OPM set
15:10:48 <social> jpena: also https://review.openstack.org/#/c/106144/13
15:13:30 <apevec> jpena, ok, but you could pull them temporary onto master-patches before they merge upstream right?
15:13:49 <rbowen> I'm here, but fairly sick. But I'm watching.
15:14:00 <jpena> apevec: I guess so. social, any issue with that?
15:14:02 <number80> rbowen: take care !
15:14:08 * eggmaster has sad for rbowen
15:14:53 <social> jpena: no, I think as I'm stuck on keystone juno bug I have enough throughput to do the master-patches rebase so feel free to merge https://github.com/redhat-openstack/openstack-puppet-modules/pull/269
15:14:55 <apevec> rbowen, get well soon! (we'll skip landing page action item, it's low prio anyway)
15:15:16 <social> apevec: jpena: https://github.com/redhat-openstack/openstack-puppet-modules/pull/269 will move us to masters of all the puppet modules
15:15:27 <rbowen> Gah! I'm sorry. Not sure how that slipped through the cracks. :(
15:15:47 <jruzicka> I don't agree it's low priority :-p
15:16:03 <apevec> jruzicka, then propose one :)
15:16:17 <jruzicka> it's there already in agenda
15:16:23 <jruzicka> for this week by me :-p
15:16:52 <apevec> social, jpena - can we merge that PR without those 3 fixes?
15:17:09 <jpena> ls
15:17:17 <jpena> (sorry, wrong window)
15:17:48 <apevec> actually, puppet-nova has been merged, and glance has one +2
15:17:58 <apevec> and 3rd is packstack
15:18:56 <apevec> and in gate, but upstream Zuul has partial outage today...
15:19:21 <jpena> apevec: yes, we can merge it, then add the patches to OPM master-patches while they are approved.
15:19:27 <apevec> ack
15:20:33 <apevec> (OT Zuul Queue lengths: 1618 events)
15:20:51 <jruzicka> phew, cloudy
15:21:02 <apevec> yeah
15:21:34 <apevec> ok, lemme skip to my action 6. - turned out ovs 2.1 doesn't help, we'll need to update to 2.3
15:21:58 <apevec> once EL 7.1 is available (needs updated kernel)
15:22:25 <apevec> 4. and 5. we have on agenda today
15:22:36 <apevec> (el6 juno status and trunk.rdo)
15:22:44 <alphacc> 4: I published a repo (self contained , epel not needed) : http://linuxsoft.cern.ch/tmp/iaas6-juno-devel/ we are using it for our I -> J test migration, including all srpm (nova, ceilometer). I didn't get time to create/send all diffs to the ML but working on it (neutron is next and rebuilding in CBS should start soon if ok with sig members).
15:23:17 <apevec> ok, let's move to that topic
15:23:24 <apevec> #topic EL6 Juno status
15:23:26 * number80 has some news too
15:23:42 <apevec> #info from alphacc published a repo (self contained , epel not needed) : http://linuxsoft.cern.ch/tmp/iaas6-juno-devel/ we are using it for our I -> J test migration, including all srpm (nova, ceilometer)
15:24:04 <number80> #info EL6 clients are being imported into CBS
15:24:14 <apevec> #action alphacc will send spec diffs to the rdo-list
15:24:28 <apevec> number80, did you get new targets created?
15:24:42 <number80> apevec: nope, using cloud6-el6
15:24:43 <apevec> or you're just using cloud-el6
15:24:48 <apevec> ack
15:24:55 <apevec> number80, any feedback on your proposal?
15:25:10 <apevec> I missed cloud sig meeting last week
15:25:21 <number80> apevec: not yet, if I don't get feedback, I'll just open a ticket
15:25:27 <apevec> ack
15:25:55 <apevec> number80, please make yourself an action item for minutes :)
15:25:58 <number80> #action hguemar move forward with CBS build targets
15:26:09 <alphacc> let me know I can create targets per project as soon as i get the ticket.
15:26:12 <number80> +1
15:26:32 <number80> alphacc: yes, I'll put you as assignee :)
15:26:48 <apevec> ok, that's good progress!
15:26:54 <apevec> now kilo
15:27:01 <apevec> #topic RDO Kilo prep
15:27:01 * number80 is eager to play with Kilo
15:27:27 <apevec> along with OPM/packstack fixes, it was uncovered Delorean packages are missing new deps in spec
15:27:52 <apevec> we're using "new-deps" topic for reviews fixing that: https://review.gerrithub.io/#/q/topic:new-deps
15:28:15 <apevec> keystone one is left b/c of missing new dep in EL7: python-cryptography
15:28:30 <apevec> (it's like, what, 3rd crypto lib ...bah)
15:28:52 <apevec> anyway, we need to update oslo clients etc in Rawhide for Kilo
15:29:18 <apevec> I saw number80 working on it, we'll need to update the list in RDO-Trunk pad
15:30:05 <apevec> jruzicka, number80, do we have any scripts/tools to compare openstack/requirements against Rawhide?
15:30:25 <number80> not yet
15:30:27 <apevec> so it would print what's out of date for Kilo in Fedora?
15:30:51 <jruzicka> not yet but
15:31:08 <apevec> would it fit into rdopkg swiss-army knife?
15:31:13 <jruzicka> I wanted to write something for rdopkg
15:31:14 <jruzicka> ;)
15:31:21 <apevec> awesome
15:31:25 <jruzicka> Just never got clear vision on exact form
15:31:42 <jruzicka> there is `rdopkg reqdiff` which diffs requirements.txt in semi-smart way
15:31:57 <apevec> yeah, I'm not sure either, let's start brainstorming ideas, maybe not now but on rdo-list ?
15:32:12 <xaeth> python-cryptography is barbican dep too.  i thought it was in fedora already
15:32:12 <jruzicka> I thought about comparing requirements.txt with .spec Requires
15:32:30 <jruzicka> but ultimately, I think we should have a simple way to answer the question
15:32:42 <apevec> jruzicka, yeah, although I think I saw it confused with latest PEP440 expressions...
15:32:43 <jruzicka> "Is this dep present in RDO? At which version?"
15:32:54 <apevec> jruzicka, right
15:33:24 <jruzicka> apevec, oh realllly? remember which project? gimme reproducer next time you see it fail
15:33:26 <apevec> jruzicka, let's open trello card, that's an excellent title
15:33:36 <number80> *nods*
15:33:38 <apevec> jruzicka, I'll try to remember
15:33:38 <jruzicka> OK, I'll open.
15:34:01 <apevec> #action jruzicka to create rdopkg "Is this dep present in RDO? At which version?" subcommand
15:34:27 <apevec> xaeth, it is in Fedora but failed to build in epel7
15:34:41 <apevec> b/c of too old build deps in base EL7
15:34:50 <xaeth> apevec hrm.  i thought i had done that too.  ok
15:34:52 <apevec> I've started Copr for such cases
15:35:10 <apevec> temporary one: https://copr.fedoraproject.org/coprs/apevec/RDO-Kilo/builds/
15:35:38 <apevec> I'll create rdo-release-kilo-0 for bootstraping RDO Kilo
15:35:57 <apevec> which will install juno + temp. kilo with new/updated deps
15:36:15 <jruzicka> nice :)
15:36:34 <apevec> #action apevec to publish rdo-release-kilo-0.rpm for bootstraping RDO Kilo
15:37:39 <apevec> I'll have it ready for testing today
15:37:54 <apevec> ok, next topic is related
15:38:06 <apevec> #topic Delorean specs
15:38:27 <apevec> jruzicka, you added that?
15:38:43 <apevec> I answered in etherpad: we want trunk packages without patches
15:38:50 <jruzicka> apevec, yeah
15:39:16 <apevec> I started removing patching out pbr and adding it as runtime dep (giving up that fight :)
15:39:30 <jruzicka> that's a new information for me, but that quite answers it all for me ;)
15:39:42 <apevec> jruzicka, oslo.version was recently archived
15:39:57 <apevec> jruzicka, it's just not worth to fight it
15:40:11 <jruzicka> yeah, that's the upstream plan - the evil of pbr is too small now to justify a big fight ;)
15:41:10 <apevec> jruzicka, but while at it: there might be room for rdopkg in Delorean, now it uses plain rpmbuild
15:41:45 <jruzicka> apevec, I have the source open right now and I was surprised by the rpmbuild indeed ;)
15:42:04 <apevec> it could use mock, although builders are already docker containers
15:42:07 <jruzicka> but it's inside docker image and pretty lightweight
15:42:12 <apevec> yes
15:42:30 <apevec> I'm just not sure if container is reset for each build?
15:42:33 <jruzicka> only thing I wondered about
15:43:11 <jruzicka> if the changes on delorean disgits will be easily cherry-pickable in fedora distgit
15:43:26 <jruzicka> but we'll see when that happens, right
15:43:30 <apevec> it must be, delorean is supposed to be ultimate packaging upstream
15:43:50 <jruzicka> right, so it either will be or we're gonna make it ;)
15:44:00 <apevec> I'm proposing some spec changes which would simplify delorean specs
15:44:06 <apevec> e.g. drop all changelog entries
15:44:09 * eggmaster bows out for next meeting...
15:44:12 <jruzicka> on that topic, could you add me to gh.com/openstack-packages maintainers?
15:44:32 <jruzicka> or is there some process/mechanism for new packages?
15:44:57 <apevec> e.g. https://review.gerrithub.io/#/c/217925/
15:45:13 <number80> +1 changelog entries are not useful in case of delorean and are annoyances
15:45:31 <apevec> jruzicka, yeah, still figuring out the new-pkg process - it does need Owner
15:45:49 <apevec> jruzicka, I'll add you
15:46:05 <apevec> #action add jruzicka to https://github.com/orgs/openstack-packages/teams/owners
15:46:33 <jruzicka> apevec, we could use rdoinfo and make script that creates gh repos for new entries in rdoinfo... but that sounds kinda like overkill
15:46:56 <jruzicka> but adding package to rdoinfo and BOOM it's there sounds pretty cool
15:46:57 <apevec> jruzicka, yeah, it's not the frequent but I do need to document all steps
15:47:09 <apevec> for the initial pkg creation
15:47:20 <jruzicka> yup, put it into https://openstack.redhat.com/packaging/rdo-packaging.html
15:47:25 <apevec> ack
15:47:44 <apevec> #action apevec to document all steps for the initial Delorean package creation
15:47:45 <jruzicka> alternatively, you can tell me how and I'll document as I need to create tempest
15:48:09 <chandankumar> hello
15:48:21 <chandankumar> i want to work on packaging of tempest
15:48:35 <apevec> jruzicka, tl;dr create project at GH, import it to gerrithub, adjust permissions (make rdo-packagers group Owner)
15:48:43 <apevec> add .gitreview
15:49:06 <apevec> and after that all changes must be through gerrithub otherwise GH/gerrithub get out of sync!
15:49:44 <jruzicka> chandankumar, hey, we have a different meeting topic now, but let's talk about tempest RPM once this meeting is over, OK?
15:49:47 <apevec> jruzicka, we can take details offline
15:49:51 <chandankumar> yes
15:50:00 <jruzicka> apevec, indeed, this is sufficient for now.
15:50:02 <apevec> last topic
15:50:06 <apevec> #topic trunk.rdoproject.org DNS
15:50:17 <jruzicka> yeah so this boils down to
15:50:19 <apevec> IP is correct now, pointing to new machine
15:50:23 <jruzicka> which is the real delorean :D
15:50:29 <apevec> new repourls are:
15:50:39 <apevec> http://trunk.rdoproject.org/f21/current/
15:50:49 <apevec> http://trunk.rdoproject.org/centos70/current/
15:51:11 <apevec> ^ NB above repos are work-in-progress, eat kittens etc.
15:51:12 <jruzicka> yes, so I need to update docs
15:51:22 <jruzicka> https://openstack.redhat.com/packaging/rdo-packaging.html#_differences_between_master_and_rawhide_packaging
15:51:28 <jruzicka> links to
15:51:29 <jruzicka> http://209.132.178.33/repos/report.html
15:51:44 <apevec> jruzicka, yes, URL changed since there are two builders now
15:52:11 <apevec> http://trunk.rdoproject.org/f21/report.html
15:52:15 <jruzicka> right
15:52:22 <apevec> http://trunk.rdoproject.org/centos70/report.html
15:53:15 <apevec> jruzicka, and yes, would be nice to put all those URLs on landing page
15:53:40 <apevec> if you have some design ideas, just put it in html :)
15:53:57 <apevec> otherwise we can just do bare bones <ul> ...
15:54:24 <apevec> ok, that was from the agend
15:54:28 <apevec> #topic open floor
15:54:28 * number80 would suggest having some coloring to make it easier to <s>parse</s> read
15:54:42 <apevec> coloring is overrated
15:54:50 <jruzicka> apevec, number80 I plan to extend delorean reporting once I get time
15:54:56 <jruzicka> especially
15:54:59 <number80> makes it easier for my bad eyesight :)
15:55:00 <alphacc> quick one: EPEL novnc (< 0.5) has some security issues, it would be nice if epel contributor can +1 version 0.5.1-2
15:55:07 <jruzicka> I'd like a list of all packages
15:55:09 <number80> alphacc: ack
15:55:18 <jruzicka> where you can tell if latest master built or not
15:55:23 <jruzicka> with colors ;)
15:55:26 <apevec> ah yes, sross has pushed the update
15:55:31 <number80> chandankumar: you're not in the packager group, so the first step is to get you sponsored
15:56:55 <apevec> any other last-minute topics for the meeting minutes?
15:57:12 <number80> nope, I'll wrap-up with chandankumar afterwards :)
15:57:26 <chandankumar> number80, i have a fas account, how i can get sponsored?
15:57:31 <apevec> alright, thanks everyone!
15:57:34 <apevec> #endmeeting