Cloud-Agnostic Instance Deployment via Orchestration Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtualized environments require modifications to accommodate different formatting, artifacts, and API calls, making it challenging to deploy virtualized instances across various cloud platforms without reconfiguration.
Innovation Solution
An orchestration system dynamically generates cloud-specific or cloud-agnostic virtualized instances by converting a standard template definition into formats supported by each virtualized environment, using APIs and operations native to those environments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If virtualized instances are modified to adhere to cloud provider-specific formatting and API calls, then deployment compatibility with that specific cloud provider is improved, but deployment complexity and time increase when moving to other cloud platforms
Solution Approach 1:
The patent introduces an intermediary layer (orchestration system with translation service) that sits between the standardized virtualized instance definition and the cloud provider-specific environments. This intermediary automatically translates and adapts the instance definitions to different cloud providers' requirements without requiring manual modification, thus maintaining deployment compatibility while avoiding instance complexity increases
Solution Approach 2:
The patent implements a universal standardized definition format (such as TOSCA) that can represent virtualized instances in a cloud-agnostic manner. This universal format serves multiple cloud providers simultaneously, allowing the same instance definition to be deployed across different platforms without modification, thereby improving adaptability while preventing complexity accumulation
2Ease of manufacture
If cloud provider-specific formatting and operations are used for virtualized instances, then deployment to that specific environment is simplified, but the ability to deploy to multiple cloud platforms is reduced
Solution Approach 1:
The patent segments the deployment process into two distinct parts: (1) a cloud-agnostic instance definition created once in standardized format, and (2) cloud-specific deployment operations handled automatically by the orchestration system. This segmentation allows the instance definition to remain simple and portable while the orchestration layer handles cloud-specific complexities, thus maintaining deployment simplicity across multiple platforms
Solution Approach 2:
The orchestration system acts as an intermediary that automatically handles cloud-specific formatting and operations. It translates the standardized instance definition into provider-specific formats and manages cloud-specific deployment steps, thereby maintaining deployment simplicity for the user while achieving multi-cloud deployability through automated adaptation
3Manufacturing precision
If manual modification of virtualized instances is performed for each cloud platform, then deployment precision for each platform is improved, but time consumption and operational effort increase
Solution Approach 1:
The patent implements preliminary automated actions through the orchestration system that prepares and translates instance definitions for specific cloud platforms before deployment. The system pre-configures cloud-specific formatting, artifacts, and API calls based on the standardized definition, ensuring deployment accuracy is achieved automatically in advance rather than through manual modification during the deployment process
Solution Approach 2:
The orchestration system provides self-service functionality by automatically detecting the target cloud platform, selecting appropriate formatting and operations, and translating the instance definition without human intervention. This self-service mechanism maintains high deployment accuracy while eliminating the time-consuming manual modification process, as the system autonomously adapts instances to each cloud platform's requirements
Data Source
AI summary
A system may receive a first definition for a virtualized instance of a network function. The first definition may include a first set of declarations in a first format that is different than respective formats supported by different virtualized environments. The system may select a first virtualized environment to run the virtualized instance based on requirements specified within the first definition, and may generate a second definition with a second set of declarations that map the first set of declarations from the first format to a second format supported by the first virtualized environment. The system may deploy the virtualized instance to the first virtualized environment using the second set of declarations from the second definition. Deploying the virtualized instance may include configuring its operation based on some of the second set of declarations matching a configuration format supported by the first virtualized environment.