Destination Compute Instance Network Address Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing data traffic on distributed storage systems in a high availability (HA) computing environment can result in unnecessary latencies and potential loss of critical data due to inefficient management of storage requests and network configurations, especially in cloud-based environments where different cloud providers have unique APIs and network environments.
Innovation Solution
Utilizing a destination compute instance to manage network address migration by updating network configurations, eliminating the need for a mediator node and optimizing the process through caching and parallel updates of cloud provider APIs, thereby enhancing failover efficiency and reducing disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a mediator node is used to manage network address migration between compute instances, then the failover process can be coordinated centrally, but the device complexity and the number of additional compute resources required increase
Solution Approach 1:
The patent applies the intermediary principle by introducing a mediator node that coordinates network address migration between compute instances. The mediator node receives migration requests, determines the target compute instance, and manages the network configuration updates. This central coordination mechanism ensures reliable failover while maintaining system manageability through a dedicated intermediary component.
Solution Approach 2:
The mediator node performs multiple functions including receiving migration requests, determining target instances, updating network configurations, and coordinating failover operations. By consolidating these diverse functions into a single multi-functional component, the system achieves reliable coordination without proportionally increasing overall system complexity.
2Ease of operation
If network configurations are updated sequentially during address migration, then the update process is simple to manage, but the productivity and failover speed decrease due to multiple sequential API calls
Solution Approach 1:
The mediator node determines the target compute instance and prepares the migration plan before executing network configuration updates. By performing preliminary analysis and preparation, the system can then execute parallel updates efficiently, achieving both operational simplicity and high speed through structured advance planning.
Solution Approach 2:
The patent merges multiple network configuration update operations into a single parallel execution phase. Instead of updating each configuration sequentially, the mediator node coordinates simultaneous updates across multiple cloud provider APIs, significantly reducing the total time required for address migration while maintaining manageable complexity through unified coordination.
3Reliability
If cloud provider APIs are called multiple times for each network configuration update, then each update can be confirmed individually, but the loss of time and API call overhead increase
Solution Approach 1:
The mediator node maintains continuous coordination throughout the parallel update process, monitoring all configuration changes simultaneously rather than interrupting to confirm each update individually. This continuous action approach ensures reliability through comprehensive oversight while minimizing time loss by eliminating repeated sequential API call cycles.
Solution Approach 2:
The system performs preliminary determination of all required network configuration updates before execution. By knowing in advance which configurations need updating and their targets, the mediator node can coordinate parallel updates with minimal confirmation overhead, reducing API call time while maintaining reliability through pre-planned verification.
4Ease of manufacture
If network address migration is performed without optimization, then the process is straightforward to implement, but unnecessary latencies occur and data availability may be disrupted
Solution Approach 1:
The mediator node serves as an intelligent intermediary that optimizes the migration process by determining the best target compute instance, coordinating parallel updates, and managing failover timing. This intermediary layer adds implementation complexity but ensures data availability and minimizes latencies through optimized decision-making and coordinated execution.
Solution Approach 2:
The system performs preliminary determination of migration targets and update strategies before execution. This advance planning enables optimized parallel processing and coordinated failover, reducing latencies and ensuring data availability while maintaining reasonable implementation complexity through structured preparation.
Data Source
AI summary
Network address migration using a destination compute instance to update network configuration information in a cloud environment is disclosed. A network interface either using a private address within a subnet corresponding to the created network interface or using a floating address outside of the subnet corresponding to the created network interface is created. A first node of the HA pair with a service provider interface. The first node is an active data server of the HA pair, and the second node is a backup node of the HA pair. Requests are serviced the first node using the created network interface. Upon failure of the first node, the second node performs a failover, wherein if the first node was utilizing a floating address, the second node registers the second node with the service provider interface by adding an address of the second node to the route table.