forked from ovn-org/ovn
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
controller: Migrate from ct zone UUID name to component name
There are two scenarios that could cause unwanted CT zone flush: 1) The SB DB is destroyed and recreated. The new database will end up with different UUIDs for various components. 2) Upgrade of existing SB DB to ovn-ic. The components are the same as before, but scattered between multiple SB DBs. This again leads to different UUIDs in SB DB. The CT zone name was based on datapath UUID which causes flush when the UUID changes. Even if the datapath is the same. To prevent the unwanted flush migrate from UUID to component name (LR/LS name). This allows the CT zones to be stable across the before mentioned scenarios. For the migration to be "flush less" itself we need to make sure to start the restoration process only after controller is connected to the SB DB e.g. the restoration can happen only during engine run and not init as it was done previously. Reported-at: https://bugzilla.redhat.com/2224199 Tested-by: Surya Seetharaman <sseethar@redhat.com> Signed-off-by: Ales Musil <amusil@redhat.com> Acked-by: Dumitru Ceara <dceara@redhat.com> Signed-off-by: Numan Siddique <numans@ovn.org>
- Loading branch information
1 parent
f5638ee
commit 5a1d82c
Showing
6 changed files
with
267 additions
and
34 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.