14:01:25 <yushiro> #startmeeting fwaas
14:01:27 <openstack> Meeting started Thu Jun  7 14:01:25 2018 UTC and is due to finish in 60 minutes.  The chair is yushiro. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:31 <openstack> The meeting name has been set to 'fwaas'
14:01:41 <mlavalle> o/
14:02:07 <yushiro> #chair SridarK xgerman_ yushiro
14:02:08 <openstack> Current chairs: SridarK xgerman_ yushiro
14:02:27 <SridarK> yushiro: xgerman_ can one of u run todays mtg
14:02:27 <amotoki> hi
14:02:32 <xgerman_> sure
14:02:46 <SridarK> i will need to step away soon as family member health issue
14:02:51 <SridarK> so on PTO today
14:02:54 <xgerman_> ok
14:03:01 <xgerman_> #topic Announcements
14:03:01 <SridarK> i will hang around for a few mins
14:03:13 <njohnston> SridarK: hope everything goes well
14:03:19 <xgerman_> +1
14:03:21 <SridarK> njohnston: thx
14:03:30 <amotoki> SridarK: take care of your family!
14:03:33 <yushiro> SridarK, Oh, boy.  I wish your family's condition would be better.
14:03:34 <xgerman_> +1
14:03:42 <SridarK> thx all
14:03:43 <annp_> +1
14:04:22 <xgerman_> They are merging PTG and summit again
14:04:30 <SridarK> +1
14:04:47 <SridarK> will make things on budget issues easier on our employers
14:05:11 <SridarK> going to 4 events in a year has been a challenge
14:05:20 * njohnston realizes he has to catch up on his openstack-dev mail
14:06:15 <xgerman_> yeah, that
14:06:24 <xgerman_> s the intent + many are also attending kubecon
14:06:43 <amotoki> xgerman_: I think it is not a decision yet... while there are various discussions
14:06:54 <yushiro> yeah.  And next next summit will be in Denver?  At that time, PTG and summit will be combined or not..
14:07:10 <xgerman_> yes, it’s Denver twice
14:07:11 <yushiro> amotoki, yes
14:07:20 <amotoki> yushiro: PTG is in Sep and summit is in Apr 2019
14:07:30 <xgerman_> +1
14:07:39 <yushiro> amotoki, Thanks
14:07:40 <annp__> +1
14:08:06 <amotoki> I visitied the convention center at the last PTG. The big blue bear is nice :)
14:08:07 <mlavalle> Denver is happening for sure
14:08:40 <njohnston> I assume Berlin is still happening as well in Nov?
14:08:43 <mlavalle> It is the PTG's after Denver that might nort happen
14:08:50 <mlavalle> Yes, Berlin is happening
14:08:56 <xgerman_> +1
14:09:07 <amotoki> CFP for Berlin is open now
14:09:33 <xgerman_> gotta come up with something
14:09:41 <SridarK> +1
14:09:53 <yushiro> Aha, CFP!
14:10:07 * mlavalle would like to discuss one point in the Open Agenda section of the meeting
14:10:15 <xgerman_> k
14:10:21 <xgerman_> R-2 is this week
14:10:23 <xgerman_> https://releases.openstack.org/rocky/schedule.html
14:10:23 <amotoki> let's move on
14:10:38 <SridarK> xgerman_: one other quick note
14:11:09 <amotoki> https://review.openstack.org/#/c/572666/ is a patch of Rocky-2 deliverables
14:11:14 <SridarK> reached out to chandan - He and Sarath will join next week so we can get updates on Horizon
14:11:26 <xgerman_> sweet
14:11:27 <SridarK> they are tied up on internal release
14:11:40 <yushiro> +1 +1 :)
14:13:13 <xgerman_> #topic Rocky
14:13:45 <xgerman_> We need to fast track
14:13:48 <xgerman_> #link https://review.openstack.org/#/c/571331/
14:14:16 <xgerman_> I think client freezes before everyhting else
14:14:29 <xgerman_> and do we have more client changes?
14:14:52 <amotoki> xgerman_: the client freeze happens at the same time as for the server side.
14:15:21 <xgerman_> yeah, but release is a week befire RC
14:15:37 <amotoki> that's true.
14:15:51 <xgerman_> so we have with client until 7/23 but server 8/6
14:16:35 <xgerman_> just putting it on the front burner and if there are more client changes needed we should get the patches in sooner
14:16:49 <yushiro> xgerman_, Currently, there is no more patch for client except 'remote_group_id' work.
14:17:07 <xgerman_> yes, I think address group isn’t ready?
14:17:54 <yushiro> xgerman_, Ah, no. I think it's not ready.
14:18:46 <amotoki> honestly it would be nice if you include more information which explains feature dependency in the server side (in the client patch)
14:19:16 <amotoki> it is sometime difficult to track the dependencies during client reviews.
14:20:06 <xgerman_> ok, will add a depends-on… it’s my first client patch in a long while
14:20:06 <amotoki> xgerman_: is https://review.openstack.org/#/c/571331/ ready in the server side or is there any dependency?
14:20:13 <yushiro> amotoki, +1 Adding 'Depends-On' topic is more easier to track.
14:20:30 <amotoki> plus blueprint or bug links would be helpful
14:20:37 <xgerman_> amotoki: the plugin works — just need to get the driver going
14:21:02 <xgerman_> #link https://review.openstack.org/#/c/521207/
14:21:07 <xgerman_> driver
14:21:12 <amotoki> I think we can evaluate the progress around R-3 if the feature has not completed then
14:21:28 <xgerman_> #link https://review.openstack.org/#/c/564888/
14:21:43 <xgerman_> amotoki: +1
14:22:27 <amotoki> if it is highly possible to land in RC phase, we can land a client patch if an API/DB patch has landed.
14:22:49 <xgerman_> yeah, DB/API are done
14:23:25 <amotoki> my understanding is same. I hope the driver stuff lands soon :)
14:23:40 <annp__> +1
14:23:46 <xgerman_> :-)
14:23:55 <yushiro> +1
14:23:59 <njohnston> +1
14:24:01 <xgerman_> ok, logging — is this still landing in R?
14:24:18 <xgerman_> spec
14:24:21 <xgerman_> #link https://review.openstack.org/#/c/509725/
14:24:41 <xgerman_> the spec is merged — will we get the implementation?
14:24:58 <yushiro> Yes, I think it is possible to landing in R with L3 side.
14:25:09 <xgerman_> great
14:25:10 <annp__> yushiro, +1
14:25:12 <yushiro> s/landing/land
14:25:55 <amotoki> the spec covers both L2 and L3 side. L3 side only?
14:27:10 <yushiro> amotoki, Spec covers both L2 and L3.  In this cycle, we're trying to support L3 logging(FWG on router) only.  And L2 will be added in Stein.
14:27:37 <annp__> yushiro, +1
14:28:19 <amotoki> yushiro: okay, so should https://blueprints.launchpad.net/neutron/+spec/extend-logging-to-fwassv2.0 be targeted to Stein?
14:28:53 <amotoki> this is just a question from the project management perspective.
14:29:04 <yushiro> amotoki, Ah, yes.  You're right.
14:29:43 <amotoki> thanks. there is nothing to block to land L3 stuff in Rokcy :)
14:30:03 <yushiro> Yas
14:30:13 <annp__> amotoki, yeah. thanks.
14:30:15 <yushiro> oops, sorry.  It is mixed 'Ya' and 'Yes'
14:30:41 <amotoki> seems a new version of 'yes' :)
14:30:50 <yushiro> Haha
14:32:19 <xgerman_> #link https://review.openstack.org/557137
14:32:24 <xgerman_> that’s the address group sepc
14:33:22 <wkite> I am confused about the l2 drivers without iptables.
14:33:50 <xgerman_> l2 is ovs
14:33:58 <yushiro> +1
14:34:05 <wkite> by odl rules?
14:34:15 <xgerman_> neutron migrated fro linux bridge -> ovs and we only made an ovs version
14:34:21 <yushiro> wkite, by OVS flow rules
14:34:38 <wkite> i see
14:35:22 <wkite> I have been very busy recently, so I have no time to study this.
14:36:35 <xgerman_> ok, I think we need to merge the spec first — is there a deadline we need to hit so we cna think Rocky or would it better to defer that feature to Stein-1?
14:36:45 <yushiro> wkite, annp__, and chandan are good teacher about that :)
14:36:47 <xgerman_> aka is there a spec freeze for neutron?
14:37:06 * xgerman_ will need their help, too
14:37:17 <annp__> yushiro, :)
14:37:39 <wkite> yushiro thx for remind
14:37:56 <yushiro> wkite, I was busy too.  I'm sorry I couldn't review your SPEC.  But I will do it!!
14:37:56 <annp__> wkite, If you need some help free feel reach out me :)
14:38:48 <yushiro> annp__, +1
14:38:54 <wkite> annp__: thank you
14:39:32 <annp__> wkite, you're welcome. :)
14:40:14 <xgerman_> amotoki: do we have a neutron spec freeze?
14:40:50 <amotoki> xgerman_: there is no deadline for specs. doublle-checking to mlavalle
14:41:15 <mlavalle> no deadline
14:41:29 <amotoki> we have only feature freeze as usual
14:41:34 <mlavalle> yes
14:41:40 <yushiro> Thanks
14:41:46 <mlavalle> but we process specs as they come
14:41:55 <xgerman_> ok
14:42:22 <xgerman_> so I think address group is very ambitious for R — but we will see…
14:42:56 <xgerman_> I think that’s all we have in flight —
14:43:09 <wkite> xgerman_: The time of Rocky is a little short.
14:43:10 <xgerman_> reminder for the cores: reviews, reviews, reviews
14:43:32 <yushiro> xgerman_, Nice reminder!!
14:43:37 <SridarK> For AG - even if we can start the implementation in R - that is good
14:43:38 <xgerman_> wkite: yep, I think so, too - Stein is more realistic
14:43:50 <SridarK> xgerman_: +1
14:43:50 <xgerman_> SridarK: +1000
14:44:01 <wkite> xgerman_: +1
14:44:27 <xgerman_> #topic Open Discussion
14:44:46 <xgerman_> mlavalle: you have the floor (and I have something to go after)
14:44:59 <mlavalle> Thanks!
14:45:11 <mlavalle> Yesterday I sent this message to the ML: http://lists.openstack.org/pipermail/openstack-dev/2018-June/131252.html
14:46:04 <mlavalle> I am implementing multiple port bindings in Neutron. Port's port_binding in the DB model is becoming an iterable
14:46:15 <mlavalle> and its name is changing to port_bindings
14:46:38 <mlavalle> corresponding change to binding in the Port's OVO is happening
14:47:02 <mlavalle> I did check with codesearch in FWaaS and thought there won't be impact
14:47:14 <mlavalle> but I would like this team to double check
14:47:50 <SridarK> mlavalle: +1 - I too think we are ok but need more thought
14:47:53 <yushiro> mlavalle, Thanks for your information.
14:48:01 <xgerman_> +1
14:48:05 <mlavalle> I will hold the change until the end of next week
14:48:14 <xgerman_> that raises the sorry state of our tempest tests…
14:48:31 <SridarK> But will be interesting to check out the live migration use cases at a broader level
14:48:46 <SridarK> xgerman_: +1
14:48:48 <yushiro> SridarK, +1
14:48:54 <xgerman_> +1
14:48:58 <amotoki> the easy way to check is to run neutron-fwaas with these patches :)
14:49:17 <mlavalle> amotoki: would you ping the VPNaaS in your side of the world to warn them about this?
14:49:42 <amotoki> mlavalle: I try them with vpnaas till the first half of next week
14:49:55 <mlavalle> I also check their repo and think won't be impact
14:50:08 <mlavalle> but it is good if you check
14:50:11 <mlavalle> thanks
14:50:22 <xgerman_> ok, I have two more things
14:50:41 <xgerman_> for the L7 topic I found a new library nDPI
14:51:03 <xgerman_> #link https://github.com/ntop/nDPI
14:51:32 <xgerman_> and they have a list of protocols
14:51:34 <SridarK> mlavalle: i guess for us to understand what happens to ovs fwaas rules on a port in a live migration scenario
14:51:35 <xgerman_> #link https://www.ntop.org/products/deep-packet-inspection/ndpi/
14:52:26 <xgerman_> SridarK: yes, we need to test that and check what SG does
14:52:31 <annp__> xgeman_ +1
14:53:08 <SridarK> Since we are no different from SG
14:53:19 <SridarK> on the ovs driver
14:53:20 <annp__> xgerman_, Thank you :)
14:53:33 <yushiro> xgerman_, wow, great.  I found the license of this code was LGPLv3.  Hopefully there is no problem :p
14:53:59 <amotoki> the first step is to check the port_binding does not break the current static setup. I think live migration support is the next step (if we have something to do)
14:54:15 <amotoki> s/the port_binding/the port_binding stuffs/
14:54:17 <SridarK> amotoki: yes agreed
14:55:02 <yushiro> In order to check fwaas behavior with 'port_bindings', should we apply https://review.openstack.org/#/c/567462  in neutron?
14:55:10 <SridarK> Also, will talk more with Chandan and Sarath this week on Horizon  so we can have a plan
14:55:20 <yushiro> SridarK, +1
14:55:35 <SridarK> i think they shd be able to attend next week
14:56:24 <xgerman_> great
14:56:25 <amotoki> mlavalle: could you confirm yushiro's question above?
14:57:22 <mlavalle> yushiro: that would work
14:57:36 <yushiro> mlavalle, Thanks.  I see.
14:59:00 <yushiro> mlavalle, BTW, I wanted to meet you in Vancouver !! ( I couldn't go there ) Stay tuned in Denver :)
14:59:19 <mlavalle> looking forward to it!
14:59:28 <yushiro> Yas!
14:59:52 <yushiro> yes!
15:00:02 <xgerman_> ok, I have to got to another meeting
15:00:08 <xgerman_> #endmeeting