| *** longkb has joined #openstack-fwaas | 00:37 | |
| *** SridarK has joined #openstack-fwaas | 00:41 | |
| *** yushiro4 has joined #openstack-fwaas | 02:32 | |
| yushiro4 | At last I joined due to some trouble.. | 02:33 |
|---|---|---|
| yushiro4 | Hi SridarK. Are you online? | 02:33 |
| SridarK | yushiro4: hi | 02:33 |
| *** yushiro4 is now known as yushiro | 02:34 | |
| SridarK | yushiro4: are u still having trouble in joining ? | 02:34 |
| yushiro | Identifying has cleared but connection to freenode are still in trouble :( I don't know why... | 02:35 |
| yushiro | So, thanks for your reviewing SridarK and xgerman_ for logging patches. | 02:35 |
| yushiro | I read your comment and now double-checking in devstack environment. | 02:35 |
| SridarK | yushiro: sigh yes i joined easily today but few days ago had issues | 02:36 |
| SridarK | yushiro: no worries - i did not +A | 02:36 |
| yushiro | SridarK, Yeah, you are waiting for my final judgement :) Thanks. | 02:36 |
| SridarK | yushiro: i want to be sure we dont land up with some issue in case we are not able to get in all the patches | 02:36 |
| SridarK | yushiro: yes - just being a bit careful - so we dont have to do reverts etc. I see that first 2 patches in the list: | 02:37 |
| SridarK | #link https://review.openstack.org/#/c/532792 | 02:37 |
| SridarK | #link https://review.openstack.org/#/c/530715 | 02:38 |
| SridarK | still need some work | 02:38 |
| yushiro | Ah, yes. Thanks for pointing. | 02:39 |
| yushiro | These patches depend on validator patch in neutron-side. However, these patches still got -1 from zuul even if validator patch has been merged.. | 02:39 |
| SridarK | yushiro: ah yes that confused me since all 3 neutron patches are in | 02:40 |
| yushiro | 3 patches don't refer validator patch in neutron-side. So, their tests has passed. | 02:41 |
| SridarK | okay | 02:42 |
| yushiro | Other 5 patches ( in other words, related logging validator patch) refers Validator in neutron side... | 02:42 |
| SridarK | ok | 02:42 |
| yushiro | SridarK, I think that to solve these error, we need to wait cutting branch in neutron. | 02:42 |
| SridarK | yushiro: hmm ok maybe u shd discuss with mlavalle ? | 02:43 |
| SridarK | so from our side we will not +A | 02:44 |
| SridarK | either xgerman_ or I will wait for u to +A | 02:44 |
| yushiro | SridarK, Maybe yes until new neutron RC-1 would be cut except 3 patches. | 02:45 |
| SridarK | yushiro: ok | 02:46 |
| yushiro | Therefore, I'll ask mlavalle some question about schedule. | 02:46 |
| SridarK | yushiro: ok | 02:46 |
| yushiro | BTW, | 02:46 |
| SridarK | yushiro: also will try to sync with u around this time or a bit earlier tomorrow as well - in case something needs my attention | 02:47 |
| yushiro | https://review.openstack.org/#/c/580552/ | 02:47 |
| yushiro | SridarK, Thanks for your kindness :) | 02:47 |
| SridarK | yushiro: no issues at all | 02:47 |
| SridarK | yushiro: ah ok u removed the -1 workflow | 02:47 |
| SridarK | did u get any feedback ? | 02:47 |
| yushiro | SridarK, Yes. Let me sync up current status of this L3HA issue. | 02:48 |
| SridarK | yushiro: ok | 02:48 |
| yushiro | I found that the issue was we cannot insert iptables rules into 'active' router's namespace. Even if we specified router-port for L3-HA, the rule has been set into 'standby' router's one. | 02:49 |
| SridarK | That issue is a bit odd as to how it goes to standby router | 02:49 |
| yushiro | SridarK, Yes. Maybe we need to verify the router's status by calling is_active() or some method in neutron.. | 02:50 |
| yushiro | Ah, or we can set firewall rules into both 'active' and 'standby'. | 02:51 |
| SridarK | yushiro: hmm ok - u think we are setting it on to standy | 02:51 |
| SridarK | yushiro: maybe setting in both is needed - so it is there when a switchover happens | 02:51 |
| SridarK | i am a bit unsure on the L3HA model tood | 02:52 |
| SridarK | *too | 02:52 |
| yushiro | BTW, I've checked switchover. When switchover has occurred, SSH was kept on connecting. | 02:52 |
| yushiro | (But there is no firewall rules) | 02:52 |
| SridarK | yushiro: oh | 02:53 |
| SridarK | should we not hit the default deny if the fwg is active ? | 02:54 |
| SridarK | oh u mean there is no fwg at all | 02:54 |
| yushiro | SridarK, sorry. Some word made you confuse.. My environment was as follows. (standby router with default fwg rule) and (active router with no default rule) | 02:56 |
| SridarK | ok | 02:56 |
| yushiro | vm0 --(SSH)--> vm1 : When switchover, this connection is kept because default fwaas rules(from vm0) are allow | 02:57 |
| yushiro | vm0 <----(ssh)--- vm1 : When switchover, this connection was reset beacuse default fwaas rules(from vm1) are deny. | 02:57 |
| SridarK | vm0 and vm1 are they on different networks so there is a path thru the router ? | 02:58 |
| SridarK | i think w.r.t default fwg ( | 02:58 |
| yushiro | Yes, different subnet: vm0 ---( net0 ) ---- (router0) ---- (net1) ---- vm1 | 02:58 |
| SridarK | ok | 02:58 |
| SridarK | and we really want to check the effect of the fwd on the router port | 02:59 |
| SridarK | *fwg on the router port | 02:59 |
| yushiro | vm0 ---( net0 ) ----(fwg)(router0, standby) ---- (net1) ---- vm1 | 03:00 |
| yushiro | ^^^^ my environment | 03:00 |
| SridarK | ok | 03:00 |
| yushiro | vm0 ---( net0 ) ----(router0, active) ---- (net1) ---- vm1 | 03:00 |
| yushiro | ^^^^ switchover environment | 03:00 |
| SridarK | now there is no fwg | 03:01 |
| yushiro | SridarK, Yes, you're right. We need to test fwg on port with Active router and switchover don't you? | 03:01 |
| SridarK | i think it all goes thru because there is no fwg | 03:01 |
| SridarK | so at L3 port level there is no filtering at all | 03:01 |
| yushiro | SridarK, Ah sorry. I draw wrong picture. | 03:02 |
| yushiro | vm0 ---( net0 ) ----(router0, active) ---- (net1) ---- vm1 | 03:02 |
| SridarK | yushiro: yes i think we should test fwg on Active router and then do switchover - agree | 03:02 |
| yushiro | ^^^ Initial status. | 03:02 |
| SridarK | ok | 03:02 |
| yushiro | vm0 ---( net0 ) ----(fwg)(router0, standby->active) ---- (net1) ---- vm1 | 03:03 |
| yushiro | ^^^ switchover (after) | 03:03 |
| SridarK | hmm ok so the fwg was never applied on the active (before swover) | 03:04 |
| yushiro | SridarK, Yes!! that is current behavior.. | 03:04 |
| SridarK | because it got appled on the standby ? | 03:04 |
| yushiro | Yes | 03:04 |
| SridarK | so initially all traffic is passed because no fwg | 03:04 |
| yushiro | SridarK, Yes, that's correct. No guard. | 03:05 |
| SridarK | but after swover - the fwg is on the old standby and new active | 03:05 |
| yushiro | Yes. That was my result for current implemantation. | 03:05 |
| SridarK | yushiro: ok thx for the detailed explanation | 03:06 |
| SridarK | yushiro: i am not sure if we need to apply on both active and standby | 03:06 |
| yushiro | SridarK, NP, haha I need more practice to explain to you more clearly. | 03:06 |
| SridarK | yushiro: oh no worries at all - u were very detailed - sorry i got confused :-) | 03:07 |
| yushiro | SridarK, Yes, I'm considering it too. I'm not sure this issue caused by fwaas side or L3-HA side | 03:07 |
| SridarK | yushiro: ok it seems this bug is a bit more tricky - which was my concern | 03:07 |
| SridarK | yushiro: yes - depends on how they sync features | 03:07 |
| SridarK | if we are responsible to do it | 03:08 |
| yushiro | SridarK, +10 Yeeeess.. | 03:08 |
| *** bbbbzhao_ has quit IRC | 03:08 | |
| SridarK | yushiro: ok - lets see if we can get some info or we may have to address this in Stein if it gets complex | 03:09 |
| yushiro | SridarK, Sure. Next, I'd like to test for sync behavior between active - standby router. E.g. If we applied fwg rule into only active router and switchover, what would happen. | 03:10 |
| SridarK | ah yes - we will know if the fwg gets synced over to standby | 03:11 |
| yushiro | And, we can ask L3-Ha guys for more detail impl as well :) | 03:11 |
| SridarK | that should tell us if fwaas is responsible to manage the apply of fwg on active and standbys | 03:12 |
| SridarK | yushiro: +1 | 03:12 |
| SridarK | ok we can sync up tomorrow - or shoot me an email if u have found some thing and i will look too | 03:12 |
| yushiro | SridarK, Yes. We definitely should clarify about that. | 03:12 |
| SridarK | yushiro: ok agreed | 03:12 |
| yushiro | Ah, SridarK , regarding fwg logging feature, what do you think to handle 3 patches which passed zuul job? I tested and these patches are OK. | 03:13 |
| SridarK | yushiro: which ones ? The one with +2 ? | 03:14 |
| *** jhesketh_ is now known as jhesketh | 03:14 | |
| yushiro | SridarK, yes, the patches which +2 from me. | 03:14 |
| SridarK | https://review.openstack.org/#/c/578718 | 03:15 |
| SridarK | ? | 03:15 |
| SridarK | and the other 2 | 03:15 |
| yushiro | Yes, this one and below 2 patches. | 03:15 |
| SridarK | https://review.openstack.org/#/c/576338 | 03:16 |
| yushiro | Yes, and https://review.openstack.org/#/c/574128/25 | 03:16 |
| yushiro | However, other 5 patches are got an issue. | 03:17 |
| SridarK | ah ok i have +2 on all these 3 | 03:17 |
| SridarK | if u think we are ok - pls +A | 03:17 |
| SridarK | but if for some reason the other patches are not able to get in | 03:17 |
| SridarK | what will happen ? | 03:18 |
| SridarK | will it cause an issue ? | 03:18 |
| SridarK | and i assume there is no dependency | 03:18 |
| yushiro | SridarK, yes, there is no dependency. It is just applied some parts and no effect I think. | 03:19 |
| SridarK | yushiro: ok then if it is safe - i think it is ok to +A | 03:19 |
| SridarK | If for some reason there is an issue and we are not able to merge some patches by the deadline | 03:20 |
| SridarK | it will be ok if these patches are in ? | 03:20 |
| yushiro | SridarK, Yes. Even if the only 3 patches are merged, there is 1 effect to add 'neutron-l3-agent-dropped/accepted' on router namespace but no issue. | 03:24 |
| SridarK | yushiro: ok | 03:24 |
| SridarK | then i think it is ok to +A | 03:24 |
| yushiro | SridarK, OK, so I'll test it again and ask Miguel about cutting Rc-1 in neutron. | 03:24 |
| SridarK | yushiro: perfect | 03:25 |
| yushiro | After that, I'll put +A . | 03:25 |
| SridarK | sounds good | 03:25 |
| yushiro | If there is no issue :p | 03:25 |
| yushiro | And will sync up with you. | 03:25 |
| yushiro | If you are not on IRC, will send e-mail. | 03:25 |
| SridarK | yushiro: ok sounds good - i will step away now - but will check back here or just send an email | 03:26 |
| SridarK | yushiro: many thx | 03:26 |
| yushiro | SridarK, You too! :) | 03:26 |
| SridarK | ok talk later | 03:27 |
| yushiro | ya | 03:27 |
| *** yushiro is now known as yushiro_lunch | 03:30 | |
| openstackgerrit | Akihiro Motoki proposed openstack/neutron-fwaas-dashboard master: Unblock Django 2.0 in requirements.txt https://review.openstack.org/589332 | 03:47 |
| *** annp has joined #openstack-fwaas | 04:19 | |
| *** yushiro_lunch is now known as yushiro | 05:32 | |
| *** velizarx has joined #openstack-fwaas | 06:56 | |
| *** yushiro has quit IRC | 07:00 | |
| *** yushiro has joined #openstack-fwaas | 07:00 | |
| openstackgerrit | Merged openstack/neutron-fwaas-dashboard master: Unblock Django 2.0 in requirements.txt https://review.openstack.org/589332 | 07:04 |
| *** velizarx has quit IRC | 07:13 | |
| *** reedip has joined #openstack-fwaas | 07:20 | |
| *** velizarx has joined #openstack-fwaas | 07:24 | |
| *** yamamoto has joined #openstack-fwaas | 08:00 | |
| *** yamamoto has quit IRC | 08:07 | |
| *** yushiro has quit IRC | 08:18 | |
| openstackgerrit | Yushiro FURUKAWA proposed openstack/neutron-fwaas master: Add dependency for generating reno https://review.openstack.org/589397 | 08:29 |
| *** yushiro has joined #openstack-fwaas | 08:40 | |
| *** yamamoto has joined #openstack-fwaas | 08:46 | |
| *** velizarx has quit IRC | 09:03 | |
| *** velizarx has joined #openstack-fwaas | 09:07 | |
| *** yamamoto has quit IRC | 09:11 | |
| openstackgerrit | Kim Bao Long proposed openstack/neutron-fwaas master: Add log validator for FWaaS v2 logging https://review.openstack.org/532792 | 09:29 |
| amotoki | yushiro: hi, do we need reno dependency in tox venv now? | 09:31 |
| yushiro | amotoki, Ah, sorry. I forgot to put workflow -1. It's ok to land to next cycle. | 09:31 |
| yushiro | I wanted to generate reno. | 09:32 |
| amotoki | yushiro: if so, you can use 'docs' tox env | 09:32 |
| amotoki | yushiro: or you can add 'releasenotes' tox env rather than adding doc/requirements.txt to 'venv' env | 09:33 |
| amotoki | this is what we do in neutorn | 09:34 |
| amotoki | *neutron | 09:34 |
| yushiro | amotoki, I see. So, I'll abandon this patch and follow neutron's way. Thank you. | 09:35 |
| yushiro | I used 'tox -e venv -- reno new hogehoge' for a long time :p. | 09:35 |
| amotoki | yushiro: ah, i see. I use '.tox/releasenotes/bin/reno new foo' instead | 09:37 |
| yushiro | amotoki, BTW, why neutron defined 'reno' in docs/requirements.txt and test-requirements.txt ? | 09:38 |
| amotoki | yushiro: looking at the commit history, boden re-added reno to test-reqs.txt. this allows us to follow reno doc instruction [1] | 09:43 |
| amotoki | [1] https://docs.openstack.org/reno/latest/user/usage.html | 09:43 |
| amotoki | but I am not sure it is the right direction. perhaps we should update reno docs. | 09:44 |
| amotoki | or your solution might be more straight forward | 09:44 |
| *** reedip has quit IRC | 09:45 | |
| yushiro | amotoki, Ah, I just referred ironic one and [1]'s page. 'tox -e venv -- reno new hoge' | 09:45 |
| yushiro | Anyway, I just wanted to generate reno :) Thanks for your kindness. | 09:46 |
| amotoki | yushiro: you're welcom | 09:46 |
| amotoki | *e | 09:46 |
| yushiro | amotoki, Ah!! I wanted to ask you cutting branch in neutron. | 09:46 |
| amotoki | yushiro: go ahead | 09:47 |
| yushiro | Currently, we're implementing fwaas logging feature. Some codes are merged into neutron side. In addition, some codes refers neutron patches from fwaas side. | 09:48 |
| yushiro | Basically, fwaas installs neutron package instead of pulling the master source code. So, fwaas code cannot refer the master code of neutron. | 09:49 |
| amotoki | yushiro: do such patches depends on neutron features after RC3? | 09:50 |
| amotoki | s/RC3/Rocky-3/ | 09:50 |
| amotoki | there are several ways to address the situation | 09:51 |
| amotoki | one is to consume neutron R-3 package if it is okay. | 09:51 |
| amotoki | another way is to specify required-projects in .zuul.yaml to consume the last neutron (master or stable branch head) | 09:52 |
| yushiro | amotoki, yes, after Rocky-3. Merged last weekend... | 09:52 |
| amotoki | if so, it sounds reasonable to specify required-projects in .zuul.yaml | 09:54 |
| amotoki | it pulls neutron master | 09:54 |
| amotoki | yushiro: for example, https://review.openstack.org/#/c/530715/ ? | 09:55 |
| amotoki | i might be wrong | 09:55 |
| yushiro | amotoki, yes, correct. haha you read my mind. | 09:55 |
| amotoki | you are talking about l-c job? | 09:56 |
| yushiro | amotoki, ahhh yes.. | 09:57 |
| amotoki | in this case, there is no release which satisfies your need, so required-projects is the only solution to me. | 09:58 |
| yushiro | Sorry, makes you confuse. l-c job failed.. | 09:58 |
| hoangcx | amotoki: yushiro I think We need neutron released with RC-1 (by this week?) and then remaining depended patch in fwaas can be land during RC-2 | 09:59 |
| amotoki | hoangcx: RC2 is limited to bug fixes strictly, so I don't think it works for you | 09:59 |
| hoangcx | amotoki: Is it possible to land more patches in RC-2 for fwaas regarding to FFE? | 09:59 |
| amotoki | yushiro: hoangcx: neutron-fwaas-dashboard .zuul.yaml does similar thing http://git.openstack.org/cgit/openstack/neutron-fwaas-dashboard/tree/.zuul.yaml#n4 | 10:00 |
| amotoki | it always consumes the latest horizon | 10:00 |
| amotoki | I believe this is what you would like to do. | 10:00 |
| yushiro | amotoki, Aha. That's good. Yes, that is what I'd like to do :) | 10:01 |
| hoangcx | amotoki: Yes. I understand this solution :) Will try to invoke with your suggestion | 10:01 |
| amotoki | neutron and fwaas are released together, so actually there is no need to care lower-constraints (lower bound of neutron) | 10:01 |
| yushiro | hoangcx, Oh, you will ?? :p | 10:01 |
| hoangcx | yushiro: yeah :p | 10:01 |
| yushiro | hoangcx, Thanks very very much. | 10:02 |
| amotoki | FYI: we will cut RC1 Thurday | 10:02 |
| amotoki | perhaps I will prepare a release patch around Thurday afternoon in Japan TZ and will wait some updates around Thurday in PCT TZ | 10:03 |
| yushiro | amotoki, Yes... Tomorrow's morning, we'll tell Miguel about our progress and judge land or not.. | 10:03 |
| amotoki | yushiro: makes sense :) | 10:04 |
| yushiro | ganbaru | 10:09 |
| *** yushiro is now known as yushiro_dinner | 10:09 | |
| openstackgerrit | Cao Xuan Hoang proposed openstack/neutron-fwaas master: Add neutron to required-projects of l-c job https://review.openstack.org/589421 | 10:18 |
| openstackgerrit | Cao Xuan Hoang proposed openstack/neutron-fwaas master: Add neutron to required-projects of l-c job https://review.openstack.org/589421 | 10:20 |
| openstackgerrit | Cao Xuan Hoang proposed openstack/neutron-fwaas master: Add log validator for FWaaS v2 logging https://review.openstack.org/532792 | 10:20 |
| * xgerman_ reading scrollback | 10:38 | |
| amotoki | hoangcx: could you explain more direct reason on your l-c change? | 10:40 |
| *** yushiro_dinner has quit IRC | 10:40 | |
| hoangcx | amotoki: Sure. I will do it right now | 10:41 |
| openstackgerrit | Cao Xuan Hoang proposed openstack/neutron-fwaas master: Add neutron to required-projects of l-c job https://review.openstack.org/589421 | 10:45 |
| *** velizarx has quit IRC | 10:46 | |
| hoangcx | amotoki: ^^ | 10:47 |
| hoangcx | amotoki: Thanks for your time and your suggestion :) | 10:47 |
| hoangcx | amotoki: http://logs.openstack.org/92/532792/25/check/openstack-tox-lower-constraints/ea2d3bb/ the job passed :) | 10:48 |
| *** velizarx has joined #openstack-fwaas | 10:59 | |
| hoangcx | amotoki: Is it possible do the same for build-openstack-sphinx-docs job? | 11:00 |
| hoangcx | amotoki: the job failed caused by the latest head commit also: http://logs.openstack.org/92/532792/25/check/build-openstack-sphinx-docs/47d3575/job-output.txt.gz#_2018-08-07_10_42_02_520810 | 11:00 |
| *** yushiro has joined #openstack-fwaas | 11:06 | |
| yushiro | hoangcx, Thanks for your patch. | 11:08 |
| yushiro | I'll read IRC log. | 11:08 |
| hoangcx | yushiro: I have checked that it is the same with build-openstack-sphinx-docs job | 11:14 |
| yushiro | hoangcx, Aha. So, we need to add 'require-project' for build-openstack-sphinx-docs as well, right ? | 11:16 |
| hoangcx | yushiro: I'm waiting amotoki feedback | 11:16 |
| yushiro | hoangcx, OK, thanks. Ah, did you tell annp about that ? Maybe he will rebase his patches. | 11:18 |
| openstackgerrit | Cao Xuan Hoang proposed openstack/neutron-fwaas master: Add neutron to required-projects of l-c job https://review.openstack.org/589421 | 11:19 |
| openstackgerrit | Cao Xuan Hoang proposed openstack/neutron-fwaas master: Add neutron to required-projects of l-c job https://review.openstack.org/589421 | 11:24 |
| openstackgerrit | Cao Xuan Hoang proposed openstack/neutron-fwaas master: Add log validator for FWaaS v2 logging https://review.openstack.org/532792 | 11:24 |
| hoangcx | yushiro: yes. I talked to him | 11:24 |
| hoangcx | yushiro: I update the l-c patch to see if build-openstack-sphinx-docs job passed | 11:25 |
| *** yushiro has quit IRC | 12:29 | |
| *** velizarx has quit IRC | 12:34 | |
| *** velizarx has joined #openstack-fwaas | 12:35 | |
| *** yushiro has joined #openstack-fwaas | 13:10 | |
| yushiro | ping hoangcx | 13:11 |
| *** longkb has quit IRC | 13:13 | |
| *** velizarx has quit IRC | 13:16 | |
| *** velizarx has joined #openstack-fwaas | 13:16 | |
| yushiro | ping SridarK xgerman_ | 13:22 |
| amotoki | yushiro: do you know why sphinx job is related in https://review.openstack.org/#/c/589421/ ? | 13:33 |
| openstackgerrit | Yushiro FURUKAWA proposed openstack/neutron-fwaas master: FWaaS v2: L3 logging agent extension https://review.openstack.org/576338 | 13:34 |
| openstackgerrit | Yushiro FURUKAWA proposed openstack/neutron-fwaas master: Introduce accepted/dropped/rejected chains for future processing https://review.openstack.org/574128 | 13:34 |
| openstackgerrit | Yushiro FURUKAWA proposed openstack/neutron-fwaas master: Add notification callback events for FWaaS v2 https://review.openstack.org/578718 | 13:34 |
| openstackgerrit | Yushiro FURUKAWA proposed openstack/neutron-fwaas master: Add neutron as required-projects https://review.openstack.org/589421 | 13:34 |
| openstackgerrit | Yushiro FURUKAWA proposed openstack/neutron-fwaas master: Add log validator for FWaaS v2 logging https://review.openstack.org/532792 | 13:34 |
| yushiro | amotoki, hi | 13:36 |
| amotoki | yushiro: hi | 13:36 |
| yushiro | amotoki, AFAIK, regarding sphinx job, this job try to make some relation for object/class. So, if we referred some module in master branch of neutron, it failed. | 13:38 |
| amotoki | yushiro: is this due to the module reference? | 13:40 |
| yushiro | amotoki, I think so. Coudld you take a look http://logs.openstack.org/92/532792/26/check/build-openstack-sphinx-docs/4ca2757/job-output.txt.gz#_2018-08-07_11_33_43_723800 | 13:42 |
| yushiro | fwg_validate.py tried to call @validators.ResourceValidateRequest.register(log_const.FIREWALL_GROUP) and @validators is at neutron. | 13:44 |
| amotoki | yushiro: thanks for the pointer. At a quick look, there is no surprise if you refer to something from the neutron master in the module reference. | 13:44 |
| yushiro | amotoki, Thanks. | 13:46 |
| yushiro | Referring master branch of neutron, all patches will work fine. | 13:47 |
| yushiro | Thank you so much. It is not over, I'll relax, carefully review and merge existing patches :p | 13:48 |
| amotoki | thanks. it makes sense. it's clear to me now | 13:49 |
| yushiro | :) | 14:33 |
| *** longkb has joined #openstack-fwaas | 14:35 | |
| *** hongbin has joined #openstack-fwaas | 14:38 | |
| *** longkb has quit IRC | 15:05 | |
| openstackgerrit | Kim Bao Long proposed openstack/neutron-fwaas master: Adding resources callback handler for FWaaS v2 logging https://review.openstack.org/580976 | 15:28 |
| *** yushiro has quit IRC | 16:13 | |
| *** velizarx has quit IRC | 16:47 | |
| *** SridarK has quit IRC | 17:05 | |
| *** Swami has joined #openstack-fwaas | 18:12 | |
| *** openstackgerrit has quit IRC | 18:49 | |
| -openstackstatus- NOTICE: Due to a bug, Zuul has been unable to report on cherry-picked changes over the last 24 hours. This has now been fixed; if you encounter a cherry-picked change missing its results (or was unable to merge), please recheck now. | 20:42 | |
| *** openstackgerrit has joined #openstack-fwaas | 22:15 | |
| openstackgerrit | Merged openstack/neutron-fwaas master: FWaaS v2: L3 logging agent extension https://review.openstack.org/576338 | 22:15 |
| openstackgerrit | Merged openstack/neutron-fwaas master: Introduce accepted/dropped/rejected chains for future processing https://review.openstack.org/574128 | 22:15 |
| *** hongbin has quit IRC | 22:39 | |
| *** Swami has quit IRC | 23:46 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!