Hardware Observer
| Channel | Revision | Published | Runs on |
|---|---|---|---|
| latest/stable | 762 | 08 Jan 2026 | |
| latest/stable | 761 | 08 Jan 2026 | |
| latest/stable | 760 | 08 Jan 2026 | |
| latest/stable | 759 | 08 Jan 2026 | |
| latest/stable | 758 | 08 Jan 2026 | |
| latest/stable | 757 | 08 Jan 2026 | |
| latest/stable | 756 | 08 Jan 2026 | |
| latest/stable | 755 | 08 Jan 2026 | |
| latest/stable | 754 | 08 Jan 2026 | |
| latest/stable | 753 | 08 Jan 2026 | |
| latest/stable | 752 | 08 Jan 2026 | |
| latest/stable | 751 | 08 Jan 2026 | |
| latest/stable | 15 | 17 Jan 2025 | |
| latest/candidate | 762 | 11 Dec 2025 | |
| latest/candidate | 761 | 11 Dec 2025 | |
| latest/candidate | 760 | 11 Dec 2025 | |
| latest/candidate | 759 | 11 Dec 2025 | |
| latest/candidate | 758 | 11 Dec 2025 | |
| latest/candidate | 757 | 11 Dec 2025 | |
| latest/candidate | 756 | 11 Dec 2025 | |
| latest/candidate | 755 | 11 Dec 2025 | |
| latest/candidate | 754 | 11 Dec 2025 | |
| latest/candidate | 753 | 11 Dec 2025 | |
| latest/candidate | 752 | 11 Dec 2025 | |
| latest/candidate | 751 | 11 Dec 2025 | |
| latest/candidate | 15 | 02 Jan 2025 | |
| latest/edge | 774 | 22 Dec 2025 | |
| latest/edge | 773 | 22 Dec 2025 | |
| latest/edge | 772 | 22 Dec 2025 | |
| latest/edge | 771 | 22 Dec 2025 | |
| latest/edge | 770 | 22 Dec 2025 | |
| latest/edge | 769 | 22 Dec 2025 | |
| latest/edge | 768 | 22 Dec 2025 | |
| latest/edge | 767 | 22 Dec 2025 | |
| latest/edge | 766 | 22 Dec 2025 | |
| latest/edge | 765 | 22 Dec 2025 | |
| latest/edge | 764 | 22 Dec 2025 | |
| latest/edge | 763 | 22 Dec 2025 | |
| latest/edge | 15 | 03 Nov 2023 |
juju deploy hardware-observer
Deploy universal operators easily with Juju, the Universal Operator Lifecycle Manager.
Platform:
DCGM snap tracks
DCGM snap is splitted into different tracks depending on the CUDA version. Each driver version corresponds to a specific CUDA version. Check the upstream documentation for more information.
| Track | CUDA Versions |
|---|---|
| v3 | 10, 11, 12 |
| v4-cuda-11 | 11 |
| v4-cuda-12 | 12 |
| v4-cuda-13 | 13 |
DCGM V3
From revision 113 to 570, the charm config dcgm-snap-channel defaults to latest/stable which installs DCGM v3 and is compatible with CUDA versions 10, 11 and 12.
DCGM V4
DCGM v4 is no longer shipped in a single monolithic package. Instead, installation assets have been split among several packages, allowing clients to opt-out of the installation of assets not applicable to their use case.
dcgm-snap-channel options
auto
Beginning from revision 571, the default value for dcgm-snap-channel is auto. With this option the charm automatically detects the installed NVIDIA driver version and selects the appropriate snap track.
v3
If for some reason users want to be strictly on v3, it’s possible to set the dcgm-snap-channel to v3/stable, v3/candidate or v3/edge . This will force units to use DCGM on v3. If for some reason the snap is already running on v4 or incompatible with v3, the unit will set blocked status.
v4
The dcgm-snap-channel accepts v4/stable, v4/candidate or v4/edge. This option forces units to use DCGM v4 and if the snap is running v3 or incompatible with v4, the unit will set blocked status.
Upgrade Behavior
When upgrading to revision > 571 if the default value of dcgm-snap-channel was not changed, the charm will switch to auto.
This means the DCGM snap will automatically upgrade to v4 with the corresponding track based on the detected driver version.
If the installed driver is CUDA 10 compatible, the charm will continue using v3/stable instead of upgrading to v4.