Friday, 2018-02-02

mlavalleyushiro: Great. I'll be very glad to see you there00:00
yushiromlavalle, Regarding reedip's RFE, I think it's reasonable.  I'll also comment in this RFE and will discuss our plan in Rocky at PTG.00:01
yushiro;)00:01
mlavalleyushiro: great, thanks!00:01
SridarKyushiro: will do00:05
SridarKmlavalle: quick q00:05
mlavallesure00:06
SridarKmlavalle: we will possibly have 2 patches that we are converging on to get merged for Queens00:06
SridarKmlavalle: are we allowed to +A when they are ready or should we wait on ur recommendations00:06
SridarKmlavalle: they require a bit more tweaking - we had a long discussion today so when the submitter (annp) is online we can get things moving00:08
mlavalleSridarK: send an email today to the ML requesting a FFE for those two patches (with the reason for the exception). I will bring it up tomorrow morning during the drivers meeting00:08
mlavalledoes that work?00:08
SridarKmlavalle: they are bugfixes00:08
SridarKissues found in testing00:08
SridarKmlavalle: since they are bug fixes do they need an FFE00:09
mlavallewe froze everything00:09
SridarKmlavalle: ah ok00:10
mlavalleSridarK: hang on00:10
SridarKso we have a RC00:10
SridarKmlavalle: no prob00:10
SridarKyushiro: lets discuss more on the patches from annp - i tried to summarize in email00:11
mlavallewe are tracking everything for RC1 here: https://launchpad.net/neutron/+milestone/queens-rc100:11
mlavalleSridarK: ^^^^00:11
SridarKmlavalle: ok00:11
yushiroSridarK, Sure.  I'm testing now :)00:11
mlavalleso to honor the process, send an email to the ML requesting the inclusion of those two bugs in the RC00:12
mlavalleit is not as you say, a FFE. Just a request for those two bug fixes to be included in the RC00:12
SridarKmlavalle: got it - i will work with the contributor and we will get those covered00:12
SridarKmlavalle: perfect many thanks00:12
yushirothanks00:13
mlavalleSridarK: thank you!00:13
SridarKmlavalle: and i will look at dscp fwaas00:13
SridarKand add some notes there00:13
mlavalle:-)00:13
SridarKmlavalle: i am sure must be going crazy with the last minute release things00:14
SridarKmlavalle: so remember to breathe :-)00:14
mlavalleit always is. it comes with the territory00:14
mlavalleactually in 20 minutes I heading to my Yoga class00:14
SridarKmlavalle: imagines he is floating down on his glider00:15
SridarKmlavalle: ah there u go - perfect and i hope u will not be on IRC on ur phone while doing a headstand :-)00:15
mlavalleoh no, I leave the cell phone in the locker00:16
SridarK:-)00:16
mlavalleI completely let go for that hour00:16
SridarKoh yes00:16
SridarKSo we will have an email out and btwn xgerman_ yushiro and myself we will support it00:17
SridarKfor inclusion00:17
SridarKmany thx mlavalle00:17
mlavalleThanks00:17
SridarKyushiro: are u okay with the approach to remove the configurable option for DFWG association00:18
SridarKit seems it can cause some confusion00:18
yushiroSridarK, Yes, I just remembered some member wanted not to use default fwg.  I think it's better to shift more securely one.00:19
SridarKyushiro: so we can remove that option for now00:20
SridarKso we will not hit conntrack issues as we discussed00:20
yushiroSridarK, OK, that's great.  So, we don't have to prevent from combination 'iptables_hybrid'(SG)  + 'ovs'(FWG), right?00:21
SridarKyushiro: i think we still need that00:22
SridarKchandan's patch in neutron merged00:22
yushiroyes.00:22
SridarKbut i think we still need more testing to be sure we will not have any interoperability issues with SG (iptables hybrid) and FWaaS L2 (ovs)00:22
SridarKso i think we can have that validation to prevent this combination for Queens00:23
yushiroSridarK, Aha, right.  we're missing more testing.00:23
SridarKonce we test more - we can remove this in R00:23
SridarKyushiro: yes better to be safe00:23
yushiroSridarK, I'm watching your e-mail now :)  OK, I totally understood.00:23
SridarKah thank u :-)00:24
SridarKso this validation will be https://review.openstack.org/#/c/536234/00:24
SridarKyushiro: i think u still had some concerns - i think once they are addressed we can merge that00:25
yushiroSridarK, Sure.  My comment is not so important just minor grammar.  I'll talk with annp if he start working ASAP.00:27
SridarKyushiro: ok perfect00:27
SridarKmay be we can connect a bit later today on IRC as well and all discuss and finalize00:28
yushiroSridarK, BTW, do we need another patch to remove auto_associate_default_firewall_group ?  I think it's also OK to remove this parameter at https://review.openstack.org/#/c/539461/500:28
yushiroYes.00:28
yushiroI'll keep log-in today.00:28
SridarKyushiro: i also think we can do it in this PS itself00:28
SridarKno need for another one00:28
SridarKI will add some comments on gerrit also00:29
SridarKyushiro: i am around - except when i drive back home it will take me an hour or so00:29
yushiroSridarK, Thank you.  OK, please take care :)00:29
yushiroSridarK, I'll also comment on gerrit to put reno about that.00:29
SridarKi think if we can connect in 3 hrs or so - chandan will also be online - i think he was testing some too00:30
yushirosure00:30
*** mlavalle has quit IRC00:42
*** openstackgerrit has joined #openstack-fwaas01:24
openstackgerritCao Xuan Hoang proposed openstack/neutron-fwaas master: Fix devstack configuration for fwaas v2  https://review.openstack.org/52704001:24
*** SridarK has quit IRC01:39
*** annp has joined #openstack-fwaas02:26
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Fix auto associate default fwg  https://review.openstack.org/53946102:40
*** chandanc has joined #openstack-fwaas02:47
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Fix auto associate default fwg  https://review.openstack.org/53946103:02
yushirochandanc, Hi.  I just updated auto association patch.03:02
yushirochandanc, I removed auto_associate_default_firewall_group parameter as teams discussed last meeting.  Could you review it?03:03
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Remove disable option for default FWG and ensure it is only applied on VM ports  https://review.openstack.org/53946103:30
*** SridarK has joined #openstack-fwaas03:37
*** yamamoto has joined #openstack-fwaas03:37
SridarKyushiro: ah ok i see u have made the updates03:39
SridarKannp: ping03:39
yushiroSridarK, Yup.  and now annp are working another patch03:40
SridarKok thx03:40
SridarKso we have 2 patches that we need to get in03:41
yushiroI just hurried so forgot updating something.  Next patch I'll add reno about removing auto-associate parameter.03:41
SridarKthx for addressing my comments03:41
SridarKyes reno is missing03:41
yushiroSridarK, NP. it was very helpful for me.03:41
SridarKyushiro: when do u head for lunch ?03:43
yushiroSridarK, I'm 12:00 to 13:00.  I'm just eating with bread and tea :)03:44
SridarKyushiro: oh i am so sorry - :-)03:44
yushiroSridarK, No-no.  That is my usual lunch time :p03:45
SridarKonce the patches are ready - lets do a quick check to make sure things are good and we can ask for it to be added03:45
SridarKyushiro: i meant u are eating a very simple lunch with bread :-)03:46
yushiroSridarK, aha, yeah.  I usually like to eat sweet bread or rice bowl for lunch.03:47
yushiroSridarK, I'll update reno for draft version.  Could you check my grammar or suitable topic?  (deprecations, critical, security, fixes, other, etc...)03:48
SridarKyushiro: yes one thing on the title03:48
SridarKi think what i suggested hope it did not go beyond 65 columns03:49
yushiroYes, maybe openstack is 50 characters for title and 72 characters for description.03:49
SridarKoh it is definitely more than 6503:51
SridarKi thought it was 65 for title03:51
SridarKsorry i should have checked that03:51
SridarKRemove disable option for default FWG and allow only on VM ports03:54
SridarKthat is 64 characters03:55
yushiroSridarK, Ok, Thanks03:55
chandancyushiro: sure let me check the patch03:58
yushirochandanc, Thank you so much.  However, I'll update it now.  Just a second..03:59
chandancsure03:59
SridarKyushiro: one minor nit04:05
SridarKcan u pls check that b4 u push patch04:05
SridarKnot so imp very minor -04:06
SridarKchandanc: hi thx for the check04:06
yushiroOK04:06
chandancSridarK: no pb04:07
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Remove disable option for default FWG and allow only on VM ports  https://review.openstack.org/53946104:08
yushiroSridarK, thanks for your comment.04:09
yushiroI just reflected at the latest patch..04:09
yushirochandanc, Sorry for late :p04:09
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: Validating if a port is supported by FWaaS V2  https://review.openstack.org/53623404:15
annpSridarK, chandanc, yushiro: hi04:15
yushiroI'm not sure but in my local environment, it didn't work "tox -e releasenotes"04:17
yushiroannp, hi04:17
chandanchello annp04:17
annpI've just updated https://review.openstack.org/536234, So could you have a look at it?04:18
chandancannp: will do04:19
annpchandanc, thanks.04:19
chandancyushiro: nit change in reno, else looks good04:20
SridarKannp: hi04:20
chandanci have a question though04:20
annpSridarK, hi04:20
SridarKannp: looking04:20
chandancare we not doing validation for l2 ports in general before adding to FWG ? am i missing something ?04:21
chandanci mean the same validation for compute only ports applies to all FWG right ?04:22
chandancyushiro: SridarK any idea ?04:23
annpchandanc, we only validate vm ports, which are intended to be added to a fwg04:25
chandancso the validation in the event handler is in addition to already existing validation ?04:26
annpchandanc, yes.04:27
chandanccan you point me to the code04:28
annphttps://review.openstack.org/#/c/536234/10/neutron_fwaas/services/firewall/fwaas_plugin_v2.py@329, right?04:28
chandancno no, i mean this https://review.openstack.org/#/c/539461/9/neutron_fwaas/services/firewall/fwaas_plugin_v2.py@295 should be applicable to all FWG04:32
chandancis this the case04:32
chandancbrb04:33
yushirochandanc, Yes, @295 can validate specified port is 'VM port'04:37
yushirochandanc, So, I'd like to prepare utility method like is_vm_port() in the future.04:37
yushirochandanc, Thanks for your review!04:38
SridarKsorry guys - i am getting a request for inclusion ready04:39
SridarKannp: on https://review.openstack.org/#/c/536234/04:39
SridarKwe will need a bug id04:39
SridarKdo u have one that u can add04:40
yushiroSridarK, https://bugs.launchpad.net/neutron/+bug/174685504:40
openstackLaunchpad bug 1746855 in neutron "FWaaS V2 doesn't support Linuxbridge" [Undecided,Confirmed]04:40
SridarKah ok04:40
yushiroAnnp has already filed but need to fix bug title I think.04:40
SridarKannp: can u pls update the Patch04:40
annpyushiro, thanks.04:40
SridarKyes i think we need a better title04:41
chandancyushiro: what happens if some one tries to add DHCP/Router ports to a user defined FWG today ?04:41
annpSridarK, I've already added bug-id at Close-Bug: # in commit message04:42
SridarKannp04:42
yushirochandanc, currently, handle_port_create_event() tries to associate  DHCP/router port with default firewall group and got an error04:42
SridarKannp: sorry my bad had to scroll down04:43
SridarKsorry04:43
chandancyushiro: yes correct, but this validation is part of event handler04:43
yushirochandanc, yes sure.04:43
annpchandanc, we only validate in case of newly vm port04:44
chandancyes04:44
annpSo you can add DHCP/router port with defined fwg.04:44
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Remove disable option for default FWG and allow only on VM ports  https://review.openstack.org/53946104:45
yushiroJust reflected chandanc 's comment.04:45
annpI mean i need to ignore if port is router or DHCP in my patch.04:45
annpSridarK: no worries.04:46
SridarKFWaaS v2 failures with SG using linuxbridge or iptables_hybrid driver04:46
SridarKannp: ^^^ does that title seem reasonable for the bug04:47
SridarKannp: also pls assign the bug to urself04:47
annpSridarK, How about FWaaS V2 failures with Ml2 is Linuxbridge or security group driver is iptables_hybrid?04:49
SridarKannp: yes thats fine too04:49
annpSridarK: Done.04:54
SridarKannp: thx04:54
SridarKi putting together some notes04:54
SridarKon the bugs - i will send tht to u - can u pls check that and req inclusion of these bugs for RC04:54
SridarKthen we can support it04:55
yushirochandanc, do you have any improvement idea ?04:57
chandancyushiro: can you move the validation here https://review.openstack.org/#/c/539461/9/neutron_fwaas/db/firewall/v2/firewall_db_v2.py@81804:58
chandancand raise a exception04:58
chandanci mean the validation https://review.openstack.org/#/c/539461/9/neutron_fwaas/services/firewall/fwaas_plugin_v2.py@29504:59
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: Validating if a port is supported by FWaaS V2  https://review.openstack.org/53623404:59
annpSridarK, yushiro, chandanc: I have to go lunch, See you later.05:01
SridarKannp: 1 min05:01
SridarKannp: i am going to send u an email with notes - pls review that after u are back from lunch05:02
annpSridark: OK05:02
annpSridarK, Sure.05:02
SridarKand u will need to send out a request05:02
SridarKmany thx05:02
annpSend email to you or Miguel?05:03
yushirochandanc, I wanted to avoid to edit common method like _set_ports_for_firewall_group().  Ah, you'd like to avoid unnecessary DB access, right?05:03
SridarKannp: u will need to send it to the list05:04
SridarKannp: no worries finish ur lunch05:04
yushirochandanc, If so, that makes sense.05:04
chandancyushiro: sure i just want to make sure we have the same validation ofr all FWG05:04
chandancfor*05:04
annpSridarK, Thanks. See you guys later.:)05:05
chandancif you have any other common point to have this check, that will work too05:05
chandancyushiro: i think annp added this in his patch05:07
chandanchttps://review.openstack.org/#/c/536234/10..11/neutron_fwaas/services/firewall/fwaas_plugin_v2.py@25105:07
chandancbut too many not condition, i am trying to understand :)05:08
yushirohaha, yes05:08
yushirohmm, it should be refactored05:09
chandancya, i am getting lost05:10
yushirowe should pass 'router:interface'  and 'compute:foo' .  In addition, we should prevent unsupported condition.05:10
yushiroI think it can be written more simply05:10
chandancsure05:11
chandancand if you do, we can then remove that validation from the other patch05:11
chandancright ?05:11
chandancjust to keep all validation in one place and apply them to both default and user defined FWGs05:12
SridarKchandanc: makes sense - but lets also minimze churn in the patches05:12
SridarKfrom a testing perspective05:13
SridarKi sent u all an email - can u pls review - so annp can send out a request for including patches05:13
chandancSridarK: sure, i would like to keep things small at this time05:13
yushirochandanc, Yes, I think so.  But I'm afraid of it because current situation05:13
chandancya agree05:14
yushiroHow about refactoring after releasing with us :)05:14
SridarKok yes05:14
chandancsure05:14
yushiroThanks chandanc05:14
yushiroSo, I've just reflected from your comments now.05:14
yushiroHowever, please review it again.05:15
chandancok sure05:15
SridarKAlso before i forget - lets all try to be on the drivers meeting05:17
SridarKFri 14:00 UTC05:17
SridarKhttp://eavesdrop.openstack.org/#Neutron_drivers_Meeting05:17
yushiroHmm,  raise Exception(_("Doesn't support this port %s"), port_id)   I think it's necessary to define an exception05:18
yushiroSridarK, Ok, thanks05:18
chandancyushiro: the reno needs change, putting comment05:18
SridarKi will be back in few mins - get some dinner05:18
yushirochandanc, OK, thanks05:19
yushirochandanc, Oh, is this not necessary?  OK05:20
chandanci mean the remove the highlighted05:20
chandancso that the sentence will become like the one in “””…””05:20
yushirochandanc, you mean,  remove 'fixes' section ?05:20
chandancya the highlighted part05:21
yushirosure.  I see that 'prelude' is enough.05:21
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Remove disable option for default FWG and allow only on VM ports  https://review.openstack.org/53946105:22
yushirochan Done :)05:22
yushiroCould you review it, please ?05:22
openstackgerritchandanc proposed openstack/neutron-fwaas master: Remove disable option for default FWG and allow only on VM ports  https://review.openstack.org/53946105:47
chandancSorry yushiro i think i confused you more05:47
chandancfixed the reno05:47
chandancsorry for all the confusion05:47
yushiroOK, lemme check.05:48
yushiroAh!05:48
chandancsorry :( i was not very clear05:49
yushiroI see!  No-no.  It's my poor reading skill ;p05:49
chandanci will run some tests05:49
chandanclets move on :)05:49
yushiroYa05:49
chandancwill update results05:49
SridarKsounds good if there is another update, tweak the reno a bit: super nit: 'check an updated port ...' -> 'check if an updated port'05:54
SridarKthis is a super nit so i am not putting it on gerrit05:54
SridarKi would rather see a zuul vote :-)05:54
SridarKNow i had one confusion05:54
SridarKIf we had an update where some one remove a user define FWG, then we need to apply the default FWG on that port05:55
SridarKchandanc: yushiro: can u pls review the email i sent u all05:57
yushiroSridarK, Sure.05:59
annpSridarK: Your mail look good to me.05:59
SridarKannp: ok u are back06:00
SridarKchandanc: do u have any comments too06:00
annpSridarK, hi :)06:00
SridarKso annp can u pls reformat or update and send that openstack-dev06:00
SridarKwith the subject line as indicated06:01
yushiroSridarK, readin your e-mail06:01
annpSridarK, Sure. I'll do06:01
SridarKMiguel would like to follow the process06:01
SridarKannp: thx06:01
yushiroOK, SridarK there is no problem.06:02
annpSridarK, you're welcome. :)06:02
yushiroSridarK, BTW, should we change priority of these bug-report?06:03
SridarKyushiro: hmm i think u had marked it High06:03
SridarKoh maybe not the other one06:03
yushiroSridarK, Yes, I've already marked 'High'06:03
yushiroI wonder 'High' or 'Critical' but it's OK 'High' .06:04
SridarKhttps://bugs.launchpad.net/neutron/+bug/1746855 is not marked High06:04
openstackLaunchpad bug 1746855 in neutron "FWaaS V2 failures with Ml2 is Linuxbridge or security group driver is iptables_hybrid" [Undecided,Confirmed] - Assigned to Nguyen Phuong An (annp)06:04
yushiroOK, will put 'High'06:04
SridarKyushiro: are u able to update06:04
yushiroSridarK, Yes.06:04
SridarKthx - i am not able to06:04
yushiroOh, really?  I thought that neutron-**aas core became a neutron bug-supervisor.  Anyway, I put 'High' now :)06:05
SridarKyushiro: i think we need to ask to get added to the list - i did not i think at that time06:07
SridarKI will ask Miguel to add me06:08
SridarKyushiro: thx06:08
annpyushiro, SridarK, shall I send the mail?06:08
SridarKannp: yes pls06:09
yushiroannp, Yes, plz06:09
yushiroYes, I think SridarK and xgerman_ are suitable person to put a priority of fwaas bug list.06:10
annpDone!06:12
SridarKannp: thanks06:13
annpSridarK, thanks for your email, too :)06:15
chandancsorry was away, mail looks good to me06:19
chandancIf we had an update where some one remove a user define FWG, then we need to apply the default FWG on that port06:20
chandancyes, this is a valid case06:21
chandancshould be part of the work flow scenario06:21
SridarKannp: no worries - lets now see what happens in the drivers mtg tomorrow06:26
SridarKi think it should not be an issue - since we are almost ready06:26
yushiroannp, thanks.06:26
yushiroannp LOG.error("Doesn't support vif type %s", port.binding.vif_type)06:29
yushiroThat is bug06:29
annpyushiro, How about LOG.debug()?06:30
yushiroannp, no-no.  I mean port.binding.vif_type is a bug.06:31
yushiroAttributeError: 'dict' object has no attribute 'binding'06:31
annpyushiro, yes, I'll update now. Please comment in gerrit.06:31
yushiroannp,  raise Exception(_("Doesn't support this port %s")  In addition, I think it is not good way to raise an exception..06:32
SridarKyushiro: good eye :-)06:34
annpYes, Can I add a new file such as exceptions.py in common folder?06:35
yushiroannp, In general, it's better to define at neutron-lib but we don't have chance to do it. So,06:36
annpyushiro, so?06:38
*** jafeha__ is now known as jafeha06:39
yushiroannp, how about defining exception class in this file temporary with TODO message like "Migrate to neutron-lib" ?06:39
yushiroAnd above error message's position was strange.06:39
yushiro"Doesn't support vif type" appeared when I deployed VM instance.  So, when a port is 'vif_type: 'unbound', we should ignore this validation.06:40
annpyushiro, :)06:41
annpok. I'll update06:42
SridarK+1 on adding here with TODO06:42
SridarKI will sign off soon, but if u can update via email on testing and status of patches. We can try to get them merged soon after drivers mtg. It will be day time for xgerman_ & me06:43
SridarKbut it will be good to validate before u guys go to bed so we can get them in ASAP.06:44
SridarKyushiro: annp: chandanc: ^^^06:44
SridarKAlso pls try to attend the drivers mtg also06:44
yushiroSridarK, Of course :)06:46
yushiroannp, I think we should ignore 'unbound' port.06:52
yushiroannp, _is_port_supported_by_l2_driver calls get_port(),  but handle_update_port() has already port object.  I think it is redundancy.06:53
yushiroAt _validate_ports_for_firewall_group(), it is also having port object.06:54
yushiroSo, it's enough to send port object as an argument of _is_port_supported_by_l2_driver.06:54
annpyushiro, As I comment in code: I'd like to re-fecth to get update-to-date data06:56
annps/re-fecth/re-fetch06:57
yushiroannp, hmm, I don't know this effect.06:59
yushiroI can understand there is differ from agent-side and server-side.07:00
annpBecause from we we receive update event, port db may be change for updating process.07:00
yushiroah, OK.07:01
yushiroI just commented.07:01
annpSo I'd like to get up-to-date data.07:01
yushiroPlease ignore 'unbound' case.07:01
yushiroannp, OK, got it.07:01
annpyes, we should check vif_type is unbound and binding failed first07:02
annpyushiro, how about change from LOG.error to LOG.debug.07:02
yushiroannp, And please check at once before pushing a code.07:02
yushiroannp, which line and why?07:03
annphttps://review.openstack.org/#/c/536234/11/neutron_fwaas/services/firewall/fwaas_plugin_v2.py@268 and 26907:03
yushiroI think debug is no meaning at production environment07:04
annpah, OK.07:05
*** threestrands has quit IRC07:05
yushiroTaking combined environment(iptables_hybrid and openvswitch) into consideration, I think WARNING is suitable.07:05
yushiroSo, please change WARNING.07:06
*** AlexeyAbashkin has joined #openstack-fwaas07:18
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: Validating if a port is supported by FWaaS V2  https://review.openstack.org/53623407:36
annpyushiro, chandanc, I've just updated https://review.openstack.org/536234. Could you please have a look at it?07:38
*** AlexeyAbashkin has quit IRC07:47
*** AlexeyAbashkin has joined #openstack-fwaas07:55
*** SridarK has quit IRC08:13
yushiroannp, Just commented.08:17
yushirodid you test in your local env?08:18
annpyushiro, Just second, I will put new patch. I've tested in my local env.08:19
yushiroOK. If possible, please reflect my comment.08:20
annpI realize in case of sg=iptables_hybrid we show duplicate log08:20
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: Validating if a port is supported by FWaaS V2  https://review.openstack.org/53623408:21
annpYushiro: Please check latest patch. I've addressed your comment.08:22
annpoh, sorry. You've just posted comments. :(08:22
yushiroPlease fix exception class name08:22
yushiroYes.08:22
annpgive me a minute08:22
yushiroannp, did you test this latest patch in your env?08:23
annpyes, I've tested.08:26
annpIt worked in my env08:26
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: Validating if a port is supported by FWaaS V2  https://review.openstack.org/53623408:28
annpyushiro, please help me to test in your env08:30
yushirook08:30
annpyushiro, thanks08:37
yushiro(openstack) firewall group create --name fwg --port vm108:54
yushiroPort bf143d12-0d53-4e76-89ca-f1a9c1f7a792 is not supported by firewall L2 driver08:54
yushiroMissing period!! "."08:54
annpthanks. I will update. Anything else?08:56
yushiroFor user perspective, how should user do for reading this error message?  Hmm,08:56
yushiroA normal user doesn't need to know what backend driver is.08:58
yushiroI think it's better to realize "This port(on this host) cannot use".08:59
annpHow about "Port xxx is not supported by firewall group at the moment"?09:00
yushiroIn addition, a normal user cannot refer binding information except vnic_type.09:01
annpyes, we doesn't show binding information to normal user09:02
yushiroat that moment, is a little ambiguous..09:02
yushiroIs it better to realize the ports on this host(device_owner) cannot use.09:03
yushiro?09:03
yushiroA user tried to a port belongs another host.09:03
annpdevice_owner is compute:nova09:03
annpI think no more information for normal user.09:04
yushiroIt is included availability zone in Nova.09:04
chandanci think you can put a generic mesg09:04
yushiroah...09:04
yushironot supported is enough?09:04
chandancjust say “This may happen due to Non VM ports or incompatible driver combination”09:05
yushiro+100 chandanc09:05
yushiroimcompatible is good09:05
chandancthen he must contact admin09:05
chandancya, thats all we can help for. :)09:05
yushiroI think it's better09:05
yushirothought?  annp09:05
annpchandanc, thanks.09:05
annpyushiro: I agree09:06
chandancsure, i did a little test, ports are getting correctly associated09:06
chandancso i am mostly +1 for this patch09:06
chandancyushiro: annp if you have other updated, let me know09:08
yushirofirewall_driver=openvswitch and firewall_l2_driver=ovs,  sometimes shows following error:09:08
yushiroPort 7a4863f1-cdb2-4e5e-ba20-9eb02d8eb823 is not managed by this agent..: OVSFWPortNotFound: Port 7a4863f1-cdb2-4e5e-ba20-9eb02d8eb823 is not managed by this agent.09:08
yushiroIs it related?  I think it is from ovs-agent.09:08
chandancis that a vm port ?09:08
annpyushiro, it's not related our patch, now09:08
yushirochandanc, YEs. and after remove this port, this error displayed.09:09
annpyushiro, sometime I saw the message in ovsfw also09:09
chandancoh09:09
chandanclet me check09:09
annpchandanc, yushiro, do we need to insert port id into error message?09:14
yushiroannp, +1 it's better.09:15
yushirofor trouble shooting perspective.09:15
chandancagree, “Port id … could not be added to firewall group” then the generic msg09:15
chandancshould be enough09:16
yushirocurrent format is Port bf143d12-0d53-4e76-89ca-f1a9c1f7a792 is not supported by firewall L2 driver09:17
yushiroSo, Port %(port_id)s  is necessary and added generic one which chandanc said.09:17
chandancya yushiro : you mesg is better09:18
chandancyour*09:18
chandanc“Port bf143d12-0d53-4e76-89ca-f1a9c1f7a792 is not supported by firewall L2 driver”09:18
chandanc“This may happen due to Non VM ports or incompatible driver combination”09:19
yushiroaha, +109:19
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: Validating if a port is supported by FWaaS V2  https://review.openstack.org/53623409:23
annpyushiro, chandanc, Done.09:24
yushiroannp, thanks09:24
annpyushiro, you're welcome. :)09:25
yushiroannp, In this timing, is there posibility a specified port is non VM?09:26
yushiroannp, non VM port is guarded in early validation.09:26
yushiroannp, In addition, "Non" is similar to 'Mon'.  So, I saw Monday.   How about 'This may happen due to incompatible driver combination.' ?09:27
annpyushiro, you're concern correct.09:27
yushirochandanc, Anything comment?09:28
annpyushiro: +109:28
yushirolet's decide message here.  After that, plz update your patch.09:29
yushironit: commit message09:29
yushiros/vm/VM09:29
yushiros/ovs/OVS09:29
annp How about "Port %(port_id)s is not supported by firewall L2 driver. This may happen due to incompatible driver combination."09:30
yushiroannp, message is good.  But I think it is not 409(CONFLICT) but 500(INTERNAL ERROR)09:32
yushiroBecause this is infra error09:32
yushiroHmm, but please wait...09:33
yushiroIf these environment is combined structure like  hybrid and openvswitch09:33
yushiroOK, 409 is enough because users can keep on running these operation except the port.09:34
yushiroI'm OK this error message.09:36
yushirolet's hear about chandanc 's opinion.09:36
annpyushiro, thanks.09:36
annpchandanc, How about you?09:36
yushiroannp, Unfortunately, I'm difficult to attend today's driver meeting.09:38
yushiroSo, would it be possible to join driver's meeting?09:38
annpyushiro, yes, I'll join the meeting.09:39
annpso no worries09:39
yushiroannp, thanks09:39
annpmaybe chandanc not around here. Shall we put the patch?09:40
annpyushiro, Jakub ask them on https://bugs.launchpad.net/bugs/174685509:42
openstackLaunchpad bug 1746855 in neutron "FWaaS V2 failures with Ml2 is Linuxbridge or security group driver is iptables_hybrid" [High,In progress] - Assigned to Nguyen Phuong An (annp)09:42
annpyushiro, can you answer him?09:42
yushiroYes, will do it.09:43
annpyushiro, thanks!09:43
yushirodone09:44
annpyushiro, thanks!09:45
yushiroin neutron channel, I've talked jakub about 2 bugs for RC candidate09:48
yushiroand you will join today's meeting.09:48
openstackgerritNguyen Phuong An proposed openstack/neutron-fwaas master: Validating if a port is supported by FWaaS L2 driver  https://review.openstack.org/53623409:49
annpyushiro, yes. I saw that in neutron channel? Will SridarK and chandanc join today's meeting?09:51
yushiroMaybe09:54
yushirosorry, I have to leave my office now.  will check on my phone09:55
yushirobye09:55
yushiroMany thanks Sridar, chandanc and annp.09:55
yushiroexit09:55
*** yushiro has quit IRC09:55
annpyushiro, see you!09:56
*** hoangcx has quit IRC10:03
*** annp has quit IRC10:03
*** AlexeyAbashkin has quit IRC10:14
*** AlexeyAbashkin has joined #openstack-fwaas10:14
*** AlexeyAbashkin has quit IRC10:23
*** AlexeyAbashkin has joined #openstack-fwaas10:23
*** chandanc has quit IRC11:10
*** reedip has joined #openstack-fwaas12:22
*** chandanc has joined #openstack-fwaas12:23
*** chandanc has quit IRC12:56
*** chandanc has joined #openstack-fwaas13:15
*** chandanc has quit IRC13:23
*** chandanc has joined #openstack-fwaas13:25
*** chandanc has quit IRC13:33
*** annp has joined #openstack-fwaas14:00
*** SridarK has joined #openstack-fwaas14:06
*** chandanc has joined #openstack-fwaas14:08
SridarKannp: chandanc: I am just up - sync up on how the patches are looking during my night time14:15
annpSridarK: I think both of the patch look good. I've tested in my env. It worked.14:21
SridarKannp: ok good - i am just catching up on email14:21
annpRegarding chandanc's concern I think we should Do that in other patch.14:22
*** chandanc has quit IRC14:22
*** chandanc has joined #openstack-fwaas14:23
SridarKannp: ok - let me also go thru14:23
annp SridarK, yes. :) maybe there is some issue. But fwaas v2 api  are good shape now :)14:25
annpchandanc, regarding your concern, would you like to put it in RC1 or we can back port later?14:27
annpchandanc, I think it's better to back port later14:28
*** chandanc has quit IRC14:30
*** chandanc has joined #openstack-fwaas14:34
annpSridarK, chandanc, I have to go out and will catch the discussion on irc log.14:36
SridarKannp: ok14:37
annpsee you later14:37
SridarKannp: thx talk ltr14:37
*** annp has quit IRC14:37
xgerman_o/15:01
*** yamamoto has quit IRC15:18
*** SridarK has quit IRC15:32
*** yamamoto has joined #openstack-fwaas15:46
*** chandanc has quit IRC15:49
*** chandanc has joined #openstack-fwaas15:51
*** AlexeyAbashkin has quit IRC16:14
*** chandanc has quit IRC16:16
*** chandanc_ has joined #openstack-fwaas16:16
*** yamamoto has quit IRC16:30
*** yamamoto has joined #openstack-fwaas16:31
*** yamamoto has quit IRC16:36
*** AlexeyAbashkin has joined #openstack-fwaas16:56
openstackgerritchandanc proposed openstack/neutron-fwaas master: Remove disable option for default FWG and allow only on VM ports  https://review.openstack.org/53946117:10
amotokiis anyone interested in fixing neutron-fwaas-dashboard bugs?17:22
amotokiI will have another release at least for translations.17:22
amotokifwaas v2 dashboard is half baked now and is far from matured, but I am not sure how we move this forward as a team.17:23
*** yamamoto has joined #openstack-fwaas17:32
*** yamamoto has quit IRC17:36
*** AlexeyAbashkin has quit IRC17:39
*** yamamoto has joined #openstack-fwaas17:45
*** yamamoto has quit IRC17:45
*** chandanc_ has quit IRC17:55
*** yamamoto has joined #openstack-fwaas18:45
*** yamamoto has quit IRC18:58
*** SridarK has joined #openstack-fwaas19:06
*** AlexeyAbashkin has joined #openstack-fwaas19:11
*** AlexeyAbashkin has quit IRC19:58
*** AlexeyAbashkin has joined #openstack-fwaas20:04
*** AlexeyAbashkin has quit IRC20:19
*** SridarK has quit IRC22:29

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