Cloud Service for Cross-Cloud Orchestration Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud computing environments lack a standardized framework for cross-cloud instance lifecycle management, as automations defined in one data center are not accessible or executable by another, hindering operations like instance migration and health monitoring across different cloud environments.
Innovation Solution
A cloud service (CS) with a peer-to-peer (P2P) cloud orchestrator service (COS) and cloud broker service (CBS) enables cross-cloud access and execution of orchestrations, allowing P2P identification and communication routing between cloud environments, thereby leveraging existing automations for cross-cloud operations without modification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If automations are customized for each cross-cloud instance migration, then cross-cloud operations can be performed, but device complexity and implementation difficulty increase significantly
Solution Approach 1:
The patent implements a universal automation framework where a single automation definition can operate across multiple cloud environments. The system uses cloud-agnostic automation templates that can be executed on any cloud platform without customization, achieving multi-functionality. The orchestration service translates universal automation commands into cloud-specific operations, allowing the same automation to work across different clouds without modification.
Solution Approach 2:
The patent introduces an intermediary orchestration service that acts as a mediator between the automation definition and cloud-specific implementations. This intermediary layer handles the translation and adaptation, allowing automations to run across different clouds without direct customization. The orchestration service receives generic automation commands and translates them into appropriate cloud-specific operations, eliminating the need for custom automation development for each cloud platform.
2Adaptability or versatility
If instance migration is performed across different cloud environments, then operational flexibility improves, but data loss and downtime risks increase
Solution Approach 1:
The patent implements preliminary actions before instance migration by creating validation checks, backup mechanisms, and pre-migration assessments. The system performs automated validation of the target cloud environment, prepares data synchronization processes in advance, and establishes rollback procedures before the actual migration occurs. This preliminary preparation ensures data integrity and minimizes downtime during cross-cloud instance migration.
3Productivity
If cloud-specific automations are used in each data center, then local operations are optimized, but cross-cloud orchestration capability is lost
Solution Approach 1:
The patent creates universal automation templates that maintain the efficiency of cloud-specific operations while enabling cross-cloud execution. These templates are designed to be cloud-agnostic yet leverage the capabilities of each specific cloud environment when executed. The orchestration service ensures that universal automations can be deployed across multiple clouds while maintaining optimal performance for each target environment.
Data Source
AI summary
A disclosed cloud service (CS) enables cross-cloud access to data resources and cross-cloud execution of orchestrations, including automations. The CS includes a peer-to-peer (P2P) cloud orchestrator service (COS) and a cloud broker service (CBS). The COS enables P2P identification and communication routing between different cloud computing environments. The CBS enables cross-cloud access to data and orchestrations (e.g., one or more scripts, workflows, and/or scheduled jobs) from different cloud computing environments. Additionally, the data center may be configured to route all orchestration calls of a data center through the CS, such that the CS can ensure that references to local data and orchestrations are handled within the data center, while references to data and orchestrations of a different data center are suitably routed to be handled by a corresponding CS of the appropriate data center.