Network Integration Engine Bipartite Graph Service Containers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network integration systems face scalability issues and resource management challenges due to the increasing number of virtual and physical infrastructure management subsystems, leading to inefficient automation and resource overload, particularly when deploying service containers for comprehensive network automation in Software Defined Datacenters.
Innovation Solution
A network integration engine identifies affiliations between service endpoints, generates an affiliation graph, converts it to a bipartite graph, and launches a service container for each controller group subset, reducing the number of service containers needed and optimizing resource usage by launching one container per controller service endpoint rather than per controller/controlled pairs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If a service container is launched for each combination of virtual infrastructure management subsystem and physical networking infrastructure management subsystem, then comprehensive network automation coverage is provided, but the number of service containers increases quadratically, causing resource overload and scalability issues
Solution Approach 1:
The patent merges multiple service container functions into a single unified service container that can handle multiple virtual infrastructure management subsystems and physical networking infrastructure management subsystems simultaneously. This consolidation reduces the quadratic growth of service containers to linear growth, resolving the contradiction between comprehensive automation coverage and system complexity.
Solution Approach 2:
The service container is designed with multi-functionality to perform automation tasks across different subsystem combinations. A single service container can monitor and synchronize multiple virtual-physical infrastructure pairs, eliminating the need for dedicated service containers for each combination and thereby reducing overall system complexity while maintaining comprehensive automation.
2Adaptability or versatility
If the number of virtual infrastructure management subsystems and physical networking infrastructure management subsystems increases, then more comprehensive management is achieved, but the number of service containers required increases quadratically, leading to resource management challenges
Solution Approach 1:
Multiple subsystem management functions are merged into a single service container instance that can dynamically handle multiple virtual infrastructure management subsystems and physical networking infrastructure management subsystems. This approach allows the system to scale adaptability linearly rather than quadratically, as one service container can serve multiple subsystem combinations through dynamic configuration and event-driven architecture.
Solution Approach 2:
The service container implements dynamic behavior by adapting its monitoring and synchronization tasks based on the current set of virtual and physical infrastructure subsystems. This dynamic capability allows a single service container to efficiently manage varying numbers of subsystems without requiring a fixed one-to-one mapping, thereby reducing the quantity of service containers needed while maintaining comprehensive adaptability.
3Extent of automation
If service containers are deployed for each infrastructure management pair, then automated synchronization is provided, but management of the growing number of automation services becomes complex and produces excessive logs and alerts
Solution Approach 1:
The patent consolidates multiple automation services into a single service container that manages synchronization across multiple virtual-physical infrastructure pairs. This unified approach merges log generation, alerting, and event handling into one centralized management point, significantly simplifying operations and reducing the complexity of managing numerous individual service containers while preserving full automated synchronization capability.
Solution Approach 2:
The service container acts as an intermediary that centralizes the management of automation services, logs, and alerts. By introducing this single intermediary component instead of multiple distributed service containers, the system simplifies operational management and reduces the proliferation of logs and alerts that would otherwise require individual handling for each service container pair.
Data Source
AI summary
A physical networking/virtual infrastructure management integration system includes a physical networking infrastructure management system providing physical networking infrastructure management subsystems, a virtual infrastructure management system providing virtual infrastructure management subsystems, and a network integration system. The network integration system identifies at least one affiliation between service endpoints provided by the physical networking infrastructure management subsystems and the virtual infrastructure management subsystems, and generates an affiliation graph that identifies each of the service endpoints and each affiliation between pairs of the service endpoints. The network integration system then converts the affiliation graph to a bipartite graph that includes a controller group including a first subset of the service endpoints and a controlled group including a second subset of the service endpoints, and launches a respective service container for each of the first subset of the service endpoints in the controller group.