Hybrid Virtual Machine Connectivity Across VNET and Physical Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
VNET virtual machines in cloud computing systems are unable to communicate directly with non-VNET virtual machines, necessitating intermediate entities for communication, which complicates migrations and deployments.
Innovation Solution
Implementing a hybrid state for virtual machines that allows them to operate with both VNET and non-VNET addresses, using distinct packet processing rule sets to manage communication with both types of machines, ensuring seamless connectivity during migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If virtual machines are assigned to virtual networks, then communication between VNET VMs is enabled, but communication between VNET VMs and non-VNET VMs becomes impossible
Solution Approach 1:
The patent implements a hybrid state for virtual machines that enables them to function in both VNET and non-VNET environments simultaneously. The network stack is configured with multiple packet processing rule sets that can handle different address spaces (VNET addresses and physical IP addresses), allowing a single VM to communicate with both VNET VMs and non-VNET VMs without requiring separate configurations or intermediate entities.
2Adaptability or versatility
If virtual machines are migrated to virtual networks, then network virtualization benefits are achieved, but service interruption occurs during migration
Solution Approach 1:
The patent applies preliminary action by pre-configuring the network stack with multiple packet processing rule sets before migration occurs. The system prepares the VM with both VNET and non-VNET address space configurations in advance, so that when migration happens, the VM can immediately use the appropriate rule sets to maintain connectivity without service interruption. The hybrid state is established beforehand to ensure seamless transition.
3Reliability
If distinct address spaces are used for VNET and non-VNET, then address conflict is avoided, but packet processing complexity increases
Solution Approach 1:
The patent segments the packet processing function by implementing separate packet processing rule sets for different address spaces within the network stack. One rule set handles VNET addresses while another handles physical IP addresses. This segmentation allows the system to maintain distinct address spaces for VNET and non-VNET VMs, preventing address conflicts, while the modular rule set structure manages the complexity by clearly separating processing logic for different address types.
Data Source
Figure 1A~1B
Figure 1C
Figure 1D~1E
AI summary
A hybrid state for a virtual machine (VM) in a cloud computing system enables a VM to communicate with other VMs that belong to a virtual network (VNET VMs) while maintaining connectivity with other VMs that do not belong to the virtual network (non-VNET VMs). A non-VNET VM can be transitioned to a hybrid VM that operates in a hybrid state. The hybrid VM can be assigned a private virtual IP address (VNET address) for communication with other VNET VMs. The hybrid VM can continue to use a physical IP address to communicate with other non-VNET VMs. In this way, the hybrid VM is able to maintain connectivity with other non-VNET VMs during and after migration to the VNET. A network stack can be configured to process data packets that are destined for non-VNET VMs differently from data packets that are destined for VNET VMs.