Friday, 2018-05-11

*** longkb has joined #openstack-fwaas00:32
*** lnicolas has joined #openstack-fwaas02:04
bzhao__hi, fw handsome guys02:05
bzhao__I have a question about how to update the existing FWG status, as we support apply fwg towards vm ports, so each l2 agent will update the fwg status if there is any port it server?   So does that mean the last update will the FWG status?02:07
bzhao__hi?02:19
bzhao__annp: ping,02:45
bzhao__njohnston: ping02:50
*** yamamoto has joined #openstack-fwaas04:37
*** yamamoto has quit IRC05:31
*** yamamoto has joined #openstack-fwaas05:46
*** reedip has quit IRC06:14
annpbzhao__, ping06:17
annpbzhao, pong06:17
bzhao__annp: hi, I need help about the fwg status, now we support adding vm port into fwg, so if several vms in different compute nodes are in the same fwg, does each l2 agent update the fwg status for processing the fwg update/create?  I found the existing code seem to update the status in each l2/l3 agent. It make me confused. So please correct me. :)06:25
annpbzhao__, from my understanding, L2 agent will update fwg status for fwg update/create.06:27
bzhao__annp:  So if the vm port locates different compute node, it will update the status twice, if the first is error, the second will overide it... So I'm not sure I understand we how to decide a fwg status.06:29
annpbzhao__, if fwg has status error, then second process won't override it, IIRC.06:31
bzhao__annp: You mean once a single port process failure from a port list which associated a fwg, it will be Error status. Could you please help me to find the code? Then I think I can make a good understand about this. Thanks. :)06:33
annpbzhao__, that mean if the fwg status is ERROR, then nobody can do any action on the fwg, I guess.06:34
*** annp has quit IRC06:36
*** annp has joined #openstack-fwaas06:36
*** longkb1 has quit IRC06:37
bzhao__annp: Yeah, Users can not operate the fwg. But how to deal with the agent side to set the status. I mean the use case like: I have 2 ports, the 2 ports are from 2 VMs, and they locates different compute nodes. Then I create a new fwg with its "child" resources,  and I add these ports into fwg. So the server will fanout the rpc to the compute nodes side,  different l2 agent in different node process its serviced port,06:38
bzhao__then update the fwg status through rpc to server.06:38
*** longkb1 has joined #openstack-fwaas06:38
bzhao__annp:  the rpc call is still set_fwg_status, and I saw the server side code is just update the status... So I'm not sure how we decide the fwg status in this case.06:40
annpbzhao__, you're right. Maybe It is a bug.06:43
annpbzhao_, In this case we have to check status of fwg before update status. if fwg status == ERROR, then don't set fwg status06:45
bzhao__annp: No matter,  yeah, we need the check.06:45
bzhao__annp:  So the status means the finnal result of all associated resources. Right?06:46
annpbzhao__, yes. It should be as you said.06:47
annpso it doesn't make user confused.06:48
bzhao__annp:  OK, it make sense to me. Thank you. Sorry for interrupt. :)06:48
annpbzhao__, No worries, you're welcome. Can you file a bug for that?06:50
bzhao__annp: OK, I will do that. :)06:50
annpbzhao__, +1 :)06:50
openstackgerritOpenStack Proposal Bot proposed openstack/neutron-fwaas-dashboard master: Imported Translations from Zanata  https://review.openstack.org/56778407:05
*** lnicolas has quit IRC07:09
*** lnicolas has joined #openstack-fwaas07:13
*** hoangcx has joined #openstack-fwaas07:30
*** yamamoto_ has joined #openstack-fwaas07:36
*** yamamoto has quit IRC07:39
*** openstack has joined #openstack-fwaas09:26
*** ChanServ sets mode: +o openstack09:26
*** yamamoto has joined #openstack-fwaas09:40
*** hoangcx has quit IRC10:12
*** longkb1 has quit IRC10:33
*** longkb has quit IRC10:33
*** yamamoto has quit IRC11:12
*** yamamoto has joined #openstack-fwaas11:20
*** yamamoto has quit IRC11:25
*** njohnston is now known as njohnston|ooo11:27
*** yamamoto has joined #openstack-fwaas11:28
*** yamamoto has quit IRC11:45
*** yamamoto has joined #openstack-fwaas11:55
*** annp has quit IRC12:01
*** yamamoto has quit IRC12:12
*** yamamoto has joined #openstack-fwaas12:13
*** yamamoto has quit IRC12:22
*** yamamoto has joined #openstack-fwaas12:23
*** yamamoto has quit IRC12:27
*** yamamoto has joined #openstack-fwaas12:46
*** yamamoto has quit IRC12:47
*** yamamoto has joined #openstack-fwaas12:47
*** yamamoto_ has joined #openstack-fwaas12:53
*** yamamoto has quit IRC12:57
*** openstackstatus has joined #openstack-fwaas13:11
*** ChanServ sets mode: +v openstackstatus13:11
-openstackstatus- NOTICE: Due to a Zuul outage, patches uploaded to Gerrit between 09:00UTC and 12:50UTC, were not properly added to Zuul. Please recheck any patches during this window and apologies for the inconvenience.13:14
*** yamamoto_ has quit IRC13:21
*** hongbin has joined #openstack-fwaas13:49
*** mlavalle has joined #openstack-fwaas13:55
mlavalleDear FWaaS team: could a member of the FWaaS team give an opinion on this RFE: https://bugs.launchpad.net/neutron/+bug/1664814?13:56
openstackLaunchpad bug 1664814 in neutron "RBAC for Firewall Policies" [Wishlist,New]13:56
*** njohnston|ooo has quit IRC14:03
*** yamamoto has joined #openstack-fwaas14:21
*** yamamoto has quit IRC14:27
*** yamamoto has joined #openstack-fwaas15:24
*** yamamoto has quit IRC15:32
*** yamamoto has joined #openstack-fwaas16:28
*** yamamoto has quit IRC16:34
*** openstackstatus has quit IRC17:00
*** openstack has joined #openstack-fwaas17:02
*** ChanServ sets mode: +o openstack17:02
*** yamamoto has joined #openstack-fwaas17:30
*** yamamoto has quit IRC17:36
*** yamamoto has joined #openstack-fwaas18:32
*** yamamoto has quit IRC18:36
*** yamamoto has joined #openstack-fwaas19:33
*** yamamoto has quit IRC19:38
*** yamamoto has joined #openstack-fwaas20:34
*** mlavalle has left #openstack-fwaas20:36
*** yamamoto has quit IRC20:39
*** openstackgerrit has joined #openstack-fwaas21:29
openstackgerritGerman Eichberger proposed openstack/neutron-fwaas master: Adds remote firewall group to plugin  https://review.openstack.org/52120721:29
*** yamamoto has joined #openstack-fwaas21:35
*** yamamoto has quit IRC21:41
*** hongbin has quit IRC22:49
*** yamamoto has joined #openstack-fwaas23:01
*** yamamoto has quit IRC23:26

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