On Thu, Mar 11, 2021 at 08:07:58PM -0500, Mark Michelson wrote: > On 3/11/21 5:58 PM, Ilya Maximets wrote: > > I'd say that eventually OVN should become less feature hungry > > or less dependent from OVS changes. Then we should consider > > to use only stable released OVS as a build dependency and > > actually wait for the next major OVS release if some new features > > required from it. But right now we can't afford that. > > I'd say the vast majority of the time these days, the OVS changes OVN > depends on are specifically OVSDB changes. One possible idea is to separate > OVSDB from OVS and semantically version the OVSDB API. Then OVS and OVN > would be consumers of the same common project. > > You'd still have the potential for needing to update the OVS submodule to > some non-released version. But hopefully the frequency of such updates would > be reduced. And if the frequency is reduced enough, it probably wouldn't be > outside the realm of reason to request backports of bug fixes and > point-releases of OVS whenever OVN requires a submodule update.
I'm adding Dmitry Yusupov to this thread because he expressed some interest in separating OVSDB from OVS in the latest OVS Orbit episode (https://ovsorbit.org/#e72). _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
