15:31:13 <markvan> #startmeeting  openstack-chef
15:31:14 <openstack> Meeting started Mon Oct 27 15:31:13 2014 UTC and is due to finish in 60 minutes.  The chair is markvan. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:31:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:31:17 <openstack> The meeting name has been set to 'openstack_chef'
15:32:02 <markvan> hi all, meeting time
15:32:05 <markvan> os-chef-bot: task list
15:32:05 <os-chef-bot> #1 - markvan look up git change log
15:33:14 <markvan> For Changelog, did not make much progress, was pulled into other work.  will continue on that this week.
15:33:42 <markvan> #topic open discussion
15:34:14 <libsysguy> juno release?
15:34:43 <markvan> sure, what about that.
15:34:53 <markvan> #topic Juno
15:36:09 <libsysguy> I was just wondering if the chef repos were behind the normal cut of stable for openstack
15:36:34 <libsysguy> I just hadn't seen a stable/juno branch pop up
15:37:53 <markvan> good question.  and Yes, we tend to stay behind to catch up with the final changes that went into the Juno branch.   I just found another one today.   And this gives us time to really attempt to make it "stable".
15:38:50 <libsysguy> okay cool. I figured that was the case.  It makes a lot of sense to do it that way.
15:39:12 <markvan> After the summit, we will bring this up again and have a high level review of any outstanding blueprint/bugs that are needed for Juno, put a plan in an action plan in place to address them and then set a date for cutting the stable Juno branch.
15:40:22 <markvan> So, we need everyone's help to report any issues or other items that may have slipped into base Juno that have not been fixed in the cookbooks.
15:40:47 <libsysguy> cool, so there is still a chance of blueprints making it into the juno release.  I am thinking specifically the upstart provider blueprint
15:40:55 <markvan> It seems there was plenty of conf changes and deprecation of key/vlaues in late Juno....
15:42:58 <markvan> Yes, I think we still have time for a blueprint like that one which is focused on a specific issue.    (See for the process to create a spec and start that discussion:  https://github.com/stackforge/openstack-chef-specs)
15:44:10 <libsysguy> thanks for that link markvan
15:44:10 <markvan> I thnk the swift cookbook has an example of that, but I have not played with it much:  https://github.com/stackforge/cookbook-openstack-object-storage/blob/master/attributes/default.rb#L348
15:46:52 <markvan> # topic Paris Summit
15:47:10 <markvan> #info  https://kilodesignsummit.sched.org/event/2eaa23e6076ea206dc9df6074ffc58c0 is the Chef session
15:47:26 <markvan> and I'll be there as well.
15:48:06 <markvan> I had another topic, our new rakefiles.
15:48:11 <markvan> #topic rake files
15:49:14 <markvan> We added rakefiles to all the cookbooks to take a step towards some amount of decoupling from the hardcoded infra job steps.   I have been looking into a infra patch to make them active, but ran into a couple issues.
15:49:56 <markvan> First, that there is other cookbooks in stackgforge using our job defs, so have to be careful no to break them as they don't have rake files.
15:50:32 <markvan> Second, the gate job env setup for Ruby and Berks is a bit ugly and might cause issues.
15:50:40 <markvan> I will conintue to look into this.
15:51:08 <markvan> os-chef-bot: task add  markvan will continue to work on infra Rakefile support
15:51:08 <os-chef-bot> Task added: #2 -  markvan will continue to work on infra Rakefile support
15:51:16 <markvan> Any other topics?
16:16:02 <markvan> #endmeeting