Instance Mapping Engine Consolidates CMDB Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing process of collecting information associated with cloud infrastructure client instances is inefficient, requiring multiple search queries to configuration management databases, making it tedious and time-consuming for users to retrieve and analyze instance-related data.
Innovation Solution
The system generates and saves information from configuration management databases into a centralized instance configuration file, allowing users to view and deploy instances efficiently, compare configuration files to diagnose issues, enforce policies, and determine financial costs without executing configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If multiple search queries are submitted to CMDBs to collect instance information, then comprehensive information can be retrieved, but the process becomes inefficient and time-consuming
Solution Approach 1:
The system performs preliminary actions by automatically collecting and consolidating instance information from multiple CMDBs in advance, creating a unified instance configuration file that contains all necessary information before the user needs it, eliminating the need for users to submit multiple search queries
Solution Approach 2:
The system merges information from multiple configuration management databases into a single consolidated instance configuration file, combining scattered data about database servers, application servers, and other instance components into one unified location that can be accessed with a single query
2Loss of information
If multiple search queries are submitted to CMDBs, then all instance data can be collected, but the operation becomes tedious and complex
Solution Approach 1:
The system implements self-service by automatically gathering instance information from multiple CMDBs without user intervention, generating and maintaining the consolidated instance configuration file autonomously, so users simply need to view or deploy from the pre-prepared file without performing complex collection operations
Solution Approach 2:
The system merges multiple data collection operations into a single unified process that automatically aggregates information from database servers, application servers, and other instance components into one instance configuration file, simplifying the user experience from multiple complex queries to a single simple access operation
3Ease of operation
If instance configuration information is stored in centralized instance configuration files, then data retrieval is simplified, but the system complexity increases
Solution Approach 1:
The instance configuration file acts as an intermediary layer between the multiple CMDBs and the users, consolidating and translating scattered configuration data into a unified format that simplifies user access while managing the complexity of data integration in the background through automated processes
4Reliability
If comprehensive instance information is collected and stored, then analysis and diagnostics are improved, but the time and resources required for collection increase
Solution Approach 1:
The system performs preliminary action by pre-collecting and consolidating comprehensive instance information into the instance configuration file before analysis is needed, so when users need to perform diagnostics or analysis, all necessary data is already organized and available, improving both reliability and productivity
Data Source
AI summary
The presently disclosed systems and methods collect information associated with client instances, and use the information associated with the instances. In particular, information related to database servers and/or applications servers providing the instance may be retrieved from databases that store information relating to instances, and written and saved in an instance configuration file. Moreover, instances may be deployed or provisioned by reading an instance configuration file and setting properties of the instance using the parameters saved in the instance configuration file. Two instance configuration files may be compared to determine differences between the two files. Additionally, the instance may be reverted back to the previously healthy version of the instance using the previous instance configuration file. The disclosed systems and methods also include enforcing policies related to instances, and determining financial costs associated with implementing an instance defined by an instance configuration file.