Hybrid Cloud Drift Detection via Blueprint and Inventory Model Comparison

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In hybrid cloud environments, detecting drifts in infrastructure configurations is challenging due to manual changes and the lack of real-time synchronization between blueprint definitions and actual deployments, leading to discontinuities and resource unavailability.

Innovation Solution

A system that generates a configuration model from blueprint definitions and an inventory model of deployed resources, comparing their relationships to detect drifts and generate reports for corrective actions, ensuring synchronization and maintaining deployment integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual user input and configuration are used to install and deploy cloud components, then flexibility and adaptability are improved, but configuration accuracy and synchronization between blueprint and deployment deteriorate

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidconfiguration accuracy
Core Design Contradiction:
Adaptability or versatilityVSManufacturing precision

Solution Approach 1:

The system performs preliminary drift detection by comparing the blueprint model with the inventory model before deployment issues arise. This proactive approach identifies configuration drifts early, allowing corrective actions to be taken before they cause resource unavailability or deployment failures, thus maintaining both flexibility and accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The drift detection system continuously monitors and compares the actual deployment state against the blueprint definition, providing feedback on configuration drifts. This feedback mechanism enables automatic or manual correction of drifts, ensuring that the deployment remains synchronized with the intended configuration while preserving manual configuration flexibility.

Inventive Principle:
Principle #23Feedback

2Stability of the object's composition

If real-time synchronization between blueprint definitions and actual deployments is implemented, then deployment stability is improved, but system complexity and computational overhead increase

Engineering Contradiction:
Improvedeployment stabilityVSAvoidsystem complexity
Core Design Contradiction:
Stability of the object's compositionVSDevice complexity

Solution Approach 1:

The system performs drift detection on a partial basis, focusing on comparing specific resource attributes and relationships that are critical for deployment stability. Rather than synchronizing every possible parameter in real-time, the system identifies and monitors key drift indicators, reducing computational overhead while maintaining deployment stability.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The drift detection process is segmented into distinct phases: generating the blueprint model, generating the inventory model, comparing the two models to identify drifts, and generating corrective actions. This segmentation allows the system to manage complexity by handling each phase independently and efficiently, rather than attempting monolithic real-time synchronization.

Inventive Principle:
Principle #1Segmentation

3Reliability

If drift detection and correction mechanisms are implemented, then resource availability is improved, but detection precision and false positive rates become challenging

Engineering Contradiction:
Improveresource availabilityVSAvoiddrift detection precision
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The system generates corrective actions as part of the drift detection process, preparing remediation strategies before actual deployment failures occur. By preliminarily identifying drifts and preparing corrections, the system ensures resource availability while using the established blueprint model as a reference to maintain detection precision and minimize false positives.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11595266B2Methods and apparatus to detect drift in a hybrid cloud environment
Publication Date: 2023.02.28 VMWARE INC
  • US11595266B2 patent drawing
  • US11595266B2 patent drawing
  • US11595266B2 patent drawing

AI summary

Methods, apparatus, systems and articles of manufacture are disclosed to detect drift in a hybrid cloud environment. An example apparatus to detect drift in a hybrid cloud environment includes a configuration model determiner to, after deployment of a blueprint in the hybrid cloud environment, generate a first model including first relationships of a first plurality of resources corresponding to the blueprint, the blueprint including a plurality of properties in which at least one of the plurality of properties is agnostic of type of cloud, an inventor model determiner to generate a second model including second relationships of a second plurality of resources as deployed in the hybrid cloud environment based on the blueprint, and a drift determiner to determine a drift value based on the first relationships and the second relationships, the drift value representative of a difference between the first relationships and the second relationships.