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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
configure_zabbix_agent(settings)on Proxmox VE and Backup Server, for a node without a container engine (NetOrk/netork#2571).zabbix-agent, and where Debian has none, Zabbix's from its repository for the server's release line./etc/zabbix/zabbix_agentd.confgets the caller's values (the old file stays as.bak, written through_write_root_file).listen_portin ufw where the node has it. pve-firewall's rules are the operator's, as for the SNMP agent._allow_sources(allowed, port, proto)inProxmoxHostMixin; 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" onzabbix_unreachablewherever it has read no container engine on the device.Checks: ruff, mypy,
napalm-standard ratchet/checkand 665 tests are green; the new tests run on both drivers.