Friday, 2018-01-19

*** yamamoto has joined #openstack-fwaas00:06
*** SridarK has quit IRC00:35
*** chandanc has joined #openstack-fwaas01:24
*** hoangcx has quit IRC01:24
*** hoangcx has joined #openstack-fwaas01:25
*** chandanc has quit IRC01:31
*** threestrands_ has joined #openstack-fwaas02:49
*** threestrands_ has quit IRC02:49
*** threestrands_ has joined #openstack-fwaas02:49
*** threestrands has quit IRC02:51
*** chandanc has joined #openstack-fwaas02:56
*** AlexeyAbashkin has joined #openstack-fwaas03:44
*** jappleii__ has joined #openstack-fwaas03:44
*** jappleii__ has quit IRC03:45
*** jappleii__ has joined #openstack-fwaas03:45
*** jappleii__ has quit IRC03:46
*** threestrands_ has quit IRC03:46
*** jappleii__ has joined #openstack-fwaas03:47
*** jappleii__ has quit IRC03:48
*** AlexeyAbashkin has quit IRC03:48
*** jappleii__ has joined #openstack-fwaas03:48
*** jappleii__ has quit IRC05:52
*** annp has joined #openstack-fwaas06:33
annpchandanc, hi06:33
chandancHello06:33
annpI've just put my comment in gerrit.06:34
annpHave you check it?06:34
annphttps://review.openstack.org/#/c/535237/1/neutron_fwaas/services/firewall/agents/l2/fwaas_v2.py06:34
chandancWe sould not have any checks in the driver06:35
chandancdriver should be dumb06:35
chandancall intelegence should be in the invoker06:36
annpchandanc, IMO we should check sg_driver at fw v2 driver06:36
annpIt's more reasonable than check sg_driver at agent extension.06:36
chandancno, i dont thnk that is correct, we always keep the driver isolated as much as possible06:38
chandancall interaction with OpenStack components including plugin/ config/ db should be avoided from driver06:39
chandancthis is what we separate driver and agent06:39
annpI mean firewall l2 agent extension can have more driver, not only currently driver.06:40
chandancSure, it can and we can paramereize them accordingly06:40
chandancbut we should have the responsibility of the driver and agent clearly defined06:41
annpIn addition, May be there is another way to implement co-existence mode06:41
chandancand pushing config parsing to driver should be avoided06:41
chandanci am ok wth another way of implementing co-existance in driver06:42
chandancbut to figureout if co-existance or not in driver based on config parsing is not right06:42
annpSorry, I don't get your point here. Why do we need to check sg_driver at firewall l2 agent extension?06:44
annpIMO, it's not reasonable to me.06:45
chandancI am saying, that we need to keep driver isolated from figuring out environment06:46
chandancthat job belongs to agent06:46
annpBut I don't see any reason why we need to check sg_driver at Fwaas Agent extension. As I said, maybe there is another way to implement co-existence mode.06:49
annpand the currently implementation used sg_enable to enabled co-existence with assuming sg-driver = 'openvswitch'06:50
chandancyes it is assuming openvswitch06:52
annpI think that, the check sg_driver is 'openswitch' should be do in https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/drivers/linux/l2/openvswitch_firewall/firewall.py#L24206:52
chandancas we are supporting ovs06:52
chandancbut if you want coexistance with iptables, we will have a different driver and still the check of coexistance need to be outside the driver06:53
chandancif you are reading config or communicating to plugin06:53
annpYou mean, sg_driver = iptables, right? if so the value of sg_enable at https://github.com/openstack/neutron-fwaas/blob/master/neutron_fwaas/services/firewall/drivers/linux/l2/openvswitch_firewall/firewall.py#L242 should be false06:58
annpWe can change name of sg_enable at driver side. However we shouldn't change sg_enable value at firewall agent extension.06:59
annpI assuming there is 2 driver DriverA and DriverB,07:01
annpHow do we start DriverA and DriverB correctly? if we check sg_driver then change value of sg_enable at Firewall agent extension?07:03
annpI assume DriverA and DriverB will use sg_enable with different action for implementing co-existence mode.07:04
chandanc“We can change name of sg_enable at driver side. However we shouldn't change sg_enable value at firewall agent extension”07:13
chandanci agree07:13
chandancin the current driver we can rename the avriable as sg_with_ovs07:14
annp+107:14
annpI think sg_with_ovs is better.07:14
chandancbut in this case for iptables driver we have to use sg_with_iptables07:15
chandancwe can keep things to mean what as the name of the variable07:15
chandanci will post an update to the patch07:16
annpOk, I will review it and dig more if i can find another better. :)07:17
annpSorry for this inconvenience. Thanks07:18
reedipbbzhao : ping07:19
*** AlexeyAbashkin has joined #openstack-fwaas08:13
*** annp has quit IRC08:28
*** hoangcx has quit IRC08:28
*** annp has joined #openstack-fwaas08:29
*** hoangcx has joined #openstack-fwaas08:29
*** jafeha has quit IRC10:00
*** jafeha has joined #openstack-fwaas10:01
*** hoangcx has quit IRC10:21
*** chandanc has quit IRC11:07
*** annp has quit IRC11:55
*** jafeha__ has joined #openstack-fwaas12:01
*** jafeha has quit IRC12:01
*** reedip has quit IRC12:28
*** reedip has joined #openstack-fwaas12:41
*** hoangcx_ has joined #openstack-fwaas12:45
*** hoangcx_ has quit IRC14:21
*** yamamoto has quit IRC15:05
*** yamamoto has joined #openstack-fwaas15:06
*** yamamoto has quit IRC15:17
*** annp has joined #openstack-fwaas15:31
*** yamamoto has joined #openstack-fwaas15:48
*** annp has quit IRC16:00
*** AlexeyAbashkin has quit IRC16:35
*** yamamoto has quit IRC17:31
*** yamamoto has joined #openstack-fwaas17:38
*** yamamoto has quit IRC17:38
*** openstackgerrit has joined #openstack-fwaas17:39
openstackgerritÉdouard Thuleau proposed openstack/neutron-fwaas master: Implements a plugable backend driver  https://review.openstack.org/48026517:39
openstackgerritÉdouard Thuleau proposed openstack/neutron-fwaas master: Implements a plugable backend driver  https://review.openstack.org/48026517:56
*** AlexeyAbashkin has joined #openstack-fwaas18:16
*** AlexeyAbashkin has quit IRC18:20
*** yamamoto has joined #openstack-fwaas18:39
*** yamamoto has quit IRC18:50
*** AlexeyAbashkin has joined #openstack-fwaas19:45
*** AlexeyAbashkin has quit IRC19:49
*** AlexeyAbashkin has joined #openstack-fwaas20:27
*** AlexeyAbashkin has quit IRC20:31
openstackgerritIhar Hrachyshka proposed openstack/neutron-fwaas master: DNM testing whether lib/neutron switch breaks this repo  https://review.openstack.org/53594620:54
*** AlexeyAbashkin has joined #openstack-fwaas23:22
*** AlexeyAbashkin has quit IRC23:26
*** yamamoto has joined #openstack-fwaas23:40
-openstackstatus- NOTICE: Zuul will be offline over the next 20 minutes to perform maintenance; active changes will be reenqueued once work completes, but new patch sets or approvals during that timeframe may need to be rechecked or reapplied as appropriate23:42

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