Redfish on ZAPP

DSX plugin

Mon, 01 Jan 0001 00:00:00 +0000

The DSX plugin adds pipeline components for collecting GPU and platform power metrics from Redfish-capable DSX hosts. Use it when a ZAPP Listener needs to manage a DSX host inventory, poll Redfish metric reports, and optionally emit selected Redfish metrics as ZAPP time-series telemetry.

The current ZAPP Listener binary registers the DSX component types. If you build a custom listener image, confirm that the image includes the DSX component registrations before you use these component types in a pipeline.

Deploy ZAPP Listeners

Mon, 01 Jan 0001 00:00:00 +0000

Deploy ZAPP Listener instances after the ZAPP Aggregator is running.

For the current Redfish listener deployment, enable only the redfish listener entry and set zapp.aggregatorHost to the ZAPP Aggregator gRPC service.

Redfish listener values

Helm replaces list values as a whole. If your values file redefines zapp.listeners, include the complete Redfish listener entry, including config.pipeline.

zapp:
 enabled: true
 image:
 repository: nvcr.io/nvidia/zapp
 tag: ""
 pullPolicy: IfNotPresent

 aggregatorHost: "zapp-aggregator.<namespace>.svc.cluster.local:9991"
 metricsPort: 8888
 manifestUI: true

 listeners:
 - name: redfish
 enabled: true
 replicas: 1
 metricsPort: 8011
 config:
 pipeline: |
 metricsPort: 8011
 envPlugins:
 sensorPipeline:
 maxRedfishConnections: 1
 redfishDevices:
 - endpoint: ${secrets.redfish_endpoint}
 username: ${secrets.redfish_username}
 password: ${secrets.redfish_password}
 version: 1.11.0
 manifest:
 path: /data/redfish-sensor-manifest.yaml
 forceReload: false
 components:
 listener:
 type: udpListener
 network: udp
 address: :9091
 targets:
 - target: payloadProcessor
 cap: 1000
 leaky: true
 payloadProcessor:
 type: payloadProcessor
 timeseries:
 targets:
 - target: aggregator
 default:
 targets:
 - target: aggregator
 aggregator:
 type: aggregatorStreamer

Important fields:

DSX plugin example

Mon, 01 Jan 0001 00:00:00 +0000

Use this example to deploy a ZAPP Listener that uses DSX plugin components to collect GPU power metrics from Redfish-capable hosts.

The standard ZAPP Listener binary includes the DSX component registrations. This example configures the registered dsxMetrics component type in the listener pipeline.

Deployment pattern

Deploy the ZAPP Aggregator first. Then deploy a ZAPP Listener with a DSX pipeline.

In this pattern:

zapp.listeners defines and enables the DSX Redfish listener
dsxMetrics manages the host inventory and polls Redfish metrics
DSX_REDFISH_PROXY_ENDPOINT configures an optional deployment-wide Redfish proxy endpoint
known_sensors_file loads the chart-provided DSX sensor catalog
host_persistence_path preserves host registrations in the listener data volume
metrics_service.listen_address exposes the DSX management gRPC service inside the listener pod
aggregatorStreamer forwards time-series telemetry to the ZAPP Aggregator

Encryption Secret

The built-in DSX listener persists managed host registrations. Before you enable the listener, create a Kubernetes Secret for the persistence encryption key:

Redfish listener pipeline

Mon, 01 Jan 0001 00:00:00 +0000

A Redfish listener pipeline uses envPlugins.sensorPipeline to discover sensor metadata and a pipeline component to emit telemetry. The direct collector pattern uses redfishCollector to poll each configured baseboard management controller (BMC) and send time-series models to downstream targets.

envPlugins:
 sensorPipeline:
 maxRedfishConnections: 1
 redfishDevices:
 - endpoint: ${secrets.redfish_endpoint}
 username: ${secrets.redfish_username}
 password: ${secrets.redfish_password}
 tls:
 insecureSkipVerify: true
 manifest:
 path: /data/redfish-sensor-manifest.yaml
 forceReload: false

components:
 redfish:
 type: redfishCollector
 timeout: 30s
 samplePeriod: 5s
 targets:
 - target: aggregator
 cap: 1000
 leaky: true

Security note

Do not use tls.insecureSkipVerify: true in production. This setting disables certificate verification for Redfish connections. Use it only for local testing or lab environments with self-signed certificates. For production deployments, configure a trusted certificate authority for the BMC endpoints and leave tls.insecureSkipVerify unset or set it to false.