RAC Coordination of Server–Component OS Boot and Shutdown
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information handling systems, particularly servers, face challenges in managing and synchronizing boot and shutdown processes due to the inefficiencies in remote access controllers (RACs) that require unnecessary memory and lack customization options, leading to increased complexity and licensing costs.
Innovation Solution
Implementing a system where a private cloud server manages and provides services to remote access controllers, allowing for a minimal set of features in the RAC with additional services retrieved from an external cloud, enabling granular subscription-based licensing and seamless management across server generations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If RAC includes full service functionality locally, then service availability is improved, but device complexity and memory requirements increase
Solution Approach 1:
The system divides service functionality into two segments: core RAC services run locally on the RAC device, while additional management services are separated and executed remotely on external servers. This segmentation allows the RAC to maintain basic functionality with reduced complexity while external servers provide extended services, resolving the contradiction between service availability and device complexity.
Solution Approach 2:
An external server acts as an intermediary between the RAC and additional service functionalities. The RAC communicates with the external server to access extended services without having to include all service logic locally. This intermediary approach enables service availability while keeping the RAC device simple and lightweight.
2Adaptability or versatility
If RAC includes all features locally, then functionality is improved, but licensing costs and customization flexibility worsen
Solution Approach 1:
The system implements dynamic service provisioning where services can be added, removed, or modified on external servers without changing the RAC hardware or firmware. This dynamic approach allows the functionality to adapt to different licensing scenarios and customization needs, maintaining versatility while simplifying licensing management at the device level.
Solution Approach 2:
The external server infrastructure provides universal service delivery capabilities that can support multiple different service types and licensing models through a single platform. This multi-functionality approach allows the system to provide diverse functionalities while maintaining a simple, standardized RAC device design that doesn't require complex licensing logic built into each device.
3Adaptability or versatility
If RAC has extended functionality, then service capabilities are improved, but memory requirements increase
Solution Approach 1:
The system extracts service functionality from the RAC device memory and relocates it to external server memory. The RAC retains only essential services in its local memory, while extended service capabilities are taken out and hosted externally. This extraction resolves the contradiction by providing extended service capabilities without increasing RAC memory requirements.
4Ease of operation
If RAC manages boot/shutdown independently, then operational autonomy is improved, but synchronization reliability with components worsens
Solution Approach 1:
The system implements feedback mechanisms where the RAC communicates boot and shutdown status to external servers, and receives coordination instructions in return. This feedback loop allows the RAC to maintain operational autonomy in executing boot/shutdown operations while ensuring synchronization with component operating systems through continuous status exchange and coordinated control, resolving the contradiction between autonomy and synchronization reliability.
Data Source
AI summary
In one or more embodiments, a server may have a server operating system (OS) and a component with a component OS. During a boot process, embodiments may ensure the server OS does not boot until after the component OS boots. During a shutdown process, embodiments may ensure the server OS does not shut down until after the component OS shuts down. In systems with multiple Remote Access Controller, embodiments may synchronize processing between the two RACs.