Centralized Gateway for Multi-Vendor Network Orchestration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Integrating multiple orchestration systems (OS) and overlay controllers (OVC) from different vendors in a network is challenging due to inconsistencies in network element configuration, leading to potential inconsistencies and improper management of network resources.
Innovation Solution
A centralized gateway is introduced to manage network connectivity and configure network elements, partitioning the network into sub-networks and setting policies to restrict data communication between OS/OVC and devices, using access control lists (ACLs) to allow or disallow data flow, thereby creating isolated views for each OS/OVC.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple orchestration systems and overlay controllers from different vendors are integrated in the same network, then the network can leverage multiple management systems for diverse functionalities, but configuration inconsistencies and management conflicts occur between the multiple OS/OVCs
Solution Approach 1:
A gateway is introduced as an intermediary component between multiple OS/OVCs and network elements. The gateway receives connectivity information from multiple OS/OVCs, determines sub-networks, and configures network elements based on policies it establishes. This intermediary role prevents direct conflicts between multiple controllers while maintaining their diverse functionalities.
Solution Approach 2:
The network is segmented into multiple sub-networks based on connectivity information from different OS/OVCs. Each sub-network is associated with specific computing management devices and computing devices, allowing isolated management views. This segmentation prevents configuration conflicts by ensuring each OS/OVC manages only its designated sub-network.
2Ease of operation
If multiple OS/OVCs directly manage network elements, then each controller can independently configure devices according to its policies, but configuration conflicts and inconsistencies arise from multiple controllers managing the same devices
Solution Approach 1:
The gateway serves as a mediator that receives connectivity information from multiple OS/OVCs and translates their management intents into coordinated network element configurations. Each OS/OVC maintains its independent configuration capability through the gateway interface, while the gateway ensures overall coordination and prevents conflicts.
Solution Approach 2:
The system introduces a new dimension of abstraction by having OS/OVCs manage virtual sub-networks rather than physical network elements directly. The gateway maps these virtual sub-networks to physical network elements, allowing independent OS/OVC operations while maintaining physical network consistency.
3Reliability
If a centralized gateway is introduced to coordinate multiple OS/OVCs, then configuration consistency is improved, but the system complexity and coordination overhead increase
Solution Approach 1:
The gateway is designed as a universal coordination point that handles multiple functions: receiving connectivity information from multiple OS/OVCs, determining sub-network assignments, establishing communication policies, and configuring network elements. This multi-functionality consolidates coordination complexity into a single device rather than requiring complex inter-controller protocols.
Solution Approach 2:
The gateway autonomously determines sub-network assignments and establishes communication policies based on connectivity information it receives from OS/OVCs. Rather than requiring manual coordination or complex negotiation protocols between controllers, the gateway self-services the coordination function by automatically analyzing connectivity information and making configuration decisions.
Data Source
AI summary
A method and apparatus of a device that restricts data communicated between a plurality of computing management devices and a plurality of computing devices is described. In one embodiment, a gateway receives network connectivity information of a network for a plurality of computing management devices and a plurality of computing devices, where the plurality of computing devices is coupled to the plurality of computing management devices via a plurality of network elements. In addition, the gateway determines a plurality of sub-networks using at least the network connectivity information, wherein for each of the plurality of sub-networks, at least one of the plurality of computing management devices and a subset of the plurality of computing devices is associated with that sub-network. Furthermore, for each of the plurality of sub-networks and for each pair of computing devices in the associated subset of plurality of computing devices, the gateway determines a policy for data being communicated between this pair of computing devices and the gateway configures at least one of the plurality of network elements coupled to this pair of computing devices to allow data communicated between this pair of computing devices using at least the first policy.