Virtual BMC Provisioning via System Control Plane Manager
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing information handling systems (IHSs) face challenges in managing virtualized environments, particularly in verifying ownership and managing hardware and software resources across multiple IHSs in a distributed environment.
Innovation Solution
The system employs a System Control Plane Manager (SCPM) to provision and manage Logical Composed Systems (LCSs) by generating a virtual Baseboard Management Controller (vBMC) that can be executed on any available IHS, enabling distributed management and resource orchestration across multiple IHSs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a vBMC is bound to a specific host IHS, then management control is simplified, but resource utilization and system flexibility deteriorate
Solution Approach 1:
The patent segments the vBMC management function by separating the vBMC instance from its host IHS. The vBMC can be independently provisioned, migrated, and managed as a separate entity through the SCPM, allowing it to be detached from any specific host while maintaining management capabilities.
Solution Approach 2:
The vBMC is designed with universal functionality to manage multiple different host IHSs rather than being dedicated to a single host. This multi-functionality allows one vBMC instance to serve multiple hosts across different physical locations, enhancing resource utilization while maintaining simplified management through the SCPM.
2Adaptability or versatility
If vBMC management is distributed across multiple IHSs, then resource utilization improves, but system complexity and verification difficulty worsen
Solution Approach 1:
The SCPM acts as an intermediary that centralizes the management of distributed vBMC instances. It provides a unified interface for provisioning, monitoring, and controlling vBMCs across multiple IHSs, thereby managing system complexity while enabling distributed resource utilization.
Solution Approach 2:
The system implements feedback mechanisms where the SCPM continuously monitors the state of distributed vBMC instances and host IHSs. This feedback enables automatic verification of ownership, resource allocation status, and system state, reducing the complexity of managing distributed components through automated control loops.
3Adaptability or versatility
If vBMC instances can migrate between hosts, then system flexibility improves, but ownership verification and security management worsen
Solution Approach 1:
The SCPM serves as a trusted intermediary that maintains authoritative records of vBMC ownership and host associations. When vBMC instances migrate between hosts, the SCPM verifies and updates ownership information, ensuring security and reliability are maintained despite the flexibility of migration.
Solution Approach 2:
The system performs preliminary ownership verification and authorization actions before allowing vBMC migration. The SCPM pre-establishes trust relationships and permissions, so that when migration occurs, ownership verification is already validated, maintaining security while enabling flexibility.
Data Source
AI summary
A method for managing an LCS includes: sending a request to a microvisor kernel (MK) of a microvisor to provision an LCS on a first IHS; initiating provisioning of the LCS based on a configuration template; receiving a notification, from the MK, specifying that the LCS has been provisioned; after the notification has been received: obtaining first metadata associated with the first IHS and second metadata associated with a second IHS; analyzing the first metadata and second metadata to extract relevant data; inferring, based on the relevant data, that the first IHS has at least the required amount of hardware resources to execute a vBMC associated with the first IHS; sending, based on the inferring, a second request to an SCP of the first IHS to generate the vBMC on the first IHS; and receiving a second notification, from the SCP, specifying that the vBMC is generated on the SCP.


