Zero-Loss VM Migration via Segment Routing Headers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques for migrating virtual machines result in packet loss during migration, as they rely on updating a mapping service with the new location of the virtual machine, leading to inefficiencies in network packet delivery and increased burden on the mapping system.
Innovation Solution
The implementation of IPv6 Segment Routing (SRv6) allows packets to be sent to both the original and destination physical machines, ensuring zero packet loss during migration by using a Segment Routing Header that automatically redirects traffic to the active machine, reducing the mapping system's load and eliminating the need for precise location updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing techniques update mapping service with VM location after migration, then mapping system can track VM location, but packet loss occurs during migration
Solution Approach 1:
The patent applies preliminary action by pre-configuring segment routing paths that include both the source and destination physical machine addresses before migration occurs. This allows packets to be automatically forwarded to the correct location without waiting for mapping service updates, eliminating packet loss during the migration transition period.
Solution Approach 2:
The segment routing header acts as an intermediary that carries routing information through the network. It includes both source and destination addresses, enabling automatic packet redirection without requiring the mapping service to be the sole intermediary for location tracking, thus preventing packet loss during migration.
2Measurement precision
If mapping service tracks and distributes active workload locations precisely, then packet routing accuracy improves, but mapping system burden increases
Solution Approach 1:
The patent extracts the location tracking function from the mapping service and embeds it directly in the segment routing header. Each packet carries its own routing information (source and destination addresses) without requiring the mapping service to track and distribute location data, thereby reducing mapping system burden while maintaining routing precision.
Solution Approach 2:
The segment routing mechanism enables self-service routing where packets automatically contain their own destination information in the routing header. This eliminates the need for the mapping service to actively track and update workload locations, reducing system complexity while maintaining precise routing.
Data Source
AI summary
Techniques for zero-loss workload mobility with segment routing for virtual machines are presented. The techniques include receiving, by a virtual router, an electronic message destined for a first virtual machine running on a first physical machine and checking a first virtual machine state for the first virtual machine. In response to determining that it is associated with a running state indicating the first physical machine, inserting a segment routing header including an indication of the source virtual machine, the first physical machine, and the first virtual machine. In response to determining that it is associated with a migration state, inserting, by the virtual router, a segment routing header indicating the source virtual machine, an END.S for the first physical machine, the first virtual machine; and an END.SBUF for a second physical machine. The message is then routed based at least in part on the inserted segment routing header.