Extensible Distributed Configuration Management via Asset Plug-ins
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing configuration management software faces challenges in managing diverse and dynamic datacenter resources due to limitations in abstraction layers, such as lack of typing and naming in script extensions and high development costs, platform specificity, and maintenance difficulties in hard-coded/native extensions, which hinder flexibility and scalability.
Innovation Solution
The implementation of an extensible distributed configuration management system using asset plug-ins and model definitions that allow conditional deployment of compatible plug-ins based on specified conditions, enabling flexible and platform-specific management of computer resources without modifying the core management software.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If script extensions are used for configuration management, then functional flexibility is improved, but typing and naming of arguments and results data is lost
Solution Approach 1:
The patent introduces an intermediary layer between the configuration management software and managed systems in the form of asset plug-ins. These plug-ins act as mediators that provide strong typing and naming conventions for arguments and results data while maintaining functional flexibility. The plug-ins are developed independently but interface through a standardized API, resolving the contradiction between flexibility and data precision.
Solution Approach 2:
The patent changes the fundamental parameters of extension mechanisms by introducing strongly-typed parameter definitions and naming conventions into the extension framework. This allows script-like flexibility while enforcing data typing and naming rules, transforming the way extensions interact with the core software.
2Manufacturing precision
If hard-coded/native extensions are used for configuration management, then typing and naming of arguments and results data is improved, but development cost and platform specificity increase
Solution Approach 1:
The patent segments the extension functionality into separate, independently developable asset plug-ins that can be created, tested, and deployed independently from the core configuration management software. This segmentation reduces development cost by allowing modular creation while maintaining strong typing and naming conventions through the standardized interface.
Solution Approach 2:
The patent creates a universal extension framework that supports multiple platforms and resource types through a common interface. Asset plug-ins can be developed for specific platforms but remain portable and functional across different environments, reducing platform specificity barriers while maintaining data precision.
3Adaptability or versatility
If hard-coded/native extensions are used for configuration management, then functionality is improved, but ease of support and upgrade in large enterprise environments deteriorates
Solution Approach 1:
The patent segments functionality into independent asset plug-ins that can be upgraded or replaced without affecting the core software or other plug-ins. This modular architecture greatly simplifies support and upgrade processes in large enterprise environments, as issues can be isolated and resolved at the plug-in level without system-wide impact.
Solution Approach 2:
The patent enables copying and replication of plug-in functionality across multiple systems. Asset plug-ins can be deployed to various managed systems, allowing consistent functionality to be replicated while maintaining independent development and update capabilities, thus improving ease of support and upgrade.
4Reliability
If hard-coded/native extensions are used for configuration management, then integration with configuration management software is improved, but ability to extend functionality by users deteriorates
Solution Approach 1:
The patent segments the extension mechanism into a standardized plug-in architecture where users can develop independent asset plug-ins that integrate with the core software through a well-defined interface. This maintains reliable integration while enabling users to extend functionality by creating their own plug-ins without modifying the core software.
Solution Approach 2:
The patent introduces asset plug-ins as intermediary components that bridge user extensions with the core configuration management software. These intermediaries provide reliable integration through standardized interfaces while giving users the flexibility to create custom functionality, effectively resolving the contradiction between integration reliability and user extendability.
Data Source
AI summary
Systems and methods for extensible distributed configuration management of computer resources are described. Examples include a computer system including a processing unit and a storage device that stores a model definition and one or more asset plug-ins (each of the one or more asset plug-ins configured to expose at least one asset object that represents a computer resource). The computer system further includes memory that stores an asset model created based at least in part on the model definition, and a network interface configured to deploy to at least one managed system a compatible asset plug-in (the model definition including at least one conditional reference to the compatible asset plug-in). If a condition specified within the asset model is satisfied the processing unit selects the compatible asset plug-in for deployment, the condition being defined within the model definition and designated as applicable to the at least one conditional reference.