16:01:41 <j^2> #startmeeting openstack-chef
16:01:42 <openstack> Meeting started Mon Aug 10 16:01:41 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:01:44 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:46 <openstack> The meeting name has been set to 'openstack_chef'
16:01:52 <j^2> hey everyone!
16:02:27 <j^2> i’ll give everyone a few mins to join
16:03:07 <sc`> o/
16:03:18 <j^2> sc`: while i have your ear...
16:03:40 <j^2> can you make the…pedantic changes for that review so we can get the testing repo in?
16:04:00 <j^2> i want to push this asap, so we can get stable stampped asap
16:04:16 <sc`> yup. i'll work on that
16:04:37 <jklare> hi o/
16:05:10 <j^2> awesome thanks sc`
16:05:23 <j^2> we need to start working on liberty like…last week
16:05:52 <markvan> howdy
16:06:32 <j^2> so i’m gonna give this free form, a shot so lets start the discussion
16:06:42 <j^2> i do have one thing i’d like to mention
16:06:57 <j^2> we’ve lost a lot of our drive lately, i’m seeing this becoming a problem
16:07:08 <j^2> is it just because its summer?
16:07:16 <j^2> or are people loosing interest in this project?
16:08:42 <jklare> no idea
16:09:29 <j^2> :(
16:09:36 <j^2> i’d like some feedback
16:09:55 <jklare> maybe everything is working too good to patch it ;)
16:10:14 <j^2> jklare: :D that would be awesome, but i don’t think thats true
16:11:07 <j^2> sc`, markvan any thoughts?
16:11:08 <markvan> for me it's 2 things, a lull between releases and other approaches being considered
16:11:32 <j^2> markvan: yep, i hear that through back channels too
16:11:47 <jklare> i think for most people its just easier to fork the upstream project and not have to deal with all these gerrit/testing/codereview stuff
16:12:43 <sc`> for myself, i have to context switch between icehouse and this project
16:12:52 <j^2> sc`: that makes sense
16:12:52 <jklare> and something maybe not directly related, but it is becoming more and more complex to understand and patch trough all of the cookbooks
16:13:32 <j^2> jklare: yep, that’s gotten to the point where its only like 1/2 of the people of the subset of the group that even thinks about this stuff can patch intelegently.
16:14:08 <jklare> i am currently trying to get a full kilo cluster with to work with our forks of the cookbooks and even tough i have read a lot of code from the cookbooks it still takes me a lot of time to figure out where to patch stuff
16:14:36 <j^2> so where does this leave us?
16:14:36 <sc`> one thing that i've noticed is that it isn't nearly as straightforward as it used to be to use the cookbooks with existing chef infrastructure
16:15:12 <jklare> so maybe a big goal for the next cycle could be to simplify all of the cookbooks
16:15:24 <j^2> i’m working on something i’m calling the “model-t” build of openstack; it’s the chef build of the install guide
16:15:42 <j^2> its not taking anything from the community, and is opinionated
16:15:51 <jklare> and maybe not support all possible options, but allow users to wrap these cookbooks more easily
16:16:07 <j^2> jklare: i’d love that, but i’m worried no one is going to around for that
16:16:25 <jklare> ?
16:16:44 <jklare> you think nobody want to do that?
16:17:18 <jklare> i mean its basically just a decision on how to continue the whole development process
16:17:24 <j^2> i think people would love to do that, but it’s a TON of work
16:17:31 <jklare> of course it is
16:17:49 <jklare> and moving a lot of code to oslo also was a lot of work
16:18:12 <j^2> yep
16:18:20 <jklare> but it will not get easier by just not doing this work
16:18:25 <j^2> true
16:19:08 <jklare> question is if the majority of our active contributors want to commit to that or not
16:19:45 <j^2> yep
16:21:21 <jklare> btw. i am not sure if that is even the reason why we do not have more contributors
16:21:30 <sc`> we need to have an alternative to build openstack from nothing using the cookbooks. chef-provisioning is awesome and all, but it doesn't lend itself to portability
16:22:31 <j^2> ok, so yeah that’s what my model t is
16:22:38 <j^2> let me push it up one sec
16:23:58 <j^2> https://github.com/chef-partners/openstack-model-t
16:24:07 <j^2> it’s still a WIP
16:25:19 <jklare> maybe that is a good topic to talk about in a additional call/hangout something ?
16:25:35 <j^2> sure?
16:25:45 <jklare> because i do not think that we can come to a good end of this discussion in this meeting
16:25:50 <j^2> agreed
16:25:52 <sc`> +1
16:25:54 <j^2> but it’s something to think about
16:25:57 <sc`> more discussion is needed
16:26:06 <jklare> markvan?
16:26:15 <j^2> i wanted to sow the seed, i’m just worried about the future that’s all
16:26:35 <j^2> we went to so much work getting part of the foundation/big tent, then we seemed to just drop it
16:27:37 <sc`> some of that is the perception that we're still not a big tent project
16:27:49 <markvan> yeah, some type of simplification of the cookbooks would be interesting step, but I don't like to dummy something down without a good reason
16:28:38 <markvan> sc`: getting ahead on liberty would be good to help with that
16:28:50 <sc`> yup
16:29:23 <jklare> do we want to go through the agenda today?
16:29:27 <j^2> markvan: the good reason is that even with the openstack-chef-repo it’s still crazy complex, and it scares adoption. I’m in the process of helping writing a doc on how to create an AIO build on metal though so you can move from the vagrant setup to something with a physical hardware
16:30:15 <j^2> jklare: not really to be honest, i’m betting there is little to no progress with anything. Granted i do ack your commited to the 6am build in infra :D
16:30:33 <j^2> i’m feeling pretty beat up about our project
16:31:19 <jklare> so, i think the specs.openstack.org thing is mainly done (at least for the simple part of using it)
16:31:45 <jklare> the cross repo testing is also working as far as i could see from markvans  patches?
16:31:54 <markvan> yeah, spending more time on the repo doc and steps would be a good thing, and would lead to better specs/blueprints to improve the cookbooks.
16:32:17 <markvan> yup, cross repo seems to be working well.
16:32:34 <markvan> but I did not see the periodic spin get run yet
16:32:34 <jklare> so i think we are making good progress overall
16:32:48 <jklare> me neither
16:32:56 <jklare> but i wanted to ask infra what has happened there
16:33:18 <markvan> yeah, don't know where to look for issues on that
16:33:24 <j^2> :D
16:33:32 <jklare> i will ping some guys on infra
16:33:52 <markvan> thx, would be good to see that get in place
16:34:04 <j^2> cool anything else?
16:34:33 <markvan> only a couple patches that we might want in kilo....set branch date ?
16:35:08 <j^2> markvan: nope, not until that centos7 patch is in
16:35:57 <j^2> i refuse to make that happen till we can repeatably build both ubuntu and centos
16:36:06 <markvan> yup, agreed
16:36:24 <j^2> sc`: promised me he’d make it happen today ;)
16:36:29 <j^2> rrriiight?
16:36:48 <sc`> the feedback is being addressed
16:37:04 <sc`> just need to sit down for a few and finish the spec stuff
16:39:00 <j^2> :D
16:39:56 <markvan> any body know if that db slave connection patch needs to get in,  I think the base one is ready https://review.openstack.org/#/c/199917/, but the use one has a typo https://review.openstack.org/#/c/203583/
16:40:53 <j^2> cool
16:41:36 <j^2> we need the other patch fixed by the community member first
16:42:01 <markvan> and j^2 I think the neutron repo one is also ready, https://review.openstack.org/#/c/196858/  it's a step in the right direction
16:42:21 <j^2> it’s still -1 :(
16:43:10 <markvan> yeah, I was going to take a look at that again to see if I can reproduce that timing issue, but I think that is unrelated to this specific patch, it's just a bug in the network cookbook somewhere
16:43:23 <j^2> makes sense
16:43:35 <j^2> anything else?
16:43:54 <j^2> that’s to everyone ^^
16:45:12 <jklare> nope
16:45:32 <markvan> no
16:45:43 <j^2> cool
16:45:52 <j^2> i’ll give yall your 15 mins back then
16:46:18 <j^2> #endmeeting