Allow microovn to install alongside existing OVS#320
Merged
fnordahl merged 1 commit intocanonical:mainfrom Mar 27, 2026
Merged
Conversation
6364121 to
9859afb
Compare
fnordahl
requested changes
Mar 27, 2026
Member
fnordahl
left a comment
There was a problem hiding this comment.
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>
Contributor
Author
|
A working and reliable CI, we are blessed |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
the blocking behavior is moved to microovn.switch, this allows the user/charm to install microovn alongside OVS, prepare migration and then bootstrap microovn.