REST-CIM Provider Interoperability for Server Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Server devices configured to use the WSMan standard face challenges in transitioning to the REDFISH® standard due to proprietary components defined by OEM extensions, which are not configured to operate with the REDFISH® standard, necessitating a solution for CIM interoperability.
Innovation Solution
An Information Handling System (IHS) with a REST-CIM provider that converts REST requests to CIM requests, utilizing a CIM provider communication subsystem to interact with CIM providers, and converts CMPI response data to JSON objects for interoperability between the CIM and REDFISH® standards.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If server devices use the WSMan standard with CIM for management, then management interoperability is achieved, but the system cannot properly support proprietary OEM extensions defined by REDFISH standard
Solution Approach 1:
The patent introduces a REST-CIM provider as an intermediary layer between the REDFISH standard and the CIM standard. This provider receives REST requests, converts them to CIM requests, processes them through the CIM provider, and converts the responses back to REST format. This mediator enables proprietary OEM extensions to work with the standard CIM infrastructure without requiring changes to the core CIM providers.
Solution Approach 2:
The system is segmented into distinct functional layers: the REST-CIM provider handles REDFISH-specific conversions, the CIM provider handles standard CIM operations, and the underlying hardware provides raw data. This segmentation allows each layer to specialize in specific standards, enabling the system to support both WSMan and REDFISH standards simultaneously without conflict.
2Productivity
If server devices transition from WSMan to REDFISH standard, then modern management capabilities are achieved, but legacy CIM providers cannot process REDFISH requests directly
Solution Approach 1:
The REST-CIM provider serves as a translation intermediary that bridges the gap between legacy CIM providers and modern REDFISH clients. It automatically converts REST requests to CIM requests and vice versa, allowing legacy providers to continue functioning while supporting new standards without requiring direct modification of the providers themselves.
Solution Approach 2:
The system changes the interface parameters by translating between different protocol formats (REST/JSON and CIM/WMI). The REST-CIM provider modifies request and response parameters to match the expected formats of each layer, enabling seamless communication between heterogeneous systems without changing the fundamental architecture.
3Adaptability or versatility
If OEM extensions are added to REDFISH standard for proprietary components, then device-specific functionality is enabled, but compatibility with standard CIM infrastructure is reduced
Solution Approach 1:
The REST-CIM provider acts as a protective intermediary that isolates proprietary OEM extensions from the standard CIM infrastructure. It translates REDFISH extensions into CIM-compatible formats for processing and converts results back to REDFISH format for clients, ensuring that standard CIM providers remain unaffected by proprietary extensions while still enabling them to function.
Data Source
AI summary
A Common Information Module (CIM) interoperability system includes a server device coupled to a network. A remote access controller in the server device is coupled to server component(s), and includes a CIM provider coupled via a CIM provider communication subsystem to a REpresentational State Transfer (REST)-CIM provider. The REST-CIM provider receives a REST request generated by a client device and redirected to the REST-CIM provider by the server device, and converts the REST request to CIM request. The REST-CIM provider then makes a call to the CIM provider that includes the CIM request and is based on a type of HTTP method request in the REST request. When the REST-CIM provider receives a CIM response from the CIM provider, it converts Common Manageability Programming Interface (CMPI) response data in that CIM response to JavaScript Object Notation (JSON) objects, and provides the JSON objects to the server device.