Live Application Migration via Routing Table Entries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current live migration techniques are inefficient as they migrate more applications or data than necessary, using excess resources and adding complexity, as they do not allow for selective migration on a per-application basis and require similar resources at the destination system.
Innovation Solution
The method involves creating routing table entries to forward traffic for specific applications or kernels to their new locations without disrupting service, using port forwarding and NAT tables to redirect traffic, allowing for selective and resource-efficient live migration of applications and kernels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If traditional checkpointing and copying methods are used for migration, then the application can be migrated to a new system, but excessive resources are consumed and the migration process becomes complex
Solution Approach 1:
The patent segments the migration process by introducing a gateway component that separates the source system, destination system, and network. The gateway handles traffic forwarding independently, allowing the migration to proceed without copying entire application states. This segmentation reduces resource consumption by only migrating necessary application data rather than complete system states.
Solution Approach 2:
The patent introduces a gateway as an intermediary component between the source and destination systems. This gateway receives traffic from the source system and forwards it to the destination system, eliminating the need for complex direct system-to-system migration protocols. The intermediary simplifies the migration architecture and reduces the computational resources required for the migration process.
2Reliability
If traditional migration methods are used, then applications can be moved between systems, but service downtime occurs during the migration process
Solution Approach 1:
The patent implements preliminary action by pre-configuring the gateway with routing information before the actual application migration occurs. The gateway is prepared to intercept and forward traffic in advance, so when the application is moved to the destination system, traffic is automatically redirected without service interruption. This preliminary setup ensures continuous service availability throughout the migration process.
Solution Approach 2:
The gateway acts as a mediator that maintains service continuity by intercepting traffic destined for the source system and automatically forwarding it to the destination system where the application has been migrated. This intermediary mechanism ensures that clients experience no downtime during migration, as the gateway seamlessly handles the traffic redirection.
3Adaptability or versatility
If traditional migration approaches are used, then applications can be relocated, but the migration lacks selectivity and requires similar resources at the destination
Solution Approach 1:
The patent applies local quality by enabling selective migration of individual applications rather than requiring migration of entire system states or all applications. The gateway can be configured to intercept and forward traffic for specific applications only, allowing administrators to migrate individual applications based on specific needs. This selective approach reduces the quantity of resources required at the destination system, as only the necessary application data and dependencies are transferred.
Data Source
AI summary
In a routing table of a first system, a routing table entry for a first application is created by a controller application executing in a controller system, the first application intended for relocation, a second application in the set of applications not intended for relocation. At the second system responsive to commencing execution of the first application in the second system at a second time, a mapping entry is created by a controller application, the mapping entry causing the forwarded packet to be delivered to the first application at the second system. Responsive to a notification that the first application is executing in the second system, the routing table entry of the first system is modified by the controller application, the modified entry causing a packet addressed to the first application to be forwarded from the first system to the second system.