Hybrid VM Connectivity Across VNET and Non-VNET Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud computing systems prevent direct communication between virtual network (VNET) virtual machines and non-VNET virtual machines, necessitating intermediate entities like load balancers, which complicates migration and communication processes.
Innovation Solution
Implementing a hybrid state for virtual machines that allows them to communicate with both VNET and non-VNET machines by assigning unique physical and virtual addresses, using distinct packet processing rules to manage data packets accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If virtual machines are assigned to virtual networks, then communication within the virtual network is enabled, but communication with non-virtual network machines is blocked
Solution Approach 1:
The patent applies dynamics by creating a hybrid state that allows virtual machines to dynamically adapt their network behavior. Virtual machines can switch between operating as pure VNET VMs (for internal communication) and hybrid VMs (for communication with non-VNET machines), enabling flexible adaptation to different network contexts without permanent configuration changes.
Solution Approach 2:
The patent introduces an intermediary mechanism through the network stack's packet processing rule sets. These rule sets act as mediators that inspect destination addresses and route packets appropriately - using encapsulation for VNET VMs and direct transmission for non-VNET machines, thereby enabling hybrid connectivity without requiring intermediate hardware devices.
2Reliability
If intermediate entities like load balancers are used for communication, then connectivity between VNET and non-VNET machines is achieved, but system complexity increases
Solution Approach 1:
The patent extracts the intermediary function from separate hardware devices and embeds it within the network stack software. By removing the need for physical load balancers or routers and implementing the routing logic directly in the virtual machine's network stack, the system eliminates hardware complexity while maintaining connectivity functionality.
Solution Approach 2:
The patent applies self-service by enabling virtual machines to autonomously determine their own routing path based on destination address analysis. The network stack automatically selects between encapsulation and direct transmission without requiring external control or intermediate devices, allowing each VM to manage its own communication needs independently.
3Adaptability or versatility
If migration of virtual machines is performed, then resource flexibility is improved, but communication disruption occurs
Solution Approach 1:
The patent applies preliminary action by pre-configuring the network stack with multiple packet processing rule sets before migration occurs. These pre-established rules enable seamless packet routing during the migration transition, ensuring that communication paths are already prepared and can be activated immediately without disruption when a VM moves between network contexts.
Data Source
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.