16:00:24 #startmeeting openstack-chef 16:00:25 Meeting started Mon Aug 24 16:00:24 2015 UTC and is due to finish in 60 minutes. The chair is j^2. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:29 The meeting name has been set to 'openstack_chef' 16:00:34 hey everyone! 16:00:55 please checkin when you’re here 16:01:12 o/ 16:01:24 hi o\ 16:01:47 o/ 16:04:01 nice i’ll give 2 more mins 16:05:06 ok cool 16:05:13 #topic stable/kilo 16:05:25 i want to stamp stable/kilo on thursday 16:05:44 i believe we have everything working and everyhting set up 16:06:01 can i ask for a volunteer to help me on thursday? 16:06:34 i’m betting if we work together we can get everything knocked out in about 2-3 hours 16:06:35 and then there was silence.... 16:06:41 yeah 16:06:46 i figured 16:07:05 let’s take a second and ask first, any objections to us stamping on thursday? 16:07:36 depending on the time of day, i might have time 16:07:47 what time works for you sc` ? 16:08:22 did any1 look at the open bugs and unfinished blueprints that were assigned to kilo? 16:08:31 markvan: 16:08:33 he did 16:08:39 probably early morning 16:08:53 aw shit 16:08:59 because as far as i can tell there are still things open 16:09:13 i was going to say i was deicating 2pmCDT onwards to this 16:09:33 all my meeting are in the morning 16:09:33 so i think we should probably have a quick walk through these and reassign if necessary before cutting kilo 16:09:40 agreed 16:09:54 want to do it right now? 16:10:01 iirc there shouldnt be much left 16:10:22 i see 4 blueprints 16:10:32 and 35 bugs 16:10:43 question is if they all should be solved in kilo 16:10:59 but probably at least the 9 ones on medium 16:11:13 #link https://blueprints.launchpad.net/openstack-chef/+spec/chef-cinder-backup 16:11:37 so that one looks complete according to what i’m reading 16:11:49 got a +1 on taht? 16:12:20 i cant read through the patches that quickly 16:12:23 give me a second 16:13:53 looks like he implemented what he described in the bp 16:14:02 no idea if its working 16:14:09 yeah 16:14:12 we don’t test that stuff 16:14:27 we only really verify compute 16:14:27 so maybe we rather ask via our mailing list people to comment on these open blueprints? 16:14:55 howdy....(out of the woods now...) 16:14:59 i’d love to, but that feedback loop is like 2 weeks at best 16:15:00 hi 16:15:33 the packages for liberty are going to start be released any day now, and we need to start working on it 16:17:09 markvan: can you follow up with your guys in china to see if they have completed their bps? 16:17:22 they look done, but they havent been closed 16:17:39 yup, I can do that, I think most are ready to close out. will berify. 16:17:48 nice 16:18:30 and i’ve bumpd the two others to Liberty, one is something i never started, and can’t any time soon, and the other one is alanmeadows who as much as he’s awesome i havent seen him around 16:18:44 speaking of, wheres my desginate cookbook eh? alanmeadows 16:21:46 ok, so with that, we need to clean up the bugs and bump ones that arent mission critical? 16:21:54 I will also scan bugs to see if anything pops out that really needed for kilo 16:21:55 markvan: are you around on thursday? 16:22:33 yup, I can help 16:23:06 awesome, i’ll post a zoom on thursday around 2pmCDT and anyone who wants to join can 16:25:59 cool, so we have the bugs and bps covered 16:26:07 we have till thursday to make this happen 16:26:12 anything else? 16:26:19 jklare: has something he’d like to talk about 16:26:30 yeah 16:26:40 i started writing down this spec https://review.openstack.org/#/c/213042/ 16:26:43 #topic review jklare want’s to talk about 16:27:08 which is basically suggesting a complete rework on how we use templates for service.confs 16:27:27 can that help us get to keystone v3? 16:27:49 i know there’s requirements in there with that 16:28:32 not sure about that 16:28:47 ah, i thought there were parallels theer 16:28:50 but i think it should simplify all the coming upgrade 16:28:51 my bad 16:28:59 that’s always good ;) 16:29:03 keystone v3 has more to do with our use of the deprecated keystone client vs the new openstack client. 16:29:20 ah yeah we need to make that happen in liberty, it HAS to happen 16:29:37 from the conversations I’ve been having, there is a HUGE push for the openstack-client 16:29:50 the whole idea behind this spec is to simplify the way we create a config file, be more generic about it through all cookbooks 16:30:07 and ofc allow people to wrap then more easily 16:30:16 i wrote about most of these things in the spec 16:30:17 +1 16:30:39 so it would be great if you could take a look at that and tell me if we want to do this or not 16:31:04 because it will mean a lot of refactoring through all cookbooks and cut a lot of code 16:31:59 yeah that’s liberty ;) 16:32:12 because that’s what were doing for liberty, simplication and more simplication 16:32:21 I'll take a peek... 16:32:29 cool 16:33:42 cool, any other objections? 16:34:11 nope 16:34:43 #topic General Discussions 16:35:12 open floor 16:35:41 just a thought that we should look at updating tool chain (chefdk, etc..) during liberty 16:37:42 yep 16:38:34 is there any roadmap for chefdk? 16:44:40 kinda 16:44:49 it moves really fast 16:45:12 i’ll take an action item to find some type of roadmap jklare 16:45:18 0.7.0 was recently released 16:45:32 yep 16:50:50 :D 16:50:57 ok, we have our things to do 16:51:14 lets make this happen and by next monday we should have stable/kilo 16:51:29 #endmeeting