Cloud-Native SDN Controller Architecture for Scalable Configuration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing software-defined networking (SDN) architectures face challenges in cloud-native adoption due to complexity in life cycle management, mandatory high resource analytics components, scale limitations in configuration management, and the lack of command-line interface-based interfaces.
Innovation Solution
A cloud-native SDN architecture with a container-based microservices design, incorporating a network controller that supports in-service upgrades, modular upgrades of components, and integrates with existing orchestration platforms like Kubernetes, providing scalable and elastic network management with optional monitoring and user interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If traditional SDN architecture is used, then network control is centralized, but device complexity and life cycle management become difficult
Solution Approach 1:
The patent segments the SDN controller into multiple independent microservices that can be deployed as containers. Each microservice handles specific network control functions, allowing independent deployment, scaling, and management. This segmentation reduces the complexity of life cycle management by enabling modular updates and failures isolation, while maintaining centralized control through the API server.
Solution Approach 2:
The patent introduces an API server as an intermediary layer between the orchestration platform and the network controllers. This API server abstracts the complexity of microservice communication and provides a standardized interface for resource provisioning and network control, simplifying the operational complexity while maintaining centralized control capabilities.
2Reliability
If mandatory high resource analytics components are added, then monitoring capability improves, but resource consumption increases
Solution Approach 1:
The patent implements monitoring selectively rather than universally. Analytics components are deployed only where needed based on network traffic patterns and policy requirements. The system can enable or disable monitoring for specific microservices or network segments, avoiding the resource consumption of mandatory full-stack monitoring while maintaining necessary monitoring capabilities for reliability.
3Adaptability or versatility
If configuration management is scaled out, then system scalability improves, but configuration consistency becomes difficult to maintain
Solution Approach 1:
The patent implements feedback mechanisms where the API server continuously monitors the actual state of network resources and compares it with the desired state defined in configurations. When inconsistencies are detected, the system automatically initiates corrective actions to align the actual state with the desired state, maintaining configuration consistency even as the system scales out multiple microservices and nodes.
Solution Approach 2:
The patent performs preliminary validation of configuration requests before they are applied to the network. The API server verifies configuration correctness, resource availability, and policy compliance in advance, preventing inconsistent configurations from being deployed. This preliminary action ensures configuration consistency is maintained as the system scales.
4Ease of operation
If command-line interface-based interfaces are removed, then ease of operation improves, but API complexity increases
Solution Approach 1:
The patent implements a universal API server that provides standardized interfaces for multiple purposes: resource provisioning, network control, monitoring, and troubleshooting. This single API layer handles diverse operational needs through unified endpoints, avoiding the complexity of multiple specialized interfaces while maintaining ease of operation through consistent interaction patterns.
Data Source
AI summary
In an example, a method includes processing, by an application programming interface (API) server implemented by a configuration node of a network controller for a software-defined networking (SDN) architecture system, requests for operations on native resources of a container orchestration system; processing, by a custom API server implemented by the configuration node, requests for operations on custom resources for SDN architecture configuration, wherein each of the custom resources for SDN architecture configuration corresponds to a type of configuration object in the SDN architecture system; detecting, by a control node of the network controller, an event on an instance of a first custom resource of the custom resources; and by the control node, in response to detecting the event on the instance of the first custom resource, obtaining configuration data for the instance of the first custom resource and configuring a corresponding instance of a configuration object in the SDN architecture.