Vendor Non-Specific Server Software System
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large organizations face challenges in efficiently managing and configuring computer servers from multiple vendors due to different protocols and interfaces, leading to time-consuming setup and maintenance processes for system administrators.
Innovation Solution
A software system comprising a bare metal automation interface, request processor, scheduler, vendor non-specific bare metal interface, and orchestration engine, which allows for automated configuration of multiple servers across various vendors using a web browser and REST/SOAP interface, enabling vendor-agnostic management and workflow execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If vendor-specific protocols and interfaces are used for each server, then each server can be managed with dedicated control, but the complexity of management increases and configuration becomes time-consuming
Solution Approach 1:
The patent implements a universal management interface that can manage multiple vendor-specific servers through a single standardized protocol. The system translates generic management commands into vendor-specific operations, allowing one interface to perform multiple vendor-specific functions without requiring separate management systems for each server type.
Solution Approach 2:
The patent introduces an intermediary translation layer between the standardized management interface and vendor-specific server interfaces. This mediator component receives generic configuration requests, translates them into appropriate vendor-specific commands, and manages the communication between the universal interface and multiple proprietary server systems.
2Manufacturing precision
If multiple vendor-specific interfaces are used, then each server type can be managed precisely, but the time required for setup and configuration increases
Solution Approach 1:
The patent implements preliminary action by pre-configuring translation rules and command mappings between the standardized interface and various vendor-specific protocols. The system prepares translation templates and configuration profiles in advance, so that when a new server is added, the management system can quickly match it with the appropriate pre-prepared translation rules rather than creating configurations from scratch.
Solution Approach 2:
The universal management interface performs multiple vendor-specific configuration tasks through a single standardized protocol, eliminating the need for administrators to learn and switch between multiple vendor-specific interface configurations. The system handles diverse server types with unified commands while maintaining precise configuration control.
3Productivity
If automated configuration systems are implemented, then administrative effort is reduced, but the system complexity increases
Solution Approach 1:
The automated configuration system uses an intermediary translation layer that automatically converts standardized configuration requests into vendor-specific commands. This mediator handles the complexity of multiple proprietary protocols internally, presenting a simple automated interface to administrators while managing the intricate translation processes in the background.
Solution Approach 2:
The system implements self-service automation where the management interface automatically detects server types, selects appropriate translation rules, and configures servers without requiring manual intervention. The automated system serves itself by having built-in knowledge bases of vendor-specific protocols and automatic protocol detection capabilities.
Data Source
AI summary
A computer server software system implemented on a computing device comprises a bare metal automation interface, a request processor, a scheduler, a vendor non-specific bare metal interface, and an orchestration engine. The bare metal automation interface is configured to receive requests for configuration of one or more of a plurality of servers. The request processor is configured to receive the requests from the bare metal automation interface and to forward the requests. The scheduler is configured to receive instructions from a runtime environment in which the computer server software system operates and forward the instructions. The vendor non-specific bare metal interface is configured to interface with a plurality of vendor-specific server interfaces, wherein each vendor-specific server interface communicates with a server from the specific vendor. The orchestration engine is configured to execute a workflow for the requests from the request processor and for the instructions from the scheduler.