14:00:26 <mlavalle> #startmeeting networking
14:00:27 <openstack> Meeting started Tue Sep 25 14:00:26 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:30 <openstack> The meeting name has been set to 'networking'
14:00:41 <njohnston> o/
14:00:45 <haleyb> hi
14:00:50 <bcafarel> hi
14:01:01 <annp> hi
14:01:06 <manjeets_> hi
14:01:10 <slaweq> hi
14:01:43 <mlavalle> ok, let's get going
14:01:52 <mlavalle> #topic Announcements
14:02:02 <munimeha1> hi all
14:02:14 <rubasov> o/
14:02:44 <mlavalle> Our next milestone is Stein-1, October 22 - 26
14:02:59 <hongbin> o/
14:03:16 <mlavalle> The complete Stein release schedule is here: https://releases.openstack.org/stein/schedule.html
14:04:11 <mlavalle> Yesterday I sent to the ML a summary of the meetings we had in Denver during the PTG:
14:04:17 <mlavalle> #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135032.html
14:04:47 <mlavalle> I hope I captured the discussions accurately
14:04:53 <njohnston> Thanks for that, it is very complete
14:05:46 <mlavalle> We will keep a pointer to that summary in the announcements section of our weekly agenda, for rapid reference
14:06:11 <mlavalle> Any other announcements?
14:06:53 <mlavalle> ok, let's move on
14:07:00 <mlavalle> #topic Blueprints
14:07:06 <munimeha1> summary looks good, thanks
14:07:47 <mlavalle> These are the blueprints that we are targeting at this point in the cycle:
14:07:54 <mlavalle> #link https://launchpad.net/neutron/+milestone/stein-1
14:08:23 <mlavalle> As a result of the PTG summary, I might update it over the next few days
14:08:50 <mlavalle> Does anyone have any updates or requests for help in regards to blueprints?
14:10:02 <tidwellr_> I've been out of the loop, does anyone know the status of https://blueprints.launchpad.net/neutron/+spec/subnet-onboard ?
14:10:15 <munimeha1> We have implemented the new solution as discussed at PTG
14:10:24 <munimeha1> i need to know if we are ok with it
14:10:33 <bcafarel> tidwellr_: that one is mine now, target for Stein indeed
14:11:03 <munimeha1> https://review.openstack.org/#/c/603501/
14:11:32 <tidwellr_> bcafarel: great! do you have a link to a review handy?
14:11:39 <mlavalle> munimeha1: I took a look on Friday at the spec. I will look again today or tomorrow, but it seemed to me that we were close to converge on a solution
14:12:04 <munimeha1> thanks
14:13:29 <mlavalle> munimeha1: also, this week, per the PTG summary, I will push a patch with the evaluation criteria to bring TaaS to the Stadium. In the first version, all the questions will be "Fail" and then you and I start working on them one by one
14:13:58 <mlavalle> we have to start from somewhere :-)
14:14:25 <bcafarel> tidwellr_: https://review.openstack.org/#/c/348080/ (I have some local changes here on top, but that's mostly it atm)
14:14:32 <manjeets_> munimeha1, spec need changes since with tap flow it will have data model impact
14:14:59 <munimeha1> manjeet i updated that in version 18
14:15:27 <mlavalle> munimeha1: thanks for the update :)
14:15:44 <mlavalle> ok, anything else on blueprints?
14:15:45 <manjeets_> cool
14:16:26 <mlavalle> let's move on then
14:16:44 <mlavalle> #topic Community goals
14:17:25 <mlavalle> amotoki is off on a well deserved vacation this week, so no update on policy in code
14:17:47 <mlavalle> njohnston: any updates worth mentioning on PY36?
14:18:07 <njohnston> The neutron-fullstack-python36 job is now voting
14:18:19 <mlavalle> \o/
14:18:44 <bcafarel> njohnston: btw I sent https://review.openstack.org/#/c/604749/ -python36 job actually still runs 3.5 :)
14:18:59 <bcafarel> it fails finding py36 though
14:19:07 <njohnston> I am going to ask the infra team if when we convert jobs from the legacy format tot he new zuulv3 format if we need to do anything to enable python 3 or if it comes by default
14:19:33 <njohnston> bcafarel: Thanks for that!  I'll check on the failing to find python 3.6 issue with infra as well
14:19:46 <mlavalle> good catch bcafarel!
14:20:25 <njohnston> I have one change up to convert the iptables_hybrid tempest job to the new format so I will see if I can use that to see if we get python 3 for free there
14:21:18 <njohnston> that's it for python 3 for now
14:21:28 <mlavalle> thanks for the update, njohnston
14:22:05 <mlavalle> slaweq: any updates on pre-upgrade checks?
14:22:14 <slaweq> mlavalle: not too much yet
14:22:24 <mlavalle> slaweq: cool, thanks
14:22:27 <slaweq> but there is topic about that in ML also: http://lists.openstack.org/pipermail/openstack-dev/2018-September/134249.html
14:22:33 <slaweq> I'm following it for now
14:22:53 <slaweq> it looks that most of the common code will be in new oslo repository so I will consume it from there
14:24:05 <mlavalle> this seems good. You have a recipe to follow and mriedem is very thorough in this type of things
14:24:23 <mlavalle> so it should cover all or close to all that you have to do
14:24:24 <slaweq> yes, I only need some time to start this patch :)
14:24:48 <mlavalle> very good
14:25:18 <mlavalle> ok, let's move on
14:25:24 <mlavalle> #topic Bugs
14:26:11 <boden> I sent a summary of last weeks bugs to the ML
14:26:18 <boden> #link http://lists.openstack.org/pipermail/openstack-dev/2018-September/135008.html
14:26:41 * mlavalle was beaten by boden posting the pointer :-)
14:26:58 <boden> I can read minds... that comes along with being married
14:27:20 <mlavalle> that's tru, LOL
14:27:33 <mlavalle> any bugs that you might want to highlight?
14:27:45 <boden> the bugs in the first 2 lists of that email still require some attention by technical experts in the respective area
14:28:56 <mlavalle> ok, I'll go over those two lists after the morning meetings. I encourage others to do the same
14:29:04 <boden> I will just note that it appears bug https://bugs.launchpad.net/neutron/+bug/1792925  breaks  ironic's grenade job... I'm assuming that's high priority for them, but not sure
14:29:04 <openstack> Launchpad bug 1792925 in neutron "q-dhcp crashes with guru meditation on ironic's grenade" [Undecided,New]
14:29:45 <mlavalle> thanks for pointing that out. I will follow up with them
14:29:46 <boden> that's all I have on this topic
14:30:33 <mlavalle> This week our deputy is njohnston
14:30:37 <munimeha1> In end can we discuss these issues, i have a question about a two issues - we want solution/can develop for it in Stein-2, One is for trunk sriov port multiple vlans on a direct port, another is bonding of SRIOV VFs for VRRP(all direct ports with 00:00:00:00) mac so tenant can do HA with changing macs of interfaces. Nics support this on VF but Openstack don't allow it since we have random mac in neutron port.
14:31:09 <mlavalle> munimeha1: yes, let's discuss that at the end
14:31:13 <njohnston> Thanks mlavalle, I am on it
14:32:04 <mlavalle> and also pelase note that I updated our bugs deputy calendar. removed garyk, since he doesn't work upstream anymore
14:32:32 <mlavalle> if any other volunteers one to add their name to the calendar, please speak up
14:32:43 <mlavalle> it's only one week every 3 months
14:33:18 <mlavalle> ok, let's move on
14:33:22 <rubasov> I could also be a bug deputy
14:33:45 <mlavalle> rubasov: of course you can :-)
14:33:54 <rubasov> please add my name too
14:34:11 <mlavalle> rubasov: will the first week of Decmber be good for you?
14:34:19 <rubasov> it's new to me but I'll try doing my best
14:34:45 <rubasov> yes
14:35:04 <mlavalle> rubasov: we have a set of guidelines in the docs, that were originally created by njohnston if I remember correctly
14:35:20 <mlavalle> and you can always yell for help
14:35:22 <rubasov> mlavalle: I'm aware
14:35:32 <rubasov> mlavalle: I'm still digesting some of it
14:35:38 <mlavalle> cool
14:35:48 <rubasov> I'm sure I will ask a few times on that week :-)
14:35:58 <mlavalle> let's move on then
14:36:05 <mlavalle> #topic os-ken
14:36:56 <mlavalle> first of all, please note that I just changed the title of this topic in our agenda: https://wiki.openstack.org/wiki/Network/Meetings#os-ken
14:37:15 <mlavalle> hongbin: any updates worth mentioning this week?
14:37:26 <hongbin> hi
14:37:30 <hongbin> #link https://review.openstack.org/#/q/project:openstack/os-ken
14:37:43 <hongbin> above is the list of patches that are under review in that repo
14:38:13 <hongbin> as we discussed, we plans the first release after those patches are merged
14:38:13 <mlavalle> ah nice. I will review them later today
14:38:21 <hongbin> mlavalle: thanks
14:38:31 <hongbin> there is a question raised in the code review though
14:38:59 <hongbin> slaweq raised a question about whether os-ken should move to storyboard? or stay at launchpad
14:39:32 <hongbin> throughts?
14:39:54 <mlavalle> that's a good question (which I fully expect slaweq to raise). and I think we should skip launchpad and go straight to storyboard
14:40:02 <njohnston> +1
14:40:09 <mlavalle> leapfrog
14:40:21 <slaweq> IMHO it might be good, small project to start playing with storyboard a bit
14:40:30 <slaweq> and we will don't need to migrate it later
14:40:31 <mlavalle> exactly right
14:40:55 <bcafarel> + no need to add additional ingredients in the curent neutron launchpad soup :)
14:41:07 <mlavalle> LOL, the soup
14:41:41 <hongbin> ok, i will look into how to setup the storyboard later
14:42:03 <njohnston> hongbin: diablo_rojo can help
14:42:29 <mlavalle> hongbin: I will copy you in an email thread that slaweq and I have been exchanging with diablo_rojo
14:42:39 <mlavalle> she is more than willing to help
14:42:46 <hongbin> mlavalle: njohnston ack, thanks
14:43:11 <mlavalle> ok, moving on
14:43:21 <mlavalle> #topic neutron-lib
14:43:51 <mlavalle> boden: any updates this week?
14:44:04 <boden> I do have a few things... I will try to be quick
14:44:24 <boden> First there's a new release of lib proposed: https://review.openstack.org/#/c/604908/   looks good to me, but others can have a looksee
14:44:42 <mlavalle> added to my pile
14:45:30 <boden> next, during the PTG we talked about identifying "current' projects and getting them updated for zuul/local testing... I started that work... details in https://etherpad.openstack.org/p/neutron-sibling-setup  under the "List of networking..." section
14:45:58 <boden> I would ask folks to keep an eye out for related patches and help out when possible
14:46:28 <mlavalle> ok, I'll lookout for those
14:46:42 <boden> we also discussed how to test with neutron-lib master... there's a discussion in https://review.openstack.org/#/c/602748/ I was hoping cores could weigh in on
14:47:23 <mlavalle> will look at it later today
14:47:28 <mlavalle> or tomorrow
14:47:31 <mlavalle> added to my pile
14:47:52 <munimeha1> tap-as-a-service is not considered as neutron sibling?
14:47:54 <boden> there's also a discussion in https://review.openstack.org/#/c/596959/ that the callback payload patches are waiting on... I added some details there a week or so ago, but waiting for some concensus
14:48:32 <mlavalle> I'll chime in
14:48:44 <boden> munimeha1 it is not.. there's no neutron-lib in requirements https://github.com/openstack/tap-as-a-service/blob/master/requirements.txt
14:49:24 <boden> finally, we talked about adding something to consumer projects that indicates they want neutron-lib updates... mlavalle were you still planning to send a note about that or should I?
14:50:10 <mlavalle> boden: yes.... I wrote the summary first. and it is one of my todo's there. I'll tackle them this week
14:50:27 <yamamoto> boden: i'm sure taas requires neutron-lib. i guess it's just a missing req.
14:50:36 <mlavalle> but if you want to do it yourself, please feel free
14:50:47 <boden> mlavalle whichever
14:51:13 <boden> yamamoto I guess so and the topic mlavalle and I are just talking about is related
14:51:35 <boden> that's enough lib fun for now since I just added a few hrs of work to mlavalle :)
14:51:45 <mlavalle> LOL
14:51:57 <mlavalle> thanks for the update
14:52:01 <boden> mlavalle I can send the ML note for the lib topic
14:52:10 <mlavalle> boden: cool, go ahead
14:52:39 <mlavalle> let's move on
14:52:47 <mlavalle> #topic On demand agenda
14:52:52 <annp> hi
14:54:09 <mlavalle> go ahead annp
14:54:29 <annp> mlavalle, thanks.
14:54:34 <annp> In order to support SNAT log extension, we inend to use libnefilter_log (Which is used for firewall logging) to capture packet log. So we’re planing to move libnetfilter_log to neutron-lib
14:54:46 <annp> But, neutron-lib doesn’t allow eventlet.
14:54:58 <annp> Currently, libnetfilter_log is using eventlet.green.zmp for communicating between libnetfilter_log process (privilege process) and log-application( un-privilege process)
14:55:10 <annp> So I’d like to get your advice: How do I deal with this issue or we should place libnetfilter_log in neutron?
14:55:36 <mlavalle> Iwould say that Neutron will have to have its own implementation of libnefilter_log
14:56:01 <annp> mlavalle, I see. Thanks.
14:56:01 <mlavalle> at least for the time being
14:56:16 <mlavalle> we could leave a comment in the code
14:56:27 <njohnston> and if neutron-fwaas does the same logging then I guess we will need to live with code duplication
14:56:50 <mlavalle> yeap, for the time being. Let's leave a todo comment
14:57:14 <mlavalle> ok, moving on....
14:57:19 <munimeha1> hi
14:57:19 <annp> mlavalle, yes. I will add todo comment. you read my mind. :-)
14:57:50 <mlavalle> munimeha1: Please file a couple of RFEs for those two things as soon as possible
14:58:30 <mlavalle> if you file them today and we can have some exchanbge of thought over the next few days, we'll see if we can discuss them in the next drivers meeting
14:58:47 <munimeha1> thanks, will do
14:59:07 <mlavalle> thank you
14:59:30 <mlavalle> ok team, we ran out of time. Thanks for attending. Have a great week!
14:59:35 <mlavalle> #endmeeting