Instance Configuration File for Cloud Infrastructure Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Collecting information associated with cloud infrastructure client instances is inefficient, requiring multiple search queries to configuration management databases, which is tedious and time-consuming.

Innovation Solution

Creating an instance configuration file that centralizes information from configuration management databases, allowing users to retrieve and view instance information without submitting multiple queries, and enabling deployment, comparison, and policy enforcement based on this file.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If multiple search queries are submitted to CMDBs to collect instance information, then complete information can be retrieved, but the process becomes inefficient and time-consuming

Engineering Contradiction:
Improveinstance information completenessVSAvoidinformation collection time
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The patent merges multiple CMDB queries into a single consolidated query mechanism. The system automatically retrieves instance information from multiple CMDBs and consolidates it into one instance configuration file, eliminating the need for users to submit multiple separate queries and manually compile the results.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The instance configuration file serves as an intermediary between the CMDBs and the user. Instead of querying multiple CMDBs directly, the system uses this configuration file as a centralized repository that automatically populates with data from multiple sources, providing users with a single point of access to all instance information.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If multiple search queries are submitted to CMDBs to collect instance information, then complete information can be retrieved, but the process becomes tedious

Engineering Contradiction:
Improveinstance information completenessVSAvoidinformation retrieval operation
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system merges multiple information retrieval operations into a single automated process. Users submit one query to retrieve instance information, and the system automatically consolidates data from multiple CMDBs into a single configuration file, dramatically simplifying the user operation.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs self-service by automatically retrieving, consolidating, and organizing instance information from multiple CMDBs without requiring user intervention. The automated generation of instance configuration files eliminates the manual effort previously needed to compile information from multiple sources.

Inventive Principle:
Principle #25Self-service

3Ease of operation

If instance information is stored in centralized configuration files, then information retrieval is simplified, but deployment complexity increases

Engineering Contradiction:
Improveinformation retrieval easeVSAvoiddeployment process complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system creates simplified copies of complex instance information from multiple CMDBs into standardized configuration files. These configuration files contain essential instance data in a uniform format that can be easily retrieved and used, while the complexity of managing multiple CMDB connections is handled by the system automatically.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11157292B2Instance mapping engine and tools
Publication Date: 2021.10.26 SERVICENOW INC
  • US11157292B2 patent drawing
  • US11157292B2 patent drawing
  • US11157292B2 patent drawing

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.