Virtualized Service Migration with Stable Network Addressing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current virtual machine migration techniques result in lag, interruptions, and downtime for end users due to complex network addressing and resource migration, leading to reduced quality of service.
Innovation Solution
Implement a method involving pre-migration of data to a storage location using mmap functions and block devices, followed by post-copy migration to minimize downtime, ensuring seamless network addressing continuity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If current virtual machine migration techniques are used, then virtualized software services can be moved between hosts, but service interruption and downtime occur for client nodes
Solution Approach 1:
The patent applies preliminary action by pre-migrating data and network configuration to the target host before the actual service migration occurs. This includes pre-establishing network namespaces, pre-configuring routing rules, and pre-transferring storage data, so that when the service instance is moved, the target environment is already ready to immediately accept and continue the service without interruption.
Solution Approach 2:
The patent uses network namespaces as an intermediary layer between the client node and the actual service instance. The network namespace abstraction allows the service to be migrated between different hosts while maintaining a consistent network identity and routing path, so clients continue to communicate through the same network interface without detecting the underlying instance migration.
2Adaptability or versatility
If data is copied over network link during migration, then virtual machine can be instantiated at new location, but lag and transfer time increase
Solution Approach 1:
The patent performs data pre-migration by copying storage data and configuration files to the target host before the service needs to migrate. This preliminary data transfer allows the actual service instantiation at the new location to proceed quickly without waiting for large data copies during the migration event itself.
Solution Approach 2:
The patent segments the migration process into distinct phases: pre-migration data preparation, network namespace setup, service instance transfer, and post-migration configuration. By dividing the migration into segments, critical path operations are minimized and can be performed in parallel where possible, reducing overall migration time.
3Adaptability or versatility
If network addressing and routing resources are migrated, then service can move to new location, but client node complexity increases and connections must be re-established
Solution Approach 1:
The patent introduces network namespaces as an intermediary layer that abstracts the complex network addressing and routing details from client nodes. The network namespace maintains consistent network identifiers, routing rules, and interface configurations, so clients interact with a stable network abstraction regardless of which physical host the service instance is running on.
Solution Approach 2:
The patent copies the network namespace configuration and routing rules from the source to the target host during migration preparation. This ensures the target host has an identical network addressing structure, allowing the service to maintain the same network identity and routing behavior at the new location without requiring client nodes to adapt to new network configurations.
4Reliability
If live migration techniques are used, then service interruption is reduced, but migration time and resource overhead increase
Solution Approach 1:
The patent performs extensive preliminary actions including data pre-migration, network namespace pre-configuration, and routing rule pre-setup at the target host before the actual service instance migration. This allows the live migration to complete quickly by only transferring the service state and minimal data, rather than performing all migration tasks during the service transition window.
Solution Approach 2:
The patent segments migration tasks into pre-migration preparation phases and execution phases. Non-critical tasks like data copying and configuration setup are performed in advance during low-impact periods, while the critical service instance transfer is executed quickly with minimal interruption to maintain live migration benefits.
Data Source
AI summary
Provided herein are various enhancements for low downtime migration of virtualized software services across different instantiations, which may include real-time migration over different cloud/server providers and platforms, physical locations, network locations, and across different network elements. Examples herein include handling of migration of data and state for virtualized software services, migration of ingress and egress traffic for the software services, and migration of other various operations aspects applicable to virtualized software services. In many instances, a client node retains the same network addressing used to reach the virtualized software services even as the virtualized software services move to different network locations and physical locations.