Virtual Switch Framework Data Plane Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The complexity of switch configuration increases with the use of multiple virtual switch implementations and different protocols from various vendors in a single system, making it difficult to manage and migrate data plane providers without reconfiguring the virtual switch.
Innovation Solution
A virtual switch framework that allows migration between multiple data plane providers using pluggable software modules, enabling the same flow management protocol and topology to be retained across different data plane providers without changing the switch topology, by creating and disconnecting datapaths as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple virtual switch implementations with different protocols from different vendors are used in a single system, then system versatility and vendor choice are improved, but switch configuration complexity and management difficulty increase
Solution Approach 1:
The patent introduces a virtual switch as an intermediary layer between the control plane and multiple data plane providers. This virtual switch abstracts the underlying data plane implementation details, allowing the control plane to interact with a standardized interface while supporting multiple vendor-specific data plane implementations simultaneously. The virtual switch translates between the standardized control plane protocols and vendor-specific data plane protocols, thereby resolving the configuration complexity issue while maintaining versatility.
Solution Approach 2:
The patent segments the network switching system into distinct functional layers: a control plane that handles flow management protocols and a data plane that handles actual packet forwarding. By separating these functions and allowing multiple data plane providers to be configured independently under a unified virtual switch, the system achieves both vendor diversity and simplified management. Each data plane provider can be configured separately without affecting the control plane or other data plane providers.
2Reliability
If data plane provider migration is performed without reconfiguring the virtual switch, then system availability and operational continuity are improved, but the complexity of managing multiple data plane providers increases
Solution Approach 1:
The patent establishes the virtual switch and its configuration before data plane provider migration is needed. The virtual switch is pre-configured with the ability to support multiple data plane providers through a standardized interface. This preliminary setup allows for seamless migration between data plane providers, as the virtual switch infrastructure is already in place and can simply switch between different data plane implementations without requiring reconfiguration during the migration process.
3Loss of time
If virtual switch configuration is retained across different data plane providers, then configuration time and operational disruption are reduced, but the ability to optimize for specific vendor features is limited
Solution Approach 1:
The patent designs the virtual switch with universal functionality that can work with multiple vendor-specific data plane providers through a standardized interface. The virtual switch maintains a consistent configuration model that is vendor-agnostic, allowing the same configuration to be retained across different data plane providers. At the same time, the system allows for vendor-specific optimizations to be applied at the data plane provider level without affecting the virtual switch configuration, thus achieving both configuration retention and vendor-specific feature optimization.
Data Source
AI summary
The disclosure relates to technology for supporting a virtual switch to change data plane providers on a framework supporting multiple data plane providers. A processing device receives a request to change a first data plane provider, where the virtual switch is configured with a topology on the first data plane provider to use a flow management protocol. The virtual switch includes network interfaces connected to ports to enable communication among entities attached to the network interfaces by forwarding data packets within a first datapath of the first data plane. In response to the change, the network interfaces are disconnected, the first datapath is removed and a second datapath is created. The virtual switch is then configured to operate with the second datapath while retaining the flow management protocol and the topology, such that the entities communicate by forwarding data packets within the second datapath on the second data plane.