14:03:03 <haleyb> #startmeeting networking-ovn
14:03:03 <openstack> Meeting started Tue Oct 15 14:03:03 2019 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:03:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:03:07 <openstack> The meeting name has been set to 'networking_ovn'
14:03:13 * haleyb will wait for quorum
14:06:12 <njohnston> o/
14:06:19 <njohnston> sorry I am late
14:06:23 <haleyb> njohnston: hi
14:06:27 <njohnston> still not used to this meeting slot :-)
14:06:34 <haleyb> you're the second person here, so not late
14:07:16 <liuyulong> not the team meeting this week?
14:07:37 <njohnston> no, that was yesterday
14:08:11 <njohnston> 17 hours ago I guess
14:08:44 <haleyb> tidwellr: ping
14:08:46 <liuyulong> OK, for me, it is today, : )
14:09:12 <njohnston> liuyulong: ah! :-)
14:11:05 <haleyb> njohnston: this is not shaping up to be a very exciting meeting with just the two of us
14:12:33 <njohnston> haleyb: https://media.giphy.com/media/KFiQXtO3rWxlzpjnrV/giphy.gif
14:13:20 <haleyb> hah
14:13:30 <haleyb> #topic Announcements
14:13:42 <haleyb> 1st announcement this will be a really short meeting
14:14:04 <haleyb> #topic ML2-OVS-DVR/OVN convergence
14:14:26 <haleyb> There has been some progress on https://etherpad.openstack.org/p/ML2-OVS-OVN-Convergence
14:14:40 * haleyb realized these notes are just for posterity
14:15:34 <haleyb> part of the outcome of going through the work items is a thought on keeping the networking-ovn code in it's own repo
14:16:22 <haleyb> i am looking into that and will talk to others offline for their thoughts
14:17:00 <liuyulong> I can imagine a bad thing is that if networking-ovn is moving forward too fast to let user overcome the gap, the community and the user group will totally walk on their own separated way.
14:17:53 <haleyb> liuyulong: yes, one of the short-term goal would have to be to close the gap on a few items
14:18:06 <njohnston> agreed
14:18:06 <liuyulong> No more feedbacks from the real user group, because users are still have large sets of cloud to operate.
14:19:13 <haleyb> liuyulong: no, the only people involved so far are the distros and neutron team
14:19:38 <slaweq> hi, sorry for being late
14:19:46 <slaweq> I again forgot about this meeting
14:20:07 <liuyulong> no matter linux bridge or ovs-agent OF flows, the ovn logical and flows or data-plane are totally different.
14:20:33 <liuyulong> migration looks not so much easily
14:20:35 <haleyb> slaweq: i will have to buy the beer in Shanghai as a meeting reminder
14:20:54 <slaweq> haleyb++ beer always works for me :)
14:22:25 <haleyb> liuyulong: thanks for reminding me of migration, that deserves a section in the convergence etherpad.  There is a rough outline of it, and it's possible, but depends on the deployment tools
14:22:48 <tidwellr> haleyb: pong
14:24:33 <liuyulong> I don't know if someday the neutron agents would be all abandoned. Maybe after that day, every company will have their own cloud services...
14:24:34 <haleyb> tidwellr: hey, OVN meeting, i can follow-up with you offline if you're going to be able to continue working on this
14:25:36 <liuyulong> But, IMO, everything should be evolving。
14:25:36 <haleyb> liuyulong: i can envision a day when the agents are deprecated...
14:27:08 <liuyulong> OVN is a better choice, for new cloud deployment I may embrace it. : )
14:27:25 <haleyb> liuyulong: what is the biggest issue you see moving to OVN?  would your customers be worried?
14:29:05 <liuyulong> haleyb, actually, all most everything. The scale, the availibility, developability and maintainability...
14:29:35 <tidwellr> haleyb: we can follow up offline
14:29:42 <haleyb> tidwellr: ack
14:30:03 <tidwellr> haleyb: I live in interesting times ;)
14:30:59 <liuyulong> tool-chain, monitor, CI/CD...
14:31:06 <haleyb> liuyulong: are there items in the "gap" your customers are using?  just trying to get a different perspective than a distro
14:33:01 <liuyulong> haleyb, no, we try to deploy a OVN based environment once, but sadly it is not in-production finally.
14:34:34 <liuyulong> haleyb, we just tested it few weeks, and almost everything we developed in neutron-agents will be needed to re-implemented one more time...
14:35:55 <liuyulong> haleyb, no times to achieve that while we are facing neutron its own bugs... : )
14:36:20 <haleyb> liuyulong: so you have your own fork of the agents?  are there things we need to add to the "gaps"?  or is it just the bugs :(
14:36:27 <liuyulong> What's the status IPv6 implementation in OVN?
14:37:51 <haleyb> liuyulong: one item missing is IPv6 PD, but it is being worked on currently
14:40:41 <liuyulong> resource monitor, IP metering, Ports probe, QoS, pps limitation and some product functions.
14:41:21 <liuyulong> And I don't think it will be accepted by our team, : )
14:42:05 <liuyulong> shared bandwidth, peer-to-peer connection, l2gw, VPN, firewall...
14:44:00 <liuyulong> So, if someday the networking-ovn move-in and become the default, maybe we can create a new repo for neutron agents, yes, a move-out. : )
14:44:40 <haleyb> liuyulong: that's a long list.  so you don't see yourself migrating to OVN in the next few years
14:46:08 <liuyulong> haleyb, for new small cloud, we can give a try if we find some best practice someday. Maybe there are tons of config options need to optimize, I guess.
14:48:20 <haleyb> liuyulong: ack, and i can add these items to the etherpad
14:48:21 <liuyulong> haleyb, I may say every cloud may have their own SLA assurance, migration can inevitablely cause data-plane down, so it has risk.
14:49:35 <haleyb> liuyulong: right, there are cases where you maybe can't do an in-place update
14:54:07 <liuyulong> One more thing, baremetal, IMO some ovsdb/openflow apps can be easily developed in python...
14:56:06 <haleyb> ok, thanks for the information
14:56:31 <liuyulong> np
14:57:47 <haleyb> any other comments from anyone?  have :3 left
14:59:24 <haleyb> ok, thanks for the discussion
14:59:28 <haleyb> #endmeeting