Open Virtualized Multitenant Network Scheme for Seamless VM Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Implementation-specific network schemes fail to maintain network connectivity when migrating virtual machines or containers between hosts with different network implementations, lacking flexibility and causing disruptions.
Innovation Solution
The implementation of an open virtualized multitenant network scheme that defines networks with specific names, creates virtual switches with multiple ports, and configures these ports to connect to various networks and network interface controllers, allowing isolated guests to establish and maintain connections based on network names, regardless of the underlying network type.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If implementation-specific network schemes are used to connect isolated guests to networks, then network connectivity can be established on individual hosts, but network connectivity is lost when migrating virtual machines or containers between hosts with different network implementations
Solution Approach 1:
The virtual switch is designed with a standardized interface that can connect isolated guests to different network implementations (physical networks, virtual networks, overlays, underlays) through a common northbound API. This universal interface allows the same virtual switch to function across multiple hosts with different network configurations, enabling seamless migration while maintaining connectivity.
Solution Approach 2:
The virtual switch acts as an intermediary layer between the isolated guest and the underlying network infrastructure. By introducing this abstraction layer with standardized northbound and southbound interfaces, the system decouples the guest from host-specific network implementations, allowing migration between hosts without losing network connectivity.
2Adaptability or versatility
If virtual switches with standardized interfaces are implemented to enable host migration, then adaptability and migration capability improve, but device complexity increases due to multiple ports and network configurations
Solution Approach 1:
The virtual switch is segmented into distinct functional ports with specific roles: northbound ports for connecting to isolated guests, southbound ports for connecting to network interface controllers, and communication ports for internal switching. This segmentation allows each port to be configured independently with standardized parameters, reducing overall complexity while maintaining migration capability.
Solution Approach 2:
Instead of configuring the virtual switch to match each specific network implementation, the system inverts the approach by having the virtual switch present a standardized interface to the isolated guest, while the southbound interface adapts to the underlying network. This inversion simplifies guest configuration and enables migration without reconfiguring the guest's network settings.
Data Source
AI summary
A multitenant network scheme system includes a memory, a physical processor in communication with the memory, an isolated guest on a host, a virtual switch, and a network interface controller. The isolated guest includes a virtual network interface controller (vNIC). The virtual switch includes a plurality ports, which include a northbound port, a communication port, and a southbound port. The northbound port is connected to a network having a respective network name. Additionally, the northbound port is associated with a virtual local area network (VLAN). The communication port is connected to the vNIC of the isolated guest and is associated with the VLAN. The network interface controller is connected to the southbound port.