16:00:00 #startmeeting Octavia 16:00:01 Meeting started Wed May 22 16:00:00 2019 UTC and is due to finish in 60 minutes. The chair is rm_work. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:02 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:04 The meeting name has been set to 'octavia' 16:00:05 o/ 16:00:10 O/ 16:00:10 hi 16:00:27 I am ... still working from yesterday, so bear with me 16:00:39 o/ 16:00:40 o/ 16:00:50 Keep forgetting I need to raise my hand now.... lol 16:01:03 good, already warmed up 16:01:11 yes, you have been demoted (promoted?) to "regular participant" :D 16:01:41 #topic Announcements 16:01:57 #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006478.html 16:02:07 Some minor requirements changes are coming. 16:02:22 I think we are mostly up to date on that, but thought I would highlight the thread 16:03:07 I'm just working away... nothing really to mention specifically... any other announcements? 16:03:17 I think the gate issues are now fixed with the requirements upper-constraints file updated this morning. 16:03:21 o/ 16:04:05 Also, if you haven't done the user survey: 16:04:07 #link http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006393.html 16:04:20 Please raise awareness that Octavia matters to you.... 16:04:23 o/ 16:04:49 ok... moving on then 16:05:00 #topic Brief progress reports / bugs needing review 16:05:23 I have pivoted from the unset work to help jump start the jobboard work. 16:05:58 I have posted a patch that creates an "amphorav2" provider driver/controller: 16:06:00 #link https://review.opendev.org/659689 16:06:46 I am currently working on the "demo" patch for switching those flows over to using the provider driver models. This will also remove the DB objects from the flows for the jobboard work. 16:07:23 However, I was a genius and picked "listener" as the demo, which is probably the most complicated of them all. A still very WIP patch: 16:07:33 #link https://review.opendev.org/660236 16:08:20 I hope I can wrap that up today. I think there is a follow on patch for octavia-lib to add the project ID to the objects. I'm pretty sure the vmware NSX driver needs that as well. 16:08:21 it will be a breeze reviewing these jobboard patches 16:08:21 I mostly rebase my changes on johnsom "amphorav2" provider driver/controlle and look at refator example - start modify patches that I already have on this topic. 16:08:36 I am working on one of the items I signed up for this cycle, multi-vip! The strategy is to add "additional_vips" as a list of subnet_id (+ optionally ip_address) that will be added to the VIP port. This would allow ipv6+ipv4 on the same LB, as an example. Maybe take a look and give feedback now if you don't like the way it's set up on the user-facing side: https://review.opendev.org/#/c/660239/ 16:08:52 #link https://review.opendev.org/#/c/660239 16:08:54 ataraday_ Feedback is welcome. Let me know if what I'm doing makes sense, etc. 16:09:31 johnsom, all seems pretty good, thanks a lot for this huge piece of work! 16:09:38 ataraday_ Also shame me if I end up doing something you have already posted. grin I'm kind of just running with this. 16:09:40 I still have a bit of work on the backend / plugging side of things 16:09:42 I pushed to Gerrit a patch I started in November that intends to implement VIP ACL API. I just rebased it before pushing, still much WIP. listener POST works, PUT doesn't 16:09:56 #link https://review.opendev.org/#/q/topic:vip-acl 16:10:23 I also want to highlight a critical patch for Octavia dashboard: 16:10:24 also this small change ready for review https://review.opendev.org/#/c/659538/ - but it is based on johnsom's change anyway 16:10:24 #link https://review.opendev.org/660768 16:10:38 backport to stein here: 16:10:45 #link https://review.opendev.org/660769 16:10:56 so much stuff in progress \o/ 16:11:10 We missed that it was trying to access flavor profiles which only admins can do. 16:12:43 yeah, i had a feeling that might have happened 16:13:18 Since lxkong isn't likely here I will also highlight his autoscaling demo using heat and octavia: https://youtu.be/dXsGnbr7DfM 16:13:45 He posted it to the openstack discuss mailing list 16:14:01 Woot!! 16:14:06 I feel like we're getting into open discussion-ish 16:14:08 opps, auto healing, not auto scaling 16:14:36 Sorry, just thought it was an update from another team member. 16:14:44 yeah that's true 16:15:04 i am just trying to move things along because my vision is starting to get sparkly and i'm looking forward to sleep :D 16:15:17 nice! I'll watch it after the meeting for sure 16:15:27 any other progress reports? 16:15:31 lol, ok, I'm done 16:16:17 #topic Open Discussion 16:16:46 anything else folks want to discuss today? we haven't really had any specific agenda items in a while 16:16:51 not sure if there is anything pressing 16:17:32 about jobboard redis and zookeeper.. 16:17:39 I don't have any other topics today. 16:18:06 I put commemt on the 9th patch set on this change https://review.opendev.org/#/c/647406/9 16:18:28 if anyone interested could take a look 16:19:19 Ah, yes. I think that should be ok to move the loop into the flow using the "retry" flow logic 16:19:42 hopefully yeah 16:20:44 #link https://docs.openstack.org/taskflow/latest/user/atoms.html#retry 16:21:34 OK, then I try to do this 16:21:55 A little bit of a meta topic -- I think we should nominate someone to update our meeting wiki -- I think johnsom was doing it before when he ran the meetings, but I basically forgot it existed until now. Any volunteers for meeting scribe? 16:21:57 Probably just need to move the loop out to a retry "times" element. 16:21:58 #link https://wiki.openstack.org/wiki/Octavia/Weekly_Meeting_Agenda 16:22:31 * johnsom takes a step back. Needs a break.... 16:22:43 the minutes are automatically created, so this is actually like ... a pre-scribe (because the idea would be to put the next meeting up ahead of time so people can add topics) 16:22:59 though also, they need to be added to here maybe? https://wiki.openstack.org/wiki/Octavia/Meeting_Minutes 16:23:16 which is just a matter of copy/pasting a link once a week after the meeting 16:23:27 Yeah, the two steps I had been doing is: create agenda, then after post the links 16:24:01 any takers? ;) 16:24:07 cgoncalves: have I delegated enough to you yet? 16:24:16 o/ 16:24:18 * cgoncalves looks away 16:24:23 eandersson: a volunteer? :D 16:24:27 lol 16:24:27 oh, there! eandersson :) 16:24:41 aha! he's volunteered! 16:24:43 I don't know if anyone cares about the links or if they are fine just using the eavesdrop page 16:24:46 unfortunately just meant to highlight that I showed up lol 16:25:10 eandersson Perfect, thanks for volunteering! 16:25:14 =]] 16:25:36 rm_work, I can be eandersson's backup 16:25:43 alright, that's all I had, eandersson will be our agenda pre-scribe moving forward ^_^ 16:26:17 I'll be on PTO next Wednesday though 16:26:20 honestly, you could probably do like a month ahead at once 16:26:29 people can pick the right date hopefully for adding their topics 16:26:45 it's just copy/pasting and changing a few digits 16:27:04 and maybe we let the minutes page die, and refer people to the eavesdrop index 16:27:18 sounds reasonable to me 16:28:17 ok, any other topics for today? we might be able to get out of here early ;) 16:29:42 looks like maybe we're done? 16:30:18 alright, thanks for the meeting folks, see you next week o/ 16:30:25 #endmeeting