15:02:07 #startmeeting Zaqar 15:02:08 Meeting started Mon Oct 5 15:02:07 2015 UTC and is due to finish in 60 minutes. The chair is flwang1. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:11 The meeting name has been set to 'zaqar' 15:02:36 hello folks 15:02:40 o/ 15:02:42 o/ 15:03:08 #topic roll call 15:03:25 vkmc: ? 15:03:45 o/ 15:03:46 HERE 15:03:49 #topic agenda 15:04:07 #link https://wiki.openstack.org/wiki/Meetings/Zaqar#Agenda 15:04:22 Pending important reviews 15:04:31 Tokyo summit sessions 15:05:03 those are the main topics today from me 15:05:16 sweeeet 15:05:24 * flaper87 thinks we should give some love to client reviews 15:05:31 * flaper87 has been bad with reviews lately 15:05:38 flaper87: i can't agree more 15:05:58 flaper87: i'm blaming myself as well 15:06:17 i should put client review on my first priority 15:06:44 lets do it! 15:07:07 sure thing 15:07:09 #link https://review.openstack.org/#/c/206080/ websocket notification 15:07:25 i have tested it manually on my local 15:07:35 and it works great 15:08:31 i'm going to +2 it after another round test since there is a new patch set to support given subscriber 15:08:44 ++ 15:08:53 I'll take a better look at the latest patchset 15:09:07 Hooray 15:09:18 therve`: hey 15:09:41 we're talking about your notification websocket patch 15:10:25 i saw there is a new patch set, seems it's adding the support for a given subscriber 15:10:42 Yep, I snicked that in :) 15:11:33 therve: that's awesome 15:12:21 guys, any other important review we should discuss? 15:13:05 yeah, there's https://review.openstack.org/230053 15:13:08 o/ 15:13:15 sorry I'm tardy for the party 15:13:17 which fixes a stacktrace in logging decorator 15:13:44 (not a large review at all 15:13:46 ) 15:14:23 jasondotstar, do you have an update for the puppet modules you want us to review? 15:14:27 clicking... 15:14:40 vkmc: that's my question :) 15:14:49 :D 15:14:59 yes.... 15:15:20 so the latest involves working on the adding the debian install side 15:15:25 ryansb: i have +2 for that one https://review.openstack.org/230053 vkmc, flaper87 pls bless it 15:15:46 flwang1, sure, thankx 15:15:53 so far, the RPM installation works fairly well using CentOS 15:16:19 there are still a few more parameters to expose to the .conf file 15:16:35 and we need to begin writing tests as well 15:16:55 but things are moving along at a decent clip, I'd say. 15:17:00 questions for me? 15:17:25 jasondotstar: so generally, it's on track, right? :) 15:17:44 flwang1: yes, in a nutshell. :-) 15:18:05 jasondotstar: are you using pooling as default in the conf? 15:18:51 jasondotstar: i'm trying to figure out what's the reference conf for puppet deployment 15:19:10 flaper87: any comments? 15:19:54 flwang1: no, not using pooling by default 15:20:13 mmh, I think we should just go with pooling by default 15:20:24 at some point, I'd love to see that config option go away 15:20:27 and just use pooling 15:20:40 unreliable is true by default (that's probably unrelated, still...) 15:20:43 That's what we recommend as a deployment and it should probably be the default 15:20:55 jasondotstar: erm, mmh. I thought flwang1 changed that 15:20:56 flaper87: duly noted. I can add it 15:21:00 there was a patch for it 15:21:08 I mean, unreliable must be False now 15:21:13 flaper87: oh ok.... 15:21:15 flaper87: yes 15:21:15 the deprecation path was respected 15:21:39 * jasondotstar will have to take a look at setting unreliable = false 15:22:10 that needs to be in the DEFAULT section, btw 15:22:28 my point is the default conf puppet is most like a referenced conf from the deployer's view 15:22:46 it is in the default section, but it set to true and not false 15:23:13 jasondotstar: i will revisit that to make sure 15:23:30 flwang1: ack. 15:24:18 #action flwang will check the unreliable conf to make sure False is the default value for puppet 15:24:45 jasondotstar: thanks for the updates, 15:25:00 flwang1: np. 15:25:14 anything else? should we move to next topic summit session? 15:25:34 we only have 3 weeks 15:25:41 I think that's it for reviews, so yeah onto summit 15:25:58 #topic summit sessions 15:26:17 #link https://etherpad.openstack.org/p/Mitaka-Zaqar 15:27:01 we have 1 fishbowl and 3 workrooms 15:27:48 we have 2 proposed sessions, both of them targeted for fishbowl 15:27:55 I think we should use 1 workroom session for Sahara 15:28:18 flwang1: what are those sessions? 15:28:19 flaper87: are u happy to host it? :) 15:28:23 * flaper87 can't find the link 15:28:26 flwang1: sure thing 15:28:30 I'm planning to 15:28:32 yeah, sahara and horizon if we are lucky 15:28:34 :D 15:28:37 flaper87: client and horizon integration 15:29:01 Session: Client & Command Line Interface 15:29:10 Session: Realtime update for Horizon tables 15:29:27 i'm supporting vkmc on the horizon one 15:29:39 yeah, I'd go with horizon 15:29:49 it sounds like the client could use a workroom, TBH 15:30:00 We should make sure we have folks from Horizon in that session 15:30:16 flaper87: we have contacted them and got YES 15:30:37 vkmc: would you mind confirming with mrunge? 15:30:47 flwang1, sure thing 15:30:48 what? 15:31:01 confirm what? 15:31:16 mrunge, Zaqar + Horizon design session 15:31:19 hi mrunge! 15:31:22 mrunge: hah, join the session about horizon zaqar integration 15:31:31 hey o/ 15:31:40 yes, I'm interested in that! 15:31:58 mrunge, if Horizon team could discuss about this topic, we would really like to have a working session with you guys 15:32:01 we are defining our slots 15:32:02 :) 15:32:15 flaper87: should we make the horizon session as workroom as well? 15:32:27 that'd work, yes! 15:32:33 workroom sounds good to me 15:32:34 flaper87: cool 15:32:48 fishbowl is great when we need to have a bigger crowd there 15:33:19 horizoners have a single fishbowl, as we found workrooms way more productive 15:33:30 mrunge: yeah, same does Zaqar 15:34:04 for reference, I added zaquar and async to https://etherpad.openstack.org/p/horizon-mitaka-summit 15:34:23 flaper87: so for now, we have 1 session for client, 1 for horizon, 1 for sahara, all of them are workrooms 15:34:34 but did not request a real cross project session 15:34:47 (they were intended for > 2 projects) 15:34:49 mrunge: thanks 15:35:14 I have to thank *you* folks! 15:37:05 :D 15:37:28 vkmc and i are going to get some comments from your guys as for the horizon demo, but we can discuss that offline, in zaqar channel 15:37:54 so do we have any topic for the fishbowl? 15:38:16 mmh, not yet! 15:38:23 we could throw a gummy-party 15:38:41 flaper87: lol, that's an option :) 15:39:05 can we have all working sessions? 15:39:15 if we don't have a topic for it, I'd rather just give it away than coming up with a random thing to talk about that could perfectly be discussed in a hallway-track 15:39:19 I always find them more productive 15:40:06 works for me 15:41:44 anything else for the summit session? 15:42:11 let's add the sessions in the etherpad 15:42:20 https://etherpad.openstack.org/p/Mitaka-Zaqar 15:43:56 vkmc: thanks for the remind, flaper87 will add the sahara session and i'm going to polish the format :) 15:44:43 #action flaper87 will host the sahara session 15:44:51 flaper87, I'm adding dynarro for the Client/CLI, let her know 15:44:53 :D 15:45:11 vkmc: awesome, thanks 15:46:03 anything else? 15:46:09 vkmc: I will 15:46:11 hahaha 15:46:40 flwang1, nothing else from my side 15:47:01 #topic open discussion 15:47:31 * flaper87 hadn't had this much sushi before in his life 15:47:41 flaper87, is it better than sushi elsewhere? 15:47:46 flaper87: r u kidding? 15:47:58 it actually is 15:48:06 sushi is always on my lunch list 15:48:13 flwang1: LOL 15:48:18 yummy 15:48:34 i would suggest a team lunch in summit 15:48:42 given we have some new members 15:48:43 that'd be great 15:48:50 nice nice nice nice nice! 15:49:05 now I want sushi 15:49:14 can we have a sushi lunch in the summit? 15:49:15 :D 15:49:19 haha 15:49:35 if the summit food is not OK, then we will go for sushi to make flaper87 happy 15:49:37 suuuuuuuuuuuuuuuuuuuuure 15:49:43 yeaaaaaah 15:49:55 and make vkmc happy either 15:50:37 should we still use wechat as the team communication tool? 15:50:51 it worked well last time, I think we can use it 15:50:56 and the group is still there 15:51:23 yeaaah 15:51:25 gotta go folks, thanks for the meeting and talk to you soon! 15:51:29 * vkmc is excited 15:51:34 bye flaper87 15:51:41 take care, eat tons of sushi for me 15:52:26 flaper87: ttyl 15:52:55 ok, anything else? otherwise we will be back to zaqar channel :) 15:53:10 not from me 15:53:39 #endmeeting