19:59:59 <johnsom> #startmeeting Octavia 20:00:00 <openstack> Meeting started Wed Jul 27 19:59:59 2016 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:01 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:04 <openstack> The meeting name has been set to 'octavia' 20:00:06 <sbalukoff> Howdy, folks! 20:00:07 <TrevorV> o/ 20:00:09 <blogan> hi 20:00:15 <johnsom> Hi everyone 20:00:35 <johnsom> Another fine week in Octavia/LBaaS land.... 20:00:44 <johnsom> #topic Announcements 20:00:59 <johnsom> #link https://wiki.openstack.org/wiki/Sprints/LbaasNewtonSprint 20:01:09 <sbalukoff> Also, voting is open for talks! 20:01:10 <johnsom> #link https://etherpad.openstack.org/p/lbaas-octavia-newton-midcycle 20:01:18 <chenli> o/ 20:01:36 <johnsom> Our mid-cycle is approaching. Please sign up on the wiki if you plan to attend 20:02:02 <johnsom> Yes, also as sbalukoff mentioned, voting for summit sessions is now open 20:02:40 <bana_k> Hi 20:03:05 <diltram> hey 20:03:33 <johnsom> We have "Load Balancing as a Service and Octavia, Newton and Beyond" up there for votes, so vote early, vote often.... 20:03:36 <johnsom> Grin 20:03:41 <sbalukoff> :) 20:03:51 <blogan> ive never seen that talk 20:04:07 <sbalukoff> Well, that's because the release name keeps changing. 20:04:19 <johnsom> blogan That is because you just sign up to talk and then bow out... Grin. JK, you have presented.... 20:04:50 <johnsom> Any other announcements before we move on to progress/patches? 20:05:05 <johnsom> #topic Brief progress reports / bugs needing review 20:05:17 <TrevorV> I have no progress reports.. the internal focus continues :( 20:05:21 <blogan> this will be the 2nd one i dont do 20:05:45 <chenli> https://review.openstack.org/#/c/342695/ Use seperate security group for o-hm0 port in devstack 20:05:48 <sbalukoff> I should have a lot more time to work on upstream stuff in the next few weeks leading up to the mid-cycle. My plan is to tackle documentation unless my superiors give me other priorities. 20:06:24 <sbalukoff> chenli: I'll have a look at that this week. 20:06:26 <johnsom> Ok, I have been working on the failover flow issue with network namespaces. I have things working except for the multi-net scenario, but I am working on that today. Sorry to say it has become a bit of a conflict magnet with the number of changes required, but it will be good to get fixed. 20:06:41 <sbalukoff> +1 20:06:58 <chenli> updated based on comments, and tested already :) 20:06:58 <chenli> sbalukoff: Thanks. :) 20:07:23 <johnsom> Cool, thanks chenli. I know there was some confusion on that one. 20:07:52 <johnsom> Any other high priority patches needing review? 20:08:19 <sbalukoff> I know we banged out a bunch in the last couple weeks. So yay for that, eh! 20:08:39 <johnsom> Yeah, and two reverts, so let's not bang them out too fast..... 20:08:44 <sbalukoff> Heh! 20:08:46 <chenli> Also this one: https://review.openstack.org/#/c/347121/. Remove network from amphorae when delete a member. But haven't tested yet... 20:08:46 <chenli> A small fix: https://review.openstack.org/#/c/347670/ : Fix issue when convert python .isoformat() string back into datetime object 20:09:52 <johnsom> 347121 Will need some close review. We had previously decided not to un-plug networks from amps, so there are places that expect that they will be there in the code. 20:10:10 <johnsom> So, cores, pay special attention and testing on that one 20:10:30 <xgerman> o/ 20:10:38 <johnsom> #topic Open Discussion 20:10:58 <chenli> johnsom: o ? sorry, I do not know that. What is the reason not to un-plug networks ? 20:11:17 <johnsom> There is a high level list of topics for the mid-cycle on the etherpad. Please add to it if you have ideas for other things we need to discuss or work on at the mid-cycle 20:11:57 <chenli> https://review.openstack.org/#/c/333800/ Has another one need discussion, about how to set the pending_status_timeout for loadbalancer.. 20:12:03 <xgerman> chenli there are/have been grand container plans 20:12:37 <johnsom> chenli I think it was to simplify the amphora management process. 20:13:23 <johnsom> Yeah, 333800 the timeout patch. I really feel strongly that this is the wrong approach to solve this problem. This is a good one for the cores to comment on. 20:13:34 <sbalukoff> So, no good reason, but code has been built potentially with assumptions, so thorough testing is needed. 20:13:47 <johnsom> sbalukoff +1 20:14:18 <sbalukoff> johnsom: I'll have a good look and think 333800 over, eh. 20:14:25 <johnsom> Thanks! 20:15:00 <johnsom> Any other topics for open discussion? 20:15:10 <sbalukoff> Short meeting today, eh! 20:15:47 <sbalukoff> (Works out OK for me, as afternoon training session is about to start.) 20:15:47 <johnsom> Yeah. I'm really happy to seem new names on patches and in the channel... Things are rolling along 20:16:10 <sbalukoff> Yeah, that has been good to see. :) 20:16:40 <johnsom> chenli Was there more you wanted to discuss on the 333800 or just wait for the comments on the patch? 20:16:54 <johnsom> I know you stayed up late for the meeting 20:18:16 <johnsom> Ok, maybe we lost them. Thanks folks. Short one today. 20:18:23 <sbalukoff> Have a good one! 20:18:32 <diltram> thx, have a good night/day 20:18:36 <johnsom> #endmeeting