On 7/18/23 19:07, Joe Liu via discuss wrote:
> Hi,
>
> I have a question about building lates OVN LTS release v22.03.2 working with
> latest OVS LTS release v2.17.7
>
> The build failed with the ovn-northd.c referencing to OVS v2.17.7 source
> missing the following function:
>
> northd/ovn-northd.c:
> ovsdb_idl_set_write_changed_only_all(ovnsb_idl_loop.idl, true);
>
>
> From OVN side, I checked the initial OVN LTS v22.03.0 did not have such
> reference, but starting with v22.03.1, the reference was introduced.
>
> From OVS side, I checked the referenced function was not available from OVS
> v2.17.7 but started available from OVS release v3.0.0:
>
> lib/ovsdb-idl.c:ovsdb_idl_set_write_changed_only_all(struct ovsdb_idl *idl,
> bool enable)
> lib/ovsdb-idl.h:void ovsdb_idl_set_write_changed_only_all(struct ovsdb_idl
> *idl, bool enable);
>
>
> My question is: how could we go with both OVN and OVS and follow their
> perspective latest LTS releases? If we go with OVN LTS v22.03.2, do we have
> to go with a non-LTS OVS release (e.g., v3.0+)? Or, if we go with OVS LTS
> v2.17.1, we might stuck with OVN LTS v22.03.0 without LTS update path?
Hi, Joe.
The version of OVS to build with and version of OVS to run with
are two different things. You should build OVN with the version
of OVS provided in a submodule. For v22.03.2 it will be OVS
commit 2410b95597fcec5f733caf77febdb46f4ffacd27.
OVN only uses some libraries from OVS sources. You should be
able to run OVN built this way with your OVS 2.17.7 without any
issues.
One inconvenience though is that, unfortunately, release archives
on GitHub do not include submodules (GitHub doesn't support that).
So, you'll need to check it out yourself.
Best regards, Ilya Maximets.
>
> Thanks in advance for your help,
> Joe
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
