Thursday, 2017-07-06

*** yuanying_ has joined #openstack-kuryr00:05
*** yuanying has quit IRC00:06
*** limao has joined #openstack-kuryr00:19
*** yuanying has joined #openstack-kuryr00:31
*** yuanying_ has quit IRC00:31
*** yuanying has quit IRC00:49
*** kzaitsev_mb has joined #openstack-kuryr00:56
*** yuanying has joined #openstack-kuryr01:02
*** yedongcan has joined #openstack-kuryr01:06
*** limao has quit IRC01:19
*** limao has joined #openstack-kuryr01:19
*** caowei has joined #openstack-kuryr01:34
*** yuanying has quit IRC01:57
*** yuanying has joined #openstack-kuryr02:00
*** hongbin has joined #openstack-kuryr02:01
*** mattmceuen has joined #openstack-kuryr02:01
*** mattmceuen has quit IRC02:26
*** yedongcan has left #openstack-kuryr03:07
*** caowei_ has joined #openstack-kuryr03:08
*** aojea has joined #openstack-kuryr03:10
*** kiennt has joined #openstack-kuryr03:10
*** caowei has quit IRC03:12
*** caowei_ is now known as caowei03:12
*** aojea has quit IRC03:15
*** hongbin_ has joined #openstack-kuryr03:20
*** hongbin has quit IRC03:21
*** hongbin has joined #openstack-kuryr03:23
*** hongbin_ has quit IRC03:24
*** raja has joined #openstack-kuryr03:27
*** raja is now known as Guest4852603:28
*** Guest48526 has left #openstack-kuryr03:29
*** yamamoto has joined #openstack-kuryr03:33
*** hongbin has quit IRC03:38
*** janki has joined #openstack-kuryr04:18
*** vikasc has quit IRC04:39
*** caowei_ has joined #openstack-kuryr04:58
*** caowei has quit IRC05:02
*** caowei_ is now known as caowei05:02
*** yboaron_ has joined #openstack-kuryr05:04
*** limao has quit IRC05:10
*** limao has joined #openstack-kuryr05:10
*** vikasc has joined #openstack-kuryr05:11
*** rustlebee has joined #openstack-kuryr05:18
*** Jiang has joined #openstack-kuryr05:22
*** russellb has quit IRC05:22
*** pc_m has quit IRC05:25
*** pc_m has joined #openstack-kuryr05:27
*** aojea has joined #openstack-kuryr05:36
*** kiennt has quit IRC05:38
*** Jiang has left #openstack-kuryr05:38
*** mestery has quit IRC05:40
*** mestery has joined #openstack-kuryr05:40
*** gsagie has quit IRC05:57
*** kiennt has joined #openstack-kuryr05:58
*** kiennt_ has joined #openstack-kuryr06:10
*** kiennt has quit IRC06:12
*** gouthamr has quit IRC06:14
*** kiennt_ has quit IRC06:16
*** kiennt has joined #openstack-kuryr06:16
*** kzaitsev_mb has quit IRC07:02
*** yboaron_ has quit IRC07:12
*** janki has quit IRC07:12
*** janki has joined #openstack-kuryr07:12
*** yamamoto has quit IRC07:29
*** yamamoto has joined #openstack-kuryr07:34
*** kural has joined #openstack-kuryr07:43
*** kural_ has joined #openstack-kuryr07:43
*** yamamoto has quit IRC07:47
*** egonzalez has joined #openstack-kuryr07:50
*** yamamoto has joined #openstack-kuryr07:53
*** garyloug has joined #openstack-kuryr08:04
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: devstack: Move to devstack-plugin-container  https://review.openstack.org/47423808:06
apuimedolimao: https://review.openstack.org/#/c/480506/108:09
limaoapuimedo: copy08:10
apuimedo;-)08:10
apuimedooanson: ping08:11
oansonpong08:11
*** yboaron_ has joined #openstack-kuryr08:12
apuimedooanson: did you already start implementing the octavia driver natively with DF?08:15
oansonI started working on the spec. Yes.08:15
apuimedooanson: is it in gerrit?08:17
oansonYes. A *very early* draft is here:08:17
oanson(1 sec. I'm finding the link and gerrit is slow)08:18
oansonhttps://review.openstack.org/#/c/477463/08:18
apuimedothanks oanson!08:18
apuimedoI want to push the networking-ovn people as well08:18
oansonI'll probably update it again by the dragonflow weekly on Monday08:18
oansonapuimedo, making competition? :)08:18
apuimedoI really want distributed SDNs to do native l4 LB08:18
apuimedootherwise I think about agents and I get sad08:19
openstackgerritMerged openstack/kuryr master: Drop MANIFEST.in - it's not needed by pbr  https://review.openstack.org/48017108:19
oansonYeah, I hear you. Agents make me sad too.08:19
apuimedooanson: do you plan to tackle both L4 and L7 at once? Or first L4 and octavia ref impl and then both l4 and l7 natively?08:20
oansonProbably the second option08:20
oansonSeeing as L7 can't be done with openflow08:20
apuimedocool08:20
apuimedooanson: did you check how to do this split approach?08:20
oansonI am still reviewing the API.08:21
oansonAs you can see from my spec, there are some things I am still investigating08:21
oansonand trying to understand08:21
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: devstack: Move to devstack-plugin-container  https://review.openstack.org/47423808:23
apuimedooanson: cool. Thanks for the update!08:27
apuimedoand good luck with it!08:28
oansonThanks.08:28
openstackgerritMerged openstack/kuryr-libnetwork master: Enforce multiple previously ignored pep8 rules  https://review.openstack.org/48050608:38
*** yamamoto has quit IRC09:00
*** kzaitsev_ws has joined #openstack-kuryr09:01
*** yamamoto has joined #openstack-kuryr09:05
*** yedongcan has joined #openstack-kuryr09:10
*** yamamoto has quit IRC09:16
*** yboaron_ has quit IRC09:21
*** yboaron_ has joined #openstack-kuryr09:26
*** limao has quit IRC09:26
*** limao has joined #openstack-kuryr09:27
*** yamamoto has joined #openstack-kuryr09:29
*** limao has quit IRC09:31
*** yboaron_ has quit IRC09:32
*** yboaron has joined #openstack-kuryr09:33
*** yamamoto has quit IRC09:53
*** yboaron has quit IRC09:54
*** vikasc has quit IRC09:57
*** yamamoto has joined #openstack-kuryr10:01
*** kiennt has quit IRC10:05
*** caowei has quit IRC10:08
*** caowei has joined #openstack-kuryr10:09
*** vikasc has joined #openstack-kuryr10:11
openstackgerritDaniel Mellado proposed openstack/kuryr-kubernetes master: DNM Test gate  https://review.openstack.org/48095410:18
*** yedongcan has quit IRC10:33
*** yedongcan has joined #openstack-kuryr10:34
*** rwallner has joined #openstack-kuryr10:49
*** caowei has quit IRC10:49
*** neiljerram has joined #openstack-kuryr10:58
openstackgerritAntoni Segura Puimedon proposed openstack/kuryr-kubernetes master: devstack: Move to devstack-plugin-container  https://review.openstack.org/47423811:22
*** garyloug has quit IRC11:33
*** dougbtv has joined #openstack-kuryr11:53
*** mattmceuen has joined #openstack-kuryr11:55
*** irenab has quit IRC12:14
*** oanson has quit IRC12:15
*** lihi has quit IRC12:15
*** irenab has joined #openstack-kuryr12:19
*** oanson has joined #openstack-kuryr12:20
*** lihi has joined #openstack-kuryr12:21
*** rustlebee is now known as russellb12:28
*** russellb has quit IRC12:28
*** russellb has joined #openstack-kuryr12:28
*** garyloug has joined #openstack-kuryr12:33
*** yedongcan has quit IRC12:34
*** yedongcan has joined #openstack-kuryr12:35
*** yboaron has joined #openstack-kuryr12:36
*** irenab has quit IRC12:44
*** irenab has joined #openstack-kuryr12:45
*** limao has joined #openstack-kuryr12:47
*** mattmceuen has quit IRC12:48
*** vikasc has quit IRC12:50
*** irenab has quit IRC12:58
*** irenab has joined #openstack-kuryr13:00
*** vikasc has joined #openstack-kuryr13:03
*** irenab has quit IRC13:13
*** irenab has joined #openstack-kuryr13:14
*** janki has quit IRC13:16
*** janki has joined #openstack-kuryr13:16
*** gouthamr has joined #openstack-kuryr13:19
*** irenab has quit IRC13:30
*** irenab has joined #openstack-kuryr13:31
*** yamamoto has quit IRC13:33
*** yamamoto has joined #openstack-kuryr13:33
*** irenab has quit IRC13:54
*** irenab has joined #openstack-kuryr13:55
*** hongbin has joined #openstack-kuryr14:01
*** zengchen1 has joined #openstack-kuryr14:09
*** irenab has quit IRC14:14
*** irenab has joined #openstack-kuryr14:15
kzaitsev_wsthe TPR/CRD situation (as well as OIR/Resource classes) is ...14:24
kzaitsev_wsdifficult )14:24
kzaitsev_wsI just hope the new iterations of these features would stick for longer14:24
apuimedokzaitsev_ws: what's the issue with the cdr?14:30
kzaitsev_wsthey're only available in 1.7 right? =)14:30
kzaitsev_wsand TPR is deprecated in 1.714:31
kzaitsev_wsbut they're not a drop-in replacement, and from the 3d party service integration point (e.g. kuryr-k8s) it's a hard decision right now what api to support14:33
kzaitsev_wsoh 1.7.0 has been released a week ago. I've missed it =(14:34
*** yedongcan has quit IRC14:34
apuimedommm14:34
apuimedoI guess that we should use TPR and then move14:34
apuimedoit sucks14:34
*** yedongcan has joined #openstack-kuryr14:34
kzaitsev_wsapuimedo: exactly! =)14:38
apuimedokzaitsev_ws: ain't that grand?14:38
kzaitsev_wsthe OIR is a bit simpler, they would have Resource Classes instead of them, but those are scheduled for 1.9/1.10 I think14:40
kzaitsev_wsapuimedo: I'm just writing up a small internal doc on multi-nic pods.14:41
kzaitsev_wsI'll probably strap together a small dirty commit, that would use annotations to request multiple ports from different networks14:42
apuimedokzaitsev_ws: in which way?14:45
apuimedoI want to check today how the other project are doing multinetwork14:45
kzaitsev_wsI'll just pass additional subnet-ids in annotations for now.14:47
kzaitsev_wsshould do the trick as a POC and maybe even ok for some simple usecases.14:47
kzaitsev_wslucky you convinced me to use multi-nic for sriov %)14:48
apuimedokzaitsev_ws: I'll write up a blueprint and share it with you so you tell me what you think14:48
kzaitsev_wsnow it's just a small patch away from actually having a simple multi-nic =)14:49
kzaitsev_wsapuimedo: a gentle reminder about vikasc's https://review.openstack.org/#/c/477066/ =)14:50
apuimedokzaitsev_ws: yeah. I know. It's just not very well aligned to what's happening upstream as far as I can tell14:51
kzaitsev_wsapuimedo: and what other projects do you have in mind?14:52
apuimedowell, first of all, CIDR shouldn't be there, I think14:53
kzaitsev_wsah it's controversial yeah. there is no way to ask for ports from different networks for example.14:56
apuimedothere is a way15:02
apuimedo:-)15:02
*** limao has quit IRC15:03
apuimedokzaitsev_ws: http://paste.openstack.org/show/614608/15:07
apuimedothis is what I had in mind15:07
apuimedothen, in the pod annotations15:07
apuimedowe have a networks key15:08
apuimedoand you can specify there name (of the network) and (ifname)15:08
apuimedos/\(ifname\)/ifname/15:08
*** aojea has quit IRC15:21
*** aojea has joined #openstack-kuryr15:21
*** reedip has quit IRC15:24
*** yboaron has quit IRC15:28
*** yedongcan has left #openstack-kuryr15:31
*** yedongcan has joined #openstack-kuryr15:31
*** janki has quit IRC15:32
*** reedip has joined #openstack-kuryr15:38
kzaitsev_wsok. that looks nice15:47
kzaitsev_ws$ kubectl get networks15:47
kzaitsev_wsthe server doesn't have a resource type "networks"15:47
kzaitsev_wsis it in 1.6.x?15:48
kzaitsev_wsapuimedo: or is it a TPR?15:50
apuimedokzaitsev_ws: I'm a cheater15:50
apuimedoit's TPR15:50
apuimedo:-)15:50
apuimedowill be cdr15:50
*** zengchen1 has quit IRC15:51
apuimedokzaitsev_ws: have you reviewed vikasc patch for network addon15:51
apuimedothat installs everythin doing kubectl create -f kuryr.yml15:51
apuimedoso in that same yml I'd put the TPD CRD15:51
apuimedokural: ping15:53
vikascapuimedo, seems you suggesting mentioning subnet-id instead cidr in network object. Is there any other big difference which i missed?15:57
vikascand ofcourse plugin: kuryr15:57
kzaitsev_wsit says `Forbidden: disallowed by cluster policy` =( I think I've got to embrace that heat deploy thing15:58
vikascapuimedo, and also i am curious to know what extra we are achieving by mentioning subnet-id and not cidr15:58
apuimedokzaitsev_ws: :-)15:59
apuimedovikasc: overlapping cidrs15:59
vikascapuimedo, hmm15:59
apuimedovikasc: and plugin is most likely ending up in the tpr crd for upstream15:59
vikascsorry, which plugin?16:00
apuimedothe plugin field16:00
vikascok16:01
apuimedovikasc: I'm still thinking through it16:02
apuimedos/through it/it through/16:02
vikascapuimedo, sure, i was just trying to be in sync16:03
apuimedovikasc: so probably I'll just propose those amendments to your spec16:03
apuimedoone thing that I was considering was that if you do not specify a subnet-id, you would just get one subnet from the pool16:03
vikascapuimedo, which pool? we dont create any pools yet IIRC16:05
*** egonzalez has quit IRC16:05
apuimedovikasc: you'd have to configure one in deployment16:05
apuimedo:p16:05
vikasci am still thinking overlapping cidr problem16:06
vikascand trying to realize it :)16:06
vikasci was thinking like this , network object wiil be a namespaced object and there will be one neutron network per namespace. Can you please help me understand with an example how overlapping cidr problem will occur?16:14
vikascapuimedo, ^16:15
apuimedovikasc: you may want to connect pod A to network X with CIDR 192.168.1.0/24 and pod B (same namespace) to network Y with CIDR 192.168.1.0/2416:16
apuimedosubnets X and Y are not of the same network at all16:16
apuimedovikasc: what you said, of net+subnet per namespace is the default behavior we have to move to16:17
apuimedobut that doesn't require multi network support16:17
apuimedomy thought is. Adding a new subnet driver called PoolDriver that instead of mapping all pods to the same subnet, it gets a subnet per namespace16:18
apuimedoand the subnets are taken from the pool16:18
apuimedothen, and as a separate thing16:18
apuimedomulti network suport16:18
apuimedo*support16:18
apuimedoin which what I propose is to create Network objects in TPR or CRD16:19
apuimedoin those objects, you can specify whichever subnet-id you want the network object to map to16:19
apuimedoor just let the "TPR kuryr driver" take from a different pool16:20
apuimedovikasc: kzaitsev_ws: does that make sense?16:20
kural_<apuimedo> Hi16:21
apuimedo kural_ I just wanted to confirm your email16:22
apuimedodid you receive a meeting invitation from me for Monday?16:22
vikascfirst of all, what is being talked as multi-networks at sig-network is multi-nic support and to achieve that i doubt that we need to create multiple neutron networks within same namespace16:22
kural_kuralamudhan.ramakrishnan@intel.com16:23
apuimedokural_: yes. I think I used that address16:23
apuimedothanks16:23
vikascor i am wondering what use case will require to have multiple neutron networks for single k8s namespace.16:23
apuimedovikasc: what is the multi-nic support good for if not to plug to different networks?16:23
kural_sorry, I didn't get the email..16:23
vikascapuimedo, different subnets16:23
apuimedovikasc: Neutron behaves better when each subnet belongs to a different net16:24
apuimedobut that's not really important16:24
kzaitsev_wsI don't like the idea of limiting 1 namespace == 1 neutron network. That seems an unnecessary limitation to me16:24
apuimedokzaitsev_ws: vikasc: and think of the case when you make a NFV namespace16:24
apuimedoand it wants to connect to one provider network16:25
kural_in my understanding multi-NIC or Multi-Network focus on the same use case.16:25
apuimedoyou'd make a Network object for that provider network16:25
apuimedoand the default provided network16:25
apuimedofor the control network16:25
vikasckural, thats my point was.. trying to understand from apuimedo what i missed16:26
vikascapuimedo, provider use case make sense to me.16:27
vikascthanks apuimedo kural_ kzaitsev_ws , i need to think and understand more :)16:29
apuimedovikasc: so it's mostly that16:29
apuimedoproviders, dpdk, sriov16:29
apuimedovikasc: did you get my meeting invite for monday16:29
apuimedo?16:29
vikascyes16:29
vikascaccepted16:29
apuimedovikasc: kzaitsev_ws: kural_: 14:00 CEST this Monday16:29
vikascgreat!16:29
apuimedothanks16:31
kzaitsev_wsyeah saw the email added to my calendar16:33
*** yamamoto has quit IRC16:33
kural_For some reason, I am not getting the error16:34
kural_*I am not getting the message16:34
apuimedo:(16:35
kural_Gary will forward me the email16:37
kural_no worries :)16:37
apuimedokural_: perfect. I want to solve it for next time thoguh16:38
apuimedo*though16:38
kural_Accepted16:39
kzaitsev_wsugh it's only Thursday =(16:43
apuimedokzaitsev_ws: longing for the weekend?16:44
apuimedocome on, one more day of Kuryr!16:44
kzaitsev_ws(=16:44
*** yedongcan1 has joined #openstack-kuryr16:59
*** yedongcan has quit IRC16:59
*** kzaitsev_ws has quit IRC17:01
*** yamamoto has joined #openstack-kuryr17:34
*** yamamoto has quit IRC17:39
*** neiljerram has quit IRC17:54
*** kural_ has quit IRC18:33
*** kural has quit IRC18:34
*** yamamoto has joined #openstack-kuryr18:37
*** yamamoto has quit IRC18:45
*** tonanhngo has joined #openstack-kuryr18:49
*** yedongcan has joined #openstack-kuryr18:59
*** yedongcan1 has quit IRC18:59
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements  https://review.openstack.org/48118619:01
*** pcaruana has quit IRC19:12
*** yamamoto has joined #openstack-kuryr19:13
*** yamamoto has quit IRC19:21
*** rwallner has quit IRC19:35
*** rwallner has joined #openstack-kuryr19:38
*** rwallner has quit IRC19:43
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr master: Updated from global requirements  https://review.openstack.org/48120419:45
openstackgerritOpenStack Proposal Bot proposed openstack/kuryr-kubernetes master: Updated from global requirements  https://review.openstack.org/48118619:45
*** yamamoto has joined #openstack-kuryr19:49
*** yamamoto has quit IRC19:53
*** yedongcan has quit IRC21:45
*** yedongcan has joined #openstack-kuryr21:45
*** aojea has quit IRC22:00
*** tonanhngo has quit IRC22:19
*** tonanhngo has joined #openstack-kuryr22:32
*** tonanhngo has quit IRC22:37
*** hongbin has quit IRC23:38

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