16:00:36 <j^2> #startmeeting openstack-chef
16:00:37 <openstack> Meeting started Mon Sep 28 16:00:36 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:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:41 <openstack> The meeting name has been set to 'openstack_chef'
16:00:43 <j^2> ah nice, your here
16:00:47 <j^2> #chair jklare
16:00:49 <openstack> Current chairs: j^2 jklare
16:00:54 <j^2> it’s all you buddy
16:01:19 <jklare> ok then
16:01:34 <jklare> i guess we will wait some minutes till everybody is here :)
16:02:04 <j^2> :D
16:02:53 <jklare> anything you want to discuss j^2 ? since we have no official agenda for today
16:03:21 <sc`> o/
16:03:43 <j^2> nothing off the top of my head, i think we’re all in all on a good path. our reviews are going through pretty quickly
16:03:44 <sc`> i'm back from the dead! :D
16:03:48 <j^2> yay!
16:04:06 <jklare> cool
16:04:16 <jklare> they did not eat your brain i hope?
16:04:30 <sc`> nope. all appears intact
16:04:38 <jklare> great :)
16:04:51 <j^2> Hey, watching “Fear the walking dead” tells me otherwise
16:05:00 <j^2> you’re in LA aren’t you Sam?
16:05:06 <jklare> ^^
16:05:07 <j^2> oh wait, bay area that’s right
16:05:08 <sc`> no, nut i was
16:05:11 <sc`> bay area
16:05:18 <j^2> :D
16:05:36 <jklare> any topics from your side sc` ?
16:05:49 <sc`> on the centos front, i have nothing new to update. liberty requires even more repos than kilo, and none of them are what we have in -common
16:07:48 <j^2> great
16:08:09 <jklare> i would like to talk a bit about the refactoring during this cycle and would be more than happy for suggestions for core features/bugs we should add/remove during this cycle
16:08:19 <j^2> there’s been announcements about rcs so we should be seeing upstream pkgs for liberty soon right?
16:08:30 <j^2> jklare: +1
16:08:51 <sc`> hopefully. there are packages out there, but shoehorning it into chef has proven trickier than initially thought
16:09:14 <jklare> #topic refactoring during liberty cycle
16:09:46 <jklare> so basically the most of my ideas is already in the spec that got merged recently
16:09:56 <jklare> http://specs.openstack.org/openstack/openstack-chef-specs/specs/liberty/all/refactor_config_templates.html
16:10:02 <sc`> i'll try to sit in on this week's rdo packaging meeting
16:10:12 <j^2> yep, they are solid, but the challenge is that it’s gonna be….a lot of work right?
16:10:30 <jklare> since this is a quite big spec, i think we should follow markvans suggestion and break it down into blueprints
16:10:54 <sc`> agreed. what, one bp per project?
16:11:00 <jklare> i think so
16:11:26 <j^2> that seems not horrible
16:11:31 <jklare> but we might need to fix our integration testing before we can actually start working on any bp
16:11:38 <j^2> but skip the spec process with it, just make the bp
16:11:48 <jklare> ^^+1
16:12:35 <jklare> because i think as long as our integration testing is not working, we should not start refacoring such big parts of cookbooks
16:12:47 <sc`> yeah. we need to get integration up and going
16:12:53 <jklare> did anybody look at this yet?
16:13:01 <sc`> otherwise, refactoring will be like shooting in the dark
16:13:32 <sc`> i'm just getting back into things. haven't looked much into anything the past week or so
16:13:49 <j^2> yeah i haven’t touched the int tests either
16:14:01 <j^2> i can spend some cycles today though between some meetings
16:14:11 <jklare> ok, so maybe we can make this our main goal until next week?
16:14:21 <j^2> seems reasonable
16:14:37 <j^2> thats the main gate before other projects can start working
16:14:54 <jklare> and in parallel i will try to write down a first blueprint with all the working steps for the compute cookbook
16:16:09 <jklare> more suggestions or comments on this topic?
16:16:40 <j^2> not here
16:16:40 * markvan hi
16:16:49 <jklare> howdy
16:16:52 <jklare> ;)
16:17:04 <sc`> hi markvan
16:17:48 <markvan> seems like int testing it close, but need to have it working to start getting benefits
16:18:09 <j^2> markvan: yep, that’s our goal for this week :D
16:18:35 <jklare> yeah, basically getting liberty to run on something would be my next topic here i guess
16:19:02 <jklare> #topic running liberty (and integration testing) on trusty?
16:19:23 <j^2> simply said, +1 :P
16:19:51 <jklare> so i have absolutely no experience in running liberty on trusty, but know that it works (with some pain) on vivid
16:20:24 <j^2> yeah i haven’t looked at it either. I don’t think they have an install guide written yet either
16:21:22 <jklare> imo the question here is if and when we want to make the switch to systemd on ubuntu and what our plan for the other distros is
16:21:38 <markvan> I have not looked at the other gates latey, have they now switched to vivid for liberty?
16:21:55 <jklare> package i don't think so
16:21:56 <j^2> they shouldn’t be, vivid isn’t LTS
16:22:42 <sc`> isn't wily shipping with liberty?
16:23:33 <jklare> not sure
16:25:18 <j^2> yeah i’m not seeing anything obvious stated either
16:26:18 <jklare> i think package wise we would be a lot faster if we went for wily, but ofc that is not an lts and also means a big switch to systemd
16:26:43 <jklare> and also i am not sure when and if we would acutally get wily instances from infra
16:26:51 <sc`> yeah. last lts is 14.04 iirc
16:27:00 <jklare> yep
16:27:39 <jklare> so stick with 14.04 and feel the full pain of the ubuntu package release management for openstack?
16:28:26 <sc`> i'd say go with what gets us the path of least resistance
16:28:31 <j^2> i think that’s our only option
16:28:45 <j^2> because that’s what the other projects are going to be doing
16:29:11 <jklare> agreed
16:29:58 <jklare> more thoughts on this?
16:30:22 <sc`> none here. seems pretty clear
16:31:02 <j^2> nope
16:31:55 <jklare> ok, one last topic from my side (which is super old)
16:32:28 <j^2> :D
16:32:41 <jklare> #topic synchronous communication meetings
16:32:52 <jklare> we have not talked about this in quite some time
16:33:08 <j^2> nope
16:33:48 <jklare> but for me this is still something that is/was important for us working together and syncing up
16:33:55 <j^2> makes sense
16:35:24 <sc`> any thoughts on how to improve it? right now, we just have this hour. everything else is async
16:35:50 <jklare> imho we need something like the hangouts sessions back
16:36:55 <jklare> and i think for the project flow itself this would be more important than beeing part of the big tent (not saying that i think we should leave it)
16:37:37 <sc`> is there something we could use that is more transparent than hangouts?
16:38:24 <jklare> there are hundrets of videochat solutions out there i guess, question is if we want to invest time into finding the best one for us, or if we think its not that important
16:39:38 <sc`> i'm in agreement that we need more synchronous communication, given the time differences, but i'm just trying to think of something that would work with the project being part of the big tent. we ditched hangouts as a provision of moving to the big tent
16:40:52 <sc`> fwiw, i'm around most hours of my evenings until pretty late, just focusing on other things
16:41:45 <jklare> j^2: markvan ?
16:41:48 <j^2> yeah i got nothing when it comes to synchronous meetings
16:42:13 <j^2> officially speaking we can’t santion one, that’s was one of the agreements for being part of the “big tent"
16:42:23 <j^2> IRC should be “good enough"
16:42:51 <sc`> it is, but there often goes some days when nothing is said in the channel
16:42:53 <markvan> yeah I miss the face to face hangouts, but maybe we should focus on better irc meetings
16:43:27 <sc`> given the size of the channel, it can be a bit confusing at first
16:43:37 <j^2> sc`: yeah it’s frustrating nothing happening said in the irc channel
16:43:41 <jklare> markvan: sounds good, any thoughts on what we should improve?
16:43:46 <markvan> we could meet a bit more often, but for shorter times and try to get a small  agenda to focus on.
16:44:28 <sc`> i lurk on other channels and there are certain folks i see that make themselves available beyond a standard work day, but i'd hate to mandate something like that
16:45:07 <sc`> given that it's all volunteer-driven, i'm not sure it could be
16:46:16 <jklare> how about everyday at 15:00 UTC for 10mins in our own channel? you all throw the topics you want to dicuss at me during the day/night and i can put together a short agenda for each evening
16:46:51 <jklare> ofc we can substitue me in this case with an etherpad or something
16:47:35 <jklare> 13min left for this meeting btw
16:48:16 <j^2> yeah i thin it would be nice to have that sync, but maybe just wed/fri? not force it everyday that sometimes’ll be over kill?
16:48:28 <j^2> but at the same time, if no progress is made, then the sync you can say no progress
16:48:31 <j^2> i dunno
16:49:04 <markvan> that concept sounds like a good way to try to sync more often
16:50:18 <sc`> definitely worth trying
16:51:42 <j^2> cool, so 1500UTC tomorrow then?
16:51:51 <jklare> sounds good, lets try meeting tomorrow 15:00 UTC in the #openstack-chef channel and i will prepare an etherpad for this
16:52:15 <markvan> k
16:52:22 <j^2> awesome
16:52:34 <jklare> any more topics for the last 8mins?
16:53:04 <sc`> packagers need to be consistent with naming things
16:53:11 <sc`> keystone.wsgi vs wsgi.py is maddening
16:53:19 <jklare> :)
16:55:11 <markvan> yeah, I see some discussion on openstack trying to create generic packages and push that across the platforms
16:55:29 <markvan> not sure how far that will actually get, seems like an up hill battle
16:55:58 <j^2> yep
16:56:15 <markvan> (Solum project0
16:57:33 <jklare> i think we have to take this discussion to our channel
16:57:41 <j^2> yep
16:57:50 <sc`> yup. we're about at time
16:57:59 <jklare> thanks for attending
16:58:03 <j^2> :D
16:58:13 <jklare> #endmeeting