Engine Hosting Solution for Cloud Provisioning Consistency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users face challenges in seamlessly utilizing different provisioning engines across various resource provider environments due to differences in plugins, security levels, and functionality, which limits their ability to maintain a consistent interactive experience.
Innovation Solution
An engine-agnostic engine hosting solution that allows users to select and utilize various provisioning engines, providing a control service with overlay APIs to interact with the selected engine, and managing infrastructure definitions to conform to standard formats, while retrieving plugins and features based on user instructions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users utilize different provisioning engines based on personal preferences across various resource provider environments, then user choice and customization are improved, but consistency in engine capabilities and interactive experience deteriorates
Solution Approach 1:
The patent introduces an engine hosting service as an intermediary layer between users and provisioning engines. This service provides a standardized interface and abstraction layer that allows users to select different provisioning engines while maintaining consistent interaction patterns. The engine hosting service manages the diversity of engines behind a unified facade, resolving the contradiction between user choice and capability consistency.
Solution Approach 2:
The engine hosting service is designed with universal functionality to support multiple provisioning engines through a common interface. It provides standardized operations, plugin management, and interaction patterns that work across different engine types, enabling users to access diverse engines while experiencing consistent behavior and capabilities.
2Adaptability or versatility
If users utilize different provisioning engines with different plugins and security levels, then engine functionality and customization are improved, but operational complexity and compatibility issues worsen
Solution Approach 1:
The engine hosting service acts as a mediator that manages plugin compatibility and security configurations across different provisioning engines. It provides a unified plugin interface, handles security level standardization, and resolves compatibility issues between engines and plugins, thereby reducing operational complexity while preserving engine functionality.
Solution Approach 2:
The system standardizes operational parameters, security levels, and plugin interfaces through the engine hosting service. By normalizing these parameters across different engines, the service maintains engine-specific functionality while presenting a consistent operational interface, thus reducing complexity without sacrificing versatility.
3Ease of operation
If a standardized interface is provided for multiple provisioning engines, then ease of operation and consistency are improved, but engine-specific capabilities and customization options may be limited
Solution Approach 1:
The engine hosting service segments functionality into two layers: a standardized interface layer for consistent operations and an engine-specific layer for specialized capabilities. This segmentation allows users to access common functions through a uniform interface while still enabling access to engine-specific features when needed, resolving the contradiction between ease of operation and adaptability.
Solution Approach 2:
The standardized interface is nested within the engine hosting service, which in turn nests multiple provisioning engines. This nested structure allows the standardized interface to provide consistency while the underlying engines retain their specific capabilities. The hosting service acts as a container that preserves both the uniform interface and the diverse engine functionalities.
Data Source
AI summary
Systems and methods provide for execution of different provisioning engines within a resource provider environment. A user may submit a request to provision one or more resources using a particular provisioning engine, which may include a provisioning engine that is non-native to the resource provider environment. A control plane may evaluate and transmit requests to the provisioning engine executing within the resource provider environment. Operations associated with the provisioning engine may be executed and stored within a data store, which may be processed upon completion and made accessible.


