16:01:02 <jklare> #startmeeting openstack_chef
16:01:03 <openstack> Meeting started Mon Jan 11 16:01:02 2016 UTC and is due to finish in 60 minutes.  The chair is jklare. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:07 <openstack> The meeting name has been set to 'openstack_chef'
16:01:09 <jklare> hey everyone
16:01:12 <j^2> Hey
16:01:17 <jklare> you were too early j^2 :D
16:01:26 <j^2> Ha!
16:01:42 <sc`> good $time_of_day
16:01:47 <jklare> hi sc`
16:01:56 <calbers_> o/
16:02:02 <jklare> sooooo
16:02:14 <jklare> topics for today (apart from the elephant in the room)
16:02:24 <jklare> ?
16:02:34 <j^2> Voting
16:02:47 <j^2> I need yalls votes
16:03:10 <j^2> For the board. It went out today/a couple hours ago
16:03:29 <jklare> saw it
16:03:36 <j^2> :)
16:03:39 <jklare> interesting candidates
16:03:47 <jklare> but not too many new faces
16:04:01 <jklare> which is also positive i guess
16:04:38 <j^2> Yep, that's my advantage. I have a new enough face, and new ideas to help steer OS in a better direction
16:05:00 <jklare> i do not think that your face is new to anyone out there in the openstack community
16:05:03 <sc`> gmail spammed the email for me. thanks, alphabet :D
16:05:04 <jklare> :)
16:05:22 <jklare> but i guess that is a big plus for your candidacy
16:05:35 <jklare> people know you even though you were not on the board
16:06:05 <sc`> j^2: i have a bit of a conflict of interest :p
16:06:53 <jklare> did somebody else offer you more money than j^2 sc` ?
16:07:03 <j^2> Hey! I though you could vote for a few? I need to double check that
16:07:10 <jklare> you can
16:07:22 <jklare> you can distribute your 8 votes between max 8 people
16:07:26 <jklare> obviously
16:07:32 <jklare> 9 would be too much here
16:07:53 <jklare> ok, lets get back to our chef-openstack meeting
16:07:58 <j^2> :)
16:08:16 <sc`> yes, back to the elephant in the room
16:08:18 <jklare> #topic refactoring (yay, yay, YAY!!!)
16:08:46 <jklare> so calbers_ and me made a lot of progress last week and markvan and j^2 did some good reviews
16:08:56 <jklare> sc` promised to do the same this week
16:08:57 <j^2> Yay!
16:09:05 <jklare> which is great
16:09:07 <jklare> YAY
16:09:24 <markvan> yup, put my chef hat back on for a bit...
16:09:26 <sc`> is any of it expected to work with openstack-chef-repo yet?
16:09:59 <jklare> i think all of the simplification patches (moving attributes around and using a new template logic) works with our integration test
16:10:50 <jklare> the new patch in common, which refactores a lot of the library code, will break all of this functionality until all cookbooks got the corresponding patches
16:11:02 <jklare> calbers_ and me did these patches for identity
16:11:43 <jklare> if we decide to go with this big common patch here https://review.openstack.org/#/c/249133/
16:12:30 <jklare> we need to add the endpoint refactoring (like done here https://review.openstack.org/#/c/264775/) to all other patches before we can merge them
16:12:41 <jklare> specs will just fail until then
16:13:02 <jklare> i think this would be the right way to go, but this is also the point of no return
16:13:41 <j^2> Go for it
16:13:59 <jklare> i shall not merge my own patches :D
16:14:15 <sc`> we should start getting this stuff merged this week
16:14:38 <markvan> I think your on the right track...and yeah, there's no going back after this
16:14:48 <sc`> yup
16:15:06 <jklare> great
16:15:11 <jklare> and YAY
16:15:40 <jklare> so calbers_  and me will try to do the same patches we did for identity (https://review.openstack.org/#/q/project:openstack/cookbook-openstack-identity+status:open) in all the other core cookbooks
16:15:58 <jklare> if we merge common first, we need to do this in one big patch i guess
16:16:35 <jklare> which will look like a 40% rewrite for most of them and 90% rewrite for network
16:16:55 <jklare> because our network cookbook is really really ugly right now
16:17:07 <markvan> that can only be goodness for the network story...
16:17:51 <jklare> i think network needs this if we want to keep up with all the stuff that has been done during the last year
16:18:16 <jklare> and we also need to simplify a lot of steps if we want to add all the cool new features in the next release
16:18:26 <j^2> Awesome!
16:19:01 <markvan> agreed, it's current layout was basd upon old neutron arch.   I would almost go as far as to say that nova networking should be a completely separate path/recipe/cookbook
16:19:40 <j^2> markvan: I can see/agreed with you there
16:19:43 <jklare> markvan agreed
16:19:49 <sc`> +1
16:20:31 <jklare> ok, i guess that means we should try to first get this one in (https://review.openstack.org/#/c/249133/)
16:20:37 <jklare> this will break everything
16:20:39 <jklare> YAY
16:20:55 <sc`> nova-network is different from neutron is different from other sdn solutions. each require their own deployment cookbooks/paths to be laid down properly. this isn't any different
16:21:38 <jklare> calbers_ and me will bring these 3 commits here (https://review.openstack.org/#/q/project:openstack/cookbook-openstack-identity+status:open) down to one big commit (which will be easier to review than the three are now i guess)
16:21:41 <sc`> jklare: let's break stuff :D
16:22:30 <jklare> after we merged this, we can do the same for all the other core cookbooks
16:23:11 <jklare> which will lead us to wonderful and shiny refactored core cookbooks
16:23:14 <markvan> jklare:  I see there are several small "issues" that have come up, I would like to see these tracked somewhere ( bugs or in BP work area)  (activesupport, refactor msg, other refactoring...)
16:23:26 <jklare> markvan agreed
16:23:44 <jklare> markvan we should track these in the bp (i created one a while ago, but forgot to use it=
16:24:13 <markvan> yes, that would be fine...
16:24:16 <jklare> but there is one big issue to this refactoring process
16:24:53 <jklare> calbers_ and me have but in a lot of effort so far to get these core cookbooks refactored and will continue this for all the ones we have targeted to far
16:25:25 <jklare> sadly our employer also wants to see some results ~= a deployed openstack
16:25:55 <jklare> which means that after we finished these cookbooks, we will mainly focus on the deployment with these ones
16:26:03 <jklare> and continue to patch them
16:26:26 <jklare> but this also means that we will probably not have the time to do the same refactoring for all the not-so-core cookbooks we have
16:26:45 <jklare> and after we merge common, these cookbooks will not work until refactored
16:27:15 <markvan> that's totally reasonable, we should just track TODOs in the BP for the other non-core cookcooks, and hopefully others that are interested will step in to help with those
16:27:49 <jklare> ok
16:28:19 <sc`> if core functionality for mitaka is there by the time my team gets to it, expect patches for the non-core cookbooks
16:28:26 <markvan> with focus on the core stuff, I'm sure there will be followup tweak patches to make this whole again, so it's probably for the best not to spread this to far yet.
16:29:36 <markvan> would be unneeded churn.  and it gives you more flexibility to "twist" this new design a bit further without worring about non-core stuff
16:29:52 <jklare> sounds good
16:29:52 <markvan> we just need to track it
16:30:24 <jklare> yep
16:30:43 <jklare> we will use the blueprint and i will also work again on the corresponding spec we approved a while ago
16:31:03 <jklare> to track all the details we refactored in core and give a good guideline what needs to be done for the others
16:31:55 <markvan> yeah, a high level todo list for the non-core stuff would be good
16:32:11 <jklare> agreed
16:33:16 <jklare> ok, no more topics on my list
16:33:22 <jklare> anything else you want to talk about?
16:34:02 <j^2> nope
16:34:25 <sc`> i'm good
16:50:44 <jklare> ok, thanks for attending and see your around
16:50:48 <jklare> #endmeeting