Third Network Manager SDN Migration Templates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current technologies lack effective tools for migrating network components between different cloud deployments, including private and public clouds, which hampers seamless transition and management of software-defined networks across varying virtualization platforms.
Innovation Solution
A method involving a third network manager that provides a graphical user interface and application programming interface to specify, review, and deploy logical network components, along with a migration manager that uses templates to convert and migrate these components between different software-defined networks, ensuring compatibility and correct deployment across different cloud environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If different network managers deploy logical network components differently in first and second SD networks, then each deployment can be optimized for its specific cloud environment, but migrating network components between deployments becomes complex and error-prone
Solution Approach 1:
The patent introduces a migration manager as an intermediary component that mediates between the first network manager and second network manager. The migration manager receives notifications from the first network manager, identifies corresponding logical network components, and coordinates with the second network manager to ensure accurate migration. This intermediary resolves the complexity by centralizing the migration logic and component mapping functionality, preventing errors that would arise from direct interaction between differently-configured network managers.
Solution Approach 2:
The migration manager performs multiple functions: it acts as a notification receiver from the first network manager, a component identifier that maps logical components across different deployments, and a coordinator with the second network manager. This multi-functional approach allows a single component to handle the entire migration workflow, reducing overall system complexity despite the underlying differences between network managers.
2Ease of operation
If a third network manager provides centralized interface for specifying logical network components, then user control and visibility are improved, but the system architecture becomes more complex
Solution Approach 1:
The patent combines the user interface functionality and the migration coordination functionality into a single third network manager component. This consolidation provides users with a centralized view and control over logical network components across multiple SD networks, while internally the third network manager leverages existing interfaces with the first and second network managers. The merging eliminates the need for separate UI components and reduces overall architectural complexity despite the enhanced functionality.
3Manufacturing precision
If migration manager uses templates to convert logical network components, then migration accuracy and compatibility are improved, but the migration process requires additional processing time
Solution Approach 1:
The patent implements templates that pre-define the mapping relationships and conversion rules between logical network components in different SD network deployments. By preparing these templates in advance, the migration manager can quickly match and convert components during migration without performing complex real-time analysis. This preliminary preparation significantly reduces migration time while maintaining high accuracy through the structured template-based approach.
Data Source
AI summary
Some embodiments provide a method of migrating a first software defined (SD) network managed by a first network manager to a second SD network managed by a second network manager. The method of some embodiments is performed by a third network manager that provides an interface that allows a set of users to specify and review logical network components, which the first and second network managers can then respectively deploy in the first and second SD networks. The third network manager in some embodiments identifies for a migration manager a first group of two or more logical network components that the third network manager previously specified for the first network manager to deploy in the first SD network. The migration manager then uses this information to correctly convert the first group of logical network components to a second group of two or more logical components in an appropriate manner that will allow the third network manager to manage the second group of logical network components that is implemented in the second SD network.