External Network Device Routing for Virtual Resource Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network devices within data centers struggle to efficiently route data between virtual resources hosted on a host device, leading to processing inefficiencies and limited scalability due to the processing overhead of virtual switch management and lack of control over internal routing.
Innovation Solution
A network device external to the host device is configured to route data between virtual resources by defining identifiers that map virtual resources to target host devices, allowing routing instructions to be executed based on classification rules and policies, thereby offloading routing functions from the host device.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a host device hosts multiple virtual resources with a local virtual switch module for routing, then routing between virtual resources can be performed, but processing overhead increases and scalability is limited
Solution Approach 1:
The patent extracts the virtual switch management and routing control functions from the host device to an external network device. The host device retains only the minimal virtual switch module, while the external network device handles the complex routing decisions, identifier mappings, and provisioning operations. This extraction reduces the processing overhead on host devices while maintaining full routing capability.
Solution Approach 2:
The patent introduces an external network device as an intermediary between virtual resources on different host devices. This intermediary handles the routing of data packets between virtual resources, managing identifier mappings and routing decisions centrally. This mediator approach enables scalable routing without burdening individual host devices with complex virtual switch management.
2Adaptability or versatility
If a host device maintains closed virtualized routing environment with local virtual switch, then routing control is maintained, but integration with data center network and routing flexibility are reduced
Solution Approach 1:
The patent extracts virtual switch management complexity from the host device to an external network device. The host device maintains minimal virtual switching capability while the external network device handles complex routing policies, identifier mappings, and network integration. This extraction increases routing flexibility and network integrability without adding complexity to host devices.
Solution Approach 2:
The external network device serves multiple functions: it acts as a virtual switch, router, policy enforcement point, and network integration gateway. By consolidating these functions externally, the system achieves greater routing flexibility and network adaptability while simplifying the host device architecture.
3Adaptability or versatility
If virtual resource migration occurs between host devices, then resource flexibility is improved, but network device routing information must be updated
Solution Approach 1:
The patent implements preliminary provisioning of routing information at the external network device before virtual resource migration occurs. The network device pre-configures identifier mappings and routing rules based on anticipated migrations. When migration happens, the pre-provisioned information enables rapid routing updates without significant processing delays, thus supporting resource mobility while minimizing routing update time.
Solution Approach 2:
The system implements feedback mechanisms where the external network device receives migration notifications from host devices and automatically updates routing information. This real-time feedback loop ensures that routing tables are synchronized with actual virtual resource locations, enabling fast adaptation to migrations without manual intervention or significant delays.
Data Source
AI summary
In one embodiment, a method includes receiving on a network side of a data center network a migration notification related to migration of a virtual resource from a source host device to a target host device. The source host device and the target host device can be on a server side of the data center network different than the network side of the data center network. The virtual resource can be logically defined at the source host device. The method can also include defining, before migration of the virtual resource is completed, an identifier representing a mapping of the virtual resource to the target host device in response to the migration notification. The defining can be performed on the network side of the data center network.