15:02:14 <apevec> #startmeeting RDO packaging meeting (2015-03-18)
15:02:14 <zodbot> Meeting started Wed Mar 18 15:02:14 2015 UTC.  The chair is apevec. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:14 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:02:22 <apevec> #chair number80 rbowen
15:02:22 <zodbot> Current chairs: apevec number80 rbowen
15:02:28 <apevec> #topic roll call
15:02:32 <number80> o/
15:02:34 <rbowen> o/
15:02:36 <apevec> o/
15:02:40 <gchamoul> o/
15:03:07 <ryansb> o/
15:03:41 <larsks> o/
15:03:45 <jruzicka> o/
15:03:49 <jruzicka> carrier has arrived
15:04:13 <apevec> pigeons ?
15:04:17 <eggmaster> o/
15:04:35 <jruzicka> apevec, http://img4.wikia.nocookie.net/__cb20080524031859/starcraft/images/0/02/Carrier_SC2_Cncpt1.jpg
15:04:48 <jruzicka> aaanyway
15:04:48 <apevec> nice!
15:05:01 <apevec> looks like we have quorum!
15:05:10 <eggmaster> jruzicka: I hope the interstellar lag is not too bad
15:05:24 <number80> :)
15:05:37 <apevec> #topic review current tasks on trello
15:05:40 <apevec> #link https://trello.com/b/HhXlqdiu/rdo
15:06:11 <apevec> #info https://trello.com/c/FrKG69Fi/34-publish-a-delorean-repo-snapshot blocked on f21/centos7 delorean repos out of sync
15:06:18 <jruzicka> eggmaster, should work fine within same solar system... :-p
15:06:45 <apevec> derekh is trying to figure out how to force sync
15:07:27 <apevec> worst case, if we don't have a quickfix today, I'll publish whatever snapshops even if slightly out of sync
15:08:13 <derekh> apevec: there wont be a quick fix today, but they are now more in sync then they were this morning when you looked
15:08:14 <apevec> #info https://trello.com/c/qgKmFZkY/45-delorean-ci-job is further out, moved to next week, hitting issues with tempest node configuration
15:08:39 <apevec> derekh, ah cool, did you do anything or just natural convergence?
15:09:31 <derekh> apevec: the centos job had stuck (again), I've foud the problem in the sh library, send a pull request to https://github.com/amoffat/sh in a few minutes
15:10:15 <apevec> derekh, thanks for debugging! Trunk chasing is always interesing...
15:10:18 <derekh> apevec: essentially setting a timeout here wasn't working https://github.com/openstack-packages/delorean/blob/master/delorean/shell.py#L277
15:10:44 <apevec> ah that's Delorean dep
15:10:58 <apevec> ok, other stuff we have targeting next week:
15:11:19 <apevec> https://trello.com/c/xM6cddla/24-implement-cbs-tag-hierarchy-for-centos-cloud-sig
15:11:37 <apevec> number80, ^ was there anything left to define?
15:11:44 * apevec looks up centos ticket
15:11:46 <number80> yes, pinging alphacc
15:12:03 <apevec> #link https://bugs.centos.org/view.php?id=8289
15:12:14 <apevec> number80, ^ there are questions
15:12:22 <apevec> he default destination tag for all target will be -testing or -candidates ?
15:12:38 <number80> #action hguemar wrap up with alphacc about CBS tags hierarchy
15:12:57 <number80> apevec: I prefer candidates
15:13:00 <apevec> number80, -candidate sounds good
15:13:18 <apevec> -testing would be when already in the testing repo right?
15:13:52 <number80> yes, and I prefer testing packages to be validated by CI
15:14:42 <apevec> right
15:15:14 <apevec> ok, I've added https://trello.com/c/DKdtUgQh/46-openstack-selinux-in-delorean today but didn't ask Lon about it yet if it makes sense
15:15:52 <apevec> in the meantime please log selinux avcs you hit with kilo/delorean packages at the bottom of https://etherpad.openstack.org/p/RDO-Trunk
15:16:51 <apevec> #info https://trello.com/c/L0X5bU5s/25-el6-juno-packages had good progress
15:17:00 <apevec> number80 did EL6 clients
15:17:05 <jruzicka> number80++
15:17:08 <jruzicka> what a guy
15:17:10 <apevec> and we have nova EL6 spec proposed
15:17:27 <number80> yes, I'm merging it, I hit an issue with sphinx, should be fixed this week
15:17:39 <jruzicka> any non-redhatters involved?
15:17:46 <number80> jruzicka: alphacc \o/
15:17:50 <apevec> number80, we can update sphinx in CBS el6
15:18:09 <number80> apevec: I pushed python-sphinx10 to keep things consistent with EPEL
15:18:11 <apevec> I'd prefer that vs using parallel installable sphinx10 ting
15:18:15 <apevec> number80, meh
15:18:28 <apevec> number80, we don't care about EPEL
15:18:36 <number80> ok
15:18:46 <apevec> we can't keep any openstack stuff there, it's just too fast moving
15:19:01 <apevec> we had Folsom in epel6 and retired it
15:19:16 <number80> well, when we'll have common repo in CBS, then we don't have to care though :)
15:19:41 <apevec> number80, yep, another reason to get that hierarchy sorted
15:19:45 <jruzicka> yay, bright future
15:19:47 <apevec> both el7 and el6
15:20:01 <apevec> jruzicka, put sunglasses
15:20:06 <jruzicka> Folsom @ EPEL experiment was pretty painful, yes ;)
15:20:08 <number80> then, I'll see if we can host our branches in git.centos.org (this was mentioned during the CBS meeting on monday)
15:20:40 <apevec> number80, that's no go without Centos account system
15:20:59 <apevec> I'd prefer we keep single spec as long as it works
15:21:00 <number80> apevec: that's also another topic to be sorted out soon
15:21:02 <apevec> before we start forking
15:21:17 <number80> I meant for deps, not openstack packages directly
15:21:39 <number80> requests, sphinx, stuff like that
15:22:33 <apevec> number80, maintainers of those are not wiling to accept random if el6 ?
15:22:48 <apevec> in fedora master
15:22:54 <number80> apevec: not always
15:23:11 <number80> and sometimes, we don't want the rawhide version but older ones
15:24:21 <apevec> ok, that actually brings us to the next topic on agenda
15:24:33 <apevec> #topic Fedora reviews for new Kilo deps
15:24:45 <apevec> #info listed in https://etherpad.openstack.org/p/RDO-Trunk
15:24:59 <number80> should be higher priority after since chandankumar isn't sponsored yet
15:24:59 <apevec> current list is outsources, yay community
15:25:15 <apevec> but there will be more coming and we need something to keep track of them
15:25:19 <chandankumar> number80, i will be updating my specs tonight or by tomorrow
15:25:28 <number80> chandankumar: thanks
15:25:31 <apevec> chandankumar, thanks!
15:25:59 <apevec> so what are suggestions, should we put all deps into rdoinfo?
15:26:20 <apevec> jruzicka, verwatch is using rdoinfo?
15:27:02 <apevec> rdoinfo should be cannonical source for all RDO info (who would guess!)
15:27:23 <apevec> for example we have outdated component list in RDO bugzilla
15:27:48 <jruzicka> apevec, it doesn't
15:27:52 <apevec> we should just generate email from rdoinfo to bz RT to keep it in sync? :)
15:28:14 <apevec> jruzicka, where verwatch pulls metadata from then?
15:28:33 <jruzicka> apevec, it has it's own now redundant configuration file
15:28:39 <jruzicka> which I will be most delighted to not maintain
15:28:46 <jruzicka> so I'll open a card
15:29:03 <jruzicka> to migrate (or even rewrite) verwatch to rdoinfo
15:29:27 <jruzicka> note that I'm working on `rdopkg query`
15:29:39 <apevec> so using rdoinfo for all things looks good to everybody?
15:29:43 <jruzicka> which will query package versions across rdo in real time
15:29:57 <apevec> it's currently targeting mostly Delorean use-case (master tracking)
15:30:09 <apevec> but we could add info about which package is which release
15:30:14 <jruzicka> oh, it's gonna be perfect with rdoinfo...
15:30:17 <apevec> jruzicka, that's not expressed in rdoinfo yet?
15:30:21 <jruzicka> it fills all the gaps of moving pieces
15:30:49 <apevec> another future so bright!
15:30:58 <jruzicka> it does optionally
15:30:59 <jruzicka> master-distgit: https://github.com/openstack-packages/python-novaclient.git
15:31:22 <jruzicka> but that's not enough...
15:31:48 <jruzicka> hmm, maybe we should add special master branch
15:31:59 <jruzicka> which would contain information about delorean
15:32:02 <apevec> yeah, what would be the data model is the question
15:32:35 <apevec> jruzicka, can you start thread on rdo-list and propose initial version?
15:32:52 <jruzicka> apevec, I'm gonna figure that out. I'm extending rdoinfo with information about repositories to query for versions
15:33:46 <jruzicka> apevec, wait, verwatch is actually superset of rdoinfo. I remember I didn't know howto merge the two without bloating rdoinfo
15:34:09 <apevec> why not bloat rdoinfo?
15:34:16 <jruzicka> that's the question...
15:34:36 <apevec> ok, let's start discussion on rdo-list
15:34:41 <jruzicka> First
15:35:04 <apevec> #action jruzicka to start discussion on rdo-list about extending rdoinfo (to bloat or not to bloat)
15:36:02 <jruzicka> ok
15:36:28 <jruzicka> I'll finish rdopkg query which will be able to query package versions in RDO including fedora and centos repos
15:36:43 <jruzicka> kinda like verwatch but only using repoquery (simpler)
15:37:09 <jruzicka> once that is done, querying delorean would be as easy as defining master branch with proper attributes
15:37:11 <jruzicka> then
15:37:18 <apevec> cool
15:37:19 <jruzicka> rdopkg query kilo/master python-pbr
15:37:55 <apevec> ok, next topic
15:38:06 <apevec> actually that was last I had
15:38:13 <apevec> #topic open floor
15:38:22 <rbowen> Tomorrow at 15:00 UTC we have the CentOS Cloud SIG meeting.
15:38:39 <rbowen> There's a lot of overlap between the two meetings. If someone could volunteer to summarize this meeting at that one, that would help.
15:38:47 <rbowen> That's in #centos-devel
15:38:57 <number80> rbowen: I'll do it
15:39:04 <rbowen> Thank you.
15:39:14 <apevec> yeah, we have overlap around CBS topics
15:39:22 <number80> #action hguemar summarize RDO packaging meeting for CentOS cloud SIG meeting
15:40:01 <larsks> I have a packaging/review question: can we include .gitreview files in the package git repositories (in dist-git)?  This would make it easier for people to get started ("git review -s" would Just Work)...
15:40:16 <ryansb> +1
15:40:44 <apevec> larsks, you mean to put it in Fedora dist and point to openstack-packages on gerrithub?
15:40:51 <larsks> Yeah.
15:41:09 <apevec> ok, why not
15:41:30 <apevec> we do have .gitreview in delorean but yeah you need to get there first :)
15:41:45 <number80> larsks: +1
15:41:47 <larsks> I am in favor of lowering the bar to entry as much as possible :)
15:41:58 <apevec> ack
15:42:11 <number80> that means also documenting the git review process
15:42:14 <apevec> larsks, it will be defaultbranch=rpm-master we'll start migrating soon
15:42:29 <larsks> number80: we have some docs already at https://www.rdoproject.org/packaging/rdo-packaging.html, right?
15:42:50 <apevec> yes, that docs needs to add this new entry point
15:42:50 <number80> larsks: yes, just updating it, not everyone is used to work with gerrit :)
15:43:41 <dpaterson> jcoufal: instructions show: # a web server containing the RHEL guest cloud image
15:43:41 <dpaterson> # export DIB_CLOUD_IMAGES="<http://server/path/containing/image>"
15:43:41 <dpaterson> # export BASE_IMAGE_FILE=<image_name.qcow2>
15:44:29 <dpaterson> jcoufal: is there a public location for DIB_CLOUD_IMAGES?
15:45:12 <apevec> number80, larsks, btw there will be still differences between Fedora master and rpm-master so we need to see this doesn't confuse people
15:45:34 <jcoufal> dpaterson: for RHEL, you need to go to your customer portal and download the image from there
15:45:48 <number80> *nods*
15:46:02 <larsks> apevec: I don't understand the relationship/difference between the two. I will need to read/ask more later.
15:46:04 <apevec> I'll try this in keystone to see if I get confused
15:46:38 <apevec> larsks, here's summary https://www.rdoproject.org/packaging/rdo-packaging.html#_differences_between_master_and_rawhide_packaging
15:46:39 <dpaterson> k
15:46:44 <dpaterson> jcoufal: tx
15:46:49 <larsks> apevec: Thanks.
15:46:59 <apevec> ok, if there aren't more topics let's close the meeting to free the channel
15:47:23 <apevec> 3
15:47:26 <number80> *n*****
15:47:35 <apevec> 2 1
15:47:39 <apevec> #endmeeting