17:00:04 #startmeeting Octavia 17:00:05 Meeting started Wed Aug 2 17:00:04 2017 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:06 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:08 The meeting name has been set to 'octavia' 17:00:12 Hi folks 17:00:22 Hi 17:00:47 o/ 17:00:52 I'm going to get things rolling while folks show up. Lots of announcements today 17:00:53 #topic Announcements 17:00:58 o/ 17:01:05 PTL nominations are open 17:01:11 #link https://governance.openstack.org/election/ 17:01:26 o/ 17:01:31 See the above link for information on the nomination process. 17:01:59 The queens PTG is September 11-15th in Denver. 17:02:06 #link https://www.openstack.org/ptg 17:02:13 I nominate johnsom! 17:02:20 I have setup a planning etherpad here: 17:02:27 #link https://etherpad.openstack.org/p/octavia-ptg-queens 17:02:39 rm_mobile Well, I think you *can* do that 17:02:54 o/ 17:03:15 Though I don't have info from my employer yet on whether they will support me in another round. 17:04:07 For the PTG, please sign up on the etherpad if you will be attending. The foundation is trying to pick room sizes for teams and would like an estimate of the folks that will be in the Octavia room. 17:04:27 Also, if you have other topics we should discuss, please feel free to add it to the list. 17:05:16 Our next milestone is the RC1 release scheduled for the week of August 7th. 17:05:23 #link https://releases.openstack.org/pike/schedule.html 17:06:04 We should strive to have any critical bugs in by then if we can. 17:06:38 Also, in case you missed the announcements, voting for sessions in Sydney has started. 17:06:48 #link https://www.openstack.org/summit/sydney-2017/vote-for-speakers 17:06:59 Vote early, vote often... 17:07:32 Even if you aren't going, you can vote for sessions you are interested in watching on YouTube after the summit. 17:08:29 We did release Pike-3 last week, so we are on track with the release schedule. 17:08:52 Also of note, I have marked us complete for one of the two community goals for queens: 17:08:56 I did some OSA stuff: 17:09:14 #link https://governance.openstack.org/tc/goals/queens/policy-in-code.html#octavia 17:09:29 https://review.openstack.org/#/c/484440/ 17:09:30 Any other announcements? 17:09:41 Enabling our V2 API in there 17:09:44 please comment 17:10:03 and then the terraform provider for LBaaS had issues: https://github.com/xgerman/terraform-provider-openstack/tree/LBaaS_V2_Timeouts 17:10:20 in case somebody is using that stuff ;-) 17:10:45 #topic Brief progress reports / bugs needing review 17:11:03 xgerman_ Cool stuff getting the v2 API setup as an option for OSA 17:11:37 What was up with the timeouts? Not waiting long enough for nova to boot? 17:11:42 os the default option is to have neutron pass through to the octavia v2 api? 17:11:54 they are just crazy — amde them more sane 17:12:13 No 17:12:26 I assumed standalone.. 17:12:49 jniesz The proxy plugin for neutron hasn't merged yet and could use some reviews: 17:12:50 #link https://review.openstack.org/#/c/418530/ 17:13:47 Yeah, standalone makes sense for the octavia role. The proxy option should be part of neutron or neutron-lbaas role I would think. 17:14:48 they all need to play nice together 17:15:11 since I wanted to introduce that change I ahven;t done the full swoop 17:15:21 I was out for a family reunion for a couple of days, so not a lot of progress to report other than the Pike-3 release and some reviews. 17:16:01 I'm hoping to get back to the failover API patch this week. Also still have some docs migration patches to do, most notably, neutron-lbaas. 17:16:47 I will also do a bug scrub today/tomorrow to make sure we have those cleaned up for Pike. We made a bunch of progress 17:16:57 Any other updates from folks? 17:17:13 I know Jude has started on our tempest plugin, yeah! 17:17:36 Yep its coming along 17:17:51 johnsom how close do you think we are with the flavor spec getting merged? 17:17:52 Cool, I hope to have a look soon. 17:18:16 Much appreciated :) 17:18:32 jniesz I think it is in good shape. We need to get some reviews logged on this revision. 17:18:45 yea, I saw you made the fixes 17:19:37 Yeah, really it is just waiting on getting some reviews 17:19:43 (there are none at the moment) 17:20:07 Remember, everyone can and should review. It's not just up to the cores.... 17:20:18 +1 17:20:35 ah speaking of: https://review.openstack.org/#/c/489015/ 17:20:58 that is a really annoying one and would love to get some reviews/testing on that 17:21:20 ah, i see it needs a unit test :P 17:21:34 k i'll do that ASAP 17:21:49 Yeah, we were looking at that yesterday. I think it's a good fix, needs a unit test, but should help the member status be super accurate. 17:22:16 #topic Mascot 17:22:33 +1 17:22:35 So the artists came back after our request to make the number of feathers eight 17:22:36 I like it 17:22:45 #link https://usercontent.irccloud-cdn.com/file/6S5klrGB/peacock.png 17:23:05 Any additional comments or can I lock this in with the foundation? 17:23:10 I like it too 17:23:15 +1 17:23:17 I think we are good to go myself 17:23:25 looks a lot better 17:23:27 +1 17:24:13 Ok, unless I hear some negative feedback, I will e-mail the foundation that we are happy with this version. 17:24:18 +1 17:24:26 we all need stickers ;-) 17:25:05 Excellent. Yeah, we should be able to have stickers for the PTG and Sydney. 17:25:40 #topic Open Discussion 17:25:51 Ok, any other topics for today? 17:26:17 I would really appreciate some reviews this week. We have L3 Act/Act spec and flavors spec open still. 17:26:35 and I am trying to get the OSA people to do reviews… 17:26:39 #link https://review.openstack.org/453005 17:26:47 #link https://review.openstack.org/392485 17:26:49 so if you have friends over there… 17:27:15 Yeah, those interested in Ansible for Octavia, those are good patches to review 17:27:34 xgerman_ we have core here on OSA 17:27:41 I can reach out 17:28:19 thx - I will mention patches in their meeting tomorrow. 17:28:29 as well 17:28:50 2nd OSA patch: https://review.openstack.org/#/c/483520/ 17:29:33 what about the openstacksdk reviews 17:29:37 did anything happen there? 17:30:02 Very good question. 17:30:12 So, no, no one has reviewed any of those yet. 17:30:28 I plan to send an e-mail out on the dev list asking some questions about that. 17:30:45 maybe WE are supposed to? 17:30:55 and if we +1 they rubber-stamp? 17:31:02 since they prolly don't know much about octavia 17:31:04 I see they did a pypi release not too long ago, but they are not using the OpenStack release team, so I'm really not sure what the story is with that project. 17:31:29 #link https://review.openstack.org/#/q/project:openstack/python-openstacksdk+status:open 17:31:37 Yeah, +1's will probably help. 17:31:58 We are basically the top set of patches there. 17:32:11 I have yet to do quota, but everything else is implemented. 17:34:10 #link https://review.openstack.org/#/q/project:openstack/python-openstacksdk+status:open+topic:%255Eoctavia.* 17:34:16 There we go, better list 17:34:44 ah, we also need stats in the octavia client still, right? 17:34:47 Back story here, others started these patches, but did not finish. I have gone through and finished them. 17:34:48 if anyone is bored :P 17:35:01 This is the python SDK 17:35:19 Yeah, I think stats and status tree are still missing, as well as integrating the quota commands 17:35:37 My plan is to use this SDK for the backend of the octavia dashboard (horizon) 17:37:13 Any other topics for today? 17:37:33 do we need to corrdinate with Neutron fort lbaasv2 17:37:46 I think for the proxy we might need to file a FFE? 17:38:29 Well, it's our project, but we should have sent out a FFE e-mail already if we thought we were going to get it into Pike. 17:39:06 ah yeah i didn't know if we would land it in Pike 17:39:17 though I don't see a problem, it's a NEW thing 17:39:24 it can't break anyone right? :P 17:39:34 Famous last words... 17:39:54 ok, if we don’t have the proxy our depreciation gets mices up but we can’t do that anyway 17:40:01 mixed 17:40:18 and also with neutron client going away things get messy when it comes to support 17:40:36 Yeah, I think we have to wait for providers before we start the deprecation clock. I think queens will be when neutron-lbaas deprecation is announced. 17:40:46 yeah i guess we can try 17:40:56 did you touch it since my last comments xgerman_? 17:41:00 wasn't sure 17:41:06 I rebased 17:41:53 I added the bug to it for tracking 17:41:55 your comment was cryptic so I ignored it ;-) 17:41:59 err lol 17:42:48 So, I'm not really feeling the need to rush this into Pike. I think we can do it at the start of Queens IMO. Open for discussion... 17:43:15 what we need to do is figure out if the delay makes us having to write an openstack client plugin for lbaasv2 17:43:53 I don't really follow how the proxy plugin helps that. 17:44:18 Did Kevin announce they are pulling the client code out? I haven't seen that. 17:44:48 it says deprecated every time I run it 17:45:17 the plan was because of the proxy plugin and the openstack client that we don’t need an lbaasv2 openstack plugin 17:45:20 Yes, but I don't think there is a hard end date on that 17:45:55 yeah, as I said it gets messy 17:46:02 I will ping Kevin just to make sure it's not getting pulled out of the code any time soon. 17:46:30 yeah, if we can save having to write code by announcing deprecation earlier I am all for it 17:46:31 Yeah, lots of things with neutron-lbaas are messy.... 17:47:11 There is no support on either side to add neutron-lbaas commands to OSC. That just isn't going to happen. 17:47:59 ummm what prevents the existing client from "working" with neutron-lbaas, more or less? 17:48:02 The plan has always been to continue to use the neutron client until all of the projects are migrated and the split is complete 17:48:11 rm_work Nothing 17:48:14 soooo 17:48:17 I don't even see a problem 17:48:23 let's verify we can make that client work 17:48:27 and... we've got one 17:48:32 Yeah, me either 17:48:57 Yeah, the neutron client continues to work 17:49:15 Some of my testing scripts still use it. 17:49:25 well even if it is removed, people can use the openstack client for octavia to hit neutron-lbaas 17:49:40 ok, we should say that somewhere 17:49:44 rm_work In theory yes. Has anyone tried it? 17:49:58 johnsom: erg you should fix that :P I have examples in mine of everything you'd need to replace i think 17:49:59 johnsom: that's what i'm saying, we need to just try it 17:50:00 and maybe there's a bug or two we can fix 17:50:28 ah like i know for neutron-lbaas for some reason member-subnet-id is required :/ 17:50:33 it should be optional 17:50:51 Ugh, debatable 17:51:02 technically anything is debatable 17:51:06 Right! 17:51:07 +1 17:51:10 do both sides have merit? I don't think so :P 17:51:27 Hahaha, I know which side you are thinking of... 17:51:31 but we can debate 17:51:44 We got bitten with deprecation V1->V2 so want to be super cautious this time around… 17:52:15 V1->V2 was handled very poorly, we are not doing that. 17:52:41 ok, https://review.openstack.org/#/c/489015/ has a unit test now 17:52:42 that’s why I ask those questions ;-) 17:53:11 Any other topics today? 17:54:05 Alright, on to reviews! 17:54:08 #endmeeting