Cloud Resource Duplication Prevention via Deployment Records
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In cloud computing environments, there is a challenge in preventing the duplication of local resources when resources created by a resource provider are discovered, leading to inefficiencies and inaccuracies in resource management.
Innovation Solution
The implementation of resource provider management circuitry that includes a blueprint service to create deployment records, a catalog service to store and manage resource records, and a provider service to manage resource deployment, ensuring that resources are uniquely identified and duplicates are avoided through auto-discovery and inventory management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If resources are automatically discovered in cloud computing environments, then resource visibility and inventory accuracy are improved, but resource duplication and management inefficiencies occur
Solution Approach 1:
The system performs preliminary actions by creating deployment records in the provisioning service before resources are actually deployed to the cloud provider. This pre-registration ensures that when auto-discovery occurs, the resources are already known to the system and won't be duplicated. The blueprint service creates these deployment records as a preliminary step in the resource lifecycle management process.
Solution Approach 2:
The system implements feedback mechanisms where the provisioning service continuously monitors and discovers resources deployed by provider plugins. When resources are discovered through auto-discovery, the system checks against existing deployment records and provides feedback to prevent duplication. This closed-loop feedback ensures inventory accuracy while preventing harmful duplicate resource creation.
2Productivity
If provider plugins deploy resources directly without provisioning service involvement, then deployment speed is improved, but resource duplication and loss of control occur
Solution Approach 1:
The system requires provider plugins to perform preliminary actions by notifying the provisioning service of resource deployments. This notification mechanism ensures that even though plugins can deploy resources directly (maintaining speed), the provisioning service is informed and can track resources to prevent duplication through its discovery and inventory management processes.
Solution Approach 2:
The provisioning service acts as an intermediary between provider plugins and the resource inventory system. Plugins deploy resources directly without provisioning service involvement in the actual deployment action, but the provisioning service mediates the tracking and discovery process, ensuring resource uniqueness while maintaining deployment speed.
3Measurement precision
If comprehensive resource tracking is implemented, then inventory accuracy is improved, but system complexity increases
Solution Approach 1:
The provisioning service performs multiple functions including resource tracking, discovery, deployment record management, and duplicate prevention within a single unified system. This multi-functionality reduces overall system complexity compared to having separate specialized systems for each function, while still achieving comprehensive resource tracking and inventory accuracy.
Data Source
AI summary
Example apparatus disclosed includes at least one memory, machine readable instructions, and programmable circuitry to at least one of instantiate or execute the machine readable instructions to generate a local state for a first resource, the first resource obtained from a cloud service model associated with a registered cloud account, the first resource including a first identifier; identify a second resource from the cloud service model, the second resource including a second identifier; and catalog the second resource when the second identifier is different from the first identifier.