16:00:31 <sc`> #startmeeting openstack_chef
16:00:31 <openstack> Meeting started Mon Jul 11 16:00:31 2016 UTC and is due to finish in 60 minutes.  The chair is sc`. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:32 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:35 <openstack> The meeting name has been set to 'openstack_chef'
16:01:12 <sc`> hi o/
16:12:27 <sc`> jklare: you there? anything from your end?
16:12:42 <jklare> sc` oh hi
16:12:45 <jklare> :D
16:12:54 <sc`> :D
16:13:15 <jklare> sc` not really, thanks for the style and unit patches again
16:13:49 <jklare> i am currently focussing on upgrading our production deployments to mitaka
16:13:58 <jklare> so more using the cookbooks than working on them :D
16:14:12 <sc`> i've started working on openstackclient and identity v3. it's incrementally going
16:14:41 <jklare> sounds good
16:16:06 <sc`> haven't gotten it to a point of convergence yet
16:18:17 <jklare> i think v3 will take some time
16:18:26 <jklare> i still try to get everything to work with it
16:18:34 <jklare> e.g. the dashboard :D
16:18:42 <sc`> :D
16:18:51 <jklare> i will push some patches as soon as i figure out all the options needed
16:21:49 <sc`> cool
16:23:15 <sc`> i'll try to separate openstackclient and identity v3 if i can, to make the patches smaller
16:24:16 <jklare> +1
16:25:34 <jklare> sadly it looks like we are down to 2 active ppl right now..
16:25:43 <jklare> i mean mark is still doing some reviews
16:25:45 <sc`> that it does
16:28:17 <sc`> per the survey, the demand for chef is dropping, and it shows in our community involvement
16:29:15 <jklare> yeah i guess there are enough tools out there to install some services and apply configuration
16:29:28 <jklare> so everybody can choose and chef is not the most fancy ;)
16:30:14 <sc`> everyone's happy to run their own forks i suppose
16:30:51 <jklare> yep
16:31:06 <jklare> the only question is were we wanna head with the project
16:31:35 <jklare> i do not see any reason to switch to another deployment tool
16:31:58 <sc`> i just had that discussion in my own team, and the decision was to stick with chef
16:32:09 <jklare> so i think we can just use the "official" project as our very own fork :D
16:32:19 <jklare> which works for me
16:33:01 <sc`> i think the focus should be on the production deployments. chef-provisioning has been scaled back in scope, so no sense in extending that too much
16:33:17 <sc`> the hows and should nots, etc.
16:34:03 <jklare> yeah, but i guess the biggest part of that is kind of company specific
16:34:10 <jklare> and should be solved in wrappers
16:34:13 <sc`> it is, in some ways
16:34:37 <sc`> it's about making things easy to consume in such a manner
16:35:28 <sc`> which from talking with you at the summit, it sounds doable in code already\
16:36:05 <jklare> yeah, i think the cookbooks right now are quite easy to wrap
16:37:35 <jklare> and i think one can maintain them with very few ppl
16:37:54 <jklare> but of course we can only maintain the distros we are using
16:38:02 <jklare> which is not ideal
16:38:10 <jklare> but i guess there is no way around that
16:38:45 <sc`> we can only support the distros we use
16:39:06 <jklare> and thats why i think if nobody but us two cares and patches the cookbooks, these will become our very own forks :)
16:39:15 <jklare> but as i said, thats fine with me
16:39:16 <sc`> while i like others just fine, i can't feasibly support something i can't test
16:41:32 <sc`> the only good thing about being the only ones left is there's nobody to say no. i think if we don't make it too hard for orgs to adapt, they can keep up at their own pace
16:42:34 <jklare> yeah
16:47:56 <sc`> we'll need to see about kidnapping someone from the community to review code should it just be you and i left
16:48:11 <jklare> i think we can just decide that +2 is enough
16:48:42 <sc`> but then who would be doing the workflow?
16:53:00 <sc`> okay. i haven't had enough coffee
16:53:11 <sc`> yeah. that's fine
16:53:14 <jklare> :)
16:53:48 <jklare> but i guess we can try to avoid that and just motivate some of our coworkers to help out
16:54:27 <jklare> lets see how that goes
16:54:29 <sc`> perhaps. coworkers are busy with mitaka as well
16:54:45 <sc`> so everyone's focus would be on stable/mitaka and not master
16:55:01 <jklare> which is probably fine
16:55:15 <jklare> if ppl wanna work on more stabilisation of mitaka
16:55:16 <jklare> why not
16:55:40 <jklare> we can still push mitaka patches to master and then backport them
16:55:48 <sc`> i'm fine with that
16:55:55 <jklare> usually the fixes that are good for mitaka will also work for master or newton
16:56:34 <jklare> so focussing on a stable release is not a bad thing imo
16:56:41 <jklare> makes testing and patches a bit easier
16:56:50 <jklare> since ppl are acutally using the code
16:57:04 <jklare> not just pushing stuff that only ever runs on jenkins nodes until the release :)
16:57:09 <sc`> sure
16:58:02 <jklare> 3mins left
16:58:03 <jklare> :)
16:58:10 <sc`> 2 :)
16:58:23 <jklare> i guess we can continue our discussion in the channel if needed ;)
16:58:29 <jklare> maybe there are more ppl there
16:58:31 <jklare> or not
16:58:35 <jklare> :D
16:59:03 <sc`> i think we've said enough for now. there isn't really much more traffic there either :D
16:59:45 <sc`> alright. calling it. have a good one
16:59:51 <jklare> same
16:59:57 <sc`> #endmeeting