Monday, 2019-07-29

*** igordc has quit IRC01:24
*** bobh has quit IRC01:45
*** bobh has joined #openstack-meeting-402:13
*** yamamoto has joined #openstack-meeting-402:18
*** bobh has quit IRC02:38
*** bobh has joined #openstack-meeting-402:39
*** bobh has quit IRC02:39
*** bobh has joined #openstack-meeting-402:40
*** bobh has quit IRC02:45
*** bobh has joined #openstack-meeting-402:59
*** bobh has quit IRC03:00
*** bobh has joined #openstack-meeting-403:01
*** bobh has quit IRC03:01
*** bobh has joined #openstack-meeting-403:02
*** bobh has quit IRC03:03
*** gcheresh has joined #openstack-meeting-403:04
*** yamamoto has quit IRC03:19
*** gcheresh has quit IRC03:23
*** gcheresh has joined #openstack-meeting-403:28
*** yamamoto has joined #openstack-meeting-403:29
*** psachin has joined #openstack-meeting-403:31
*** psachin has quit IRC03:34
*** psachin has joined #openstack-meeting-403:37
*** cheng1 has quit IRC03:41
*** cheng1 has joined #openstack-meeting-403:42
*** psachin has quit IRC03:55
*** gcheresh has quit IRC04:15
*** LXM has joined #openstack-meeting-404:25
*** yamamoto has quit IRC04:29
*** yamamoto has joined #openstack-meeting-404:41
*** davee_ has quit IRC05:03
*** davee_ has joined #openstack-meeting-405:03
*** Luzi has joined #openstack-meeting-405:06
*** gcheresh has joined #openstack-meeting-405:14
*** radeks has joined #openstack-meeting-405:35
*** e0ne has joined #openstack-meeting-405:41
*** radeks has quit IRC05:49
*** radeks has joined #openstack-meeting-405:49
*** e0ne has quit IRC06:11
*** links has joined #openstack-meeting-406:32
*** slaweq has joined #openstack-meeting-406:58
*** janki has joined #openstack-meeting-407:02
*** cheng1 has quit IRC07:31
*** LXM has quit IRC07:31
*** pcaruana has joined #openstack-meeting-407:31
*** cheng1 has joined #openstack-meeting-407:33
*** jchhatbar has joined #openstack-meeting-407:34
*** janki has quit IRC07:38
*** iyamahat has joined #openstack-meeting-407:39
*** jchhatbar has quit IRC07:46
*** jchhatbar has joined #openstack-meeting-407:50
*** lpetrut has joined #openstack-meeting-407:51
*** ralonsoh has joined #openstack-meeting-408:08
*** ktibi has joined #openstack-meeting-408:18
*** lemko has joined #openstack-meeting-408:42
*** gkadam has joined #openstack-meeting-408:44
*** janki has joined #openstack-meeting-408:45
*** jchhatbar has quit IRC08:45
*** k_mouza has joined #openstack-meeting-408:55
*** lpetrut has quit IRC08:58
*** e0ne has joined #openstack-meeting-409:08
*** jchhatbar has joined #openstack-meeting-409:10
*** janki has quit IRC09:10
*** trident has quit IRC09:16
*** trident has joined #openstack-meeting-409:17
*** zhipeng[m] has quit IRC09:22
*** yamamoto has quit IRC09:23
*** altlogbot_0 has quit IRC09:24
*** yamamoto has joined #openstack-meeting-409:24
*** altlogbot_0 has joined #openstack-meeting-409:25
*** yamamoto has quit IRC09:27
*** yamamoto has joined #openstack-meeting-409:29
*** zhipeng[m] has joined #openstack-meeting-409:31
*** yamamoto has quit IRC09:41
*** yamamoto has joined #openstack-meeting-409:49
*** jraju__ has joined #openstack-meeting-410:37
*** links has quit IRC10:38
*** gkadam has quit IRC11:02
*** lpetrut has joined #openstack-meeting-411:07
*** gkadam has joined #openstack-meeting-411:17
*** links has joined #openstack-meeting-411:33
*** jraju__ has quit IRC11:34
*** gkadam has quit IRC11:42
*** gkadam has joined #openstack-meeting-411:44
*** abhishekk has joined #openstack-meeting-411:54
*** yamamoto has quit IRC12:44
*** yamamoto has joined #openstack-meeting-412:45
*** bh526r has joined #openstack-meeting-412:45
*** jroll has quit IRC13:07
*** jroll has joined #openstack-meeting-413:08
*** jchhatbar has quit IRC13:15
*** yamamoto has quit IRC13:57
*** cheng1 has quit IRC13:58
*** aperevalov has joined #openstack-meeting-413:58
*** dklyle has quit IRC14:00
*** dklyle has joined #openstack-meeting-414:00
dulek#startmeeting Kuryr14:00
openstackMeeting started Mon Jul 29 14:00:33 2019 UTC and is due to finish in 60 minutes.  The chair is dulek. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Kuryr)"14:00
openstackThe meeting name has been set to 'kuryr'14:00
dulekWell, it's been a few weeks since I run this. Sorry about that, crazy time with some deadlines for other projects.14:01
*** cheng1 has joined #openstack-meeting-414:01
dulekThere are a few things that's going to change for Kuryr, so here they are.14:01
dulekFirst of all dmellado cannot be involved too much in the project, so me and ltomasbo are probably the go-to people here. I should probably figure out how to do a PTL change during the cycle to make sure all the formal things are ironed out.14:03
ltomasboo/14:04
aperevalovo/14:04
dulekSecond of all there's not a lot activity in those meetings, so I'd probably vote to switch to the office hours model, when this time during the week we'll simply welcome any questions on the #openstack-kuryr.14:04
dulekAny thoughts on that?14:05
dulekIf there's none and we're here, I guess aperevalov can talk a bit about improve-pod-launch-time blueprint?14:05
aperevalovno problem, it's ok for us.14:05
aperevalovyes, it's a problem for us, I guess it's not problem for your, due to you are using ovn.14:06
dulekaperevalov: Well, not really, we're mostly running nested.14:07
dulekIn that case ports are immediately ACTIVE, so the time is cut.14:07
dulekaperevalov: But I totally agree there's room for improvement.14:08
aperevalovnested - means you are plugging port to nova-instance?14:08
dulekaperevalov: Yup - trunk ports and subports.14:09
dulekPods get the subports.14:09
aperevalovdulek, thanks14:09
aperevalovthere are several parts in that blueprint. The first part about direct RPC (kuryr-controller - kuryr-daemon). Which probably should be faster than doing it through k8s.14:09
aperevalovand keep storing states into k8s, for fallback.14:10
dulekaperevalov: So we had some ideas about that in the past, I even crafted some code.14:10
dulekaperevalov: First of all… Are you using port pools?14:10
aperevalovyes,14:10
aperevalovwe measured it, in bm case - 2x times faster14:11
dulekaperevalov: Direct?14:11
aperevalovyes, it was direct ports, but we still waiting for neutron's status Active.14:11
*** cheng1 has quit IRC14:12
aperevalovand than more ports we requested than more waiting time interval14:12
dulekaperevalov: Hm, okay, I don't think I'm immediately against direct communication.14:13
dulekWe would just need to make sure we're not abusing some K8s paradigms.14:13
aperevalovit also depends on openstack controller performance14:13
dulekaperevalov: But here's an idea we had a long while ago. I think it addresses all the issues you list in the blueprint.14:14
dulekaperevalov: So basically we wanted to extend the port pools concept.14:14
aperevalovdo you have a blueprint for it?14:14
dulekaperevalov: As we have host in the pool key, pools are already "attached" to a kuryr-daemon.14:14
*** cheng1 has joined #openstack-meeting-414:14
dulekaperevalov: Yes, just a sec…14:14
dulekaperevalov: https://blueprints.launchpad.net/kuryr-kubernetes/+spec/daemon-pool-port-choice14:15
aperevalovso, do you want to do "prebind" ports14:15
aperevalovwait a minute, I'm reading14:15
dulekYup, that was part of the idea.14:15
dulekaperevalov: So the idea is that kuryr-controller would create ports for the pools and for each port create KuryrPort CRD.14:15
dulekaperevalov: kuryr-daemon would watch for those and choose the ports on their own. So if there are ports in the pool - daemon won't wait for kuryr-controller at all.14:16
dulekaperevalov: Then another improvement would be to "pre-bind" ports, so they become ACTIVE in Neutron even before pods get created. Then on the "real" binding only the interface gets moved to another netns.14:17
aperevalovif I truly understand you, all ports from such pool will be with ACTIVE status14:19
dulekaperevalov: Yup, so we won't wait for that.14:20
dulekaperevalov: Does this make any sense for you? I had some POC, it's listed on the blueprint.14:21
dulekWhile it was working okay, I haven't noticed much performance improvement back then.14:22
dulekBut probably I made some mistakes somewhere in there.14:22
*** michael-beaver has joined #openstack-meeting-414:23
aperevalovbut technically, e.g. neutron-openvswitch-agent - it's a controller for ports in ovs, it responsible for openflow rules and it set that rules when/after we attached tap into ovs. So you propose to create ovs port (osvif->plug) in batch, before real pod launch happend.14:23
dulekaperevalov: Yep, that was the idea. It was attaching those ports to a fake network namespace.14:24
dulekaperevalov: And on pod creation that port was moved to pod namespace.14:24
aperevalovlooks like it will work with SR-IOV too, but in none pool mode we still have to wait for neutron updates.14:25
dulekaperevalov: Yes, that idea doesn't really have a lot of sense without pools.14:27
aperevalovwe tried to improve wait mechanism, so please review https://review.opendev.org/#/c/669642/ )14:27
*** yamamoto has joined #openstack-meeting-414:27
dulekaperevalov: This seems to be broken for containerized case?14:29
dulekHm, maybe just a coincidence.14:30
aperevalovdo you mean containerized kuryr? no, no, we checked it in containerized case.14:30
aperevalovthis test kuryr-kubernetes-tempest-containerized passed14:31
dulekaperevalov: I see. Okay, I'll take a look, but I'm not totally convinced as it's pretty unusual case when you have access to RabbitMQ from Kuryr point.14:32
dulekaperevalov: That would only happen in clouds you manage. If you wanted to run Kubernetes + Kuryr on any OpenStack public cloud, that would not work.14:32
aperevalovok, in this case kuryr will work as before, by request.14:33
dulekaperevalov: I see it's failing back to that, sure.14:34
aperevalovFallback method should be invisible14:34
dulekaperevalov: Yes, yes, I see.14:35
dulekaperevalov: Okay, I'll take a look on that patch. Will you think about that daemon-pool-port-choice? It seems to be a bit more Kubernetes-style than to just allow direct communication.14:36
aperevalovit's a nice idea, who will finish implementation? We have resources for this...14:38
*** yamamoto has quit IRC14:38
dulekaperevalov: I'm pretty sure me, ltomasbo and Maysa are unable to work on that now.14:39
dulekSo if you think it would help your use case - I'd be super happy if you can grab it.14:39
*** yamamoto has joined #openstack-meeting-414:39
*** lpetrut has quit IRC14:39
aperevalovok, this review https://review.opendev.org/#/c/527243 was about it, wasn't it?14:41
*** happyhemant has joined #openstack-meeting-414:42
dulekaperevalov: Yes, but it's probably super outdated.14:42
dulekaperevalov: Back then we had some issue with CRD's support, but that's definitely fixed by now.14:43
dulekaperevalov: K8s API wasn't working as it should when using CRD's.14:43
*** yamamoto has quit IRC14:44
dulekOkay, I guess I'll just close the meeting. Thanks all!14:49
aperevalovThanks!!!14:49
dulek#endmeeting14:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:50
openstackMeeting ended Mon Jul 29 14:50:20 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kuryr/2019/kuryr.2019-07-29-14.00.html14:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kuryr/2019/kuryr.2019-07-29-14.00.txt14:50
openstackLog:            http://eavesdrop.openstack.org/meetings/kuryr/2019/kuryr.2019-07-29-14.00.log.html14:50
*** belmoreira has joined #openstack-meeting-414:51
*** gcheresh has quit IRC15:00
*** Luzi has quit IRC15:06
*** radeks_ has joined #openstack-meeting-415:11
*** radeks has quit IRC15:14
*** jamesgu has joined #openstack-meeting-415:16
*** e0ne has quit IRC15:30
*** links has quit IRC15:56
*** ktibi has quit IRC16:03
*** belmoreira has quit IRC16:05
*** diablo_rojo has joined #openstack-meeting-416:23
*** bh526r has quit IRC16:25
*** igordc has joined #openstack-meeting-416:59
*** happyhemant has quit IRC17:12
*** e0ne has joined #openstack-meeting-417:14
*** e0ne has quit IRC17:20
*** ralonsoh has quit IRC17:25
*** radeks_ has quit IRC17:31
*** trident has quit IRC17:47
*** trident has joined #openstack-meeting-417:51
*** lemko has quit IRC18:14
*** abhishekk has quit IRC18:44
*** e0ne has joined #openstack-meeting-419:22
*** yamamoto has joined #openstack-meeting-419:25
*** k_mouza has quit IRC19:26
*** yamamoto has quit IRC19:32
*** radeks_ has joined #openstack-meeting-419:41
*** iyamahat has quit IRC19:42
*** belmoreira has joined #openstack-meeting-420:09
*** k_mouza has joined #openstack-meeting-420:11
*** lemko has joined #openstack-meeting-420:30
*** slaweq has quit IRC20:35
*** radeks_ has quit IRC20:38
*** e0ne has quit IRC20:46
*** trident has quit IRC20:49
*** trident has joined #openstack-meeting-420:52
*** k_mouza has quit IRC21:04
*** belmoreira has quit IRC21:17
*** iyamahat has joined #openstack-meeting-421:57
*** k_mouza has joined #openstack-meeting-422:05
*** yamahata has joined #openstack-meeting-422:13
*** k_mouza has quit IRC22:20
*** davee_ has quit IRC22:25
*** davee_ has joined #openstack-meeting-422:26
*** michael-beaver has quit IRC22:32
*** diablo_rojo has quit IRC22:45
*** diablo_rojo has joined #openstack-meeting-422:52
*** yamahata has quit IRC23:12
*** lemko has quit IRC23:13
*** diablo_rojo has quit IRC23:48

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!