Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade OVS to 3.x in Linux image #5399

Open
antoninbas opened this issue Aug 17, 2023 · 6 comments
Open

Upgrade OVS to 3.x in Linux image #5399

antoninbas opened this issue Aug 17, 2023 · 6 comments
Labels
area/dependency Issues or PRs related to dependency changes. area/ovs Issues or PRs related to OVS kind/task Categorizes issue or PR as related to a routine task that needs to be performed priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@antoninbas
Copy link
Contributor

In #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.

@antoninbas antoninbas added priority/backlog Higher priority than priority/awaiting-more-evidence. area/ovs Issues or PRs related to OVS kind/task Categorizes issue or PR as related to a routine task that needs to be performed area/dependency Issues or PRs related to dependency changes. labels Aug 17, 2023
@wenyingd
Copy link
Contributor

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

@antoninbas
Copy link
Contributor Author

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

Copy link
Contributor

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 github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 24, 2023
@luolanzone luolanzone removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 24, 2023
Copy link
Contributor

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 github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 23, 2024
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 23, 2024
Copy link
Contributor

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 github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2024
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 24, 2024
Copy link
Contributor

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 github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 23, 2024
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependency Issues or PRs related to dependency changes. area/ovs Issues or PRs related to OVS kind/task Categorizes issue or PR as related to a routine task that needs to be performed priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

3 participants