search

antrea-io / antrea

Kubernetes networking based on Open vSwitch
https://antrea.io
Apache License 2.0
1.63k stars 346 forks source link

Upgrade OVS to 3.x in Linux image #5399

Open antoninbas opened 11 months ago

antoninbas commented 11 months ago

In https://github.com/antrea-io/antrea/pull/5120, we updated OVS to 3.0.5 for Windows.

We should also update to OVS 3 in Linux images (Ubuntu / UBI), for consistency.

Refer to https://github.com/openvswitch/ovs/blob/master/NEWS for changes in OVS 3. The reason for the major version bump seems to be a non fully backwards-compatible change in libopenvswitch. This should not affect us.

wenyingd commented 10 months ago

Hi @antoninbas the latest released OVS is 3.2.0, do we need to keep on 3.0.X or to the latest?

antoninbas commented 10 months ago

No strong preference for me.

I see a change in 3.2 that might impact Antrea downgrade operations, I don't know if this is an actual concern:

Changed format in which ovsdb schema conversion operations are stored in clustered database files. Such operations are now allowed to contain the bare schema (without data). This allows to significantly improve the schema conversion performance. New ovsdb-server process will be able to read old database format, but old processes will fail to read database created by the new one, if conversion operation is present. For the cluster service model follow upgrade instructions in 'Upgrading from version 3.1 and earlier to 3.2 and later' section of ovsdb(7).

BTW, for Windows we are supposed to be using OVS "v3.0.5", but I don't see that tag upstream: https://github.com/openvswitch/ovs/tags

github-actions[bot] commented 7 months ago

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

github-actions[bot] commented 4 months ago

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

github-actions[bot] commented 1 month ago

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days