Thursday, 2018-05-17

*** yamamoto has joined #openstack-fwaas00:12
*** yamamoto has quit IRC00:16
*** longkb has joined #openstack-fwaas00:24
*** yamamoto has joined #openstack-fwaas00:33
*** yamamoto has quit IRC00:37
*** annp has quit IRC00:53
*** longkb1 has quit IRC00:53
*** annp has joined #openstack-fwaas00:53
*** yamamoto has joined #openstack-fwaas00:54
*** longkb1 has joined #openstack-fwaas00:55
*** yamamoto has quit IRC01:00
*** yamamoto has joined #openstack-fwaas01:16
*** yamamoto has quit IRC01:20
*** yamamoto has joined #openstack-fwaas01:38
*** yamamoto has quit IRC01:44
*** yamamoto has joined #openstack-fwaas02:00
*** yamamoto has quit IRC02:05
*** yamamoto has joined #openstack-fwaas02:21
*** yamamoto has quit IRC02:25
*** yamamoto has joined #openstack-fwaas02:41
*** yamamoto has quit IRC02:48
*** yamamoto has joined #openstack-fwaas03:04
*** yamamoto has quit IRC03:08
*** yamamoto has joined #openstack-fwaas03:25
*** yamamoto has quit IRC03:29
*** yamamoto has joined #openstack-fwaas03:47
*** yamamoto has quit IRC03:53
*** yamamoto has joined #openstack-fwaas04:08
openstackgerritGerman Eichberger proposed openstack/neutron-fwaas master: [WIP] Adds remote firewall group to plugin  https://review.openstack.org/52120704:13
*** yamamoto has quit IRC04:13
*** yamamoto has joined #openstack-fwaas04:14
*** yamamoto has quit IRC05:24
*** yamamoto has joined #openstack-fwaas05:25
*** yamamoto_ has joined #openstack-fwaas05:28
*** yamamoto has quit IRC05:32
*** AlexeyAbashkin has joined #openstack-fwaas07:47
*** yamamoto_ has quit IRC08:10
*** yamamoto has joined #openstack-fwaas08:10
*** yamamoto_ has joined #openstack-fwaas08:41
*** yamamoto has quit IRC08:45
annpls09:30
*** AlexeyAbashkin has quit IRC09:53
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: [WIP] [log] Logging driver based iptables for FWaaS  https://review.openstack.org/55373810:05
*** annp has quit IRC10:15
*** AlexeyAbashkin has joined #openstack-fwaas10:54
*** yamamoto_ has quit IRC11:30
*** longkb has quit IRC11:31
*** yamamoto has joined #openstack-fwaas11:47
*** yamamoto has quit IRC12:52
*** yamamoto has joined #openstack-fwaas13:13
*** yamamoto has quit IRC13:18
*** yamamoto has joined #openstack-fwaas13:23
*** wkite has joined #openstack-fwaas13:50
*** annp has joined #openstack-fwaas13:58
doudeHi13:59
*** SridarK has joined #openstack-fwaas13:59
SridarKHi FWaaS folks13:59
annphi14:00
SridarK#startmeeting fwaas14:00
openstackMeeting started Thu May 17 14:00:23 2018 UTC and is due to finish in 60 minutes.  The chair is SridarK. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: fwaas)"14:00
openstackThe meeting name has been set to 'fwaas'14:00
*** mlavalle has joined #openstack-fwaas14:00
SridarK#chair xgerman_14:01
openstackCurrent chairs: SridarK xgerman_14:01
mlavalleo/14:01
SridarKI see yushiro cannot make today's mtg14:01
SridarKI think today was his turn - i can chair14:02
SridarKWe are getting close to summit14:02
xgerman_o/14:03
xgerman_SridarK: sounds good14:03
SridarKLook fwd to meeting folks that are travelling to summit next week14:03
xgerman_+114:03
annp+114:04
SridarKxgerman_: any announcements u want to bring up14:05
xgerman_quiet week14:05
SridarKok lets move on14:05
SridarK#topic Rocky Pluggable backend driver14:06
*** openstack changes topic to "Rocky Pluggable backend driver (Meeting topic: fwaas)"14:06
SridarKdoude: pls go ahead14:06
doudeok14:06
doudeso I had two +1 reviews14:06
annpdoube, thanks for your great work on that.14:06
doudeone from annp , thanksq14:06
njohnstono/14:07
annpdoube, you're welcome :)14:07
SridarKannp: were u able to verify the multinode ?14:07
doudeand one from NSX developer after I explain how they have to use it14:07
annpSridarK, yes. I already tested doube's patch with multinode.14:07
doudeand I just realized a +2 from Yushiro14:08
SridarKannp thx14:08
SridarKdoude: yes14:08
annpSridarK, It worked fined in my local environment.14:08
doudewith that comment14:08
doude'I tested devstack with AIO and multi nodes. There is no issue at present. Thanks for your great work, doube!!'14:08
SridarKdoude: let me run thru it once today and i can +A14:08
annpSridarK, +114:08
SridarKdoude: yes i just saw his coment too14:08
SridarKdoude: give me  a couple of hours  -14:09
SridarKdoude: BTW are u at the summit ?14:09
doudecool14:10
doudethank SridarK14:10
doudeno I could not (that was the first I missed since 5 years now)14:10
SridarKdoude: ok :-( yes u are usually there14:11
SridarKlets move on14:11
SridarK#topic Remote FWG14:11
*** openstack changes topic to "Remote FWG (Meeting topic: fwaas)"14:11
SridarKxgerman_: pls go ahead14:11
doudeyes but baby is coming :)14:11
SridarKoh doude congrats14:11
mlavalledoude: congrats!14:12
doudethanks14:12
mlavallefirst one?14:12
annpdoude, congrats!14:12
doudeno second14:12
xgerman_sqlalchemy has been the bane of my existsnce the last few weeks — I even got someone else to look at it with no resolution14:12
xgerman_SridarK: +114:12
SridarKdoude: cool keep us posted14:12
xgerman_+114:12
SridarKxgerman_: ok14:12
doudeok thanks guys14:12
annpxgerman_, I think revise id not matching with down_revision14:13
xgerman_ah, that could be14:13
xgerman_also saw your comment — not sure if we want to cascade deletion of the ruke/fwg14:13
xgerman_I rather have a user delete the rule/fwg before they can delete the rest14:14
SridarKxgerman_: let me also look on the delete14:16
SridarKwe can talk more during the next week as well14:16
annpSridarK, +114:17
xgerman_+114:17
annpxgerman_, let's discuss at the summit.14:17
SridarKok14:17
SridarK#topic FWaaS Logging Spec14:17
*** openstack changes topic to "FWaaS Logging Spec (Meeting topic: fwaas)"14:17
annpHi SridarK,14:18
SridarKI think we are almost ready to get this in14:18
SridarKannp: pls go ahead14:18
annpCurrently, The spec is waiting +A from Akihiro or Miguel14:18
SridarKmlavalle: if u can also take a look to see if u are good with it14:18
mlavalleannp: I;ll review it today14:18
SridarKmlavalle: thx14:18
mlavallesorry for the delay14:18
amotokiannp: sorry for late.14:19
annpmlavalle, thanks.14:19
mlavalleI've been reviewing a lot of specs over the past few days14:19
SridarKamotoki: thx14:19
annpamotoki, no problem. :)14:19
xgerman_SridarK: +114:19
SridarKmlavalle: yes indeed14:19
SridarKamotoki: i think ur last set of comments were also addressed14:19
annpmlavalle, I know you were busy, Everyone want to reach you :)14:19
*** chandanc has joined #openstack-fwaas14:20
amotokiSridarK: yeah, at a glance, it has been addressed.14:20
amotokii just would like to look through it.14:20
SridarKamotoki: +114:20
annpamotoki +114:20
SridarKok lets move on14:21
SridarK#topic Rocky Address Group spec14:21
*** openstack changes topic to "Rocky Address Group spec (Meeting topic: fwaas)"14:21
SridarKwkite: pls go ahead14:21
wkiteok14:21
SridarKIf we can get a few more eyes on this for review14:22
SridarK#link https://review.openstack.org/55713714:22
mlavalleis this similar to what I proposed last week about address groups?14:23
SridarKmlavalle: i think we have good alignment - i just want to look thru for any specific differences14:23
SridarKI also see ZhaoBo has reached out to wkite14:23
mlavalleI will take a look at this spec14:23
mlavalleif we are making progress in this front, it is just great14:24
SridarKmlavalle: thx - this was in the orig spec and we chose not to cover it in the initial implementation14:24
SridarKwkite: has picked it up with a few changes14:24
SridarKi think we can converge on this quickly14:25
wkitethis my github https://github.com/wkite/neutron_fwaas14:25
mlavallecool!14:25
SridarKmlavalle: we can discuss this in detail next week when we meet to go over the Huawei proposal too14:25
mlavalleyeap14:25
SridarKwkite: did u want to discuss something specific here14:26
mlavallebut it will be good if I look at this spec, so I'm aware of the possible overlaps14:26
wkiteSridarK: ok14:26
SridarKmlavalle: sounds good14:27
xgerman_+114:27
annp+114:27
SridarKok lets move on14:27
SridarK#topic Open Discussion14:27
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"14:27
njohnstonmlavalle asked me to look at bug https://bugs.launchpad.net/neutron/+bug/177057514:28
openstackLaunchpad bug 1770575 in neutron "FWG status will be overided by mutilple l2 agent" [Undecided,New]14:28
xgerman_PSA early bird for Denver ends today14:28
njohnstonit seems to me that this is a legit case but I am not sure how to rate it in terms of severity14:28
SridarKI was swamped last few days so we could not connect on bug scrub14:28
SridarKnjohnston: ok14:28
njohnstonI have not been able to reproduce locally (issues getting my testing setup working again) but the theory seems sound14:29
amotokire: bug 1770575, I think we need to use provisioning block to maintain the status of FWG14:29
openstackbug 1770575 in neutron "FWG status will be overided by mutilple l2 agent" [Undecided,New] https://launchpad.net/bugs/177057514:29
SridarKannp: perhaps u can take a look too on ur inputs14:29
annpSridark, I will look14:29
annpamotoki, are you going to vancouver?14:30
amotokiannp: yes, I will be there14:30
SridarKIn general the FWG status is something we need to look into14:30
annpamotoki, I happy to hear that. :)14:31
amotokiif multiple agents or drivers are involved, it is suggested to use provisioning block.14:31
SridarKwith multiple ports - and the fact that all ports will not always cooperatate in unison w.r.t to the FWG status14:31
annpSridarK, I haved discussed with zhaobo in irc about this bug14:32
SridarKamotoki: ok i will also look into that, but i think even with a single agent we can have some issues14:32
SridarKannp: ok14:32
xgerman_+114:32
mlavallenjohnston: thanks for looking at it ;-)14:32
annpSridarK, Maybe we need to check FWG status before we update it.14:32
amotokiSridarK: your point looks important too. we might need to revisit what is the status of FWG.14:32
* mlavalle and njohnston are both multitasking in the same meetings.... LOL14:33
xgerman_annp: that might be a possibility14:33
annpSridarK, In case of if FWG status=ERROR, we shouldn't update status of FWG from rpc callback14:33
SridarKamotoki: yes this is something that we need to get specific on this14:34
xgerman_also we need to lock the status properly - so both don’t update at the same time14:34
SridarKannp: yes but we will need to indicate that some specific port associate is in ERROR14:34
amotokiannp: it sounds like compare-and-swap. perhaps we need to discuss what it should be.14:34
njohnston+114:34
SridarKAt the extreme - we can have a port specific status for every port that has a FWG associated14:35
annpamotoki, yes. compare-and-swap or revision_number14:35
SridarKthat may be an overkill - we can possibly come to some midground14:35
xgerman_yeah, I thibk proper locking would be enough — no need to keep history14:36
SridarKxgerman_: yes no need for history14:36
chandancif you want to support port as part of multiple FWG in future, we need to think anout that case too14:38
SridarKon a different topic, annp thx for the email - so we can sync up some time early in the week regarding the L7 topics for forum14:38
SridarKchandanc: yes good point14:38
xgerman_chandanc: +114:38
annpSridarK, xgerman_, amotoki, I'm asking Yushiro, Maybe he can help us arrange a meeting room at the summit14:39
SridarKannp: amotoki: xgerman_ : we can coordinate on a time to meet to review14:39
SridarKannp: yes sounds good14:39
xgerman_that would be sweet — otherwise there is usually some developer “lounge”14:39
SridarKwe can coordinate on that email thread14:39
amotokiyeah. I just started to check my session schedule today :(14:39
annpTomorrow, I will ask him again. I will let you know later14:40
xgerman_still need to sogn up for booth duty…14:40
SridarKamotoki: ok but it is good u are able to make it14:40
amotoki:)14:40
xgerman_+114:40
annp+114:40
amotokii thin yushiro can join every time :)14:40
chandancagree, lucky to make it14:40
xgerman_again if you missed it: prices for Denver PTG later this year are going up tomorrow — so book today to save $20014:40
SridarKxgerman_: thx14:41
amotokiearly bird deadline is approaching too fast. good reminder14:41
xgerman_yeah, they approved me today to save that $$14:41
mlavallethat's cool14:41
annpamotoki, yes, yushiro is always available :)14:41
SridarKxgerman_: i am asking my boss today - i forgot earlier - thx for the reminder14:42
annpxgerman_, congrats!14:42
xgerman_thanks — not my doing the others prodeed14:43
amotokieven if you cannot make it, you won't lose $$. there is a good cancelation policy (though we don't want it to happe)14:43
SridarK:-)14:43
xgerman_:-)14:43
annp:)14:44
amotokibtw, do we plan to cover some new features in rocky in the dashboard?14:44
amotokiI don't know the plan, but if any I can help a bit.14:45
amotokiCLI too.14:45
SridarKamotoki: yes we will need to address that14:45
xgerman_+114:45
SridarKchandanc: can u pls check in with SarathMekala - i think he has been busy on other things14:46
chandancI will SridarK14:46
SridarKchandanc: thx14:46
mlavalleSridarK: I have one request for you14:46
amotokiperhaps we can list priority things first and then choose some of them14:46
SridarKmlavalle: pls go ahead14:47
SridarKamotoki: +114:47
mlavalleI am giving a Neutron project update on Monday14:47
mlavalleand I want to cover FWaaS as well14:47
mlavallethere is a set of slides with the features released in Queens14:47
mlavallefor this, I looked at the release notes and already added my underdtanding14:48
mlavallehowever, I would like you to review it14:48
SridarKmlavalle: ok surely thx14:48
mlavalleis 2 or 3 highlights14:48
mlavallealso there is another set of slides on what is planned for Rocky14:48
mlavalleI would like you to list highlights in that section14:49
SridarKmlavalle: ok will do14:49
amotokii think we need to clarify what is the initial version of FWaaS v214:49
amotokithe initial blueprint of fwaas v2 covered a lot of things, but we selected more important things14:49
mlavalleamotoki: you mean in the update next week?14:49
amotokimlavalle: hopefully so (but it is not a requirement)14:50
amotokiI heard some confusions on fwaas v2 from folks who see the fwaas-v2 spec.14:50
mlavalleI'll be glad to talk about that14:51
amotokiit is a comment from operators perspective.14:51
mlavalleif we can do it in a few minutes14:51
mlavalleand if SridarK gives me a hand14:51
SridarKamotoki: ok we can clarify14:51
SridarKmlavalle: surely14:52
mlavallecool14:52
amotokione good example is that address group hasn't landed.14:52
mlavallethat's a good point14:52
amotokianyway we made a good progress in queens and hopefully rocky. it would be nice to cover this :)14:53
SridarKamotoki: +114:54
SridarKOk sounds good - if nothing else we can call it a meeting14:54
SridarKok folks have a great week and thx for joining14:56
mlavalleare we meeting next week?14:56
SridarKwe can possibly cancel the meeting next week14:56
mlavalleyeah, that makes sense14:56
SridarKi will send a notification14:56
SridarKThx and bye all14:57
SridarK#endmeeting14:57
*** openstack changes topic to "Queens (Meeting topic: fwaas)"14:57
openstackMeeting ended Thu May 17 14:57:23 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-05-17-14.00.html14:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-05-17-14.00.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-05-17-14.00.log.html14:57
mlavalleo/14:57
*** yamamoto has quit IRC14:58
annpthanks and bye all :)15:00
*** annp has quit IRC15:00
amotokio/15:02
*** wkite has quit IRC15:03
*** SridarK has quit IRC15:06
*** AlexeyAbashkin has quit IRC15:12
*** chandanc has quit IRC15:12
*** AlexeyAbashkin has joined #openstack-fwaas15:15
*** yamamoto has joined #openstack-fwaas15:19
*** yamamoto has quit IRC15:23
*** yamamoto has joined #openstack-fwaas15:40
*** yamamoto has quit IRC15:45
*** yamamoto has joined #openstack-fwaas16:01
*** yamamoto has quit IRC16:06
*** yamamoto has joined #openstack-fwaas16:21
*** yamamoto has quit IRC16:26
*** yamamoto has joined #openstack-fwaas16:42
*** yamamoto has quit IRC16:49
*** hongbin has joined #openstack-fwaas16:53
*** AlexeyAbashkin has quit IRC17:04
*** yamamoto has joined #openstack-fwaas17:05
*** yamamoto has quit IRC17:10
*** yamamoto has joined #openstack-fwaas17:26
*** yamamoto has quit IRC17:30
openstackgerritGerman Eichberger proposed openstack/neutron-fwaas master: [WIP] Adds remote firewall group to plugin  https://review.openstack.org/52120717:47
*** yamamoto has joined #openstack-fwaas17:48
*** yamamoto has quit IRC17:53
*** yamamoto has joined #openstack-fwaas18:09
*** yamamoto has quit IRC18:13
*** yamamoto has joined #openstack-fwaas18:30
*** yamamoto has quit IRC18:34
*** yamamoto has joined #openstack-fwaas18:51
*** yamamoto has quit IRC18:55
*** yamamoto has joined #openstack-fwaas19:12
*** yamamoto has quit IRC19:16
*** yamamoto has joined #openstack-fwaas19:32
*** yamamoto has quit IRC19:37
*** yamamoto has joined #openstack-fwaas19:53
*** yamamoto has quit IRC19:59
*** yamamoto has joined #openstack-fwaas20:16
*** yamamoto has quit IRC20:20
*** yamamoto has joined #openstack-fwaas20:37
*** yamamoto has quit IRC20:41
*** yamamoto has joined #openstack-fwaas20:59
*** yamamoto has quit IRC21:04
*** yamamoto has joined #openstack-fwaas21:20
*** yamamoto has quit IRC21:26
*** yamamoto has joined #openstack-fwaas21:43
*** yamamoto has quit IRC21:49
*** yamamoto has joined #openstack-fwaas22:05
*** yamamoto has quit IRC22:10
*** yamamoto has joined #openstack-fwaas22:26
*** yamamoto has quit IRC22:31
*** threestrands has joined #openstack-fwaas22:37
*** hongbin has quit IRC22:40
*** yamamoto has joined #openstack-fwaas22:47
*** yamamoto has quit IRC22:51
*** mlavalle has left #openstack-fwaas23:02
*** yamamoto has joined #openstack-fwaas23:07
*** yamamoto has quit IRC23:12
*** yamamoto has joined #openstack-fwaas23:28
*** yamamoto has quit IRC23:32
*** yamamoto has joined #openstack-fwaas23:50
*** yamamoto has quit IRC23:55

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