Integration Plugin Script Generation for Cloud Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud-based automation platforms face challenges in seamlessly integrating functionalities across different cloud environments, leading to limitations in service accessibility and quality for customers.
Innovation Solution
A management node with an integration plugin generates scripts to integrate functionalities of one cloud-based automation platform with another, by parsing custom form schemas to determine form fields and dependencies, and dynamically generating client scripts to support these dependencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If virtualization software features are not well integrated with service management unit, then service accessibility is limited, but system complexity is reduced
Solution Approach 1:
An integration plugin is introduced as an intermediary component between the virtualization software and the service management unit. The plugin receives form data from the service management unit, dynamically generates client scripts based on form field dependencies, and executes these scripts to achieve seamless integration. This mediator resolves the contradiction by enabling service accessibility without requiring direct complex integration between the virtualization software and service management unit.
Solution Approach 2:
The system implements self-service through automatic client script generation and execution. When form data is submitted, the integration plugin automatically analyzes form field dependencies, generates appropriate client scripts, and executes them without manual intervention. This self-service mechanism enables the system to integrate services dynamically, improving accessibility while maintaining manageable complexity through automation.
2Adaptability or versatility
If multiple cloud platforms are integrated, then service versatility is improved, but system complexity increases
Solution Approach 1:
The integration plugin implements universality by providing a standardized interface that can integrate multiple cloud-based automation platforms (ServiceNow, VMware Aria, Microsoft Azure, AWS) through a common mechanism. The plugin receives form data in a standardized format and dynamically generates client scripts that work across different platforms, enabling service versatility without requiring separate integration solutions for each platform pair.
Solution Approach 2:
The system uses parameter changes dynamically by analyzing form field dependencies and generating client scripts with specific parameters tailored to each integration scenario. The plugin modifies script parameters based on the form data received, enabling adaptable integration across different cloud platforms without hardcoding platform-specific configurations, thus achieving versatility while managing complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An example method may include executing, using an integration plugin installed on a first cloud-based automation platform running in a first management node, a schedule job to obtain an API response from a second management node executing a second cloud-based automation platform. The API response may include a custom form schema of a first form associated with the second cloud-based automation platform in a first defined data format. Further, the method may include parsing the custom form schema to determine form fields and dependency of the form fields. Furthermore, the method may include translating the custom form schema into a second defined data format supported by the first cloud-based automation platform based on the parsed custom form schema. Further, the method may include persisting the translated custom form schema in a database associated with the first cloud-based automation platform.