Friday, 2017-07-21

*** yamamoto has joined #openstack-kuryr00:03
*** s1061123_ has quit IRC00:06
*** yamamoto has quit IRC00:08
*** s1061123 has joined #openstack-kuryr00:23
*** mattmceuen has quit IRC00:27
*** kiennt has joined #openstack-kuryr00:57
*** yedongcan has joined #openstack-kuryr01:04
*** rwallner has joined #openstack-kuryr01:15
*** mattmceuen has joined #openstack-kuryr01:18
*** rwallner has quit IRC01:20
*** caowei has quit IRC01:50
*** caowei has joined #openstack-kuryr02:16
*** yamamoto has joined #openstack-kuryr02:36
*** gouthamr has quit IRC02:40
*** yamamoto has quit IRC03:08
*** caowei has quit IRC03:15
*** gouthamr has joined #openstack-kuryr04:05
*** openstackgerrit has joined #openstack-kuryr04:37
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr-libnetwork master: Updated from global requirements  https://review.openstack.org/48455504:37
*** yamamoto has joined #openstack-kuryr04:39
*** yamamoto has quit IRC04:48
*** yamamoto has joined #openstack-kuryr04:51
*** yedongcan1 has joined #openstack-kuryr04:57
*** yedongcan has quit IRC04:59
*** yamamoto has quit IRC05:15
*** kiennt has quit IRC05:44
*** kiennt has joined #openstack-kuryr06:03
*** caowei has joined #openstack-kuryr06:22
*** s1061123_ has joined #openstack-kuryr06:22
*** s1061123 has quit IRC06:22
*** gouthamr has quit IRC06:36
openstackgerritLiang Cui proposed openstack/kuryr-kubernetes master: Update URLs in documents according to document migration  https://review.openstack.org/48599506:47
*** pc_m has quit IRC06:58
*** pc_m has joined #openstack-kuryr07:00
*** pc_m has quit IRC07:07
*** pc_m has joined #openstack-kuryr07:08
*** aojea has joined #openstack-kuryr07:16
*** yamamoto has joined #openstack-kuryr07:20
*** yamamoto has quit IRC07:42
apuimedojanonymous: I had an idea08:02
*** neiljerram has joined #openstack-kuryr08:02
apuimedommmm08:02
apuimedonevermind08:02
apuimedolet me think about it a bit longer08:03
apuimedovikasc: ping08:03
vikascapuimedo, pong08:03
*** neiljerram has quit IRC08:07
*** dims has quit IRC08:09
*** dims has joined #openstack-kuryr08:11
*** vikasc has quit IRC08:17
janonymousapuimedo: :)08:18
apuimedojanonymous: well, the idea is to run pyroute under the privsep context08:18
apuimedoit's the lowest cost solution08:18
apuimedothis way the eventlet stuff won't mess with it08:18
apuimedoI wonder what kind of perf impact will it have08:19
apuimedoIIUC, if I send the patch to force privsep into fork mode, we'll only fork once08:19
apuimedoand then the price will be low08:19
janonymousapuimedo: something like own process space08:20
janonymousfor pyroute part too08:20
*** egonzalez has joined #openstack-kuryr08:21
*** dims has quit IRC08:21
apuimedojanonymous: right08:22
apuimedolet me show you08:22
janonymousapuimedo:  one random thought, how about using greenpool for eventlet for pyroute08:23
apuimedohttps://github.com/openstack/os-vif/blob/8b1e906f2c356959adfc05ad7a7153dbb68ace9d/vif_plug_linux_bridge/privsep.py08:23
*** dims has joined #openstack-kuryr08:23
apuimedojanonymous: green pool?08:24
apuimedoI'm not familiar with it08:24
janonymousapuimedo:  ohkay08:24
apuimedojanonymous: can you give me more details about greenpool?08:25
janonymousapuimedo: it is like thread pool with own context08:25
janonymousapuimedo:  so if using nested eventlet threads, problem of switching might occur08:25
apuimedojanonymous: does any openstack project use it08:26
janonymousapuimedo: swift used that last i remember..08:26
apuimedoI'll check it08:28
* apuimedo currently fighting octavia devstack08:28
janonymousapuimedo:  But not exactly sure on that too..but privsep looks good :)08:28
apuimedojanonymous: can you check with privsep, then?08:28
janonymousapuimedo: sure, i will give a try :)08:29
janonymousapuimedo:  till you get free :D08:30
*** vikasc has joined #openstack-kuryr08:30
apuimedothanks08:31
*** kural has joined #openstack-kuryr08:39
*** kural_ has joined #openstack-kuryr08:39
*** garyloug has joined #openstack-kuryr08:43
*** garyloug has joined #openstack-kuryr08:47
*** neiljerram has joined #openstack-kuryr09:05
*** yedongcan1 has left #openstack-kuryr09:43
*** kiennt has quit IRC09:53
*** zengchen has quit IRC10:07
*** vikasc has quit IRC10:23
*** pc_m has quit IRC10:41
*** vikasc has joined #openstack-kuryr10:42
*** yamamoto_ has joined #openstack-kuryr10:48
*** pc_m has joined #openstack-kuryr10:50
*** rwallner has joined #openstack-kuryr11:08
*** yboaron__ has joined #openstack-kuryr11:09
*** aojea has quit IRC11:22
*** aojea has joined #openstack-kuryr11:30
*** yamamoto_ has quit IRC11:32
*** aojea has quit IRC11:34
*** aojea has joined #openstack-kuryr11:39
*** aojea has quit IRC11:43
*** kzaitsev_ws has quit IRC11:48
*** aojea has joined #openstack-kuryr11:48
*** yamamoto has joined #openstack-kuryr11:52
*** aojea has quit IRC11:53
*** yamamoto has quit IRC11:56
*** aojea has joined #openstack-kuryr11:57
*** aojea has quit IRC12:01
*** kzaitsev_ws has joined #openstack-kuryr12:06
*** aojea has joined #openstack-kuryr12:06
*** aojea has quit IRC12:09
*** aojea has joined #openstack-kuryr12:09
*** yboaron__ has quit IRC12:20
*** atoth is now known as atoth_guinea_pig12:37
*** atoth_guinea_pig is now known as atoth12:37
*** yamamoto has joined #openstack-kuryr12:42
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: Use a separate network for services subnet  https://review.openstack.org/48613412:50
*** mattmceuen has quit IRC12:51
*** yamamoto has quit IRC12:52
*** yamamoto has joined #openstack-kuryr12:52
*** caowei has quit IRC13:07
garylougHi all, we have some general questions regarding the kuryr_conf option in kuryr cni (as passed from /opt/stack/cni/conf/10-kuryr.conf). What is the significance of this variable to the controller and the cni?13:23
apuimedonone to the controller13:27
apuimedoto the cni it is just to specify where to find the kuryr config file13:27
*** yamamoto_ has joined #openstack-kuryr13:28
*** yamamoto_ has quit IRC13:28
*** yamamoto has quit IRC13:28
garylougOk, for example, if we want to run 2 kuryr controllers e.g one with nested macvlan and another with our DPDK PoC plugin, is there a way we can configure kuryr cni to use different config files?13:31
apuimedogaryloug: with or without multus?13:32
garyloug:-) for a PoC we are working with Multus for now13:32
apuimedogaryloug: what kind of config does the DPDK plugin use?13:37
* apuimedo wondering if we could do with just a single cni conf13:37
apuimedosince the vif info will come from the controllers13:37
apuimedoin the future I want it to be possible with a single controller as well13:37
apuimedoonce we have multi network support13:38
kuralDPDK is only do rx/tx packets, for kubernetes we have to send back the IPAM information, we planning to have kuryr nested MACVLAN as the control/Mgnt plane and nested-DPDK as the data plane13:40
apuimedokural: yeah, yeah. I get that13:40
apuimedowhat's the timeline to this PoC?13:40
kuralFor the 1st phase, we planning to use Multus to configure with nested MACVLAN and nested DPDK..13:40
kuralWe will contribute to the Multi-network PoC as well as. We about to finish the kubernetes network native support..But Multi-network support in Kuryr we need modification in Kuryr controller. For the time being, we planning to run two controller and configure the pod network them using Multus..13:43
kzaitsev_wsgaryloug: kural: if you guys are using multus you'll be able to use different kuryr.conf files. so I don't really get the question =)13:43
kzaitsev_wswhat would be the difference between them btw?13:43
kzaitsev_wskural: have you looked at my patches, that add multi-VIF support btw?13:44
garylougWe tried to use 2 different config files with Multus - 1 uses the nested-macvlan plugin, the other uses the DPDK PoC. However, it looks like Kuryr uses the usual /etc/kuryr/kuryr.conf in the controller no matter what config Multus passes to it.13:46
kural<kzaitsev_ws> : I yet to check it:(13:46
*** yamamoto has joined #openstack-kuryr13:47
kzaitsev_wskural: I would really appreciate it. and also it's kind of already working13:47
apuimedokzaitsev_ws: yeah, I thought the same13:48
kuralOk cool, we will apply your patches that support Multi-VIF in the controller..13:48
apuimedogaryloug: what were you passing with multus? the path to different /etc/kuryr/kuryr-x.conf or directly kuryr config ini content?13:49
garylougthe path to a new conf file with a different pod_vif_driver13:51
*** gouthamr has joined #openstack-kuryr13:51
garylougYou think this should work?13:51
apuimedoit should13:52
apuimedolet me confirm13:52
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: Use a separate network for services subnet  https://review.openstack.org/48613413:53
garylougok, thanks :-)13:53
apuimedogaryloug: it should work13:54
apuimedoin the openshift integration what I do is:13:54
apuimedo/etc/kuryr/kuryr-controller.conf for the controller13:54
apuimedoand /etc/kuryr/cni.conf for the CNI part13:54
apuimedoand in /opt/stack/cni/conf/10-kuryr.conf13:55
apuimedothe kuryr_conf parameter13:55
apuimedopoints to the /etc/kuryr/cni.conf13:55
apuimedoand it is confirmed to work13:55
*** kzaitsev_ws has quit IRC13:56
garylougdid you manually create the controller and cni conf files?13:57
apuimedogaryloug: I have a jinja template in my ansible13:58
apuimedohttp://paste.openstack.org/show/61617013:58
kuralapuimedo: I am new to Kuryr, we like to understand the difference between the the /etc/kuryr/kuryr-controller.conf and  /etc/kuryr/cni.conf. We running kuryr-kubernetes --config-file /etc/kuryr/kuryr-controller.conf14:03
kuralwith pod_vif_driver nested-macvlan14:04
apuimedokural: the difference is that the cni part needs to know nothing about the [neutron] section, basically14:04
kuralthen created the  /etc/kuryr/dpdk-cni.conf with pod_vif_driver nested-dpdk and /etc/kuryr/macvlan-cni.conf with pod_vif_driver nested-macvlan14:05
kuralusing CRD to create network objects  and assign them in the pod spec using Multus14:05
kuralmultus invoke kuryr-cni with different conf file information.14:06
kuralin our case only MACVLAN is invoked twice, different pod_vif_driver from cni.conf is ignored by kuryr controller14:07
apuimedokural: as I said, multus should just invoke kuryr cni with the json conf pointing to different kuryr config files in the kuryr_conf section14:08
garylougok, thanks Toni, we will try again with separate configs14:09
apuimedopod_vif_driver only matters for the controller IIRC14:10
apuimedothe cni part gets the vif kind from the vif annotation14:10
kuralThanks Toni, we will try it out14:19
kural;)14:19
apuimedokural: garyloug: report back if you find any issue :-)14:19
apuimedoand if you want to discuss the next phase over bluejeans with Kuryr native multi networks let me know14:19
* apuimedo should update the spec14:20
*** mattmceuen has joined #openstack-kuryr14:22
*** atoth has quit IRC14:56
*** aojea has quit IRC15:30
*** aojea has joined #openstack-kuryr15:30
*** aojea has quit IRC15:35
*** yamamoto has quit IRC15:44
*** yamamoto has joined #openstack-kuryr15:44
*** yamamoto has quit IRC15:49
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: Use a separate network for services subnet  https://review.openstack.org/48613415:56
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: Use a separate network for services subnet  https://review.openstack.org/48613416:13
*** egonzalez has quit IRC16:16
*** neiljerram has quit IRC16:39
*** garyloug has quit IRC16:46
*** yamamoto has joined #openstack-kuryr16:50
*** kural_ has quit IRC16:54
*** kural has quit IRC16:54
*** vikasc has quit IRC17:03
*** yamamoto has quit IRC17:05
*** atoth has joined #openstack-kuryr17:11
*** vikasc has joined #openstack-kuryr17:16
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: Use a separate network for services subnet  https://review.openstack.org/48613417:20
*** atoth has quit IRC18:07
*** ajo has quit IRC18:18
*** tonanhngo has joined #openstack-kuryr19:07
*** aojea has joined #openstack-kuryr20:01
*** rwallner has quit IRC20:46
*** rwallner has joined #openstack-kuryr20:48
*** rwallner_ has joined #openstack-kuryr20:49
*** rwallner has quit IRC20:53
*** rwallner_ has quit IRC20:54
*** gouthamr has quit IRC21:14
*** mestery has quit IRC21:40
*** mestery_ has joined #openstack-kuryr21:40
*** mestery_ is now known as mestery21:42
*** kural has joined #openstack-kuryr21:44
*** kural_ has joined #openstack-kuryr21:44
*** kural_ has quit IRC22:32
*** kural has quit IRC22:32
*** mattmceuen has quit IRC22:49
*** aojea has quit IRC22:51
*** aojea has joined #openstack-kuryr22:52
*** aojea has quit IRC22:56
*** gouthamr has joined #openstack-kuryr22:59
*** mattmceuen has joined #openstack-kuryr23:42
*** mattmceuen has quit IRC23:52
*** gouthamr has quit IRC23:52

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