Virtual NOC for Cross-Cloud Hybrid Service Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Hybrid cloud computing systems face challenges in managing compatible software versions across multiple sites, leading to issues with component version incompatibilities and the lack of continuous monitoring, which complicates upgrades and can break connectivity between on-premise and cloud computing systems.
Innovation Solution
A virtual network operations center (NOC) is introduced to gather information from hybridity managers in both on-premise and cloud systems, analyze compatibility, and publish server-initiated upgrade notifications, ensuring that upgrades are compatible across sites, and revoking notifications if versions become incompatible.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If client-initiated upgrades are used, then users can upgrade components at their own pace, but users lack visibility into the entire deployment topology and cannot ensure compatibility across sites
Solution Approach 1:
A centralized upgrade coordination service is introduced as an intermediary between hybridity managers at different sites. This service maintains a holistic view of the entire deployment topology, including all hybridity managers and their dependent components across on-premise and cloud environments. When an upgrade is requested, the coordination service evaluates compatibility across the entire topology before approving or rejecting the upgrade, thus providing both user autonomy and global compatibility assurance.
2Measurement precision
If manual version tracking is performed, then users can monitor component versions, but continuous monitoring across multiple sites is not achieved and compatibility issues cannot be prevented
Solution Approach 1:
The system implements continuous automated monitoring of component versions across all sites through the upgrade coordination service. The service continuously collects version information from hybridity managers and their dependent components, maintains an up-to-date inventory of the deployment topology, and automatically evaluates compatibility when upgrades are proposed. This continuous monitoring eliminates the need for manual version tracking while accelerating upgrade deployment through automated compatibility assessment.
Solution Approach 2:
The upgrade coordination service establishes a feedback loop that continuously monitors component versions across the hybrid cloud environment. When version changes are detected or upgrade requests are received, the service automatically evaluates compatibility against the current deployment topology and provides real-time feedback on upgrade feasibility. This feedback mechanism prevents compatibility issues before they occur and enables rapid, informed upgrade decisions.
3Reliability
If holistic view of deployment topology is maintained, then compatible upgrades can be determined across sites, but system complexity increases
Solution Approach 1:
The upgrade coordination service performs multiple functions within a single centralized system: maintaining the deployment topology inventory, collecting version information from all sites, evaluating upgrade compatibility, and communicating upgrade recommendations. By consolidating these functions into a universal platform, the system achieves reliable cross-site compatibility assessment without proportionally increasing complexity, as the same infrastructure serves multiple purposes.
Data Source
AI summary
Techniques are disclosed for cross-cloud hybrid services upgradability. In one embodiment, a virtual network operations center (NOC) with a centralized view of distributed, cross-cloud hybridity manager installations is responsible for continuously gathering information on the environments of on-premise and cloud computing systems, analyzing the gathered information to identify upgrades to hybridity manager instances that are compatible with dependent components and paired hybridity manager(s), and publishing notifications of compatible upgrades to the hybridity manager instances based on the analysis. The publishing of upgrade notifications by the virtual NOC is a server-initiated upgrade that is coordinated across hybrid cloud computing system sites, in contrast to traditional isolated client-initiated upgrades. In addition, the virtual NOC may revoke previous notifications if the associated upgrade versions are no longer compatible with the dependent components and/or the paired hybridity managers.