Bug 2025910 - Revert ML2/OVS to ML2/OVN migration
Summary: Revert ML2/OVS to ML2/OVN migration
Keywords:
Status: CLOSED DUPLICATE of bug 1823324
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: beta
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-23 11:28 UTC by Slawek Kaplonski
Modified: 2022-01-06 14:22 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-06 14:22:05 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-11001 0 None None None 2021-11-23 11:30:28 UTC

Description Slawek Kaplonski 2021-11-23 11:28:55 UTC
There need to be some tool which will be able to revert migration from ML2/OVS to ML2/OVN if e.g. something would go wrong during the migration.

As first step, lets focus only on the simple case which is revert of the migration if there were e.g. no new instances spawned on the ML2/OVN yet, so all is plugged still to the br-int as it was before migration.
In such case migration should:
1. Revert network type and mtu changes done in the neutron db,
2. prepare tripleo images with ML2/OVS,
3. remove ovn "agents" from the nodes,
4. We will see what more could be maybe needed...


This procedure will be very basic as first step. Later we can move on with some more complex use cases if that will be needed.

Comment 1 Jakub Libosvar 2022-01-06 14:22:05 UTC

*** This bug has been marked as a duplicate of bug 1823324 ***


Note You need to log in before you can comment on or make changes to this bug.