15:01:05 <number80> #startmeeting RDO packaging (2015-01-28)
15:01:05 <zodbot> Meeting started Wed Jan 28 15:01:05 2015 UTC.  The chair is number80. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:05 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:15 <number80> #topic roll call
15:01:36 * apevec yo
15:01:41 <number80> agenda is here: https://etherpad.openstack.org/p/RDO-Packaging
15:01:43 * number80 waves
15:02:04 <apevec> number80, is there specific meetbot command for roll call?
15:02:27 <number80> nope, usually, we use a topic
15:02:31 <ryansb> \o
15:02:54 <gchamoul> o/
15:02:59 <trown> o/
15:03:36 * chandankumar waves back to all :)
15:03:45 <number80> I guess Rich is on his way to FOSDEM
15:04:23 <apevec> ah yes, it's that time of the year again
15:04:51 <number80> then let's start
15:04:59 <apevec> yes
15:05:01 <number80> #topic FPCA legal stuff
15:05:27 <apevec> so we still have that fpca is required for Fedora dist-git commits,
15:05:37 <apevec> and I'm proposing to move primary RDO dist-git completely to github/openstack-packages/ then sync to Fedora
15:06:06 <apevec> Question is now for potential contributors if signed-off-by would be acceptable
15:06:21 <apevec> I'm waiting for legal if s-o-b line is enough
15:06:40 <apevec> to cover my and other people's a** who would sync that to Fedora dist-git
15:06:53 <number80> though I'm not a lawyer, I guess it should work
15:07:20 <apevec> I would like to avoid forking, that would be NOT win-win situation
15:07:30 <gchamoul> nope
15:07:48 <number80> #idea moving primary RDO dist-git completely to github/openstack-packages/ then sync to Fedora
15:07:50 <number80> gchamoul: ?
15:08:17 <gchamoul> number80: was just confirming the apevec's pov ;-)
15:08:30 <apevec> anyone from cern to confirm if s-o-b is fine for their lawyers?
15:08:31 <number80> ok
15:08:47 <apevec> we need link to kernel's s-o-b policy
15:08:54 <apevec> anyone has it handy?
15:09:17 <number80> http://ltsi.linuxfoundation.org/developers/signed-process
15:10:13 <apevec> number80, thanks, will that get automatically into minutes summary?
15:10:17 <number80> yes
15:10:26 * kashyap is lurking
15:10:44 <number80> Anything else on that topic ?
15:11:33 <apevec> I wanted to hear from potential contributiors
15:11:40 <kashyap> QEMU also has that policy, IIRC
15:11:42 <apevec> but I guess will try that on the list thread
15:11:47 <apevec> kashyap, link?
15:12:14 <number80> #action apevec request input on s-o-b policy on rdo m-l
15:12:15 <kashyap> apevec, I know you'll ask, was looking already
15:13:05 <kashyap> apevec, http://wiki.qemu.org/Contribute/SubmitAPatch
15:13:16 <kashyap> That refers to Kernel policy though :-)
15:13:37 <apevec> kashyap, which is what I'd do too :)
15:13:41 <apevec> ok, let's move on
15:14:06 <apevec> #topic trunk.rdoproject.org
15:14:42 <number80> #topic trunk.rdoproject.org
15:14:51 <apevec> rbowen is traveling, jruzicka have you heard anything back?
15:14:58 <number80> #chair apevec gchamoul trown ryansb kashyap
15:14:58 <zodbot> Current chairs: apevec gchamoul kashyap number80 ryansb trown
15:15:24 <gchamoul> apevec trunk.rdoproject.org seems to redirect to openstack.redhat.com
15:15:40 <apevec> ok, so DNS is done, cool
15:15:56 <apevec> now we need apache vhost configure, and jruzicka has access afaik
15:15:58 <gchamoul> seems to be in all case ;-)
15:16:11 <jruzicka> I might
15:16:31 <jruzicka> but I'm not too much of a serveradmin
15:16:34 <apevec> ah, looks like it's wildcard dns alias
15:16:39 <jruzicka> I use lighttpd on mah servers
15:16:43 <number80> #chair jruzicka
15:16:43 <zodbot> Current chairs: apevec gchamoul jruzicka kashyap number80 ryansb trown
15:16:56 <gchamoul> jruzicka: you will need puppet for that !
15:17:02 <apevec> jruzicka, yeah, need to check with OSAS admin, is that mscherer?
15:17:13 * gchamoul is kidding, of course
15:17:15 <apevec> not sure what OSAS webteam is using
15:17:18 <number80> apevec: yes (misc or csim)
15:17:24 <number80> they use ansible
15:17:27 <gchamoul> apevec: yes should be
15:18:04 <apevec> ok, jruzicka can you take action to contact csim about configuring vhost
15:18:09 <number80> btw, misc will be at centos dojo
15:18:31 <apevec> or did we want to point directly to Delorean server in OS1 cloud?
15:18:33 <jruzicka> oooh, great
15:18:42 <jruzicka> so I'll poke him physically with my hand :D
15:18:56 <gchamoul> ;-)
15:19:03 <apevec> jruzicka, maybe trunk.rdoproject.org could be a landing page with links to actual Delorean host?
15:19:34 <apevec> we'll probably move Delorean build machine at one point
15:19:47 <apevec> so indirection jump page seems like a good idea
15:19:56 <jruzicka> apevec, yeah, makes sense
15:20:18 <apevec> #action jruzicka to poke csim about trunk.rdoproject.org vhost on rdo site
15:21:12 <apevec> ok, next?
15:21:17 <number80> +1
15:21:18 <apevec> #topic installer for trunk aka Packstack against Delorean repo
15:21:21 <apevec> gchamoul, ^
15:21:27 <apevec> anything new from last week?
15:21:42 <apevec> we need this so we can publish Kilo snapshots
15:21:49 <apevec> and K-2 is coming next week
15:21:51 <gchamoul> well .... it doesn't work well so far
15:21:55 <apevec> no pressure :)
15:22:06 <gchamoul> I am actually working on fixing the beast
15:22:14 <apevec> what are issues? updating pupped modules did not help?
15:22:44 <apevec> #action gchamoul will fix the beast
15:22:56 <gchamoul> need to fix some stuffs in the packstack composition layer
15:23:22 <gchamoul> for working with the last master puppet-openstack modules
15:23:57 <apevec> so it's not openstack Kilo but puppet modules changes?
15:24:36 <apevec> is stackforge puppet master open for Kilo actually or is it still supposed to work with Juno?
15:25:03 * apevec never understood puppet module branching policy
15:25:36 <gchamoul> like I said ... we just need to adapt the manifests used by packstack
15:25:48 <apevec> ok, any ETA ?
15:25:50 <gchamoul> according to the latest commits
15:26:07 <gchamoul> I expect the end of the week
15:27:11 <apevec> #info Packstack master to work with Delorean repo by EOW
15:27:23 <apevec> ok, moving on
15:27:26 <apevec> #topic rdopkg CI docs
15:27:44 <apevec> eggmaster ^
15:28:00 <number80> #chair eggmaster
15:28:00 <zodbot> Current chairs: apevec eggmaster gchamoul jruzicka kashyap number80 ryansb trown
15:28:48 <eggmaster> hi.
15:28:51 <apevec> hi!
15:29:10 <number80> :)
15:29:18 <apevec> eggmaster, any estimate for the docs/post to rdo-list ?
15:29:25 <eggmaster> So, I meant to finish the CI doc email yesterday. Now I mean to finish it today.
15:29:38 <gchamoul> :-)
15:29:43 <apevec> #info expecting CI doc today
15:29:48 <eggmaster> Just finished big push for end of sprint demo yesterday, needed recovery cycles :P
15:29:58 <apevec> eggmaster, nope :)
15:30:45 <apevec> eggmaster, btw I've only few icehouse rdo updates in internal queue, then we're ready to switch to gerrithub rdo-update.git
15:30:53 <eggmaster> mind said "work!" body said "nuh-uh!"
15:31:15 <number80> btw, weshay and I are getting access to ci.centos.org
15:31:17 <apevec> I know the feeling
15:31:36 <apevec> number80, yep, that will be good to look at
15:31:49 <apevec> but for now we'll just redirect internal jenkins to public rdo-update.git
15:31:57 <number80> *nods*
15:32:04 <apevec> ok, that was review of action items from last week
15:32:24 <apevec> now new topics
15:32:28 <apevec> #topic moving to CBS builds for RDO Juno EL7 updates
15:32:55 <apevec> since initial builds last month, CloudSIG went out of sync with RDO Juno EL7
15:33:33 <apevec> to avoid this, I propose to close el7 juno copr and push CBS el7 builds in rdo juno updates
15:33:52 <number80> +1
15:34:08 <apevec> We'll need everybody to ask for CBS Koji accounts, but that's a manual process for now
15:34:10 <number80> I'm currently sync-ing the builds
15:34:17 <apevec> until centos account system is ready
15:34:44 <apevec> so number80 and others already in cloud sig will sync the builds
15:35:01 <apevec> i.e. anyone would push rdo update with Fedora build
15:35:29 <apevec> and we'll build it in CBS and amend the update
15:35:45 <apevec> but first we need source: cbs
15:35:56 <apevec> jruzicka, ^ it should be just koji -p cbs
15:36:07 <apevec> afaict centpkg sets "cbs" koji profile
15:36:21 <apevec> but need to check, I didn't use it
15:36:42 <apevec> I used manual koji configuration, as described in http://wiki.centos.org/HowTos/CommunityBuildSystem
15:36:57 <apevec> #action jruzicka to add rdoupdate cbs source
15:37:23 <apevec> jruzicka, and koji tag is cloud7-testing, can you add that in rdopkg automagic?
15:37:41 <jruzicka> #action jruzicka to acquire CBS account
15:38:01 <apevec> right, I emailed you the procedure
15:38:05 <jruzicka> y
15:38:27 <apevec> number80, did you hear any news on centos account system?
15:38:41 <apevec> number80, and is there any limit on # of SIG Koji accounts?
15:38:57 <jruzicka> apevec, hmm, which automagic in particular?
15:39:01 <number80> apevec: 1. not yet, I'll see with Arrfab in Brussels 2. no
15:39:17 <apevec> jruzicka, to generate source: koji-cbs for RDO Juno EL7
15:40:11 <apevec> jruzicka, i.e. in place of current copr-jruzicka
15:40:36 <apevec> jruzicka, also to know which cbs koji tag to look at
15:40:42 <jruzicka> apevec, oh, indeed
15:40:49 <apevec> actually, build NVR is global, so tag doesn't matter?
15:41:09 <jruzicka> apevec, yep, tag shouldn't matter
15:41:26 <apevec> cool
15:41:37 <apevec> ok, last topic
15:41:39 <apevec> #topic Juno/EL6 packages
15:42:06 <apevec> moving to CBS is a prep to enable this
15:42:43 <apevec> is there anyone to report status on this?
15:42:56 <apevec> there were few interested folks on rdo-list few weeks ago?
15:42:59 <number80> David, Thomas, Matt ?
15:44:22 <number80> there were discussion about using python27 and maintain even post-juno releases on EL6, so I wanted to discuss that first :/
15:44:56 <apevec> yeah
15:45:14 <apevec> looks like we'll have to revive "Juno EPEL packages" thread again
15:45:59 <number80> I invited them to come discuss with us during FOSDEM, if they're too shy to come on irc :)
15:45:59 <apevec> number80, actually you did invite to this meeting on that thread
15:46:05 <apevec> ok
15:46:11 <apevec> we'll check status next week
15:46:20 <number80> ack
15:46:41 <apevec> that was all topics we had on agenda
15:46:55 <apevec> any last-minute additions?
15:47:09 <number80> atm, nope :)
15:47:38 <apevec> ok, thanks everybody, please reply on posted meeting minutes if you have updates!
15:47:57 <apevec> have fun to those going to fosdem/centos dojo!
15:48:26 <apevec> #endmeeting