15:06:32 <bstinson> #startmeeting sig-cloud 15:06:32 <centbot> Meeting started Thu Nov 13 15:06:32 2014 UTC. The chair is bstinson. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:06:32 <centbot> Useful Commands: #action #agreed #help #info #idea #link #topic. 15:06:44 <bstinson> don't know much about the cloud sig, but i can do meetbot things :) 15:06:49 <bstinson> #chair number80 kbsingh 15:06:49 <centbot> Current chairs: bstinson kbsingh number80 15:07:09 <kbsingh> thanks 15:07:14 <kbsingh> who all do we have today ? 15:07:33 <bstinson> #topic Greetings and Introductions 15:07:37 * michel_slm is here 15:07:44 * kbsingh is here 15:08:03 <kbsingh> rbowen: ping 15:08:12 <rbowen> Good morning. What's up? 15:08:26 <kbsingh> rbowen: hello, welcome to the Cloud SIG meeting / syncup 15:09:19 <rbowen> Ah. I had the time wrong. Ok, you have my attention now. :-) 15:10:32 <michel_slm> kbsingh: remind me to ask about the exact list of packages we need to get Puppet running, and where we should keep track of this 15:13:20 * number80 is hguemar 15:13:21 <kbsingh> michel_slm: I believe the issue is that there is no way to run puppet-3.x on el5/6, and there is no puppet2.7 support in el7 15:13:59 <kbsingh> Kushal had a few personal things to take care of and cant make this meeting today 15:14:18 <michel_slm> taking care of his first child :) 15:15:20 <michel_slm> will need to look into the matter further. how tied is CentOS as a project to puppet? 15:15:26 <kbsingh> rbowen: so i guess one thing that would be good to see if how you visualise the Cloud SIG contributing into and facilitating the RDO process 15:15:53 <kbsingh> michel_slm: lets sync up post-meeting with Arrfab as well, he's the guy owning most of the puppet pain at this point 15:16:03 <rbowen> This might be a good place for apevec to jump in. 15:16:08 <michel_slm> kbsingh: sure 15:16:28 <kbsingh> apevec: hello 15:17:08 <rbowen> This was a part of the conversation that I had hoped would happen in Paris last week, but we apparently never got the right people together at the right time. 15:17:39 <kbsingh> yeah, also i think the crowd was a bit too large for the RDO syncup 15:17:40 * Jeff_S here idling 15:18:06 <Jeff_S> kbsingh: puppet 3.x runs fine on EL6, it's available in the puppetlabs yum repo 15:18:14 <Jeff_S> el5... I don't know 15:18:39 <apevec> rbowen, sorry, was in other irc conversations.. what's the question? 15:18:46 <apevec> hi 15:18:49 <apevec> btw :) 15:18:56 <Jeff_S> They seem to have el5 packages also FWIW http://yum.puppetlabs.com/el/5/products/x86_64/ 15:18:58 <kbsingh> rbowen: were moving on ( but havent completed ) the process for user contributed content on git.centos.org. i wonder if we might have a initial step of importing rdo content into git.c.o and trying to use that as a user contrib path 15:19:31 <kbsingh> Jeff_S: cool, lets sync with michel_slm and Arrfab in a bit 15:20:00 <apevec> kbsingh, that sounds good: so tl;dr we currently build RDO EL builds in Copr and would like to move to CentOS Koji 15:20:18 <apevec> but I'd like to avoid fork and keep master spec in Fedora 15:20:25 <rbowen> So that's a useful thing in the context of the conversation that happened in Paris - there's a number of people that want to start contributing to the rdo project, and that would be a good place for that to happen. However, what apevec talked about in paris was doing this via the Fedora community. 15:20:26 <kbsingh> apevec: using a dist-git like format for the sources is acceptable ? 15:20:29 <Jeff_S> (sorry didn't realize that wasn't a meeting item) :) 15:20:40 <apevec> so I'd merge just before doing centos builds 15:20:46 <kbsingh> apevec: cant use centos.org infra from outside of centos.org - so the sources will need to move 15:21:00 <kbsingh> or we'd need a local mirror in git.centos.org anyway 15:21:15 <kbsingh> however, given the really high barrier to entry with the fedora process, why would you want to keep specs there anyway ? 15:21:24 <number80> kbsingh: can centpkg send a rpm ? 15:21:27 <apevec> it's fine, I'll import what's needed to git.centos 15:21:28 <number80> srpm sorry 15:21:32 <kbsingh> number80: only to scratch builds 15:21:44 <kbsingh> you cant do repo builds ( or wont be able to ) once we have the git integration going 15:21:52 <number80> ok 15:21:58 <apevec> what I'm saying is that I want all spec/systemd etc changes done in Fedora first 15:22:04 <apevec> then merged to git.centos 15:22:10 <kbsingh> i believe we have srpm -> builds working at the moment to not block the sig's on the integration work that is still pending 15:22:15 <imcleod> kbsingh: WIll there be no centpkg equivalent of "fedpkg import"? 15:22:25 <kbsingh> apevec: ah ok, that would work. 15:22:44 <bstinson> imcleod: that functionality should work in centpkg 15:23:06 <kbsingh> bstinson: i guess the only bit missing yet in that is the bin sources bit that MerlinTHP and i were talking about earlier ? 15:23:16 <imcleod> kbsingh: OK. So that's actually a fairly simple path, that is g.c.o friendly, to get SRPMS in. 15:23:30 <kbsingh> apevec: but it should not be a requirement for people to post against the fedora git sources only 15:23:35 <bstinson> kbsingh: correct 15:24:11 <apevec> kbsingh, I'd like just to avoid forking 15:24:19 <kbsingh> apevec: someone would need to take patches / fix/ additions from the git.c.o and upstream into fedora as needed as well right ? 15:24:34 <apevec> I'd accept patches from anywhere 15:24:43 <bstinson> #topic General Discussion 15:24:49 <bstinson> sorry, missed my bot duties 15:24:54 <kbsingh> apevec: so what problem do we solve by keeping this code in fedora git ? 15:24:59 <apevec> kbsingh, just not sure what is default license for CentOS contributions? 15:25:25 <kbsingh> apevec: we have none, the SIG's can work their own as long as its legal to re-distribute content and people claiming ownership really own it 15:25:32 <apevec> kbsingh, it's the same code essentially, so must be one cannonical upstream imho 15:25:33 <kbsingh> ( ie. bin packages and not-from-source is fine as well ) 15:26:25 <apevec> kbsingh, ok, that would be packages which cannot fit fedora 15:26:31 <kushal> Sorry for being late. 15:26:37 <apevec> and it's not the case for openstack-* 15:26:42 <kushal> apevec, Yes. 15:26:59 <apevec> but yeah, we could have such cases, like ODL java stuff for example 15:26:59 <kbsingh> apevec: not sure what you mean ? 15:27:00 <kushal> apevec, It will be a case for Eucalyptus java jars. 15:27:19 <apevec> kushal, or any java thing ;) 15:27:31 <kushal> apevec, True :) 15:27:51 <kbsingh> well, this helps Java - but the real usecase we were chasing is HPC and embedded 15:27:55 <number80> apevec: you're thinking about opendaylight or something else ? 15:28:03 <apevec> kbsingh, I mean what I said earlier: I want to avoid any chance of forking packaging in centos 15:28:12 <apevec> it must be kept in sync w/ Fedora 15:28:28 <apevec> number80, ODL = opendaylight, yes 15:28:30 <kbsingh> why ? 15:28:39 <apevec> b/c... forks are bad? 15:28:46 <kbsingh> really ? 15:28:52 <bstinson> so not sure if this is helpful, but do note that the CentOS dist-git layout and the Fedora dist-git layout are different (We have {SOURCES,SPECS,...}) for example 15:28:55 <number80> +1, duplication of work 15:29:06 <apevec> kbsingh, really :) 15:29:25 <apevec> anyway, let's get this up and running and I'll keep an eye on this 15:29:35 <apevec> this=centos only changes 15:30:00 <apevec> bstinson, yep, I noticed, I think we can manage that 15:30:13 <kbsingh> not sure how much of open source politics we want to go into here, 15:30:27 <kushal> kbsingh, I don't want any :) 15:30:34 <kbsingh> the problem i can see is that fedora does not work in sync with centos release patterns 15:30:40 <michel_slm> kushal: you're here! 15:30:42 <apevec> kbsingh, all I want is e.g. that we don't lose any bugfix somebody does in centos only 15:30:49 <kbsingh> and needing someone to contrib against fedora tree's makes the entire process a bit irrelevant for us 15:31:22 <apevec> kbsingh, as I said let's get this up and running and I'll keep an eye on centos only changes 15:32:04 <number80> kbsingh: interesting topic, but I'll save this after the meeting 15:32:17 <kbsingh> how close are we to the visibility of the rdo packager scripts that were mentioned ? 15:32:39 <apevec> kbsingh, rdopkg is not required, it's just helping tool 15:32:49 <apevec> I need yet to grab it's main developer 15:32:55 <kbsingh> ok 15:33:11 <apevec> I asked him to prepare it for public repo before the summit 15:33:24 <kbsingh> so what is the scope of the work that needs to be done ? 15:33:57 <kbsingh> lets assume a target is : yum install centos-release-openstack && packstack --allinone -> just works, completely from cbs.centos.org built content 15:33:58 <apevec> step1 would be initial import of RDO Juno from Fedora Rawhide 15:34:15 <apevec> ack to the target 15:34:28 <kushal> kbsingh, I would really love to see that. 15:34:55 <kbsingh> kushal: and yum install centos-release-eucalyptus :) 15:35:07 <kushal> :) 15:35:29 <kbsingh> apevec: i guess that is just a case of cp'ing a bunch of srpms and running them into a target on koji ? 15:35:46 <apevec> kbsingh, yep, should be and I volunteer for that task 15:36:03 <bstinson> #topic Scope of Work for Openstack 15:36:04 <apevec> just need someone to give me howto using cbs 15:36:14 <apevec> also account 15:36:23 <kbsingh> there are a couple of things we'd need to get done before the builds: open bugs.centos.org request for build targets in koji, we'd need atleast a defauly sig-cloud for http://cbs.centos.org/repos/ 15:36:38 <bstinson> #info need to import RDO Juno from Fedora Rawhide (apevec volunteers) 15:36:42 <kbsingh> then we'd need requets on bugs.centos.org for people to get build perms on those targets ( also done via bugs.c.o ) 15:36:57 <apevec> rbowen, ^ can you handle filing those BZs ? 15:37:40 <kbsingh> kushal might 15:37:54 <rbowen> Yes, I'll do that. 15:38:06 <kbsingh> ( given that kushal's done that in the past, and likely has an idea on process etc ) 15:38:11 <kushal> kbsingh, always get someone to volunteer :p 15:38:12 <rbowen> Oh, ok. 15:38:22 * number80 could help apevec for importing RDO juno 15:38:23 <kushal> rbowen, I will give you the template :) 15:38:29 <rbowen> Thanks. 15:38:30 <kushal> number80, thank you :) 15:38:39 <kbsingh> technically : http://wiki.centos.org/SpecialInterestGroup/Cloud lists people, all of them are able to get access etc 15:38:46 <bstinson> #action rbowen will file bugs for CBS build targets and accounts 15:38:48 <kbsingh> the rest will need someone from that list to propose and +1 15:39:11 <kbsingh> also, apologies, but i need to drop off for a bit. 15:40:43 <kushal> This sounds good. 15:41:04 <apevec> kushal, number80, rbowen - please add me to the list for http://wiki.centos.org/SpecialInterestGroup/Cloud 15:41:18 <apevec> AlanPevec 15:41:40 <apevec> do I need to open an account somewhere? 15:42:06 <bstinson> apevec: for the wiki? 15:42:18 <kushal> apevec, wiki account and also give any one of us some intro text about you, so that we can do a small email vote :) 15:42:54 <number80> I still don't have the rights to edit this page 15:42:59 <michel_slm> kushal: ah, so the process is existing members vote on new members? 15:43:09 <kushal> number80, yeah, that was given to me for now. 15:43:15 <rbowen> Yeah, I don't appear to have edit rights on that page, either. 15:44:14 <kushal> michel_slm, yes, and we want to keep whole list tighter (for the bootstrap). 15:44:34 <michel_slm> sounds sensible 15:46:03 <kushal> Anyone from OpenNebula team here? 15:46:19 <kushal> or cloud stack? 15:46:22 <number80> kushal: at least, we should keep a list of people interested 15:46:45 <bstinson> #topic Open Discussion 15:46:49 <rbowen> The Cloudstack people are interested, but I don't see any of them here. 15:46:51 <apevec> kushal, ok, 1-liner would be: "Alan works in OpenStack on stable branch maintenance, Keystone identity service and packaging OpenStack for Fedora/RDO/CentOS." 15:46:58 <number80> jzb ? 15:47:07 <number80> ^cloudstack ! 15:47:11 <rbowen> Oh, I didn't see him there. :) 15:47:18 <rbowen> Yes, he's on the Cloudstack PMC. 15:47:19 <kushal> number80, yes, may be we can ask for a mailing list where people can join in. 15:47:36 <number80> kushal: agreed 15:48:45 <kushal> bstinson, btw, can anyone use centbot for meetings here? Asking for the future meetings. 15:48:53 <kushal> bstinson, I never used it in the last meeting. 15:49:29 <bstinson> kushal: i believe so, there's also some discussion items open with the board about distributing minutes (and the access controls needed for that) 15:49:49 <kushal> bstinson, that means I should apply for permission :) 15:50:27 <kushal> Any other topic for the open floor ? 15:50:40 <bstinson> #chair kushal 15:50:40 <centbot> Current chairs: bstinson kbsingh kushal number80 15:52:38 <kushal> I think we can end today's meeting then. Next week same time we will be meeting again. 15:53:30 <bstinson> ok, closing 15:53:53 <bstinson> #endmeeting