API Converter Skeleton Model for Cloud SDN Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud virtualization management systems, integrating with external Software Defined Networking (SDN) systems is challenging due to mismatched APIs between management systems and SDN controllers, requiring extensive 'glue' code that is time-consuming and error-prone to generate manually.
Innovation Solution
A processing logic that maps resources, relationships, and fields from the management system API to the SDN API, automatically generating a skeleton model to facilitate communication between the two systems, which can be modified and saved for future use.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual generation of glue code is used to integrate management systems with SDN controllers, then integration functionality is achieved, but time consumption and error rate increase significantly
Solution Approach 1:
The system enables self-service by allowing the skeleton model to automatically generate integration code between management systems and SDN controllers. The processing logic autonomously maps resources, relationships, and fields from management system APIs to SDN APIs, eliminating the need for manual code generation and reducing both time consumption and human error.
Solution Approach 2:
The patent introduces an intermediary skeleton model that acts as a mediator between management system APIs and SDN APIs. This skeleton model contains mapping rules that translate between different API structures, resource representations, and field formats, enabling seamless integration without direct manual mapping.
2Adaptability or versatility
If extensive manual glue code is generated for API integration, then communication between systems is established, but complexity and error-proneness increase
Solution Approach 1:
The system uses copying by creating a standardized skeleton model template that can be replicated and applied to multiple integration scenarios. Once the skeleton model is established with proper mapping rules, it can be copied and reused for integrating different management systems with various SDN controllers, reducing complexity while maintaining adaptability.
Solution Approach 2:
The skeleton model is designed with universal applicability, containing generic mapping rules and structures that can handle multiple API types and formats. The processing logic can adapt to different management system APIs and SDN controller APIs using the same skeleton model framework, reducing the need for custom glue code for each integration scenario.
3Productivity
If automatic skeleton model generation is implemented, then efficiency in API generation improves, but system complexity increases
Solution Approach 1:
The processing logic is segmented into distinct functional modules: resource mapping, relationship mapping, field mapping, and code generation. This segmentation allows each module to handle a specific aspect of the integration process independently, making the overall complex system manageable and maintainable while achieving high automation efficiency.
Data Source
AI summary
A method includes identifying a cloud and virtualization management system application programming interface (API), and identifying a software defined networking (SDN) API. The method further includes determining, by a processing device, one or more resources, relationships, or fields corresponding to the cloud and virtualization management system API and the SDN API. The method further includes generating, by the processing device, a skeleton model representing mappings between the one or more resources, relationships, or fields corresponding to the cloud and virtualization management system API and the SDN API. The method further includes and providing the skeleton model to a client device for display.