Heterogeneous System Configuration via Logical Device Mapping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Deploying information handling systems in a multi-server environment is costly and error-prone, especially in heterogeneous environments where systems vary by model, peripherals, and storage components, leading to high fixed and variable costs, as well as increased risks of deployment errors due to complex automated delivery processes.
Innovation Solution
An automated method for configuring heterogeneous systems using a logical device naming scheme that maps physical identifiers to logical and implementation identifiers, enabling late binding of configurations with zero exceptions, allowing for a single system configuration to be developed for multiple systems, reducing human interaction and deployment errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If automated delivery processes are used for heterogeneous systems, then deployment speed increases, but complexity and error risk increase
Solution Approach 1:
The patent introduces an intermediary layer consisting of abstract configuration schemas and device abstraction models that mediate between the automated delivery process and heterogeneous system devices. This intermediary layer standardizes interactions across different device types, enabling automation without proportionally increasing complexity.
Solution Approach 2:
The patent changes parameters by transitioning from concrete device-specific configurations to abstract parameter-based configurations. Configuration data is defined in terms of generic parameters and properties that can be mapped to various device types, allowing the same automated process to handle diverse hardware through parameter variation rather than process complexity.
2Manufacturing precision
If configuration binding is done early in the planning phase, then deployment precision improves, but adaptability to heterogeneous systems decreases
Solution Approach 1:
The patent segments the configuration binding process into two distinct phases: abstract schema binding in the planning phase and concrete device binding in the deployment phase. This segmentation allows precision in defining configuration structures while maintaining adaptability for specific device instances through the late binding of abstract schemas to actual devices.
Solution Approach 2:
The patent makes the configuration binding process dynamic by allowing bindings to be established, modified, and resolved at different stages based on system heterogeneity. The binding process transitions from static abstract definitions to dynamic device-specific mappings, enabling both precision and adaptability.
3Reliability
If deployment processes are customized for each system type, then deployment accuracy improves, but fixed costs increase
Solution Approach 1:
The patent creates universal configuration schemas and abstraction models that can serve multiple device types simultaneously. A single automated delivery process uses these universal schemas to accurately deploy configurations across heterogeneous systems, eliminating the need for separate customized processes for each system type while maintaining deployment accuracy.
4Adaptability or versatility
If manual deployment methods are used for heterogeneous systems, then adaptability improves, but productivity decreases
Solution Approach 1:
The patent enables self-service deployment where the system automatically discovers device types, selects appropriate abstract configuration schemas, and binds configurations to devices without manual intervention. The automated delivery process serves itself by using the device abstraction model to handle heterogeneity, maintaining both adaptability and high productivity.
Data Source
AI summary
A method for provisioning systems within a solution which includes mapping a physical identifier of a component within a system to a logical identifier of the component within a system and mapping the logical identifier of the component within a system to an implementation identifier of the component within the system. The mapping conforms to a predetermined user identifiable naming convention.