16:01:19 #startmeeting openstack-chef 16:01:20 Meeting started Mon Nov 9 16:01:19 2015 UTC and is due to finish in 60 minutes. The chair is jklare. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:24 The meeting name has been set to 'openstack_chef' 16:01:36 hi 16:01:41 o/ 16:01:44 hi 16:01:51 howdy 16:02:27 any topics from you guys for today? 16:02:56 i think the burning topic is branching stable/liberty. afaik, all needed patches are in 16:04:19 ok, then lets start with this one 16:04:25 #topic branching stable/liberty 16:05:13 so, centos is working? 16:05:47 yes. markvan found a needed change to the server-apache recipe that got centos going 16:06:18 that's already been merged and validated 16:06:33 i ran into some issues with the latest patch for the openstack-chef-repo regarding the array of possible interfaces, since it exploded with an error while trying to .lowercase the array 16:06:44 has anybody else seen that? 16:07:23 humm. no, I've been using it without issues... vagrant 1.7.4 16:07:44 i have not. running an aio build right now 16:08:18 ok, maybe that was related to the vagrant version i was using 16:08:25 also vagrant 1.7.4 here 16:08:34 i will check that, just wanted to see if anybody else saw this one 16:09:31 so lets branch stable/liberty then 16:09:46 i tried to figure out the exact process to do this 16:10:01 since there were a lot of mails regarding this topic in the last time 16:10:06 still not sure about it 16:10:17 biggest question for me are the permissions right now 16:10:33 who has the permissions to branch our repos? 16:10:43 who did it last time? 16:10:47 we have a wiki page for the basic's https://wiki.openstack.org/wiki/OpenstackChefStablebranchCreateNotes 16:12:22 I think project owners need to handle the branching, jj did the initial branch work 16:13:08 ok, i will ping him later about this 16:13:59 so i can start the branching today if there are no objections? 16:14:13 sounds good to me 16:14:24 but I think the branching is done from within gerrit, here: https://review.openstack.org/#/admin/projects/openstack/cookbook-openstack-bare-metal,branches looks like all the cores can do it. 16:14:49 looks good 16:15:49 then after branching, some patches are needed on both sides, stable and master. 16:15:55 i found something that i'll get in a bug: trove cookbook doesn't have good test coverage (only suse tests) 16:16:41 not sure if we should go for a better suse coverage without anybody from suse support the project ;) 16:17:52 #action jklare branch all our repos for stable/liberty 16:18:08 yeah. someone from suse helping drive support there would be great 16:18:50 sc` i think that leads into our next topic 16:19:18 #topic refactoring our cookbooks (step by step) 16:19:49 since we have already talked about this multiple times, i will just jump into the actual work here 16:20:57 at the summit we discussed, that we want to get this started directly after the stable/liberty branch is done and that it is ok/needed to break the master with the related patches during refactoring 16:21:24 i thought a lot about how to properly do this to make it reviewable 16:21:59 hey i’m here now 16:22:19 imo we should try to break it down into 5 steps and push each step with a new patchset but only have one commit per cookbook in the end for the first cleanup step 16:22:36 1) remove all unneeded attributes from the attributes file and template 16:22:54 2) move all specific attributes either to documentation or a specific recipe 16:23:25 3) cleanup the rest of the attributes by replacing the template with the new template logic and adapt the recipe where the template ressource is called 16:23:49 4) adapt the specs (unit tests) to work again 16:24:43 5) wait for the other cookbooks to get finished with the same steps to make proper integration testing possible again 16:25:18 if we hit step 5 for all cookbooks, we should be able to make all the small adaptions to all cookbooks to get a full stack up and running again before we actually merge anything 16:25:54 seems reasonable 16:29:26 RE: i found something that i'll get in a bug: trove cookbook doesn't have good test coverage (only suse tests) 16:29:44 jklare, didn’t we have a discussion about dropping SUSE 16:30:30 i know it's not officially called out as supported on the wiki, only ubuntu 14.04 and centos 7.1 16:30:31 yeah, that is the next thing i wanted to discuss here if everybody is fine with the plan for our refactoring commits 16:30:34 jklare: sounds like a resaonable approach, probbaly need to track in the commit msg what step each cookbook is on to make it easy to track 16:30:52 markvan yeah, or as a comment or something 16:31:18 but the commit message might be better since its easy to see in the gerrit overview 16:32:49 so any comments or thoughts about dropping old code (like the vmware attributes or suse support) that has not been adapted in the last year 16:33:04 ? 16:33:22 DO IT 16:33:26 that’s my comment 16:33:40 echoing j^2 16:33:58 if it hasn't been touched in the past year, nobody cares 16:34:08 and if somebody does care, they can submit a review to add it back 16:34:14 agreed 16:34:43 that said, i wonder how many of our cookbook consumers are actually on icehouse/juno 16:35:02 i am :D 16:35:10 with all production setups ;) 16:35:40 yup. same here 16:36:21 we are actually on liberty...but have wrappered most of the cookbooks for our needs 16:37:39 ok, if there are no big objections against dropping the code here, i will warp this meeting and our decisions later i a short mail to the mailing list to get people informed 16:38:49 s/warp/wrap/ 16:39:43 sounds perfect 16:39:51 another topic related to this refactor and branching... 16:40:11 what are the plans for moving tools/platforms forward? 16:40:41 I think we're good on the ChefDK for now, but what about U 15.x? tackle that after the refatoring? 16:40:50 ubuntu? 16:40:54 no no no no no no no 16:41:02 only “LTS” versions 16:41:41 ok, then we should add some doc around our version table in regards to that 16:41:50 i think we can look into 15.x after the refactoring in the form of a wrapper recipe or something similar 16:41:55 god i don’t want to even think of that moving target 16:42:05 and 16.04 isn’t that far away 16:42:19 openstack-model-t could fill that gap :x 16:42:32 when our community grows then we can look at the non-LTS supports 16:42:39 sc`: actually, that’s not a horrible idea 16:42:48 our goal for now is 14.04 with refactored cookbooks and liberty i think 16:43:07 and as soon as there are mitaka packages its 14.04 with refactored cookbooks and mitaka 16:43:22 then we can release refactores/stable/mitake 16:43:42 and look into 16.04 mitaka support 16:43:53 sure, good summary 16:44:10 i think the main blocker for 14.04 mitaka might be the ubuntu packages 16:44:11 yeah. i think for now just targeting LTS releases of ubuntu is going to be the best way forward 16:44:12 agreed 16:44:13 but we will see 16:44:19 until we get more active contributors :D 16:44:51 and with the work we’re doing and the salesmanship we should start doing we should see our community grow soon 16:45:41 we have one new guy from my team here today :) 16:45:48 o/ 16:45:53 hi! 16:47:04 hi! 16:47:53 welcome calbers 16:48:26 i'll get the refactoring of the cookbooks started soon :) 16:49:30 sounds good 16:49:49 jklare: just to clarify, get the branch done, but skip step 4 for the new master branch https://wiki.openstack.org/wiki/OpenstackChefStablebranchCreateNotes to stick with liberty packages 16:50:08 markvan ok 16:50:20 more topics for today? we have 10min left 16:50:59 the tl;dr on stable/liberty? 16:51:05 we stamping this week? 16:51:16 <— to lazy to scroll 16:51:27 j^2 i have an action item to branch today 16:51:33 or asap ;) 16:51:36 nice, you’ll take care of it? 16:51:48 j^2 thats something i wanted to talk to you about 16:51:58 cool, we can take it offline 16:52:05 j^2 we can have a quick zoom session after this one if you can spare some minutes? 16:52:08 sure 16:52:37 ok, if there are no more topics, thanks for attending and see you around in the channel or next week on monday :) 16:52:41 #endmeeting