Blade Server Redundancy and Configuration Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Implementing a distributed computing architecture using blade servers that is highly available and scalable, particularly for shared storage of high bandwidth real-time media data, while maintaining low costs and managing quality of service, presents challenges due to the need for efficient redundancy and configuration management.
Innovation Solution
A blade-based distributed computing system with redundant components, a centralized configuration manager for assigning high-level network addresses, and a switch that allocates bandwidth based on client requirements, along with a graphical user interface for monitoring and recovery operations, ensures high availability and scalability.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If blade servers are used to reduce costs and space, then device complexity and implementation cost are reduced, but system reliability and availability deteriorate due to the lack of redundant components
Solution Approach 1:
The system is divided into modular blade servers, each containing specific functional components (storage, processing, networking). This segmentation allows individual blades to be replaced or upgraded without affecting the entire system, maintaining reliability while keeping device complexity manageable through standardized modules.
Solution Approach 2:
The patent implements dynamic configuration parameters including virtualization settings, resource allocation parameters, and failover thresholds. These parameters can be adjusted to optimize the balance between system availability and complexity based on operational requirements, allowing the system to adapt redundancy levels dynamically.
2Reliability
If redundant components are added to achieve high availability, then system reliability is improved, but device complexity and cost increase
Solution Approach 1:
Multiple functional components are merged into integrated blade server units that combine storage, processing, and networking capabilities. This consolidation provides redundancy at the blade level rather than requiring separate redundant components for each function, reducing overall device complexity while maintaining high availability through blade-level failover.
Solution Approach 2:
The blade server architecture uses universal chassis and interface standards that allow different blade types to be interchangeably deployed. A single chassis can host multiple functional blades, and any blade can potentially replace another in case of failure, providing redundancy without requiring dedicated backup components for each specific function.
3Ease of operation
If configuration management is centralized in one location, then ease of operation is improved, but system scalability and fault tolerance deteriorate
Solution Approach 1:
A configuration management server acts as an intermediary between administrators and blade servers. This centralized mediator handles configuration tasks while implementing distributed configuration propagation, allowing easy centralized management while maintaining scalability through automated configuration distribution and local configuration caching on each blade.
Solution Approach 2:
Configuration parameters and policies are pre-configured and stored in a centralized repository before being deployed to blade servers. This preliminary action enables rapid system provisioning and scaling, as new blades can be quickly integrated by retrieving pre-configured settings rather than requiring manual configuration, thus maintaining both ease of operation and scalability.
4Ease of operation
If bandwidth is allocated equally to all clients, then ease of operation is improved, but productivity and quality of service deteriorate for high bandwidth applications
Solution Approach 1:
The system implements quality of service (QoS) policies that allocate bandwidth differently based on local conditions and application requirements. High bandwidth applications such as real-time media data transfer receive prioritized bandwidth allocation, while other applications receive standard allocation. This local quality differentiation maintains ease of operation through automated policy-based management while significantly improving productivity for bandwidth-intensive operations.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
A blade-based distributed computing system, for applications such as a storage network system, is made highly-available. The blade server integrates several computing blades and a blade for a switch that connects to the computing blades. Redundant components permit failover of operations from one component to its redundant component. Configuration of one or more blade servers, such as assignment of high level network addresses to each blade, can be performed by a centralized process, called a configuration manager, on one blade in the system. High level network addresses can be assigned using a set of sequential network addresses for each blade server. A range of high level network addresses is assigned to each blade server. Each blade server in turn assigns high level network addresses to its blades. The high level network address for each blade can be mapped to its chassis identifier and slot identifier. Configuration information also may include software version information and software upgrades. By distributing configuration information among the various components of one or more blade servers, configuration information can be accessed by any component that acts as the configuration manager.