Application Package Translation for Late-Binding Multi-Cloud Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing technologies fail to address the need for late-binding and reconfiguration of applications in multi-cloud environments, particularly in telecommunications scenarios, where applications have specific capability requirements that are not met by general-purpose cloud platforms, and prior approaches create tight bindings between target environments and application packages, necessitating prior knowledge of cluster capabilities.
Innovation Solution
A model-based approach for late-binding and reconfiguration of applications, using capability models to modify deployment manifests dynamically based on cluster capabilities, allowing applications to be instantiated without prior knowledge of exact platform capabilities, and utilizing a translator package to abstract and customize resource types.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application packages are designed with specific capability requirements for target environments, then the applications can meet their operational needs, but tight bindings are created between target environments and application packages, necessitating prior knowledge of cluster capabilities
Solution Approach 1:
The patent segments the deployment process into distinct phases: capability modeling, capability matching, and late-binding. The capability model separates general application requirements from specific platform implementations, allowing the deployment manifest to reference abstract capabilities rather than concrete platform details. This segmentation enables applications to be deployed to different platforms without redesign.
Solution Approach 2:
The patent performs preliminary capability modeling of target platforms before application deployment. The capability model is created in advance, documenting what capabilities each platform provides. During deployment, the system matches application requirements against this pre-established capability model, enabling automated platform selection and configuration without requiring application developers to have prior knowledge of specific cluster capabilities.
2Adaptability or versatility
If general-purpose cloud platforms are used, then deployment flexibility is improved, but specific capability requirements of applications in telecommunications scenarios are not met
Solution Approach 1:
The patent creates a universal capability model that can represent both general-purpose cloud platform capabilities and telecommunications-specific platform capabilities. The deployment manifest uses abstract capability references that can be satisfied by any platform providing those capabilities, whether general-purpose or specialized. This universality allows a single application package to be deployed across diverse platforms while ensuring capability requirements are met.
Solution Approach 2:
The patent introduces a capability model as an intermediary layer between the application and the underlying platform. Instead of applications directly specifying platform-specific capabilities, they reference abstract capabilities defined in the capability model. The deployment system acts as a mediator, matching these abstract requirements against actual platform capabilities and performing the necessary binding. This intermediary approach enables both flexibility and capability fulfillment.
3Adaptability or versatility
If late-binding is implemented to reduce tight bindings, then deployment flexibility improves, but capability configuration and translation become more complex
Solution Approach 1:
The patent segments the late-binding process into distinct components: capability matching, manifest modification, and capability configuration. The deployment manifest is divided into capability declarations and capability bindings, with the bindings being generated automatically through matching. This segmentation reduces the complexity of late-binding by automating the matching process and separating concerns between application requirements and platform-specific configurations.
Solution Approach 2:
The patent implements self-service capability matching where the deployment system automatically matches application capability requirements against platform capabilities without requiring manual intervention. The system self-configures the capability bindings by comparing the capability model with the deployment manifest and automatically generating the appropriate translations. This automation reduces the operational complexity of late-binding despite the increased structural complexity of the capability model.
Data Source
AI summary
A system can identify an application package of an application that is configured to execute via a computing platform, wherein the application package comprises a deployment manifest. The system can model respective capabilities of respective computing platforms to produce capability models. The system can, based on determining to execute the application via a selected computing platform of the computing platforms, determine a capability of capabilities of the selected computing platform based on the capability models and the deployment manifest, modify the deployment manifest based on the capability to produce a modified deployment manifest, configure the capability corresponding to specifications of the application identified in the modified deployment manifest, and instantiate the application via the selected computing platform with the modified deployment manifest.