Virtual Network Interface Failover via Dynamic IP Pools
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud environments, virtual network interface cards have immutable primary IP addresses, making it impossible to fail over by moving the primary IP address from a failed virtual machine to a non-failed one, and users face complex manual steps and large input data requirements for deploying cloud-based node clusters with features like load balancing and dynamic network file system failover.
Innovation Solution
The technology divides a delegated subnet into static and dynamic pools of IP addresses, where static pools contain immutable primary IP addresses for virtual network interface cards and dynamic pools contain secondary IP addresses that can be reassigned for failover, simplifying the deployment and management of node clusters by automating IP address management and reducing user interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a virtual network interface card uses an immutable primary IP address, then the network interface can be deployed in cloud environments, but failover cannot be achieved by moving the primary IP address from a failed virtual machine to a non-failed one
Solution Approach 1:
The patent segments the IP addressing system into two distinct pools: a static pool containing immutable primary IP addresses for each virtual network interface card, and a dynamic pool containing secondary IP addresses that can be reassigned during failover. This segmentation allows the system to maintain both the immutability requirement for primary addresses and the reassignability needed for failover capability.
Solution Approach 2:
The patent introduces secondary IP addresses from the dynamic pool as an intermediary mechanism for failover. When a virtual machine fails, secondary IP addresses are reassigned to non-failed virtual machines, enabling failover without requiring the primary IP address to be movable. This intermediary approach resolves the contradiction between immutable primary addresses and failover capability.
2Reliability
If users deploy cloud-based node clusters with load balancing and dynamic network file system failover, then high availability is achieved, but users must provide large input data and deal with many manual steps
Solution Approach 1:
The patent implements self-service automation where the system automatically performs IP address allocation, pool management, and failover operations without requiring user intervention. The automated orchestration engine manages the static and dynamic IP pools, handles failover decisions, and configures load balancing, thereby achieving high availability while eliminating the need for users to provide large input data or perform manual steps.
Solution Approach 2:
The patent performs preliminary actions by pre-establishing the static and dynamic IP address pools during cluster deployment. The system proactively configures the failover mechanism in advance, including pre-allocating secondary IP addresses and setting up the automated orchestration logic, so that when failures occur, failover can happen automatically without requiring user input or manual configuration at the time of failure.
3Ease of operation
If automated IP address management is implemented, then deployment and management of node clusters is simplified, but additional IP address pool management mechanisms are required
Solution Approach 1:
The patent creates a universal IP address management system that handles multiple functions through a unified mechanism. The same automated orchestration engine manages both the static pool (for primary addresses) and the dynamic pool (for secondary addresses), performs allocation, monitoring, and failover operations. This multi-functional approach simplifies deployment by providing a single automated system rather than requiring separate management mechanisms for different IP address types.
Data Source
AI summary
The technology described herein is directed towards deploying a node cluster, e.g., in a cloud environment, based on user input data, including storage capacity and a delegated subnet. The subnet is divided into groups of internet protocol (IP) addresses for different usages, including for use by virtual network interface cards associated with virtual machines of the cluster. Based on the number of nodes determined from the input data, a static pool of primary IP addresses and a dynamic pool of secondary IP addresses are created for association with the virtual network interface cards. When the node cluster is operational, a failed virtual machine can be failed over to non-failed virtual machines by use of the secondary IP addresses previously associated with the failed virtual machine. Also described is handling IP address association with virtual network interface cards when the number of virtual machines of the cluster is increased or decreased.