08:00:27 #startmeeting Dragonflow 08:00:27 Meeting started Mon Feb 19 08:00:27 2018 UTC and is due to finish in 60 minutes. The chair is oanson. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:30 The meeting name has been set to 'dragonflow' 08:00:44 Hi 08:00:52 o/ 08:00:55 Hi 08:01:13 All right. 08:01:17 #info lihi dimak leyal in meeting 08:01:23 snapiri, are you in as well? 08:02:11 All right, let's go ahead, and hope any stragglers will join 08:02:14 #topic Roadmap 08:02:29 We are nearing the end of the cycle. I will tag Queens this weekend. 08:02:49 Since there are no critical bugs, I don't plan on backporting anything. 08:02:51 Woohoo 08:02:59 :) 08:03:03 But obviously anyone can suggest a patch, and it will be considered. 08:03:12 🎊🎊 08:03:21 That being said 08:03:42 Dragonflow won't have an explicit room in the PTG. 08:03:49 Since only I, irenab, and snapiri are going to be there 08:04:33 hi, sorry didn't pay attention to the time 08:04:40 If anyone is looking for us, you can probably ping us on IRC. 08:04:50 irenab, no worries. We're happy to have you anytime :) 08:05:18 Basically this means two things: The meeting next week is canceled. 08:05:38 Because I don't plan on it interfering with my planned Irish drinking :) 08:06:09 And the meeting after that we will decide on the plan for next cycle. If one hour won't be enough, we will continue on the channel. 08:06:29 I hope during the PTG we will get enough feedback from FEMDC and Neutron to give us something to do :) 08:06:48 And now! On to the roadmap! (Unless someone has something to add?) 08:06:49 oanson, do not forget kuryr 08:07:07 irenab, right. 08:07:20 I hope during the PTG we will get enough feedback from FEMDC, Neutron, and kuryr* to give us something to do :) 08:07:25 And now! On to the roadmap! (Unless someone has something to add?) 08:07:57 Great! 08:08:12 DNS - lihi, any progress? Or were you bogged down by OSA? 08:08:36 Nothing yet :( 08:09:14 No worries. 08:09:19 Upgrades 08:09:46 The grenade gate is coming along - which leads to the sad news it won't be ready for this cycle 08:10:03 I think there are some major bugs we fixed in queens that are necessary for an upgrade 08:10:32 So as much as we wanted to have an upgrade from pike, we're gonna have to have it from queens. Sorry about that. 08:11:11 Mostly since I don't want to go back through the history and find the fix and backport it. 08:11:17 Any objections? 08:12:00 I don't think we did DB changes, so that will be OK 08:12:01 I'll take that as a no 08:12:13 +1 08:12:16 lihi, sorry, we typed at the same time :) 08:12:23 +1 08:12:29 +1 08:12:40 Actually, there are a number of 'migration' patches. The base will be kept. The actual migration will be abandoned. 08:12:56 lihi, ^^^ 08:13:16 So first thing next cycle I'll work on that, so if there are any bugs, it will be easy to fix on both branches 08:13:24 Next item: OSA 08:13:51 Hi 08:14:14 #info irenab and snapiri also in meeting 08:14:16 Unfortunately that also won't be ready for Queens 08:14:21 oanson, can you post a link to patches? 08:14:45 irenab, it's quite a list. Can we do that offline later? Or do you want it on record? 08:15:30 irenab, let's do it differently: This is the base patch: https://review.openstack.org/#/c/401210/ . The one on top of it adds the grenade gate. Anything on top of that is migration scripts (which will have to be abandoned) 08:15:38 I guess there is a topic, just wnated it to be logged. We can take it offline 08:15:45 lihi, sorry - the floor is yours again 08:15:45 There's some mis-match with how the db-role decided on which hosts it operates (in order to configure the redis clusters), and how osa-neutron role decided on which hosts the DB will be installed 08:15:58 I'm trying to resolve this conflict without having to re-write the db-role 08:16:43 Sure 08:16:52 But even if that will work, I won't be able to test it properly in time 08:17:08 No rush. 08:17:28 Don't forget we can always backport anything we need. 08:17:36 (And I doubt we will actually need) 08:17:50 RPM packaging - 08:18:25 No progress here. Sorry 08:18:38 Importing Neutron DB into Dragonflow DB - snapiri ? 08:18:56 No progress. Was working on Skydive and Kuryr 08:19:38 Sure 08:20:10 Gates - Grenade - I covered this before. In summary - won't work from pike, will have to settle from queens 08:20:48 Tempest - That's blocked by bug (One sec, I lost the bug) 08:21:14 Bug 1740739 08:21:14 bug 1740739 in DragonFlow "Security group mismatch for floating IP" [High,New] https://launchpad.net/bugs/1740739 - Assigned to Omer Anson (omer-anson) 08:21:41 I uploaded https://review.openstack.org/#/c/543863/ (Refactor sg to use reg6/reg7 and not IPs ) It's *very* WIP (that's why it's also DNR) 08:21:49 But it shows the general idea of what I plan to do 08:22:23 Once the gates pass, I'll also change it to be an 'alternate secgroup implementation', until we iron out all the rough edges. 08:22:39 Kuryr integration gate - snapiri, irenab, I understand you guys did some work here? 08:23:16 dmellado, has initial patch for zuulv3 support and suggests all following patches to be rebased on it 08:23:16 Indeed, worked on adding DF gate to Kuryr, almost got it to work 08:23:30 but put it aside due to dmellado's patch 08:23:32 snapiri: oanson 08:23:37 I've got a working DF gate 08:23:38 irenab, snapiri, links? 08:23:42 zuulv3 native 08:23:43 dmellado, hi. Welcome! :) 08:23:56 dmellado, very cool! Do you have a link? 08:24:17 https://review.openstack.org/#/c/544959/ 08:24:19 oanson: there you go! 08:24:23 IIIRC I added you as reviewer 08:24:37 Yep. You did. 08:24:38 what I've seen is that while passing the tempest tests from k-kubernetes 08:24:49 dragonflow fails on the pod to vm communication 08:25:01 maybe you can have a look at the logs of that gate in case you've the time 08:25:29 dmellado, sure. We'll assign someone to it. 08:25:31 as per as multinode gates on zuulv3 08:25:32 Any volunteers? 08:25:36 currently they're bs 08:25:55 as zuulv3 doesn't have a proper support for role assignment on multi node 08:26:00 subnodes, in fact 08:26:04 and it just install the things 2 times 08:26:15 that should be addressed at the PTG 08:26:33 and afterwards hopefully we can have a proper multinoding xD 08:26:41 snapiri, can we check this together tomorrow? 08:27:00 the DF pod to VM communication failure 08:27:04 dmellado, that sounds great! 08:27:18 irenab: please grab me when you want to do it 08:27:28 cool, thanks 08:27:56 snapiri: irenab oanson FYI http://logs.openstack.org/59/544959/22/check/tempest-kuryr-kubernetes-dragonflow/5d396e9/controller/logs/test_results.html.gz 08:28:24 oanson: that bug that you mention could be the issue there 08:28:35 was just scrolling back, as we do use FIPs for that test 08:28:38 dmellado: I see many tests just timed out, known reason? 08:28:49 snapiri: do you mean on the gates? 08:28:56 dmellado: yes 08:28:57 dmellado, Could be. What's the topology? 08:29:01 that's because of the openshift thing 08:29:05 will need to check that part 08:29:11 but that'll land on experimental anyway 08:29:22 oanson: so, pod on one network 08:29:27 vm on another one with a FIP 08:29:38 then ping 08:29:46 So yes. This sounds like exactly the same bug :) 08:29:58 we do create a SG on the fly to the vm with the proper sgr 08:30:03 but looks like this could be related 08:30:10 if so, awesome, tempest on DF caught a real bug xD 08:30:23 Not the first, either! :D 08:30:50 snapiri: in any case I do plan to create a bluejeans for the infra session on kuryr next mon afternoon 08:31:02 if you want to join I'll send an email to the ML mid week ;) 08:31:20 oanson: lol 08:31:22 dmellado: please do 08:31:32 dmellado, snapiri will be attending the ptg 08:31:38 oh, even better 08:31:48 snapiri: please add you name to the attendee list here 08:31:55 https://etherpad.openstack.org/p/kuryr-ptg-rocky 08:32:43 dmellado: will do 08:32:50 thanks! 08:33:37 All right. Anything else for the kuryr gate? (Or gates in general?) 08:34:28 Last but not least - Troubleshooting - snapiri ? 08:35:16 Skydive integration is still in progress, not much though... encountered several issues 08:35:33 will probably have to upload some spec to discuss things 08:35:36 last time I tried skydive their devstack plugin was just plain broken 08:35:55 snapiri: you might want to speak with bcafareli when he's around 08:36:00 dmellado: I am working directly with the python client 08:36:09 snapiri: oh, then that'll be easier 08:36:59 dmellado, snapiri is on a first name basis with their core developers, and even contributed several patches :) 08:37:24 oanson: good to know next time I try it xD 08:37:36 :-P 08:37:49 snapiri: we'll get to talk about that next week xD 08:38:16 snapiri, sounds good. Looking forward to reading the spec. 08:38:32 dmellado: about your gate patch - I believe we can discuss it, as there are things I have encountered that do not seem to be addressed in your patch 08:38:55 let's take it offline 08:38:57 snapiri: totally, in fact that's my plan 08:39:06 we'll discuss it with the infra folks on Mon 08:39:13 would you be able to be there? 08:41:11 snapiri, ? 08:41:43 indeed 08:41:49 this is my plan :) 08:42:25 awesome ;) 08:42:28 Great! 08:42:42 All right. Let me just move us to Open Discussion, and we can continue 08:42:45 #topic Open Discussion 08:42:49 All right, go nuts! 08:43:12 lol 08:43:44 what about change evening meeting time? 08:43:58 snapiri: oanson I told irenab but during this week I'll be slightly offline due to some personal issues. If you need something from my side feel free to drop me an email 08:44:16 dmellado: will do 08:44:29 dmellado, sure. Thanks! I hope everything turns out well. 08:44:33 thanks! 08:44:53 leyal, I spoke with mlavalle and he said that he plans to attend *some* of the meetings. 08:45:14 So I think we'll postpone the vote till next-next week (after the PTG) to see what reception we have in Dublin. 08:45:28 Unless I'm completely outvoted now :) 08:45:28 +1 08:45:37 +1 08:45:43 +1 08:45:45 oanson, sure . 08:46:14 oanson, you have quorum 08:46:22 We can also change the structure of the evening meetings - during Monday you guys send me updates according to the agenda, and then I can just spill it into the meeting. As a sort of half-way. 08:46:34 Sure. Then let's do the first thing (wait for a couple of weeks) 08:46:42 Anything else to discuss? 08:47:57 All right. Thanks everyone for coming! Great meeting today! 08:48:09 #endmeeting