XML

Word

Printable

Epic Name:
cclm-localnet-spike
Story Points:
77
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Component Fix Version(s):
None
Current Status:
Red
Epic Status:
In Progress
Hierarchy Progress Bar:

40% To Do, 0% In Progress, 60% Done
Status Summary:

Hide

2026-01-30:
The spike summary document needs more work. This should be finalized in the first week after 4.21.0. Moving the target to 4.22....

Show
2026-01-30: The spike summary document needs more work. This should be finalized in the first week after 4.21.0. Moving the target to 4.22....

Goal

Understand the stuntime of localnet networking during cross-cluster live migration, explain it in an RCA document, and propose how to improve it.

User Stories

As a user migrating a VM between sites,
I want the stuntime to be as little as if I was migrating within a cluster,
so my application and my clients do not suffer any unexpected issues.

<List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

We assume that due to the way OVN Kubernetes handles live-migration with localnet, the stuntime during migration between clusters will be considerably higher than within a cluster, due to lack of any "handover".

blocks

CNV-64466 Localnet does not work well with cross-cluster live-migration

is cloned by

CNV-78203 Fix localnet stuntime during cross-cluster live migration

is depended on by

CNV-78203 Fix localnet stuntime during cross-cluster live migration

relates to

CNV-50823 Cross-cluster live migration - GA

1.	upstream roadmap issue	Closed	Unassigned
2.	upstream design	Closed	Unassigned
3.	upstream documentation	Closed	Unassigned
4.	upgrade consideration	Closed	Unassigned
5.	test plans in polarion	Closed	Unassigned
6.	automated tests	Closed	Unassigned
7.	downstream documentation merged	Closed	Unassigned
8.	CNV QE DevOps Requirement/Enablement	Closed	Unassigned