feat(zabbix): a native Zabbix agent on both drivers through ZabbixAgentMixin (NetOrk/netork#2571) #69

Merged
christianmanivong merged 1 commits from feat/zabbix-agent-native into main 2026-11-17 04:32:24 +00:00
Owner

configure_zabbix_agent(settings) on Proxmox VE and Backup Server, for a node without a container engine (NetOrk/netork#2571).

  • Install: Debian's zabbix-agent, and where Debian has none, Zabbix's from its repository for the server's release line.
  • Configure: /etc/zabbix/zabbix_agentd.conf gets the caller's values (the old file stays as .bak, written through _write_root_file).
  • Firewall: tcp/listen_port in ufw where the node has it. pve-firewall's rules are the operator's, as for the SNMP agent.
  • The SNMP agent's ufw step is the shared _allow_sources(allowed, port, proto) in ProxmoxHostMixin; the rule for udp/161 is the same.

Needs napalm-device-types 4.40.0 (ZabbixAgentMixin, NAPALM/napalm-device-types#124). netOrk asks for it in "Install agent" on zabbix_unreachable wherever it has read no container engine on the device.

Checks: ruff, mypy, napalm-standard ratchet/check and 665 tests are green; the new tests run on both drivers.

`configure_zabbix_agent(settings)` on Proxmox VE and Backup Server, for a node without a container engine (NetOrk/netork#2571). - **Install:** Debian's `zabbix-agent`, and where Debian has none, Zabbix's from its repository for the server's release line. - **Configure:** `/etc/zabbix/zabbix_agentd.conf` gets the caller's values (the old file stays as `.bak`, written through `_write_root_file`). - **Firewall:** tcp/`listen_port` in ufw where the node has it. pve-firewall's rules are the operator's, as for the SNMP agent. - The SNMP agent's ufw step is the shared `_allow_sources(allowed, port, proto)` in `ProxmoxHostMixin`; the rule for udp/161 is the same. Needs napalm-device-types 4.40.0 (`ZabbixAgentMixin`, NAPALM/napalm-device-types#124). netOrk asks for it in "Install agent" on `zabbix_unreachable` wherever it has read no container engine on the device. **Checks:** ruff, mypy, `napalm-standard ratchet`/`check` and 665 tests are green; the new tests run on both drivers.
christianmanivong added 1 commit 2026-11-17 04:11:59 +00:00
feat(zabbix): a native Zabbix agent on both drivers through ZabbixAgentMixin (NetOrk/netork#2571)
driver / standard (pull_request) Successful in 17s
driver / lint (pull_request) Successful in 13s
driver / types (pull_request) Successful in 46s
driver / test (3.12) (pull_request) Successful in 57s
driver / lowest (pull_request) Successful in 26s
driver / test (3.13) (pull_request) Successful in 54s
driver / build (pull_request) Successful in 24s
driver / security (pull_request) Successful in 48s
CI / driver (pull_request) Successful in 2m13s
driver / publish (pull_request) Skipped
92108f0ff3
A node runs no container engine. configure_zabbix_agent(settings) installs
Debian's zabbix-agent, and where Debian has none, Zabbix's from its repository
for the server's release line. It writes the caller's values into
/etc/zabbix/zabbix_agentd.conf (the old file stays as .bak) and opens
tcp/ListenPort in ufw where the node has it; pve-firewall's rules are the
operator's, as for the SNMP agent.

The SNMP agent's ufw step is the shared _allow_sources(allowed, port, proto) in
ProxmoxHostMixin now; the rule it writes for udp/161 is the same.
Needs napalm-device-types 4.40.0.
christianmanivong merged commit 449230c624 into main 2026-11-17 04:32:24 +00:00
christianmanivong deleted branch feat/zabbix-agent-native 2026-11-17 04:32:24 +00:00
Sign in to join this conversation.