16:06:09 #startmeeting oslo 16:06:10 ./ 16:06:10 Meeting started Mon Apr 27 16:06:09 2015 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:06:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:06:13 The meeting name has been set to 'oslo' 16:06:18 o/ 16:06:22 yo 16:06:24 o/ 16:06:25 sorry, everyone 16:06:25 o/ 16:06:26 our agenda: 16:06:26 #link https://wiki.openstack.org/wiki/Meetings/Oslo 16:06:26 courtesy ping for jd__, dims, bnemec, flaper87, harlowja, viktors, rpodolyaka, zzzeek, sileht, kgiusti, dansmith, sdague 16:06:26 courtesy ping for redrobot, jungleboyj, zhiyan, therve, amotoki, GheRivero, bknudson, ihrachyshka, jogo, dougwig, sreshetnyak, amrith 16:06:34 fancy meeting y'all again ... been a while. 16:06:38 * jungleboyj is so confused 16:06:48 * dhellmann is glad dims is taking over next week 16:06:49 Ah, so that wasn't intentional. :-) 16:06:50 o/ 16:06:54 :) 16:06:55 hi 16:07:02 jungleboyj: sorry, I didn't notice I was in the wrong window 16:07:13 * redrobot is also somewhat confused 16:07:45 FTR, I'll hand over the chair to dims next week, but I figured I'd help out since he was away last week 16:07:57 #topic Review action items from previous meeting 16:08:01 dhellmann: thanks! 16:08:04 'thanks again to harlowja_away for running the meeting last week 16:08:07 np 16:08:11 #link http://eavesdrop.openstack.org/meetings/oslo/2015/oslo.2015-04-20-16.00.log.html 16:08:11 it was jee golly fun 16:08:18 #info harlowja_at_home poke dhellmann with stick about https://review.openstack.org/#/c/163163/ 16:08:23 he did, and I added a comment 16:08:38 a couple of weeks back we had said we would approve some of the specs 16:08:39 lol 16:08:47 deja vu 16:08:57 I did that with some, but someone edited my notes and now I don't have the links 16:09:00 * dhellmann glares at dims 16:09:18 sorry dhellmann! 16:09:24 I think it was just http://specs.openstack.org/openstack/oslo-specs/specs/policy/test-tools.html actually 16:09:57 the one on oslo.log (https://review.openstack.org/#/c/164851/) is ready, I think -- sdague has told me he was thinking of another approach, but that he believes this one might work 16:10:03 or something to that effect 16:10:32 there are quite a lot of other specs up for review 16:10:35 #link https://review.openstack.org/#/q/project:openstack/oslo-specs+is:open,n,z 16:11:08 we can talk more about that when we get to liberty planning 16:11:09 dhellmann: so i can Workflow+1 the https://review.openstack.org/#/c/164851/ today 16:11:18 dims: sounds good 16:11:32 o/ 16:11:43 #topic Red flags for/from liaisons 16:12:01 none for keystone 16:12:39 none for Cinder 16:12:48 dhellmann: do we have a list of people (and their projects) who volunteered to be liaisons? 16:13:08 dims: good question, we need to send out a new request for volunteers 16:13:13 https://wiki.openstack.org/wiki/CrossProjectLiaisons 16:13:19 dhellmann: ack, i'll do that 16:13:22 the list is in the wiki at ^^ (thanks bknudson ) 16:13:35 thanks bknudson 16:13:40 #link https://wiki.openstack.org/wiki/CrossProjectLiaisons 16:14:02 we also need to sort out volunteers from our team to be liaisons for other teams (like release and qa) 16:14:22 dims: I'm happy to stay on as the doc team liaison 16:14:37 dhellmann: thanks 16:14:37 dims: and for the logging working group 16:15:00 we should get someone else involved in the stable branch work, so we have more training there 16:15:05 anyone interested in the other groups, please let me know 16:15:08 right dhellmann 16:15:31 #action dims send email to -dev list requesting volunteers for liaisons 16:15:46 #info dhellmann to be oslo liaison to documentation team for liberty 16:15:57 #info dhellmann to be oslo liaison to logging working group for liberty 16:16:34 #topic Releases for this week 16:16:46 #info oslo.messaging 1.8.2 for kilo (this release includes fixes related to the heartbeat feature) 16:17:08 I'll tag that as soon as we get https://review.openstack.org/#/c/177772 to merge 16:17:22 are there any other releases needed? 16:17:47 not that i know 16:17:52 i did not see any other requests 16:18:22 ok, we can look at the unreleased changes between now and next week and make plans for next week if we have others 16:18:35 #topic Ongoing work & Review priorities 16:18:48 we have quite a few specs open, as mentioned earlier 16:18:52 #link https://review.openstack.org/#/q/project:openstack%2Foslo-specs+is:open,n,z 16:19:09 we need to settle on which we're going to try to finish for sure in liberty 16:19:27 though we tend to approve new ones at any point in the cycle, so that won't be the full list, just the start 16:19:35 right 16:19:36 for some of those older than 4 months, should we just abandon them? 16:19:56 or put nice comment, saying something, then abandon? 16:20:06 +1 to nice comment first 16:20:20 :-) That usually works best 16:20:20 * harlowja_at_home wonders what our policy should be for that (its not that important, just wondering) 16:20:22 harlowja_at_home: based on that email thread from a while back, I think abandoning sends the wrong message. A nice message and a -1 seems better, and we'll just leave them out of our reviews. 16:20:28 k 16:20:44 dhellmann: i'd even wait a week before -1 16:20:53 dims: sure 16:21:09 we could put a nice cat picture and then -1 (who doesn't like nice cat pictures, lol) 16:21:22 heh 16:21:26 :-) 16:21:28 are there any other critical issues to be looking at? 16:22:06 dhellmann: the oslo.messaging is the only one 16:22:17 ok, good 16:22:26 #topic liberty planning 16:22:39 as with the kilo summit, we need to be working together on the schedule 16:22:58 dhellmann: is there a calendar of some kind ? 16:23:02 we can leave it up to dims to decide when to schedule something, but we should help him out with deciding *what* to discuss 16:23:16 #link https://etherpad.openstack.org/p/liberty-oslo-summit-planning 16:23:20 zzzeek: we have slots 16:23:37 #link https://libertydesignsummit.sched.org/overview/type/design+summit/Oslo 16:23:38 zzzeek: the slot schedule is at https://docs.google.com/spreadsheets/d/1VsFdRYGbX5eCde81XDV7TrPBfEC7cgtOFikruYmqbPY/edit#gid=569963128 16:23:52 dhellmann: ah! yes this is what i was looking for 16:23:52 oh, or that easier to read form :-) 16:23:55 y either one 16:24:12 ah great 16:24:24 so this is everyone! great 16:24:24 we will have even more overlap than usual with other projects because we asked for and received more slots 16:24:49 please see the "Doug's proposed allocation" at the end of the etherpad 16:24:55 Yeah, when I was checking boxes for my personal schedule there was a lot of Oslo. :-) 16:25:21 as dims said, my first take at a schedule is at the bottom of the etherpad 16:25:23 cool, looks like yet another super-fun summit :-P 16:25:37 I came up with 8 fishbowl out of 9, and 8 working out of 8 16:25:52 I have a couple of proposals for what to do with the extra fishbowl session 16:26:10 given the recent conversations about deprecation, I proposed a new topic on line 208 16:26:13 * harlowja_at_home keeps on thinking of https://tinyurl.com/pk8amfa (or similar) when fishbowl is mentioned, lol 16:26:42 bring SCUBA gear. 16:26:46 several proposed sessions need "drivers" for the meeting 16:26:55 ++ 16:26:58 in the past we've said we wouldn't hold sessions without a driver, so we need folks to step up for those 16:27:59 dhellmann: earlier we start filling up the sched.org the better it is for everyone to plan their schedule i think 16:28:03 if you're interested in the deprecation topic, please add your name to the list so we know if that's a useful idea or if we should discuss something else instead 16:28:28 +1 16:29:19 the fewer oslo topics there are the more other groups we can barge in on. 16:29:42 :) 16:29:51 there's already a lot of overlap with keystone sessions :( 16:30:08 bknudson: reminds me, is there a policy session in your track? 16:30:21 dims: we haven't defined the sessions yet 16:30:27 dims: that is planned for tomorrow. 16:30:27 bknudson: yeah, I'm going to be running back and forth between sessions in other tracks all week 16:30:29 I think there will be a lot of discussions around policy. 16:30:31 morganfainberg: ok 16:30:52 and i do expect a ton of discussion around policy 16:31:10 dims: i was holding off on sessions until we had liberty priorities lined up 16:31:15 dims: which is also tomorrow 16:31:19 :) 16:32:32 is there anything people really wanted to talk about but not in the list? 16:33:04 I left out 2 sessions from the original proposal list, "something something new libraries" and "improving developer docs". Were those particularly important to anyone? 16:33:43 they're important... not sure that a session is reqd for either. 16:33:51 right bknudson 16:33:54 right, I meant the sessions 16:34:59 there's nothing graduating? 16:35:08 harlowja_at_home: help me come up with catchy titles for sessions? :) 16:35:08 https://review.openstack.org/#/c/141961/ 16:35:18 bknudson: working session #1 is to figure that out 16:35:28 ^ maybe new library that i'd like to make (ironic has copied it into itself) 16:35:58 dims, sureee, will help with title,s ha 16:36:07 harlowja_at_home: maybe we can include that in working session #1? make it about new libs not just graduations? 16:36:13 I'm looking forward to a bunch of meetings with "something something" 16:36:22 I want to get morganfainberg's strictabc stuff into a library asap 16:36:22 can someone constrast “fishbowl” with “working” room styles for me quick 16:36:41 bknudson: the more vague we make it, the less likely we'll have people who won't have useful contributions? :-) 16:36:45 dhellmann: I'll roll that up into a github repo as my next priority 16:37:07 zzzeek: a fishbowl session is like what you experienced at the last summit, with contributors up front and observers spread out in the back of the room 16:37:12 fishbowl - traditional one or two rows of active participants and everyone else listening in. 16:37:16 a working session is a smaller room, and just contributors 16:37:20 dhellmann, sure, sounds good 16:37:21 dhellmann: k 16:37:30 morganfainberg: ++ 16:37:33 zzzeek: working rooms are much smaller. 16:37:43 working - square or round everyone actually doing something together 16:37:51 not much fun to look at 16:37:52 zzzeek: we wanted a way to get just the actual contributors together in a room to do some actual design work 16:38:30 the workroom sessions should be more like a meetup. 16:38:31 harlowja_at_home: cool, I'll update the notes 16:38:49 like the midcycle meeupts 16:38:51 meetups 16:38:58 bknudson: you mean mid-cycle stule 16:39:02 y 16:39:09 bknudson: not having been to one, I'm not sure what those look like either 16:39:37 you are invited to the keystone one. 16:39:44 :) 16:39:46 aw, thanks! :-) 16:40:07 dhellmann: yes come to keystone midcycle ;) 16:40:12 should we have a oslo mid-cycle too? :) 16:40:26 do you want to get stuff done? might want to have one. 16:40:33 In Hawaii please. ;-) 16:40:35 dims: we did, during juno -- jd__ & the other enovance folks hosted it 16:40:49 bknudson: +++++ 16:40:56 bnemec: somewhere cool during the summer, please 16:40:57 bnemec: ++ 16:41:16 I think the nova midcycle is here in rochester ( bnemec ) 16:41:31 bknudson: No kidding? 16:41:35 i'll try to figure out something 16:41:40 bnemec: yes, bldg 025 16:42:19 bknudson: Cool, I may have to drop by. Maybe I can get my pxe booting spec written before then. 16:42:40 bknudson: rochester, mn or rochester, ny? 16:42:44 mn 16:43:05 it's a hotbed for openstack activity 16:43:13 +1! :-) 16:43:35 bknudson: and i know both the indian restaurants :) 16:43:35 isn't there a list of these somewhere in the wiki? 16:43:55 Yeah, there used to be anyway. 16:44:20 dhellmann: are we having an oslo dinner in vancouver ? :) 16:44:31 the most senior person pays right? 16:44:33 zzzeek: we could -- I haven't planned anything 16:44:33 lol 16:44:33 * bnemec can't find it though 16:44:44 my guess is dhellmann has to then pay? 16:45:07 haha 16:45:24 *maybe not, not sure who has been around this industry the longest :-P 16:45:47 I think by definition dims is most senior now. :-) 16:45:52 * dhellmann thinks harlowja_at_home is calling him old 16:45:53 :) 16:45:55 lol 16:45:57 *senior( 16:46:00 *senior* 16:46:00 #link https://wiki.openstack.org/wiki/Sprints 16:46:07 they're called sprints I guess. 16:46:22 bknudson: is that it? I don't see one for nova on that list so I wasn't sure if that was really it 16:46:35 y i haven't heard the nova one yet 16:46:56 That's the page I am aware of. 16:47:02 yeah, apparently that's it: http://lists.openstack.org/pipermail/openstack-dev/2015-February/056310.html 16:47:04 so action for me, research oslo mid-cycle possibilities 16:47:04 there's no keystone mentioned either 16:47:16 dims: you can #action yourself 16:47:20 Probably not populated yet since we haven't actually made it past summit. 16:47:22 ah k 16:47:38 #action dims to research oslo mid-cycle possibilities 16:48:06 as much as I'd like to spend a few days in a conference room with all of you, we should probably have a theme or focus identified first :-) 16:48:16 agree dhellmann 16:48:39 like a party theme? 16:48:40 nice 16:48:49 Hawaiian? 16:49:04 ;) 16:49:28 dims: has ttx given you a deadline for settling our summit schedule? 16:49:28 harlowja_at_home: i am still groggy from TZ 16:50:04 dhellmann: was just checking my emails, i did not see a specific date yet. will respond back on oslo channel when i see one 16:50:18 earlier the better i think 16:50:22 dims: sounds good 16:50:23 yeah 16:51:05 we should also start making notes about things like "don't let this overlap with a keystone session so bknudson can attend" and that sort of thing 16:51:15 that will make fitting them into the slots easier when the time comes 16:51:44 so bknudson et all, make sure you add your names in the etherpad so i can adjust 16:52:03 is there a constraint solver that runs on the sessions schedule, can we like borrow that for pip, lol 16:52:13 harlowja_at_home: haha 16:52:15 we can't promise everyone a perfect schedule, but we can try to make sure key folks have a chance to be at sessions 16:52:40 harlowja_at_home: I wish. This is probably one of the hardest parts of the PTL role. :-) 16:52:40 +1 16:52:51 is the list at the bottom (proposed allocation) the likely topics? 16:53:08 bknudson: yes "Doug's proposed allocation" 16:53:24 bknudson: unless there is a really really strong new candidate in the next couple of days, which seems unlikely 16:53:51 out of the list proposed so far, I think only 2 aren't in that set in any way (some were combined) 16:54:36 I don't see myself needing to attend any of those, so you don't have to work around my schedule. I'll just show up at whatever's open. 16:55:01 bknudson: ok, I was just using you as an example 16:55:35 a better example is that oslo.versionedobjects intro, for which we'll need dansmith 16:56:06 alright, we're about out of time and I want to end my term under budget 16:56:12 #topic open discussion 16:56:29 oslo.messaging stable/kilo release today? 16:56:37 bknudson: yeah, we need one more patch to land first 16:56:52 https://review.openstack.org/#/c/177772/4 16:57:05 recheck 16:57:18 did we hit some sort of race? 16:57:43 "Too many connections" -- probably not unexpected in a large-ops test. 16:58:03 hmm 16:58:22 ok, I'll work with sileht on that 16:58:56 must be caused by that help string getting slightly longer. 16:59:21 * dhellmann hopes not 16:59:38 alright, I think that's all for today 16:59:40 haha 17:00:11 thank you all again for your help this release, it has been great working with you all as ptl and I look forward to being part of the team again for liberty 17:00:20 :) 17:00:26 woot 17:00:29 many many thanks dhellmann 17:00:35 o/\o dhellmann 17:00:35 for he was a jolly good fellow and nobody shall deny 17:00:54 (that's a high five, not some weird bird face, ftr) 17:01:07 bnemec: ok, I thought maybe it was a midwestern cricket or something 17:01:12 :-) 17:01:16 Heh 17:01:17 thanks, all! 17:01:19 #endmeeting