Tuesday, 2018-01-23

*** lnicolas has quit IRC00:09
*** AlexeyAbashkin has joined #openstack-fwaas00:16
*** AlexeyAbashkin has quit IRC00:21
*** openstackgerrit has joined #openstack-fwaas00:24
openstackgerritMerged openstack/neutron-fwaas master: Updated from global requirements  https://review.openstack.org/53502600:24
*** lnicolas has joined #openstack-fwaas00:25
*** reedip has quit IRC00:52
*** reedip has joined #openstack-fwaas00:54
*** annp has joined #openstack-fwaas02:28
openstackgerritGhanshyam Mann proposed openstack/neutron-fwaas master: Shrink Tempest scenario manager copy  https://review.openstack.org/50686603:06
*** annp has quit IRC03:29
*** bbzhao has quit IRC03:32
*** bbzhao has joined #openstack-fwaas03:38
*** annp has joined #openstack-fwaas03:47
*** annp has quit IRC04:28
*** annp has joined #openstack-fwaas04:28
*** chandanc has joined #openstack-fwaas05:27
*** SridarK has joined #openstack-fwaas05:27
*** yushiro has joined #openstack-fwaas05:29
*** amotoki has quit IRC06:03
*** amotoki has joined #openstack-fwaas06:04
chandancHello annp06:16
yushiropin xgerman_06:19
chandancCould you please verify the traffic drop for communication between ports in FWG to ports outside FWG with SG disabled06:19
annphi chandanc,06:29
annpchandanc, have you tested with my case in your environment?06:30
chandancannp: abit coughtup in office today, i will try it during night06:31
yushiroannp, chandanc : Hi.  Sorry for last meeting.  I'm OK now :)06:32
annpchandanc, Ok, no problem.06:32
yushiroLet me sync up with you for this issue regarding co-existing.06:32
annpyushiro, yes, let sync up06:33
chandancbrb in 5 mins06:33
yushirosure chandanc06:34
chandancback06:43
yushiro1. fwg(OVS) + sg(OVS)06:44
yushiro2. fwg(OVS) + sg(iptables_hybrid)06:44
yushiro3. fwg(OVS) + sg(noop)   We're talking about "2", right?06:44
annpI'm talking about use 2.06:44
yushiroYes, and actually, we've targeted to support "1." for fwaas v2.06:45
annpYes, But there can be a bug if user try to attach a hybrid port to FWG.06:46
chandancannp what is the result of the test in 106:46
yushiroannp, I understood.06:46
annpTest1 is OK.06:46
yushiroI understood that chandanc found a bug in case of "2.".06:47
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: WIP: validate port in coexistence mode  https://review.openstack.org/53623406:47
yushiroI watched your patch and you're validating a specified port is 'iptables_hybrid' or 'openvswitch'.06:49
annpI just proposed the patch to prevent a hybird_port or linuxbridge port to fwg at  https://review.openstack.org/53623406:50
annpyushiro, yes, you're right. So I think we no need to check coexistence at Firewall L2 agent.06:51
yushiroannp, if mechanism_driver is 'iptables', what was the value of 'vif_details' for the port?06:52
annpyushiro, :) mechanism_driver is Openvswitch or LinuxBrigde06:53
annpvif_details is http://git.openstack.org/cgit/openstack/neutron/tree/neutron/plugins/ml2/drivers/openvswitch/mech_driver/mech_openvswitch.py#n5306:54
yushirooh, sorry.  I wanted to talk about 'firewall_drivers' for security_group06:54
yushirohttps://github.com/openstack/neutron/blob/master/setup.cfg#L15706:54
chandancannp are you saying that we will not support “2. fwg(OVS) + sg(iptables_hybrid)” combination ?06:55
yushiroThere are 4 types:  'noop', 'iptables', 'iptables_hybrid', 'openvswitch'06:55
annpchandanc, yes,06:55
chandancbut this is the mmost common deployment06:55
annpBut If we support that, the behavior of FWG can be break, at least it is not as user expected.06:57
annpexcept you've tested and it worked fine.06:57
chandanchmm, i will surely run some test06:58
chandancin my case both borts was part of FWG06:58
chandancports*06:58
annpchandanc, So please help to test my case in your environment. I'm afraid my environment not clean.06:59
chandancSure annp07:00
chandanci will run some tests in the night07:00
yushiroHmm, In order to support hybrid case correctly, we need to add 'iptables' driver for fwaas v2...  Because the order of filtering is different due to structure.07:00
annpchandanc, thanks in advance. That's reason I put -1 in your patch :)07:00
yushiroAnyway, I'll try chandanc's step.07:01
chandancannp: SURE LET ME CHECK AGAIN07:02
chandancbut did you figure out where the traffic was dropping07:02
annpyushiro, But I think in near future hybrid solution will be deprecated so I think we don't need to care much.07:02
yushiroannp, Yes, that is my honestly opinion too.  We should indicate to a users as a WARNING / ERROR message.07:03
annpactually, I haven't figured out the issue yet. I've just tested with my case. Then I'm focusing to update my patch, because I think my solution is more clear to user. Do you think so? :)07:04
annpyushiro, +107:05
yushiroIn my understanding, currently, Neutron supports mixtured environment both iptables_hybrid and openvswitch.07:05
annpyushiro, yep!07:06
yushiroAnd, WARNING means they can continue to operate/work.  ERROR means they cannot continue to operate/work for this condition.07:08
yushiroIf fwg(OVS) + sg(iptables_hybrid) doesn't work correctly and it is dangerous to keep on operating/working, it should be notified it as an ERROR.07:09
annpyushiro, +1. If we prevent attaching a port to fwg at API level, then we won't worry about coexistence mode.07:12
yushiroannp, Yes, but we should also describe carefully in docs about that.07:12
chandancannp: coexistance is enabled only for OVS + OVS07:13
yushirochandanc, +107:13
chandancfwg(OVS) + sg(iptables_hybrid) is still considered as standalone07:13
yushirochandanc, Sorry, what's mean 'standalone' ?07:15
annpfrom user perspective, Do you think user want to care about a VM, which is run in FWG(OVS) + SG(iptables_hybrid)?07:16
chandancstandalone means FWaaS OVS driver will not redirect packets to SG OVS tables07:16
annpchandanc, yes07:17
yushirochandanc, aha, I see.07:17
chandancannp: that is the default as of now07:17
yushiroHowever, can we select 'standalone' or 'coexisting' mode for fwaas v2?07:17
annpchandanc, So I've asked you to confirm in this case fwg will be work as expected or not07:18
chandancyushiro: yes07:18
yushirochandanc, OK, sorry I forgot whether it is possible to choose.07:18
chandancit is auto detected as of now07:18
yushiroAha.07:19
chandancthe patch we are discussing is about figuring out how to detect this situation07:19
annpchandanc, yushiro, As I said above, I'm afraid that will be break behavior of FWG07:19
yushirochandanc, Ah, that's why you were considering agen-side parameters.07:19
chandancyushiro: yes07:20
chandancannp: let me confirm07:20
annpchandanc, thanks in advance.07:20
yushiroPatternA:  VM ---> sg(iptables on linuxbridge) ---> fwg(OVS with standalone mode) ---->07:21
yushiroPatternB:  VM ---> fwg(OVS with co-existing) ---> sg(OVS) --->07:22
chandancyushiro: PatternA is not possible as l2 agent can be either LB or OVS07:22
yushiroIn my understanding, flows are handled in above ordering.07:23
yushirochandanc, ah, PatternA is that we're discussing to support 'standalone' or not support, right?07:24
annp PatternA: VM -->sg(iptales hybrid)--> fwg(OVS with standalone mode)?07:25
chandancannp: correct07:25
chandancneed to go for lunch07:25
yushiroannp, Yes, I wrote in backend technology.. (iptables)   Configuration is 'iptables_hybrid'07:25
chandancwill catch up on your logs07:26
yushiroOK,07:26
chandancplease carry on with the discussion07:26
annpchandanc, enjoy!07:26
annpPlease go ahead yushiro07:26
yushiroannp, I know your considering PatternA and PatternB is totally different for flow validation order.07:26
yushiros/your/you're07:27
annpthen?07:27
yushiroPatternA:  ingress: 1.fwg(ovs with standalone), 2.sg(iptables_hybrid) , 3. VM   egress: 1.VM, 2:sg(iptables_hybrid), 3:fwg(ovs with standalone)07:28
annpyep07:29
yushiroPatternB:  ingress: 1.fwg(ovs with coexisting), 2.sg(ovs) , 3. VM   egress: 1.VM, 2:fwg(ovs with coexisting), 3:sg(ovs)07:29
yushiroThis is my understanding for flow validation order.07:29
yushiroI think a place is different to be dropped both A and B.07:31
yushiros/both/between07:31
annpyushiro, I agree with your flows07:32
annpIf Pattern A will work as expected, then we can go with chandanc's patch07:34
*** bbzhao has quit IRC07:35
annpIf Pattern A won't work as expected,then I think we should prevent hybrid port in API level. That's my opinion.07:35
*** bbzhao has joined #openstack-fwaas07:35
annpDo you think so?07:36
*** SridarK has quit IRC07:36
annpsorry, s/won't/doesn't07:36
annpIf we prevent hybrid port at API side, then there is no worry at firewall l2 agent side, right?07:37
yushiroannp, Sure.07:48
yushiroYes, if "A" works correctly, I think it's OK to go with chandanc's one.07:50
yushiroIf "A" doesn't work corretly, it's OK for your approach(validating in API layer)07:51
annpyushiro, yes, I think so.07:52
yushiroAnyway, I think it's better to notify ERROR message for your patch.  I'll comment it either.07:52
annpSo we should waiting confirm from chandanc, then we can discuss something :)07:53
yushiroYes.07:53
yushiroBTW, did you see my e-mail for default fwg?07:53
annpyushiro, I think your solution reasonable. But lets wait for others07:54
yushiroannp, Yes, but I'd like to know current behavior.07:55
yushiroWhether non-admin user can apply default fwg to a port.07:55
annpwhat does your mean 'apply' is 'action=update' or ..?07:59
yushiroYes, update07:59
annpnon-admin user can't update for default fwg.07:59
yushiroYes, so auto-association works correctly.  But, if a user wants to change from default fwg to user-created fwg,08:00
yushiroit will be failed.08:00
annpyes, I think so.08:00
yushiroOK.08:00
yushirowe're on same page now.08:00
annpSo it should be a bug.08:00
yushiroyes.08:01
yushiroIn my memory, when auto-association, we evelated a context into admin priviledge08:01
annpI think we have enough time for bug fix, right?08:01
yushiroOf course!08:01
annpI have to go to another meeting now. See you later.08:02
yushiroOK.08:05
*** AlexeyAbashkin has joined #openstack-fwaas08:05
*** yushiro has quit IRC08:05
*** annp has quit IRC08:38
*** annp has joined #openstack-fwaas08:38
*** jafeha__ is now known as jafeha08:44
*** bbzhao has quit IRC09:24
*** bbzhao has joined #openstack-fwaas09:24
openstackgerritÉdouard Thuleau proposed openstack/neutron-fwaas master: Implements a plugable backend driver  https://review.openstack.org/48026510:07
*** yushiro has joined #openstack-fwaas10:35
*** annp has quit IRC11:03
*** AlexeyAbashkin has quit IRC11:06
*** yushiro has quit IRC11:07
*** chandanc has quit IRC11:09
*** chandanc has joined #openstack-fwaas11:14
*** bbzhao has quit IRC11:16
*** bbzhao has joined #openstack-fwaas11:16
*** chandanc has quit IRC11:19
*** AlexeyAbashkin has joined #openstack-fwaas11:23
*** yushiro has joined #openstack-fwaas14:07
yushiroping doude14:08
doudehi yushiro14:08
doudehow are you doing?14:08
yushirodoude, hi.  Fine thanks :)  Sorry for last meeting.14:09
doudeno problem14:09
doudehope you are doing well now14:09
yushirodoude, Yup:) And, thanks for your e-mail regarding default fwg.14:09
yushiroGood catch.  This was a bug and just fixed now :)14:10
doudeyes do you confirm what I saw?14:10
yushiroYes.14:10
doudecool do you have a review I can test/review?14:10
yushiroyes, please.  Just a moment, please.  I'm running py35 now.14:10
doudeok great14:11
yushiroyou can test following procedure:  https://etherpad.openstack.org/p/fwaas-sandbox14:12
yushiroJust I'm writing :)14:12
doudeyes I see that yushiro14:14
doudefyi, you can specify specific configurations flag in the devstack local.conf file14:15
doudeas you can see here http://paste.openstack.org/show/650292/ on lines 29 to 31, yushiro14:16
yushirodoude, awesome :)14:17
yushirofirewall_driver = ovs14:17
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Enable to associate ports with default fwg for non-admin users  https://review.openstack.org/53684514:26
yushiroAfter applying this patch, non-admin user also can associate ports with default FWG.14:27
yushiroAh, but don't care about 'ingress_firewall_policy_id' and 'egress_firewall_policy_id' !!  will fix..14:34
yushirohmm,,, but waiting other reviews..14:35
*** cleong has joined #openstack-fwaas14:42
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Enable to associate ports with default fwg for non-admin users  https://review.openstack.org/53684514:44
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Enable to associate ports with default fwg for non-admin users  https://review.openstack.org/53684514:53
yushirosorry, please review from PS3.14:53
*** yushiro has quit IRC15:00
xgerman_o/15:36
*** SridarK has joined #openstack-fwaas15:41
SridarKdoude: hi15:41
doudehi SridarK15:42
SridarKdoude any thoughts on the email i sent u - to see if we can get this done in 2 phases15:42
SridarKi am not sure that is possible15:42
SridarKbut if we can minimize impact on the reference implementation  - will make life a bit easier15:43
SridarKin looking thru the changes - maybe it is a bit tricky but i wanted to explore every option15:43
xgerman_yeah, with the clock ticking smaller bites are better…15:44
* xgerman_ catching up what happened last night15:44
doudeI thnik about that and I think we (at Contrail) can develop our own FWaaS service plugin until we could propose a driver based on the same service plugin as the reference implementation15:45
xgerman_we can definitely try to get your code into R-115:45
doudebut I think it's better for FWaaS to propose an interface to plug exoctic drivers like Contrail15:46
doudeimo15:46
doudeyes xgerman_ we should not abandon my patch15:46
doudeIt re-organize FWaaS code and split clearly DB from plugin code15:46
doudeand that will permit to factorize15:46
xgerman_+115:46
SridarKyes exactly15:47
doudeI'll explain that to my management15:47
SridarKthis is long standing and we need to get that done15:47
doudes/explain/propose15:47
xgerman_yes, so usually Neutron merges Wedensday night so we have about two more days…15:47
SridarKdoude so do u think we can get a patch in with just the interface defined that u can use for Contrail but the reference implementation stays as is15:49
SridarKor u are proposing an out of tree service plugin for now15:49
SridarKand then we refactor in R115:49
doudean out of tree for the moment15:49
SridarKdoude ok15:50
SridarKand we will keep this patchset15:50
SridarKbut lets propose a bp and get that approved for R-115:50
SridarKso we are in line with the process requirements15:50
doudewe don't need it in the FWaaS tree as it's a temporary solution that will be replace when my patch will merge in R15:50
SridarKdoude: perfect15:50
doudeyes we are15:51
SridarKthere should be a very old bp for service drivers but i think u should propose a new bp15:52
SridarKwe have 2 patchsets in flight at least - that will cause more churn15:53
SridarKok so summary: 1) doude will use an out of tree implementation as a temporary solution for customers15:53
SridarK2) We will retain the current PS15:54
SridarK3) doude will propose a bp for service driver refactor15:54
SridarK4) We will target merge in R-1 as the highest priority15:54
SridarKxgerman_: does that seem rational15:55
SridarKdoude: xgerman_ are we on the same page ?15:55
doudesounds good15:55
xgerman_yep15:56
SridarKdoude: ok - we can see if it makes sense to break up the PS - if reqd - but we can discuss later and if we are early in the cycle - less risk15:57
doudesure15:57
SridarKdoude: thx for ur understanding15:57
doudeand I think fter my patch we can also continue to improve/refactor code15:57
SridarKdoude: +115:57
doudeI think principlly about sanity checks we is common for all drivers15:58
SridarKagreed15:58
doudeI think principally about sanity checks which are common for all drivers15:58
*** openstackgerrit has quit IRC16:03
*** bbzhao has quit IRC16:06
*** bbzhao has joined #openstack-fwaas16:07
*** SridarK has quit IRC16:07
*** AlexeyAbashkin has quit IRC17:02
*** bbzhao has quit IRC17:10
*** bbzhao has joined #openstack-fwaas17:11
*** bbzhao has quit IRC17:16
*** 7JTADEBX8 has joined #openstack-fwaas17:17
*** bbzhao has joined #openstack-fwaas17:17
*** AlexeyAbashkin has joined #openstack-fwaas18:31
*** AlexeyAbashkin has quit IRC18:35
*** cleong has quit IRC21:35

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