Skip to content

Allow microovn to install alongside existing OVS#320

Merged
fnordahl merged 1 commit intocanonical:mainfrom
crypticC0der:newovsm
Mar 27, 2026
Merged

Allow microovn to install alongside existing OVS#320
fnordahl merged 1 commit intocanonical:mainfrom
crypticC0der:newovsm

Conversation

@crypticC0der
Copy link
Copy Markdown
Contributor

the blocking behavior is moved to microovn.switch, this allows the user/charm to install microovn alongside OVS, prepare migration and then bootstrap microovn.

@crypticC0der crypticC0der requested a review from a team as a code owner March 26, 2026 17:12
@crypticC0der crypticC0der force-pushed the newovsm branch 2 times, most recently from 6364121 to 9859afb Compare March 26, 2026 18:02
Copy link
Copy Markdown
Member

@fnordahl fnordahl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As caught by the tests, this proposal does not work with restarts or upgrades, so I'm not sure how viable it is.

Please also see my comment on the canonical/microovn-operator#68 side of the feature.

MicroOVN will now check for a file, which if it finds it will allow the
user to force install microovn alongside system OVS. The file should
only exist if the user *really* knows what they are doing and
intentionally creates it.

Signed-off-by: MJ Ponsonby <mj.ponsonby@canonical.com>
@crypticC0der
Copy link
Copy Markdown
Contributor Author

A working and reliable CI, we are blessed

Copy link
Copy Markdown
Member

@fnordahl fnordahl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@fnordahl fnordahl merged commit b41956d into canonical:main Mar 27, 2026
46 of 94 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants