08:00:20 #startmeeting Dragonflow 08:00:21 Meeting started Mon Aug 21 08:00:20 2017 UTC and is due to finish in 60 minutes. The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:24 The meeting name has been set to 'dragonflow' 08:00:30 Hey 08:00:42 Hi,guys 08:01:11 Hi all. 08:01:23 Let's wait another minute. Maybe lihi and irenab will join us. And then we'll start 08:01:41 Hi 08:01:52 hi everyone 08:02:35 All right! Let's start 08:02:43 #info dimak kkxue lihi itamaro in meeting 08:02:47 #topic Roadmap 08:02:53 hi 08:03:11 Before we start with actual roadmap items, I want to post the trello board for Dragonflow 08:03:19 #link Dragonflow Trello board https://trello.com/b/PM7nah4Z/project-dragonflow 08:03:33 I am not sure how well using Trello will work out, but we'll see :) 08:03:52 #info irenab also in meeting 08:04:09 All right. Roadmap: The LBaaS spec is uploaded 08:04:15 I think it's ready for a real review 08:04:24 #link LBaaS spec https://review.openstack.org/#/c/477463/ 08:05:07 oanson, added to my todo list 08:05:07 There's no real rush with it, as it is physically impossible to get it into pike 08:06:04 Once we went over it, it might be helpful to ask the Kuryr and Octavia people to look at it as well. 08:06:32 oanson: look at the lbaas spec? 08:06:39 apuimedo, yes 08:06:43 ok 08:06:52 I'd be happy to hear feedback. 08:06:55 oanson, I can assure you, we will test it too 08:07:20 irenab, I didn't doubt it for a second :) 08:07:37 Anything else for LBaaS? 08:07:52 oanson, just one comment 08:07:58 Shoot 08:08:11 we should keep the option to integrate 3rd party LB with dragonflow 08:08:27 Yes, we should 08:08:58 irenab, could you leave a comment on the spec so it won't be forgotten? 08:09:06 sure 08:09:10 Thanks. 08:10:20 L3 flavour - dimak, any progress? 08:10:25 Or were you bug-hunting? 08:10:52 oanson, not this week, was working on other stuff this week 08:11:02 Sure 08:11:21 ETCD publisher - lihi, I saw you uploaded a WIP for the publisher 08:11:23 I'll focus on it after we tag pike 08:11:31 And updated the etcd3 patch to be non-wip 08:11:43 dimak, sure. That's the timeframe we discussed 08:12:15 #link etcd3 driver https://review.openstack.org/#/c/489246/ 08:12:20 Yeah. Right now I'm working on getting it installed with devstack :) 08:12:43 Cool 08:13:07 Once that's done the next step is the OSA deployment with it? 08:13:31 And make sure it really works 08:14:08 Very cool! 08:14:51 I didn't get to work on RPM packaging this week. I won't make any promises this time, since there are a couple of patches I feel need to get in before tag date since they change DB structure 08:15:00 Sorry, anything else for etcd? 08:15:16 No 08:15:32 All right. Anything else for roadmap? 08:16:24 #topic Bugs 08:16:46 Let's start with bug 1708178 08:16:47 bug 1708178 in DragonFlow "LBaaSv2 with 3rd party provider does not work if L3agent is disabled" [Critical,New] https://launchpad.net/bugs/1708178 08:17:01 I understand it can be worked around with selective-proactive disabled? 08:17:06 I suggest to close it as invalid 08:17:20 It is not related to selective proactive IMO 08:17:32 its just that selective proactive is rather broken 08:17:35 oanson, checking it now for BM, and we saw it works for nested environment 08:17:39 I understood it works without selective-proactive, but not with it 08:18:00 irenab, but with selective-proactive off? 08:18:04 same way routing through shared router doesn't work 08:18:09 oanson, yes 08:18:21 lbaas integration itself works alright 08:18:46 There are two options. 08:18:53 We either update the bug, or open a new one instead. 08:19:05 It's a regular 'VM' port as far as dragonflow is concerned 08:19:14 I suggest a new one 08:19:15 Selective-proactive being broken this way is still critical, since we claim that it's working 08:19:21 I might have one for it 08:19:29 dimak, linky? 08:19:34 looking 08:19:48 oanson, shall we set deafault to selective proactive disabled till it fixed? 08:19:55 Also, how complicated would it be to see if https://review.openstack.org/#/c/480196 solves the issue? 08:20:23 irenab, if we have to, but let's wait till the tag cut-off for it. I don't think a week will make much of a difference in this case. 08:20:46 Scratch that - we'll disable it now, and re-enable it when the bug is fixed 08:21:05 +1 08:21:16 oanson, I'll find it after the meeting, if there isn't one I'll open a new bug 08:21:25 dimak, sure. 08:21:47 I am still interested to know if it's possible to test again with https://review.openstack.org/#/c/480196 applied? 08:22:01 (Including all dependencies) 08:22:07 We can test it in tempest ;) 08:22:15 We should 08:23:14 dimak, irenab ? 08:23:29 Sure, I can try bringing up an env 08:23:51 Thanks. If you prefer, you can also walk me through the process. 08:24:33 dimak, note that this bug also has l3-agent support elements. Might be worth checking and updating in subsequent related bugs as well 08:24:47 Bug 1658479 08:24:48 bug 1658479 in DragonFlow "tenant_id is still being used" [High,In progress] https://launchpad.net/bugs/1658479 - Assigned to Omer Anson (omer-anson) 08:25:09 I uploaded a WIP for it, https://review.openstack.org/#/c/480196 08:25:09 oanson, I skimmed over the patch, does it subscribe to new topics? 08:25:29 It should be an in-place replacement, so it should 08:26:00 The first question is do we want it at this time? According to https://specs.openstack.org/openstack/neutron-specs/specs/newton/moving-to-keystone-v3.html#neutron-api , tenant_id isn't removed yet 08:26:08 And it will stay for a while. 08:26:34 And the patch forces us to support both, which is... wrong... 08:26:52 then lets wait with all the models that are not through yet 08:27:29 Right. So I'm bumping the bug back to medium. I'll leave the patch for later. 08:27:51 Bug 1684108 08:27:53 bug 1703334 in pulseaudio (Ubuntu) "duplicate for #1684108 start-pulseaudio-x11 tries to load /usr/share/sounds/ubuntu/stereo/bell.ogg which is missing in Kubuntu" [High,Fix released] https://launchpad.net/bugs/1703334 - Assigned to Daniel van Vugt (vanvugt) 08:28:12 Heh, that's not the same one, openstack 08:28:20 Let's try again 08:28:21 Bug 1684108 08:28:37 DHCP port does not have an ARP/ICMP responders 08:28:41 https://bugs.launchpad.net/dragonflow/+bug/1686108 08:28:42 Launchpad bug 1686108 in DragonFlow "DHCP port does not have an ARP/ICMP responders" [High,In progress] - Assigned to Eyal Leshem (leyal) 08:28:55 Should be solved by either https://review.openstack.org/#/c/493794/ or https://review.openstack.org/#/c/495544/ 08:29:13 Yes, I opted for a quick fix 08:29:46 I think we should remove it and move it into 'install subnet dhcp flows' once we refactor dhcp app a bit 08:30:04 dimak, I don't understand, sorry. 08:30:49 I say that we should {,un}install responders at the same time we install the rest of subnet dhcp related flows 08:31:10 So the way it's done in leyal's patch 08:31:12 yes 08:31:25 but to get it before pike, I proposed to do it separately 08:31:48 Then let's go with that. You think you can update leyal's patch to pass review? (leyal is out for the week, and the tag cut-off is coming) 08:32:04 Or do you want me to do it? 08:32:10 Or do we think that it can wait a week? 08:32:19 what do refer to as that 08:32:39 dimak, sorry? 08:32:55 >> Then let's go with that 08:33:24 Sounds like a plan. dimak, since I am also making changes in that area, let's coordinate offline 08:33:42 ok 08:33:59 Bug 1705503 08:34:00 bug 1705503 in DragonFlow "Trunk subport will not be available after controller restart" [High,Fix committed] https://launchpad.net/bugs/1705503 08:34:12 https://review.openstack.org/#/c/493282/ 08:34:18 Deals with it 08:34:21 reviews welcome 08:34:47 Very cool. Reviewers, start picking it apart :) 08:35:12 👍 08:35:12 oanson, any idea if there are trunk tests for tempest? 08:35:38 dimak, no idea. 08:35:51 But we'll have a kuryr-integration gate which will test this feature thoroughly 08:36:04 I'll take a look later on 08:36:20 Sure. Thanks 08:36:23 Bug 1707496 08:36:25 bug 1707496 in DragonFlow "Stabilize tempest job" [High,In progress] https://launchpad.net/bugs/1707496 - Assigned to Dima Kuznetsov (dimakuz) 08:36:38 https://review.openstack.org/#/c/489003/ shows that only bgp is failing 08:37:00 It works on my environment. I think the gate environment is missing some config. I'll try to update today. 08:37:28 Hangs on 3 patches, https://review.openstack.org/#/c/493359/ https://review.openstack.org/#/c/483385/ and either of the DHCP responder patches 08:37:36 dimak, https://github.com/openstack/neutron/blob/master/neutron/tests/tempest/scenario/test_trunk.py 08:37:45 on your previous question 08:37:53 irenab, thanks! 08:38:09 I'll make sure we run it in our tempest job 08:38:16 great 08:38:19 Cool! 08:38:34 Last High bug: 1708157 08:38:35 bug 1708157 in DragonFlow "Implement port locality spec" [High,In progress] https://launchpad.net/bugs/1708157 - Assigned to Dima Kuznetsov (dimakuz) 08:38:54 Yes 08:39:06 Some work was done last week introducing bind events 08:39:11 Is it blocking anything we need for pike? 08:39:16 now we need to add distributed ports 08:39:19 nope 08:39:37 Then I want to bump it down to medium, and get back to it after that tag cut-off 08:39:56 well, we could have solved DHCP responders with it I think, but we'll get to it later 08:40:37 I don't think it can be finished *and* used before the tag cut-off. I don't want to tie things we can finish in advance on something that will take us more time 08:40:44 Yes 08:40:52 Yes it can, or yes it can't? 08:41:29 Yes we don't need it before the tag 08:41:41 easier to accomplish our goals without it for now 08:41:42 So it's bumped down, unless there are objections? 08:42:43 This was the last high bug for now. Unless we find something new, we're in good shape 08:43:18 All right, anything else for bugs? 08:44:05 #topic Open Discussion 08:44:10 Fire away 08:45:16 If that's the case, we can finish early :) 08:45:23 Anything before we close? 08:45:36 Well, yes 08:45:49 itamaro, the fire away :) 08:45:52 then* 08:46:08 I want to bring up again the issue of flow tagging using coockie 08:46:22 itamaro, linky? 08:46:37 one sec 08:47:11 > https://review.openstack.org/#/c/424123/ 08:47:56 it is basically a debug tool which allows each application to color it's flows. 08:48:29 the coloring itself, is defined in run time. 08:49:14 I was asked at the time to make fullstack tests for this feature. 08:49:45 itamaro, let's start by rebasing the patch 08:49:51 if this is a debug tool, do we need full stack tests for it? 08:50:00 Let me also find something in the tests code 08:50:35 Ok. I'll start by doing a rebase. 08:51:04 sound like a plan. 08:51:09 :) 08:51:18 We also have a test_app_base.DFAppTestBase base class that allows you to start a controller with a given list of apps 08:51:48 So only one app can do? 08:51:50 A unit test can then read verify the correct apps write the correct cookie colour 08:52:04 It's a list. I think several apps can be given. 08:52:38 But maybe just a simple unit test to make sure the global cookie is registered will do. It's a unit test, not integration test, for a development feature 08:52:46 That relies on a tested library 08:53:10 Yes I thing unit test will do. 08:53:16 +1 08:53:25 Great! 08:53:29 Anything else? 08:54:54 All right. Thanks everyone for coming 08:55:15 #endmeeting