Helm on ZAPP

Deploy the ZAPP Aggregator

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

Deploy the ZAPP Aggregator before deploying ZAPP Listener instances.

The ZAPP Aggregator receives telemetry from listeners and exposes listener gRPC, UDP telemetry ingest, subscriber gRPC, metrics, and manifest endpoints.

ZAPP Aggregator values

Most deployments only need to review the image, replica count, ports, resources, metrics, and ServiceMonitor settings.

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

 replicas: 1
 logLevel: info
 metricsPort: 8888
 manifestUI: true

 containerPorts:
 listenerGrpc: 9991
 udpTelemetry: 9992
 clientGrpc: 9999

 serviceMonitor:
 enabled: false
 interval: 30s

Important fields:

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:

Deployment

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

Use these pages to deploy the ZAPP Aggregator and Redfish listener chart in your own infrastructure with Helm.

Deploy the ZAPP Aggregator first. Then adapt the ZAPP Listener chart for the telemetry sources in your environment and point ZAPP Listeners at the ZAPP Aggregator listener gRPC service.