15:37:43 <markvan> #startmeeting openstack-chef
15:37:43 <openstack> Meeting started Thu Jan 15 15:37:43 2015 UTC and is due to finish in 60 minutes.  The chair is markvan. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:37:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:37:47 <openstack> The meeting name has been set to 'openstack_chef'
15:38:10 <markvan> #action list
15:38:30 <j^2> I had an insulin pump failure last night, I'm not in any condition to meet
15:38:56 <markvan> j^2: ouch, np
15:39:00 <libsysguy> oh damn man
15:39:06 <libsysguy> feel better
15:39:28 <j^2> Thanks, back to getting my head on straight
15:39:37 <markvan> #topic  kilo branching
15:40:23 <markvan> just an update, we have taken an initial pass thru the bugs list and marked a few that we want in juno, all else can be done in kilo.
15:40:31 <zhiwei> I want to ask a question, how many meetings per week? I only know there is one on Monday 15:30 GMT.
15:40:42 <markvan> please review your bugs and if you don't agree speak up.
15:41:12 <markvan> zhiwei: meetings are on Mon 930am and Thru 930am.  soury if I told ya wrong info.
15:41:23 <markvan> Mon is live chat,  Thru is this irc chat.
15:41:41 <zhiwei> ok, got it.
15:42:04 <zhiwei> thanks, maybe I misunderstood.
15:42:31 <markvan> Next pass on kilo will be going thru the blueprints/specs and and misc patches that are not associated with a bug/bp.
15:42:35 <wenchma_> https://wiki.openstack.org/wiki/Meetings/ChefCookbook#Weekly_Chef_Cookbook_Meeting
15:43:08 <markvan> that's all I had on kilo, libsysguy, anything else on that one?
15:43:11 <libsysguy> not that I really like the idea, but patches should really have bugs/specs attached to them
15:43:58 <markvan> libsysguy: yeah, I would agree, but I'm also a guilty party to that as well.   It's been pretty good for the most part.
15:43:58 <libsysguy> that's pretty much all I have to add
15:44:08 <libsysguy> I'm terrible about it :p
15:44:17 <markvan> other topics  anyone?
15:45:57 <zhiwei> I think the rake need to be remove from Gemfile in stable/juno release.
15:46:19 <markvan> #topic rake in gemfile
15:46:21 <wenchma_> #topic ironic cookbook
15:46:36 <markvan> go ahead wenchma_
15:47:00 <wenchma_> as known, ironic cookbook begin from kilo
15:47:38 <markvan> #link https://review.openstack.org/#/c/145120/
15:47:41 <wenchma_> same as your topic above
15:47:44 <wenchma_> kilo branching
15:48:17 <markvan> I think that review is in pretty good shape now.  Others please take a look, thx.
15:48:25 <wenchma_> we need to go on the ironic cookbook
15:48:44 <wenchma_> markvan: thanks
15:49:48 <markvan> #topic rake in Gemfile
15:50:25 <zhiwei> ok, I was tormented with the gems.
15:50:26 <markvan> zhiwei:   Trying to understand this one.  We are trying to move to rake, so isn't it needed in the Gemfile to make sure it's there.
15:51:28 <markvan> For the builds/gate jobs, we have it hardcoded to install rake
15:51:28 <zhiwei> yeah, we should remove it from Gemfile. this need to submita series of patches.
15:51:31 <markvan> # link https://review.openstack.org/#/c/137134/
15:52:14 <markvan> Humm, but for folks doing this on there own boxes (outside of gates), this would still be a needed step, to make sure rake is installed.
15:53:23 <zhiwei> yes, rake should preinstalled before doing test.
15:54:37 <zhiwei> developers should install rake on there machine before doing the test. If not, they can't do the test. the the `bundle install` command was driven by rake.
15:56:16 <libsysguy> this is an interesting point since the push is it use chafed going forward
15:56:20 <libsysguy> chefdk**
15:56:25 <markvan> ah, understand now.   yup that is a good point, and we already state that pre-req in the TESTING.rb files.
15:57:15 <libsysguy> so are you saying this should be the push for kilo?
15:57:16 <markvan> libsysguy: good point, going to Chef 12, means going to Chef DK probably as well.
15:58:00 <markvan> We could cleanup the Gemfiles for Juno, but for kilo, another set of changes will be required for Chef 12/ Chef DK/ Gates
15:58:18 <libsysguy> I can get onboard with that
15:58:56 <libsysguy> zhiwei: you wanna file a bug to cleanup the Gemfiles?
15:59:09 <zhiwei> yes.
15:59:21 <markvan> kilo gates will be  ubuntu 14.04, Chef 12, Ruby 2.x, Chef DK, so a bunch of infra/cross cookbook work to do there once we branch
16:00:09 <markvan> and we have to some how keep the existing gates with ubuntu 12.04, Chef 11, Ruby 1.9, in place to allow for juno/stable patches and backports.
16:00:29 <markvan> thx for stepping up zhiwei
16:00:38 <zhiwei> :)
16:00:41 <zhiwei> another thing
16:00:54 <libsysguy> yeah I have a feeling I am going to get really familiar with those infra guys
16:01:15 <zhiwei> it is very hard for beginners to deploy OpenStack by using Chef.
16:01:31 <markvan> yeah, was just about to push a bit for the existing rake patch we have out there....
16:01:49 <zhiwei> So, I submitted a patch to add a getting started page. I'd like to submit this patch https://review.openstack.org/#/c/147472/ in juno branch.
16:02:12 <markvan> #topic beginners using Chef and OpenStack
16:02:36 <zhiwei> I think it is necessay to merge this patch in Juno branch.
16:03:16 <markvan> that other way to handle this type of Doc is to just create a new wiki page: https://wiki.openstack.org/wiki/Chef/GettingStarted
16:04:18 <markvan> and then in the repo maybe just add a link to that.  That way we can easily flow Doc into the wiki at any point.    As I don't think this type of Doc really needs full formal reviews...
16:04:39 <zhiwei> got it.
16:05:13 <markvan> but, this patch has some good coding examples that belong in the repo, so I think the patch is a good approach for this level.
16:05:36 <markvan> But we can also add to with with wiki doc if needed as well.
16:06:17 <markvan> I was thinking about more highlevel Doc that explains the Chef OpenStack world from 10,000 feet, that would be good for wiki.
16:06:55 <markvan> zhiwei: thx for this patch, I'll give it a review today.
16:07:11 <markvan> Other topics?
16:07:44 <wenchma_> #topic openstack-chef in launchpad
16:08:07 <wenchma_> #link https://launchpad.net/openstack-chef
16:08:14 <wenchma_> should update the content
16:09:18 <markvan> ah, good point.   I see ceph still in there, and it's missing database, data-processing and new bare metal
16:09:24 <wenchma_> should change https://github.com/stackforge/cookbook-ceph   which is deprecated
16:09:32 <wenchma_> also add ironic cookboo
16:09:40 <wenchma_> cookbook-openstack-bare-metal
16:10:05 <markvan> humm, I thought I had acess to change that, but I guess I don't, I'll give action to j^2 to either update it, or give me access.
16:10:22 <zhiwei> Do we also need to add a link to Chef wiki page on openstack site?
16:10:37 <markvan> #action j^2  Update  https://launchpad.net/openstack-chef  cookbook list  and add link to wiki
16:12:35 <markvan> #topic  New Core nominations
16:12:53 <libsysguy> uh oh
16:13:01 <zhiwei> good
16:13:53 <markvan> We could use more Core, please submit your nominations to the ML with maybe some brief background and plans.  And others can chime in and vote.  sound good?
16:14:28 <openstackgerrit> Ma Wen Cheng proposed stackforge/cookbook-openstack-bare-metal: Initial basic cookbook files  https://review.openstack.org/145120
16:14:42 <zhiwei> yes.
16:15:05 <libsysguy> should existing cores re-apply?
16:15:12 * libsysguy is asking as a new core
16:15:24 <markvan> no, your in for life  ;)
16:15:29 <wenchma_> remove rake in Gemfile
16:15:42 <libsysguy> good because I already changed my hip chat alias at work to @core
16:15:44 <libsysguy> :p
16:16:30 <markvan> crown getting heavy?
16:16:52 <libsysguy> nah, just ego
16:17:18 <markvan> other last topics?
16:17:49 <libsysguy> none from me
16:17:58 <zhiwei> mee to
16:18:41 <markvan> thx all.
16:18:44 <markvan> #endmeeting