Friday, 2017-08-11

*** limao has joined #openstack-kuryr00:03
*** tonanhngo has joined #openstack-kuryr00:12
*** tonanhngo has quit IRC00:34
*** tonanhngo has joined #openstack-kuryr00:35
*** tonanhngo has quit IRC00:40
*** tonanhngo has joined #openstack-kuryr00:43
*** tonanhngo has quit IRC00:43
*** yedongcan has joined #openstack-kuryr01:09
*** hongbin has joined #openstack-kuryr01:38
*** caowei has joined #openstack-kuryr01:47
*** edisonxiang_ has joined #openstack-kuryr02:10
*** hongbin_ has joined #openstack-kuryr02:11
*** dougbtv_ has joined #openstack-kuryr02:15
*** hongbin has quit IRC02:18
*** dougbtv has quit IRC02:18
*** edisonxiang has quit IRC02:18
*** kzaitsev1pi has quit IRC02:18
*** kzaitsev_pi has joined #openstack-kuryr02:19
*** huats has joined #openstack-kuryr02:19
*** kzaitsev1pi has joined #openstack-kuryr02:25
*** edisonxiang_ is now known as edisonxiang02:27
*** huats_ has quit IRC02:28
*** kzaitsev_pi has quit IRC02:28
*** hongbin_ has quit IRC02:43
*** yamamoto has quit IRC02:52
*** yamamoto has joined #openstack-kuryr02:53
janonymouszengchen: sry could not reply earlier, i saw your discussion in sig-machinery though02:54
*** hongbin has joined #openstack-kuryr02:55
*** limao has quit IRC03:05
*** kiennt has joined #openstack-kuryr03:11
*** limao has joined #openstack-kuryr03:36
*** aojea has joined #openstack-kuryr03:41
*** limao has quit IRC03:42
*** aojea has quit IRC03:46
*** hongbin has quit IRC03:56
*** tonanhngo has joined #openstack-kuryr04:02
*** openstackgerrit has joined #openstack-kuryr04:44
openstackgerritJaivish Kothari(janonymous) proposed openstack/kuryr-kubernetes master: CNI Daemon template  https://review.openstack.org/48002804:44
*** caowei has quit IRC04:56
*** yamamoto has quit IRC05:03
*** yamamoto has joined #openstack-kuryr05:04
*** yamamoto has quit IRC05:11
*** limao has joined #openstack-kuryr05:24
*** caowei has joined #openstack-kuryr05:33
*** kiennt has quit IRC05:50
*** kiennt has joined #openstack-kuryr06:08
*** janki has joined #openstack-kuryr06:16
*** yamamoto has joined #openstack-kuryr06:19
*** kiennt has quit IRC06:22
*** kiennt has joined #openstack-kuryr06:23
*** yamamoto has quit IRC06:24
*** kzaitsev_ws has joined #openstack-kuryr06:39
*** ashishb has joined #openstack-kuryr06:42
*** ajo has joined #openstack-kuryr06:44
*** yamamoto has joined #openstack-kuryr06:52
*** yamamoto has quit IRC07:07
zengchenjanonymous:yes, After discussing with them, I think the design of watch framework is almost right. Why need 'list + watch' pattern? Because 'watch' may failed with the exception of 'resource version too old'. That means07:37
zengchenthe resource version sending to K8S by 'watch' is smaller than the one k8s keep in its cache. Why it will happen? The capacity of cache of K8S is limited. The 'watch' will fail when the speed of fetching the events(by watch) is less than the speed of generating events. At this scenario, it can not get events by 'watch' anymore and should 'list' all the resources and watch again.07:37
apuimedozengchen: resourceversion=0 can never get 'version too old'07:48
zengchenapuimedo: it will get a new resource version when calling 'watch' one time. Then call 'watch' with the new resource version which will be too old.07:50
apuimedozengchen: IIRC, if you do watch with resourceversion=0 it will get the current state and continue watching07:55
apuimedoyou don't need to send two watches07:55
zengchenapuimedo:how do you get the results when the watch does not return? there is a parameter of timeout for watch interface. IF you don't set, k8s may give it a default value. the request will return after that time.08:00
*** garyloug has joined #openstack-kuryr08:01
apuimedozengchen: I'm not sure I got the question08:01
janonymousapuimedo:  http://paste.openstack.org/show/618133/08:01
apuimedowhat does it matter if they are in order08:02
apuimedo?08:02
*** openstackgerrit has quit IRC08:02
apuimedowhat does it matter to know when you've caught up?08:03
apuimedothat is to say08:03
apuimedowhat do you do with the information that you've caught up?08:03
apuimedoline 6 makes a point though08:04
janonymousapuimedo:  i pasted reply for zenchen's query by k8s guy, zenchen may explain now :)08:04
*** yamamoto has joined #openstack-kuryr08:04
zengchenjanonymous:ho, you have copyed the explanation liggitt said.08:05
janonymouszengchen: ya , just for apuimedo to get context :)08:05
zengchenjanonymous:do you understand liggitt's comments?08:06
janonymouszengchen: yea, but i have similar doubts like apuimedo's though..08:07
zengchenjanonymous:I think liggitt's meaning is that the watch interface is not very reliable. it should use list + watch together.08:07
apuimedozengchen: that was my intention with the PoC08:07
apuimedobut I worried that between the list and the watch we may have enough events to go out of the cache08:07
apuimedo(resourceversion wise)08:08
janonymousapuimedo: As per ivc comment on 480028 , should i upload a dependent patch as many changes were needed for that and would take more time to test..08:09
apuimedohttps://github.com/kubernetes/kubernetes/pull/85208:09
apuimedojanonymous: link?08:10
janonymoushttps://review.openstack.org/#/c/480028/1208:10
zengchenapuimedo: it can not use only 'watch' at the current disign of k8s.08:11
apuimedozengchen: I would really like more information as to why08:11
zengchenapuimedo:yes, I will try.08:12
*** yamamoto has quit IRC08:17
apuimedozengchen: regarding "If you're watching a rarely changed resource, the most recent resourceVersion on a particular object in a stream of events you get by watching from 0 may still be old enough to be outside the watch window or have already been compacted." it seems to me that if we keep a resourceversion per resource type, this does not affect us08:20
apuimedozengchen: reading https://github.com/kubernetes/kubernetes/pull/1391008:21
apuimedothey are discussing the safety of reasourceversion=008:21
apuimedohttp://paste.openstack.org/show/618136/08:24
zengchenyes, it seems a little complex. I need some time to understand the design of watch.08:27
apuimedozengchen: you know what08:30
apuimedo?08:30
apuimedosince there is https://github.com/kubernetes/kubernetes/issues/13969 anyway. which means they want to kill the watch with resourceversion=008:31
apuimedodo it with list + watch08:31
zengchenapuimedo:I think we should reach an agreement first before doing next work.08:33
*** yamamoto has joined #openstack-kuryr08:44
apuimedozengchen: I thought you wanted to do list+watch, so my previous message was me agreeing to it08:45
apuimedo:P08:46
*** yamamoto has quit IRC08:56
janonymousapuimedo:  suggestions on how to proceed with patch09:00
apuimedojanonymous: I'll look09:02
janonymousapuimedo: thanks09:03
apuimedois this about ivc's comment to https://review.openstack.org/#/c/480028/10/kuryr_kubernetes/cni/api.py ?09:03
janonymousapuimedo: yeah the last comment: CNIDaemonizedRunner09:05
janonymousapuimedo:  and CNIStandaloneRunner09:06
janonymousapuimedo:  Last comment in https://review.openstack.org/#/c/480028/09:06
janonymousso, should i upload a dependent patch or in same patch09:10
apuimedojanonymous: should be in the same patch09:12
janonymousapuimedo: ohkay!09:13
apuimedothanks janonymous09:13
*** openstackgerrit has joined #openstack-kuryr09:13
openstackgerritJaivish Kothari(janonymous) proposed openstack/kuryr-kubernetes master: CNI Daemon template  https://review.openstack.org/48002809:13
janonymousapuimedo:  but tests are still required :( , and release date is short..09:14
apuimedojanonymous: don't worry about that09:16
janonymousapuimedo:  :)09:16
apuimedowe'll make Pike a 0.2.0 and then early queens we'll release 1.0.009:16
janonymousapuimedo: oh ohkay, thanks!09:17
*** yamamoto has joined #openstack-kuryr09:24
apuimedothanks to you ;-)09:25
*** limao has quit IRC09:26
*** yamamoto has quit IRC09:35
*** kiennt has quit IRC10:01
*** egonzalez has joined #openstack-kuryr10:03
zengchenapuimedo:sorry, i left for a conference. I will update the patch and keep on studying the pattern of list + watch. I hope I will solve your questions.10:12
*** zengchen has quit IRC10:18
*** yamamoto has joined #openstack-kuryr10:32
*** limao has joined #openstack-kuryr10:40
*** yamamoto has quit IRC10:48
*** limao_ has joined #openstack-kuryr11:03
*** limao has quit IRC11:03
*** limao_ has quit IRC11:09
*** limao has joined #openstack-kuryr11:09
*** garyloug has quit IRC11:12
*** garyloug has joined #openstack-kuryr11:12
*** caowei has quit IRC11:15
*** garyloug_ has joined #openstack-kuryr11:20
*** garyloug has quit IRC11:20
*** ajo has quit IRC11:22
*** limao has quit IRC11:24
*** egonzalez has quit IRC11:24
*** garyloug_ has quit IRC11:25
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: documentation: Document how to install services  https://review.openstack.org/49295911:27
apuimedojanonymous: kzaitsev_ws: please, take a look at this patch ^^11:28
apuimedoit was painful to do11:28
apuimedo(I found two bugs in Octavia while writing it that thankfully got fixed in the last two days)11:28
janonymousapuimedo : Great! i will review shortly :D11:29
*** limao has joined #openstack-kuryr11:30
*** garyloug has joined #openstack-kuryr11:30
apuimedothanks11:32
*** yamamoto has joined #openstack-kuryr11:35
*** dougbtv_ is now known as dougbtv11:39
*** yamamoto has quit IRC11:48
*** yamamoto has joined #openstack-kuryr11:48
*** garyloug has quit IRC11:54
*** yamamoto has quit IRC11:55
*** yamamoto has joined #openstack-kuryr11:57
*** egonzalez has joined #openstack-kuryr12:05
*** janonymous has quit IRC12:19
*** janonymous has joined #openstack-kuryr12:19
*** gouthamr has joined #openstack-kuryr12:19
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: documentation: Document how to install services  https://review.openstack.org/49295912:30
*** janki has quit IRC12:58
*** egonzalez has quit IRC13:13
*** egonzalez has joined #openstack-kuryr13:16
*** irenab has quit IRC13:18
*** lihi has quit IRC13:18
*** ajo has joined #openstack-kuryr13:18
*** oanson has quit IRC13:19
*** irenab has joined #openstack-kuryr13:19
*** oanson has joined #openstack-kuryr13:19
*** lihi has joined #openstack-kuryr13:20
*** hongbin has joined #openstack-kuryr13:44
hongbinlimao: hi liping13:44
limaohongbin: Hi13:45
hongbinlimao: need your help for one thing, i need this patch to cut the stable/pike branch for fuxi: https://review.openstack.org/#/c/489844/13:45
limaosure, let me see13:45
hongbinlimao: :)13:45
limaohongbin: this is OK for me , at that time one CI is failed, it is ok now, merging13:46
hongbinlimao: thx13:46
hongbinlimao: have a good weekend13:46
limaohongbin: wlc, you too ;-)13:47
*** ajo has quit IRC14:30
*** egonzalez has quit IRC16:12
*** kzaitsev_ws has quit IRC16:13
*** ajo has joined #openstack-kuryr16:40
*** egonzalez has joined #openstack-kuryr16:46
*** ajo has quit IRC17:04
*** ajo has joined #openstack-kuryr17:09
*** ajo has quit IRC17:11
*** yamamoto has quit IRC17:43
*** ajo has joined #openstack-kuryr17:46
*** egonzalez has quit IRC17:56
*** egonzalez has joined #openstack-kuryr18:04
*** egonzalez has quit IRC18:08
*** yamamoto has joined #openstack-kuryr18:44
*** yamamoto has quit IRC18:49
*** limao has quit IRC19:32
*** limao has joined #openstack-kuryr19:32
*** limao has quit IRC19:37
*** yamamoto has joined #openstack-kuryr19:46
*** egonzalez has joined #openstack-kuryr19:51
*** yamamoto has quit IRC19:55
*** dougbtv_ has joined #openstack-kuryr19:56
*** dougbtv has quit IRC19:59
*** pc_m has quit IRC20:04
*** pc_m has joined #openstack-kuryr20:04
*** gouthamr has quit IRC20:14
*** vikasc has quit IRC20:27
*** vikasc has joined #openstack-kuryr20:28
*** gouthamr has joined #openstack-kuryr20:32
*** dougbtv__ has joined #openstack-kuryr21:02
*** dougbtv_ has quit IRC21:06
openstackgerritMerged openstack/fuxi master: Deploy fuxi-server via uwsgi  https://review.openstack.org/48984421:09
*** egonzalez has quit IRC21:11
*** atoth has quit IRC21:25
*** hongbin has quit IRC23:12
*** limao has joined #openstack-kuryr23:34
*** limao has quit IRC23:40

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