Tuesday, 2017-03-21

*** ZZelle has quit IRC00:04
*** amotoki has joined #openstack-fwaas00:26
*** hoangcx has joined #openstack-fwaas00:48
*** reedip has quit IRC00:59
*** yamamoto has joined #openstack-fwaas01:12
*** cuongnv has joined #openstack-fwaas01:45
*** reedip has joined #openstack-fwaas02:27
*** mickeys has quit IRC02:32
*** yamamoto has quit IRC02:41
*** yamamoto has joined #openstack-fwaas02:48
*** mickeys has joined #openstack-fwaas02:57
*** yamamoto has quit IRC03:25
*** mickeys has quit IRC03:58
*** yamamoto has joined #openstack-fwaas04:09
*** chandanc_ has joined #openstack-fwaas04:38
*** mickeys has joined #openstack-fwaas04:59
*** padkrish has joined #openstack-fwaas05:00
*** mickeys has quit IRC05:04
chandanc_Hello padkrish05:04
padkrishhello chandanc_05:05
chandanc_do you want to setup the call ?05:05
padkrishsure, but do you want to wait for Sridar?05:06
chandanc_ya sure05:06
padkrishlet's give 5 mins....05:06
chandanc_ok05:06
padkrishi have pinged his cell05:06
padkrishlets see05:06
chandanc_ok05:07
padkrishin the email, he has said 10-10.30...05:11
chandanc_padkrish, let start the discussion, we can update him by mail05:11
chandanc_yes05:11
padkrishso, should we wait till 10.30 and start?05:11
chandanc_10 or 10:3005:11
padkrishyes, i don't believe we fixed the time at 1005:12
padkrishright?05:12
chandanc_its already 10:4005:12
chandanc_oh you mean US time ?05:12
padkrishyeah05:12
chandanc_ok05:12
padkrishif you have other meetings, we can start now and i can update him05:12
chandanc_no the mail says IST05:12
chandanc_sure, we can have a quick one05:13
padkrishThanks Chandan. Shall we try for Tue morning (IST)/Mon night (PDT) ? Possibly around 10am or 10:30am India time ?05:13
padkrishanyways :)05:13
padkrishlet me send a webex05:14
chandanc_sure05:14
padkrishhave sent the invite05:16
*** mickeys has joined #openstack-fwaas05:34
*** chandanc_ has quit IRC06:03
*** mickeys has quit IRC06:34
*** mickeys has joined #openstack-fwaas06:47
*** amotoki_ has joined #openstack-fwaas07:00
*** amotoki has quit IRC07:03
*** padkrish has quit IRC07:07
*** amotoki has joined #openstack-fwaas07:18
*** amotoki_ has quit IRC07:21
*** padkrish has joined #openstack-fwaas07:46
*** padkrish has quit IRC08:05
-openstackstatus- NOTICE: Wiki is broken with database problems, we are working to resolve it08:30
*** ChanServ changes topic to "Wiki is broken with database problems, we are working to resolve it"08:30
*** ChanServ changes topic to "#openstack-fwaas"08:39
-openstackstatus- NOTICE: Wiki problems have been fixed, it's up and running08:39
*** mickeys has quit IRC08:53
*** reedip has quit IRC08:56
*** reedip has joined #openstack-fwaas09:09
*** mickeys has joined #openstack-fwaas09:54
*** mickeys has quit IRC09:58
*** cuongnv has quit IRC10:10
*** amotoki has quit IRC10:17
*** hoangcx has quit IRC10:19
*** reedip has quit IRC10:30
*** faizy has joined #openstack-fwaas10:56
*** faizy has quit IRC10:59
*** faizy has joined #openstack-fwaas11:00
*** faizy_ has joined #openstack-fwaas11:24
*** faizy has quit IRC11:25
*** reedip has joined #openstack-fwaas11:33
*** amotoki has joined #openstack-fwaas11:36
*** faizy_ has quit IRC11:48
*** vks1 has joined #openstack-fwaas13:09
*** mickeys has joined #openstack-fwaas13:14
*** mickeys has quit IRC13:20
*** faizy_ has joined #openstack-fwaas13:31
*** faizy__ has joined #openstack-fwaas13:33
*** faizy_ has quit IRC13:36
*** SarathMekala has joined #openstack-fwaas13:41
*** hoangcx has joined #openstack-fwaas13:49
*** faizy__ has quit IRC13:51
*** ZZelle_ has left #openstack-fwaas13:59
*** chandanc_ has joined #openstack-fwaas13:59
*** ZZelle has joined #openstack-fwaas13:59
*** ZZelle is now known as Guest9367214:00
*** Guest93672 is now known as ZZelle__14:01
*** ZZelle__ is now known as ZZelle_14:04
*** vishwanathj has joined #openstack-fwaas14:36
*** SarathMekala has quit IRC14:51
*** faizy has joined #openstack-fwaas14:57
*** annp has joined #openstack-fwaas14:57
reediphi15:00
*** yushiro has joined #openstack-fwaas15:00
annphi15:00
*** chandanc_ has quit IRC15:00
*** SridarK has joined #openstack-fwaas15:00
yushirohi15:00
reedipSridarK about the bug https://bugs.launchpad.net/neutron/+bug/162309915:00
openstackLaunchpad bug 1623099 in neutron "FWaaSv2 - 'firewall_policy_id' is missing in firewall_rule response body" [Low,New] - Assigned to Reedip (reedip-banerjee)15:00
SridarKreedip: hi15:02
reedipHi SridarK15:02
reedipabout that, we had a small discussion in https://review.openstack.org/#/c/370731/15:03
SridarKyes the key thing is that now since rules can be associated with multiple policies15:03
SridarKwe need to reflect that in the response15:04
*** hoangcx has quit IRC15:04
SridarKearlier it was easier with a single association15:04
SridarKI think i put a todo on this when i coded the db layer for v215:04
SridarKi dont recall exactly there was some complexity so we decided that we can live with this initially15:05
SridarKso other dependent patches can make fwd progress15:05
reedipSridarK : ok15:06
SridarKlet me go back and look at the review15:07
reedipSridarK : IMHO, we can keep firewall_policies as [] in firewall_rules15:07
SridarKreedip: yes that is the thought15:07
reedipbcz one rule cant rule them all, one rule cant find them ... one rule cant win them all and in the FWG bind them :D15:08
yushiroSridarK, reedip : firewall_policy includes 'firewall_rules' and firewall_rule includes 'firewall_policies' ?15:08
SridarKLOTR ;-)15:08
reedipSridarK : Yessss !15:08
reedipyushiro : now a days code is also complicated ....:) And yess ...15:09
reedipyushiro : that was your bug :)\15:09
SridarKwe will need to derive this from the policy rule association15:09
yushiroreedip, yes, I just remembered :) ahaha15:09
yushiroIs annp here ?15:09
annpyes.15:09
annpi'm here. :)15:10
SridarKreedip: let me look as well and we can discuss more15:10
reedipSridarK_  : Ok, please put your thoughts on the review, I will resurrect it tomorrow15:10
reediphttps://review.openstack.org/#/c/370731/15:10
annpAs I mentioned on the meeting. I'd like to make netlink conntrack more maintainable to pyroute2 than using libnetfilter conntrack ctypes binding. Something related netlink was discussion here https://bugs.launchpad.net/neutron/+bug/1492714.15:10
annpwhat do you think?15:10
openstackLaunchpad bug 1492714 in neutron "RFE: Pure Python driven Linux network configuration" [Wishlist,New]15:10
SridarKi will step away to get ready to head to work15:10
reedipand I will step away to sleep ! :|15:10
yushiroannp, could you explain it again for others?( I mean that could you paste previous message?)15:10
*** faizy has quit IRC15:10
*** faizy has joined #openstack-fwaas15:11
yushiroreedip, https://review.openstack.org/#/c/370731/  I'll review it too.15:12
annpyushiro, currently, we're using a python binding for libnetlink_conntrack for improve performance15:13
reedipyushiro : if you have time, sure :)15:13
yushiroannp, yes.15:13
annpyushiro, libnetlink_conntrack is shared library written by C15:13
*** faizy_ has joined #openstack-fwaas15:14
annpyushiro, So, maintaining for a ctypes binding is more difficult than a pure python netlink.15:15
*** padkrish has joined #openstack-fwaas15:15
annpyushiro, I'd like to support netlink_conntrack to pyrout2, then we can use pyroute2 for netlink solution in fwaas.15:16
annpyushiro, that's my idea.15:17
*** faizy__ has joined #openstack-fwaas15:17
*** faizy has quit IRC15:18
yushiroannp(or Tu), OK. so, is there some performance difference b/w libnetlink_conntrack and netlink_conntrack?15:18
yushiroIf we can improve performance by using netlink_conntrack, I think it's better to support.15:19
*** faizy_ has quit IRC15:20
*** faizy__ has quit IRC15:21
annpabout performance between libnetlink_conntrack ctype binding and a native netlink conntrack in pyroute2. I think netlink conntrack in pyroute will slower by libnetlink_conntrack is C code. :) But I'm not sure.15:21
*** faizy__ has joined #openstack-fwaas15:21
annpHowever, using netlink conntrack native will be more maintainable.15:21
annpabout performance between libnetlink_conntrack ctype binding and a native netlink conntrack in pyroute2. I think netlink conntrack in pyroute will slower because libnetlink_conntrack is written by C code. :) But I'm not sure15:22
annpyushiro, what do you think?15:23
yushiroannp, I understand your point.  So, you or Tu may check performance again by using netlink_conntrack in pyroute2.15:23
*** faizy__ has quit IRC15:24
annpcurrently, netlink conntrack haven't supported in pyroute2 yet. We're planning to do that.15:24
*** faizy__ has joined #openstack-fwaas15:24
yushiroannp, aha, OK.  Is it in Pike-2 ?15:25
annpIt's just idea. It's under discussion on https://bugs.launchpad.net/neutron/+bug/1492714.15:25
openstackLaunchpad bug 1492714 in neutron "RFE: Pure Python driven Linux network configuration" [Wishlist,New]15:25
*** faizy__ has quit IRC15:26
*** faizy__ has joined #openstack-fwaas15:27
annpyushiro, I'm not sure. Anyway, we can replace libnetfilter_conntrack when netlink conntrack is available on pyroute2.15:28
annpyushiro, Let's discuss it later. Is it ok?15:28
yushiroannp, Yes.  IMO, I agree with you opinion if we can achieve performance improvement by using netlink_conntrack on pyroute2.15:29
annpyushiro, I think it's better for maintainer. :)15:29
*** faizy__ has quit IRC15:29
*** faizy__ has joined #openstack-fwaas15:30
annpyushiro, thanks for discussion.15:31
annpyushiro, SridarK, reedip, I should go to sleep. See you tomorrow. :)15:34
reedip:)15:35
yushirome too..15:38
yushiroGood night15:38
reedipyushiro  : It was android 16 !15:38
reedipkame-hame-ha !!!15:38
annpG915:39
*** annp has quit IRC15:39
*** yushiro has quit IRC15:48
*** padkrish has quit IRC16:01
*** mickeys has joined #openstack-fwaas16:02
*** mickeys has quit IRC16:06
*** amotoki has quit IRC16:13
*** vks1 has quit IRC16:39
*** faizy__ has quit IRC16:40
*** mickeys has joined #openstack-fwaas16:58
*** SridarK has quit IRC17:21
*** SridarK has joined #openstack-fwaas18:17
*** SridarK has quit IRC22:41

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