1. Introduction
Redfish defines an easy-to-use and implement RESTful interface that lets users manage a wide range of devices and environments including stand-alone servers, composable infrastructures, and large-scale cloud environments.
Redfish defines a JSON-encoded data model. Because it requires JSON representation, Redfish is easy to both interpret and integrate with programming environments. To support various schema-aware tools, the Redfish data model is schema-based and is published in the following formats:
- JSON Schema
Although the Redfish data model is schema-based, it's not necessary for new users to understand schema in order to use Redfish. This guide will show users how to navigate the Redfish model and perform common management operations.
ERMI (Edge Remote Management Interface) Architecture Overview
| Component | Stack Type | Runs On | Role / Description |
|---|---|---|---|
| Client | Control Layer | Developer Portal / Platform | Sends API commands and receives data via the ERMI API. Acts as the user interface for remote monitoring and control. |
| ERMI Module | Hardware Stack | Integrated on Jetson | Dedicated hardware for out-of-band control; operates independently from the main OS. |
| NVIDIA Jetson | Hardware Stack | - | Primary edge device running AI workloads; connects to ERMI Module for remote management support. |
| ERMI API | Software Stack | Accessed by Client | Redfish®-based API for remote control, diagnostics, and integration into third-party platforms. |
| ERMI Firmware | Software Stack | Runs on ERMI Module | Executes low-level tasks and responds to API calls for power, logs, and telemetry. |
| ERMI Daemon | Software Stack | Runs on Jetson | Collects device info and sends it to ERMI Module for API access. |