Monday, 2017-07-24

*** yamamoto has joined #openstack-kuryr00:08
*** kiennt has joined #openstack-kuryr00:35
*** limao has joined #openstack-kuryr00:54
*** gouthamr has joined #openstack-kuryr01:01
*** aojea has joined #openstack-kuryr01:08
*** aojea has quit IRC01:13
*** edisonxiang has quit IRC01:18
*** limao has quit IRC01:31
*** limao has joined #openstack-kuryr01:33
*** limao has quit IRC01:33
*** limao has joined #openstack-kuryr01:33
*** edisonxiang has joined #openstack-kuryr01:53
*** yedongcan has joined #openstack-kuryr01:54
*** gouthamr has quit IRC02:49
*** aojea has joined #openstack-kuryr03:09
*** aojea has quit IRC03:14
*** yedongcan has quit IRC03:50
*** yedongcan has joined #openstack-kuryr03:52
*** yboaron has joined #openstack-kuryr04:08
janonymousapuimedo: hi, tried privsep but got another error ..trying to work on it : http://paste.openstack.org/show/616262/04:16
*** limao has quit IRC04:17
*** limao has joined #openstack-kuryr04:17
*** limao has quit IRC04:22
*** limao has joined #openstack-kuryr05:03
*** tonanhngo has joined #openstack-kuryr05:10
*** aojea has joined #openstack-kuryr05:10
*** aojea has quit IRC05:15
*** janki has joined #openstack-kuryr05:25
*** kiennt has quit IRC05:32
*** aojea has joined #openstack-kuryr05:44
*** kiennt has joined #openstack-kuryr06:04
*** aojea has quit IRC06:10
*** longfei_zhang has joined #openstack-kuryr06:16
*** kiennt has quit IRC06:18
*** kiennt has joined #openstack-kuryr06:18
longfei_zhangHi, do we support the fixed ip address for clusterip service type? i mean i need to use a fixed ip when k8s creating the kube-dns service.06:28
*** yedongcan has quit IRC06:29
*** yedongcan has joined #openstack-kuryr06:30
*** yamamoto has quit IRC06:34
*** kzaitsev_ws has joined #openstack-kuryr06:34
longfei_zhangkzaitsev_ws, Hi, do we support the fixed ip address for clusterip service type? i mean i need to use a fixed ip when k8s creating the kube-dns service.06:35
janonymousapuimedo: making this change:paste.openstack.org/show/616267/ and moving it out of eventlet dir it was able to work atleast.....06:36
longfei_zhangjanonymous, Hi, do we support the fixed ip address for clusterip service type? i mean i need to use a fixed ip when k8s creating the kube-dns service.06:37
kzaitsev_wslongfei_zhang: I believe kuryr-k8s does not support clusterip06:41
longfei_zhangso we just support ClusterIP type, but can not specify the fix ip for ClusterIP service , right?06:44
kzaitsev_wslongfei_zhang: https://github.com/openstack/kuryr-kubernetes/blob/master/kuryr_kubernetes/controller/handlers/lbaas.py#L5606:44
longfei_zhangkzaitsev_ws, I know we only support  ClusterIP service type,  i'm not sure if we support use a fixed ip for this service?06:45
longfei_zhangi mean usually we have a fixed ip for dns service06:46
longfei_zhangkube-dns as a service in k8s cluster, so we fixed this ip in the yaml file06:47
longfei_zhangi'm not sure if kuryr will take this fixed ip when creating lb for it ?06:48
irenablongfei_zhang, please submit the bug if it does not work06:50
janonymouslongfei_zhang:  ^^06:50
longfei_zhangirenab, ok06:55
*** tonanhngo has quit IRC07:13
openstackgerritHangdong Zhang proposed openstack/fuxi master: Update the documentation link for doc migration  https://review.openstack.org/48651007:25
*** aojea has joined #openstack-kuryr07:28
*** janki is now known as janki|lunch07:37
*** apuimedo has quit IRC07:43
*** yamamoto has joined #openstack-kuryr07:45
*** apuimedo has joined #openstack-kuryr07:47
*** egonzalez has joined #openstack-kuryr07:47
*** tonanhngo has joined #openstack-kuryr08:04
*** tonanhngo has quit IRC08:08
*** kural_ has joined #openstack-kuryr08:09
*** kural has joined #openstack-kuryr08:09
openstackgerritHangdong Zhang proposed openstack/kuryr master: Update the documentation link for doc migration  https://review.openstack.org/48652308:24
*** tonanhngo has joined #openstack-kuryr08:32
*** tonanhngo has quit IRC08:37
*** janki|lunch is now known as janki08:40
*** c00281451 has joined #openstack-kuryr08:41
*** c00281451 is now known as zengchen08:41
*** garyloug has joined #openstack-kuryr08:47
*** yamamoto has quit IRC09:02
*** yamamoto has joined #openstack-kuryr09:15
longfei_zhanggaryloug, ping09:23
*** limao has quit IRC09:23
*** tonanhngo has joined #openstack-kuryr09:24
longfei_zhangi have a question about MACVLAN mode, there are some pods that have defined livenessprobe, which means the kubelet need to communicate with the pods through the pods ip,    kubelet process and pods are on the same vm, so for macvlan mode , the kubelet can not communicate with the pods through the pod ip09:28
*** tonanhngo has quit IRC09:28
garylougHi longfei_zhang, this is a limitation of the Linux MACVLAN driver. The slave devices (pods) cannot reach the master (VM) and vice versa.09:41
apuimedogaryloug: longfei_zhang note that you can always add an extra port for the VM for that purpose09:44
apuimedoso that kubernetes probes work09:44
longfei_zhanggaryloug, slave pods can not reach the master vm?09:45
longfei_zhanggaryloug, do you mean the pod (on the slave vm )can not reach the slave vm or master vm ?09:47
*** yamamoto has quit IRC09:47
garylouglongfei_zhang, when I say master and slave I am referring to MACVLAN only. The MACVLAN master device is the VM interface. On top of this master interface we create slave devices, these are inserted into the pod namespace.09:49
garylougThe limitation with the driver is the slaves cannot contact their own master and master cannot contact it's own slaves. All other communication is possible.09:50
*** longfei_zhang has quit IRC09:54
*** longfei_zhang has joined #openstack-kuryr09:59
longfei_zhanggaryloug, oh i got10:00
*** yamamoto has joined #openstack-kuryr10:02
*** yamamoto has quit IRC10:02
*** tonanhngo has joined #openstack-kuryr10:18
*** tonanhngo_ has joined #openstack-kuryr10:20
*** tonanhngo has quit IRC10:23
*** tonanhngo_ has quit IRC10:25
longfei_zhangapuimedo, thank you for the information, and i found one solution in this article http://backreference.org/2014/03/20/some-notes-on-macvlanmacvtap/10:28
longfei_zhang" just create another macvlan on the host on the same lower device, and use this to communicate with the guest"10:28
apuimedoright10:29
apuimedothat's what I do10:29
*** yamamoto has joined #openstack-kuryr10:33
*** kiennt has quit IRC10:33
*** tonanhngo has joined #openstack-kuryr11:02
*** tonanhngo has quit IRC11:07
apuimedojanonymous: so the problem was on the unix server you were using to listen to the requests?11:27
apuimedojanonymous: yes. from the explanation of the unixstreamserver you were using before "These four classes process requests synchronously; each request must be completed before the next request can be started. This isn’t suitable if each request takes a long time to complete, because it requires a lot of computation, or because it returns a lot of data which the client is slow to process. The solution11:31
apuimedois to create a separate process or thread to handle each request; the ForkingMixIn and ThreadingMixIn mix-in classes can be used to support asynchronous behaviour."11:31
apuimedoit was a not a good fit for cni -> cni_daemon comm11:32
apuimedowhere a lot of cni execs can talk to the cni_daemon at once11:32
*** tonanhngo has joined #openstack-kuryr11:34
*** tonanhngo has quit IRC11:39
irenabjanonymous, ping11:53
irenababout https://review.openstack.org/#/c/484754/, the gate is failing while waiting for the k8s-api to respond11:54
irenabsee in http://logs.openstack.org/54/484754/1/check/gate-install-dsvm-default-kuryr-kubernetes/18df2b1/logs/devstacklog.txt.gz11:55
irenab"Waiting for Kubernetes API Server to respond++ /opt/stack/new/kuryr-kubernetes/devstack/plugin.sh:wait_for:363 :   curl -o /dev/null -sIf http://158.69.84.20:8080"11:55
*** yamamoto has quit IRC12:19
openstackgerritMerged openstack/kuryr-kubernetes master: Updated from global requirements  https://review.openstack.org/48118612:19
openstackgerritKirill Zaitsev proposed openstack/kuryr-kubernetes master: Allow passing multiple VIFs to CNI  https://review.openstack.org/47101212:21
irenabkzaitsev_ws, hi12:24
irenabI have some time slot to go through the list of awaiting revie patches. I wonder if you plan to follow-up on https://review.openstack.org/#/c/478458/12:25
*** yamamoto has joined #openstack-kuryr12:36
*** yamamoto has quit IRC12:36
kzaitsev_wsirenab: I am12:36
kzaitsev_wsbut12:36
kzaitsev_wsit's a patch that sits on top of 3 other12:36
kzaitsev_wsI thought I'll update it after we sort out the implementation12:37
kzaitsev_wsthere's not much sense in updating the docs all the time.12:37
kzaitsev_wsI can -WF it if you like12:37
* kzaitsev_ws fighting ironic at the moment %)12:38
openstackgerritBerezovsky Irena proposed openstack/kuryr-kubernetes master: devstack: Move to devstack-plugin-container  https://review.openstack.org/47423812:41
*** yedongcan has left #openstack-kuryr12:42
irenabkzaitsev_ws, no problem. Will try to progress with the former 3 patches12:44
kzaitsev_wsirenab: while we're at it we can try and discuss the plugin mechanism for the vifs12:45
irenabsure12:47
kzaitsev_wsalso: the additional-subnets https://review.openstack.org/#/c/482544 is there mainly for demo reasons (and in case we decide to go with phased approach before TPR/CRD)12:47
kzaitsev_wslike phase-1 simple annotations, phase-2 TPR/CRD12:47
irenabLet me try to sum-on what I have in mind12:47
irenabmaybe worth to mark as WIP or something, so we will not merge by accident12:48
irenabBack to the pluggable VIF12:48
irenabI do not like that now we need to modify VIF to add handling for any new annoation we add12:49
irenabI think somethign similar to ML2 mech/extensions drivers will be a good way to provide extandability12:49
irenabVIF will call some sort of 'processorsManager' that will propogate Pod to all existing 'processors'12:50
kzaitsev_wssmth like 'enabled_drivers' in the config, that is a list of drivers, that get a pod object and do whatever they want with it?12:50
irenabyes12:51
kzaitsev_wsI'm not sure we need a separate entity for that. it'll be a singleton anyway12:51
irenabso VIF stays without the change, while any  exotic annotation is added for some new use case12:51
irenabwe already have SR_IOV/Requested-port/subnets12:52
kzaitsev_wsyeah, VIFHandler's on_present would become unmanagable pretty soon.12:53
kzaitsev_wsagree on that12:53
irenabwe need to clarify the API on this callback and then as you said, list of drivers to invoke12:56
kzaitsev_wsI can draft my idea with 'enabled_drivers' or 'vif_drivers' or 'vif_pipeline' (thinking about paste) and we can check if we can go somewhere from there12:57
irenabkzaitsev_ws, this will be great.12:59
irenabIf you won't get to it during coming days, I may have some time later this week or next to draft something12:59
*** tonanhngo has joined #openstack-kuryr13:00
*** rwallner has joined #openstack-kuryr13:00
*** rwallner has quit IRC13:01
*** rwallner has joined #openstack-kuryr13:01
kzaitsev_wsyeah. I guess it would need to know about already allocate vif-names and some way to request new names, but apart from that a pod should suffice13:05
kzaitsev_wsthe only problem is that it would be a rather invasive refactor13:06
kzaitsev_wsprobably )13:06
kzaitsev_wsirenab: I'll try to get to it tomorrow (gotta have a short day today and a long one tomorrow) and I'll ping you as soon as I upload the thing13:07
irenabkzaitsev_ws, thanks!13:11
*** longfei_zhang has quit IRC13:14
*** yboaron_ has joined #openstack-kuryr13:15
kzaitsev_wsirenab: ah, I see where the problem is. The drivers (vif/subnets/secgroups) are currently loosely coupled13:17
*** rwallner has quit IRC13:17
kzaitsev_wswe gotta think of a way for them to work together interchangeably13:17
*** rwallner has joined #openstack-kuryr13:17
*** yboaron has quit IRC13:17
kzaitsev_wsmaybe also through config13:18
*** yamamoto has joined #openstack-kuryr13:36
*** gouthamr has joined #openstack-kuryr13:40
*** yamamoto has quit IRC13:44
*** limao has joined #openstack-kuryr13:47
*** yboaron_ has quit IRC13:49
*** yboaron_ has joined #openstack-kuryr13:49
apuimedoI'll have to start the minutes 5 minutes later13:58
apuimedodmellado: can you start it and I'll join when I finish the current one?13:59
dmelladoapuimedo: sure13:59
apuimedothanks13:59
*** kzaitsev_ws has quit IRC14:03
*** yboaron_ has quit IRC14:08
*** yboaron has joined #openstack-kuryr14:12
*** zengchen1 has joined #openstack-kuryr14:23
janonymousirenab: aah, i will try to check what is wrong..last time gate was failing due to bug in gate..14:24
irenabdmellado: apuimedo : in zun it is what apuimedo did: https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/zun.yaml#L3114:40
dmelladoirenab: ack, I'll need to check what does this do and how it would affect the gates14:40
*** yboaron has quit IRC14:52
*** reedip has quit IRC14:56
*** zengchen1 has quit IRC14:57
*** apuimedo has quit IRC15:00
*** apuimedo has joined #openstack-kuryr15:01
*** reedip has joined #openstack-kuryr15:03
*** janki has quit IRC15:35
*** lihi has quit IRC15:37
*** lihi has joined #openstack-kuryr15:38
*** apuimedo has quit IRC15:41
*** apuimedo has joined #openstack-kuryr15:42
*** apuimedo has quit IRC15:43
*** apuimedo has joined #openstack-kuryr15:43
garylougHi all, we have updated TPR/CDR section in this doc with our findings. https://docs.google.com/document/d/1GNZbmVxE2n5j07YRlkx4zP-XbFSPI9UEcVifX1MRXyY/edit#heading=h.12z7zo4b90h715:49
apuimedothansk!15:51
*** atoth has joined #openstack-kuryr15:52
*** aojea has quit IRC16:03
*** egonzalez has quit IRC16:08
*** aojea has joined #openstack-kuryr16:12
*** aojea has quit IRC16:17
*** vikasc has joined #openstack-kuryr16:18
*** aojea has joined #openstack-kuryr16:21
*** aojea has quit IRC16:26
*** aojea has joined #openstack-kuryr16:31
*** aojea has quit IRC16:36
*** aojea has joined #openstack-kuryr16:40
*** aojea has quit IRC16:44
*** garyloug has quit IRC17:06
*** alraddarla_ has joined #openstack-kuryr17:14
*** alraddarla has quit IRC17:17
*** alraddarla_ has quit IRC17:17
*** alraddarla has joined #openstack-kuryr17:18
*** atoth has quit IRC17:53
*** kural_ has quit IRC18:10
*** kural has quit IRC18:10
*** vikasc has quit IRC18:24
*** atoth has joined #openstack-kuryr19:21
*** alraddarla has quit IRC20:02
*** alraddarla has joined #openstack-kuryr20:06
*** aojea has joined #openstack-kuryr20:09
*** aojea has quit IRC20:13
*** aojea has joined #openstack-kuryr20:18
*** aojea has quit IRC20:22
*** aojea has joined #openstack-kuryr20:45
*** aojea has quit IRC20:50
*** alraddarla has quit IRC20:58
*** aojea has joined #openstack-kuryr21:03
*** aojea has quit IRC21:09
*** yamamoto_ has joined #openstack-kuryr21:09
*** pc_m has quit IRC21:11
*** yamamoto_ has quit IRC21:20
*** aojea has joined #openstack-kuryr21:21
*** aojea has quit IRC21:26
*** aojea has joined #openstack-kuryr21:40
*** pc_m has joined #openstack-kuryr21:40
*** aojea has quit IRC21:44
*** rwallner has quit IRC22:01
*** yamamoto has joined #openstack-kuryr22:01
*** aojea has joined #openstack-kuryr22:07
*** jgriffith has quit IRC22:10
*** jgriffith has joined #openstack-kuryr22:10
*** aojea has quit IRC22:12
*** jgriffith has quit IRC22:12
*** jgriffith has joined #openstack-kuryr22:15
*** jgriffith has quit IRC22:16
*** jgriffith has joined #openstack-kuryr22:19
*** jgriffith has quit IRC22:19
*** jgriffith has joined #openstack-kuryr22:23
*** gouthamr has quit IRC22:27
*** gouthamr has joined #openstack-kuryr22:41
*** aojea has joined #openstack-kuryr23:20
*** aojea has quit IRC23:24
*** aojea has joined #openstack-kuryr23:29
*** aojea has quit IRC23:33
*** aojea has joined #openstack-kuryr23:38
*** aojea has quit IRC23:42

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