feature/apt-source-release
71
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
f654076560 |
feat(apt): read the release each source names, move a file to the host's (NetOrk/netork#2614)
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 1m6s
CI / driver (pull_request) Successful in 2m28s
driver / standard (pull_request) Successful in 15s
driver / types (pull_request) Successful in 55s
driver / test (3.13) (pull_request) Successful in 1m7s
driver / test (3.12) (pull_request) Successful in 1m16s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 12s
A release upgrade leaves third-party apt sources on the old release, where they still answer and their packages stop getting updates once the vendor stops building for it: z2m-house, Ubuntu 24.04, kept Docker's source on focal and never saw a Docker newer than 28.1.1. AptReleaseMixin.get_apt_source_releases() reports the host's /etc/os-release and every enabled source apt reads, one-line and deb822, with its file, line, types, URI, suites and components. set_apt_source_release(path, release, codename) moves every suite of release in one of apt's source files to codename, once each new suite's InRelease or Release is fetched with apt-helper through apt's own proxy; where the vendor has none, nothing is written. AptProxyMixin brings it, so every apt driver has it. |
||
|
|
3422b7d030 |
Merge remote-tracking branch 'origin/main' into feat/zabbix-agent-native
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 33s
driver / security (pull_request) Successful in 1m2s
CI / driver (pull_request) Successful in 2m38s
driver / standard (pull_request) Successful in 14s
driver / lint (pull_request) Successful in 12s
driver / types (pull_request) Successful in 55s
driver / test (3.12) (pull_request) Successful in 1m10s
driver / test (3.13) (pull_request) Successful in 59s
driver / publish (pull_request) Skipped
# Conflicts: # CHANGELOG.md |
||
|
|
5217c6e333 |
feat(fixes): ZabbixAgentMixin, a native Zabbix agent for a host without a container engine (NetOrk/netork#2571)
driver / lowest (pull_request) Successful in 34s
driver / build (pull_request) Successful in 24s
driver / security (pull_request) Successful in 55s
CI / driver (pull_request) Successful in 2m20s
driver / lint (pull_request) Successful in 16s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 49s
driver / test (3.13) (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m11s
driver / publish (pull_request) Skipped
configure_zabbix_agent(settings) loads the package index where the driver can, installs ZABBIX_AGENT_PACKAGE from the host's own packages and, where those have none and settings["release"] names the server's release line, from Zabbix's repository (the driver's _add_zabbix_repository); then the driver writes the configuration and opens the firewall, and the service is enabled and restarted. Settings that do not hold raise ValueError before anything changes. zabbix_agent.py holds what is the same on every host, without I/O: the settings check, the agent's configuration with Server, ServerActive, ListenPort and Hostname set and the rest kept, and the root command that adds Zabbix's repository for Debian, Ubuntu, Raspberry Pi OS and the RHEL family, in the layout before and since 7.2. LldpAgentMixin and ZabbixAgentMixin share the start step (enable_and_restart). |
||
|
|
7051199589 |
feat(container-engine): reach rootful Podman like Docker (NetOrk/netork#818)
driver / lowest (pull_request) Successful in 37s
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m2s
CI / driver (pull_request) Successful in 2m27s
driver / lint (pull_request) Successful in 16s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 55s
driver / test (3.13) (pull_request) Successful in 1m5s
driver / test (3.12) (pull_request) Successful in 1m13s
driver / publish (pull_request) Skipped
container_engines() lists Podman with the API podman-libpod, and
open_container_engine("podman") reaches it with podman system dial-stdio
(Podman 4.0 and later). It is the host's rootful Podman: the engine of the
system's containers and of Quadlet's units, whose socket is root's. So the
connection runs every call as root (ContainerEngineConnection.privileged).
An engine is listed only when its CLI names itself on --version:
podman-docker's docker is podman, and listing it as Docker would read the
login user's rootless Podman a second time.
|
||
|
|
9ecc6823c8 |
feat(system-identity): read the system firmware with the identity
driver / lowest (pull_request) Successful in 39s
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 58s
CI / driver (pull_request) Failing after 2m17s
driver / lint (pull_request) Successful in 13s
driver / standard (pull_request) Failing after 15s
driver / types (pull_request) Successful in 52s
driver / test (3.13) (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m11s
driver / publish (pull_request) Skipped
get_system_identity() also reads bios_vendor, bios_version and bios_date from /sys/class/dmi/id, in the same round trip as the SMBIOS identity. The date is given as ISO 8601; anything that is no MM/DD/YYYY reads as empty. Only the vendors' text defaults are placeholders for the firmware: a version of "1" is a version, unlike a serial of one repeated character. Output of the three identity fields alone still parses, with the firmware empty. NetOrk/netork#2518 |
||
|
|
43e0210ff6 |
feat(config-revisions): declare a device's own configuration history
driver / lowest (pull_request) Successful in 47s
driver / build (pull_request) Successful in 34s
driver / security (pull_request) Successful in 3m34s
CI / driver (pull_request) Successful in 5m2s
driver / lint (pull_request) Successful in 13s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m3s
driver / test (3.13) (pull_request) Successful in 1m12s
driver / test (3.12) (pull_request) Successful in 1m18s
driver / publish (pull_request) Skipped
Some devices keep a copy of their configuration for every save and can go back to one. An application restores a configuration there by reverting to the revision that holds it; on OPNsense that is the only way, since its API takes no uploaded config.xml (NetOrk/netork#2511). ConfigRevisionsMixin declares get_config_revisions() (newest first, as ConfigRevisionDict) and get_config_revision(revision_id). revert_config_revision(revision_id) is a template over the driver's _revert_to_config_revision step: it refuses an id that is not in the history (UnknownConfigRevision), reads the revision before the revert can rotate it out, and afterwards checks that the newest revision holds its configuration (ConfigRevertFailed otherwise), since a device may report a revert it did not make. config_revision_content(text) is the hook where a driver leaves out what its device stamps into every save, so revisions with the same configuration compare equal. Refs NetOrk/netork#2511 |
||
|
|
b4cdcfd347 |
fix(dhcp): release an address before another reservation takes it
driver / lowest (pull_request) Successful in 45s
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m10s
CI / driver (pull_request) Successful in 3m6s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m25s
driver / test (3.13) (pull_request) Successful in 1m13s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
apply_dhcp_reservationset wrote adds first, then updates in the order of the desired set. Kea keeps addresses unique at each write, so when an address moved from one reservation to another, the reservation taking it was refused as a duplicate whenever it came first. The changes are now ordered (_dhcp_order): an update that moves a reservation off its address goes before the change that takes that address, along a chain from its free end, and adds come after every update. A swap or rotation of addresses has no such order; its changes are still tried, so a server that checks only at the commit takes them, and a refused one's [failed] line says it was a swap and with which reservations. Nothing is moved to a temporary address: the contract knows no free one, and a failed second write would leave it there. The diff is computed against one read of the reservations, shared with diff_dhcp_reservations. Refused rows still do not stop the others, the rest is committed and DhcpApplyError follows, as since 4.35.1. Closes #106 |
||
|
|
ac38c68feb |
feat(time-sync): DHCP-provided NTP servers count and are read apart
driver / lowest (pull_request) Successful in 41s
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Successful in 3m22s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m16s
driver / test (3.13) (pull_request) Successful in 1m29s
driver / test (3.12) (pull_request) Successful in 1m33s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 31s
A device that gets the site's time giver through DHCP option 42 is aligned (NetOrk/netork#2380): most clients already learn it that way. 4.35.0 switched that off on every write -- chrony's DHCP sourcedir was commented out, and systemd-timesyncd's link servers failed the verify step -- and folded DHCP's servers into ntp_servers, so an application could not tell configured from DHCP-provided servers. TimeSyncDict gains dhcp_ntp_servers (not required): the servers the device got by DHCP and uses, in its order; [] for none, absent or None where the driver cannot tell. ntp_servers keeps only the configured ones. PosixTimeSyncMixin reads chrony's sources from the DHCP client's sourcedir (CHRONY_DHCP_DIRS, /run/chrony-dhcp by default) as chronyd reads them, and systemd-timesyncd's LinkNTPServers; ntpd and OpenNTPD keep DHCP's servers in a configuration of their own, so there it is unknown. A chrony write now comments out only server, pool and peer lines and leaves every sourcedir and the DHCP client's files alone. A DHCP sourcedir that 4.35.0 commented out behind the mark is given back on the next write, with a restart, so hosts it aligned hear DHCP again. Version 4.36.0. |
||
|
|
073087da69 |
feat(time-sync): TimeSyncMixin, PosixTimeSyncMixin and the posix_tz helpers
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 1m0s
CI / driver (pull_request) Successful in 2m23s
driver / standard (pull_request) Successful in 19s
driver / lint (pull_request) Successful in 19s
driver / types (pull_request) Successful in 57s
driver / test (3.13) (pull_request) Successful in 1m4s
driver / test (3.12) (pull_request) Successful in 1m14s
driver / publish (pull_request) Skipped
netOrk gets one list of NTP servers and a time zone per site and aligns every device that differs (NetOrk/netork#2360). The contract comes first, so the drivers can be built against it at the same time (#2361): TimeSyncMixin declares get_time_sync() -> TimeSyncDict (servers in the device's order, the zone as an IANA name, synchronised, the client) and carries configure_time_sync(ntp_servers=None, timezone=None) as a fix template: None leaves a value alone, the device ends up with exactly the servers given, and a verify step reads it back. time_sync_writes says which of the two values a driver writes; anything else, an unknown zone, a malformed server or an empty list is refused before anything is written. PosixTimeSyncMixin implements it over run_command for Linux-like hosts: one reading as the login user (timedatectl, chrony's configuration and chronyc, timedatectl show-timesync, ntpd and OpenNTPD), the zone through timedatectl set-timezone, chrony's servers in a file of their own with every other source commented out, systemd-timesyncd's in a drop-in that resets NTP= and empties FallbackNTP=. ntpd and OpenNTPD are read only. posix_tz moves here from netOrk, so OpenWrt can write the POSIX rule and a switch the UTC offset and summer-time rule (parse_posix_tz). It reads the tzdata package, now a dependency. Release 4.35.0: the drivers that implement it need it on PyPI. |
||
|
|
658f1c8ab2 |
Merge remote-tracking branch 'origin/main' into feat/interrupted-pm-851
# Conflicts: # CHANGELOG.md |
||
|
|
1d71ff8f91 |
feat(ssh-server): read how sshd lets people log in
driver / lowest (pull_request) Successful in 44s
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Successful in 2m48s
driver / lint (pull_request) Successful in 15s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m10s
driver / test (3.13) (pull_request) Successful in 1m25s
driver / test (3.12) (pull_request) Successful in 1m32s
driver / publish (pull_request) Skipped
SshServerAuthMixin.get_ssh_server_auth() reads the authentication settings from sshd -T as root (password, keyboard-interactive, public key, host-based, GSSAPI, AuthenticationMethods, PermitRootLogin, UsePAM) and, with PAM on, the modules of sshd's PAM auth stack from /etc/pam.d with its includes followed. It reports the facts; whether a module is a second factor is the consumer's call. OpenSshServerMixin carries it and both read sshd -T by the same fixed command, so every driver that can harden sshd can say this too. Refs NetOrk/netork#662 |
||
|
|
58ed0f0a94 |
feat(host-status): tell an interrupted dnf, yum, apk or opkg
driver / lowest (pull_request) Successful in 39s
driver / build (pull_request) Successful in 36s
driver / security (pull_request) Failing after 1m1s
CI / driver (pull_request) Failing after 2m42s
driver / standard (pull_request) Failing after 18s
driver / lint (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m9s
driver / test (3.12) (pull_request) Successful in 1m22s
driver / test (3.13) (pull_request) Successful in 2m14s
driver / publish (pull_request) Skipped
get_host_status() read only dpkg's state. It now also reads the rpm database and dnf's history (or yum's journal), apk's installed database and opkg's status file, without root, and names the manager it read in the new package_manager field. While one of them runs, the answer is unknown, as for dpkg. Refs NetOrk/netork#851 |
||
|
|
8557710724 |
feat: where a host's logs go beyond it (4.31.0)
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 1m2s
CI / driver (pull_request) Failing after 2m23s
driver / lint (pull_request) Successful in 16s
driver / standard (pull_request) Failing after 17s
driver / types (pull_request) Successful in 1m8s
driver / test (3.13) (pull_request) Successful in 1m4s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / publish (pull_request) Skipped
get_log_sources() reads, in the same command, whether rsyslog runs, its forwarding rules (legacy @/@@/:omrelp: and RainerScript omfwd/omrelp, with selector, ruleset and whether they take every message), its imfile inputs, and whether the journal reaches it (imjournal, or imuxsock with journald's ForwardToSyslog; failing a setting, the default the distribution ships commented out). Returned as `forwarding`; parse_log_forwarding and parse_rsyslog are public (NetOrk/netork#2053). |
||
|
|
5daba5d37c |
feat: which logs a host writes, and who writes each (4.30.0)
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 33s
driver / security (pull_request) Successful in 1m14s
CI / driver (pull_request) Failing after 2m45s
driver / standard (pull_request) Failing after 19s
driver / lint (pull_request) Successful in 20s
driver / types (pull_request) Successful in 1m14s
driver / test (3.13) (pull_request) Successful in 1m11s
driver / test (3.12) (pull_request) Successful in 1m18s
driver / publish (pull_request) Skipped
LogSourcesMixin.get_log_sources() reads, in one sh -c call as root, the units journald holds entries for, the log files running processes hold open (/proc/<pid>/fd: *.log, *.log.N, anything under /var/log) with size and last write from stat -L on the descriptor, and the engine's own file of each container's output as that container's stream. Each file names the service or container of its first writer from /proc/<pid>/cgroup; a file a container writes keeps the container's own path. journald's store, deleted files and a database's write-ahead log (LevelDB's 000004.log) are left out. Without root it reads again and says so (attributed: false); a host whose find cannot list open files (busybox) raises LogSourcesUnavailable rather than reading as no files. Refs NetOrk/netork#2049 |
||
|
|
f573fa53d2 |
feat(scheduled-jobs): ScheduledJobsMixin and its POSIX implementation (#86)
driver / build (pull_request) Successful in 43s
driver / security (pull_request) Successful in 1m27s
CI / driver (pull_request) Successful in 3m11s
driver / standard (pull_request) Successful in 20s
driver / types (pull_request) Successful in 1m16s
driver / test (3.13) (pull_request) Successful in 1m18s
driver / test (3.12) (pull_request) Successful in 1m27s
driver / lowest (pull_request) Successful in 46s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 23s
What a host runs on its own schedule as one shape: cron lines, run-parts scripts, anacron, systemd timers, periodic, a platform's own jobs, Windows tasks. Every job says who owns its definition and what the driver can do to it; every write names the digest the caller saw and is refused when the host's definition changed since. PosixScheduledJobsMixin reads everything in one framed report as root, switches a cron line behind #napalm-disabled:, a timer by systemctl and a run-parts script by its execute bit, runs a job now bounded by timeout, and writes an application's job as a timer where systemd runs, else in /etc/cron.d or the user's crontab. napalm_device_types.cron parses cron expressions, gives their next runs and writes them as OnCalendar lines. get_cron_jobs and CronJobDict go: nothing called them. Version 4.26.0, so drivers can require it before the release is tagged. Closes #86 |
||
|
|
95e3aa1e26 |
feat(backup): BackupServerDriver, a role base for backup servers (#82)
driver / lowest (pull_request) Successful in 30s
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 58s
CI / driver (pull_request) Successful in 2m22s
driver / lint (pull_request) Successful in 15s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m6s
driver / test (3.13) (pull_request) Successful in 1m7s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / publish (pull_request) Skipped
A backup server keeps datastores, one backup group per source with its snapshots, and the jobs that keep them healthy: garbage collection, verify, prune, sync and tape. None of that is a pool, a volume or a replication job, so it is a role of its own instead of being bent into StorageDriver. A server that manages its own disks lists StorageDriver second. The role declares the reads (datastores, groups with their newest snapshot, a group's snapshots, jobs, remotes) and the actions (garbage collection, running a job, verifying, protecting and deleting a snapshot), which start a task and return its id for get_backup_task. The shapes live in napalm_device_types.backups. ClusterStorageDict gains an optional backup_server: which server, datastore and namespace a hypervisor's backup storage writes to, with the fingerprint it pins. Matching that to a server is the application's. |
||
|
|
2542081c6f |
feat(lldp): report the neighbour's chassis MAC in lldp_neighbors
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 31s
driver / security (pull_request) Successful in 1m13s
CI / driver (pull_request) Failing after 3m1s
driver / standard (pull_request) Successful in 20s
driver / lint (pull_request) Failing after 15s
driver / types (pull_request) Successful in 1m13s
driver / test (3.12) (pull_request) Successful in 1m19s
driver / test (3.13) (pull_request) Successful in 1m12s
driver / publish (pull_request) Skipped
An application matches an LLDP neighbour by its chassis MAC first, and napalm-linux and napalm-netgear report it as mac; the projection did not, so every driver built on it would have reported neighbours by name only (NAPALM/napalm-openwrt#31). lldp_neighbors now carries mac, lower case, when the chassis id is a MAC address (LldpNeighborDict). |
||
|
|
4427be35cc |
feat(lldp): parse lldpctl keyvalue into one row per neighbour
driver / lowest (pull_request) Successful in 50s
driver / build (pull_request) Successful in 37s
driver / security (pull_request) Successful in 1m18s
CI / driver (pull_request) Failing after 3m7s
driver / standard (pull_request) Successful in 16s
driver / lint (pull_request) Failing after 16s
driver / types (pull_request) Successful in 1m8s
driver / test (3.12) (pull_request) Successful in 1m18s
driver / test (3.13) (pull_request) Successful in 1m3s
driver / publish (pull_request) Skipped
napalm-linux, napalm-openwrt and napalm-proxmox each parsed lldpd's neighbours on their own, and the copies grouped lines by interface (two neighbours on one port merged), cut the interface name at its first dot and looked for chassis.id.value, a key lldpd never prints. The parse lives here once now: neighbours are split at their via line, the interface name runs up to the neighbour's first field, ids are read under the type lldpd prints them with, and a failed lldpctl raises. The rows project into NAPALM's two LLDP shapes with lldp_neighbors and lldp_neighbors_detail, the projection part of #10. Refs #10 |
||
|
|
516fb18c0e |
Merge remote-tracking branch 'origin/main' into feat/tls-fingerprint-tofu
driver / lowest (pull_request) Successful in 34s
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 59s
CI / driver (pull_request) Failing after 2m34s
driver / lint (pull_request) Successful in 14s
driver / standard (pull_request) Successful in 15s
driver / test (3.13) (pull_request) Successful in 1m14s
driver / types (pull_request) Failing after 1m35s
driver / test (3.12) (pull_request) Successful in 1m27s
driver / publish (pull_request) Skipped
# Conflicts: # CHANGELOG.md |
||
|
|
51e8c849bb |
Merge remote-tracking branch 'origin/main' into feat/lldp-agent-template
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 33s
driver / security (pull_request) Successful in 1m10s
CI / driver (pull_request) Successful in 2m45s
driver / standard (pull_request) Successful in 18s
driver / lint (pull_request) Successful in 14s
driver / types (pull_request) Successful in 1m6s
driver / test (3.13) (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m14s
driver / publish (pull_request) Skipped
# Conflicts: # CHANGELOG.md |
||
|
|
e98d4763f3 |
Merge remote-tracking branch 'origin/main' into feat/health-profile-unknown
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m11s
CI / driver (pull_request) Successful in 2m57s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 1m7s
driver / test (3.12) (pull_request) Successful in 1m8s
driver / test (3.13) (pull_request) Successful in 1m9s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 18s
# Conflicts: # CHANGELOG.md |
||
|
|
46c1c9dc4e |
feat: TLS certificates by trust on first use
driver / lowest (pull_request) Successful in 38s
driver / build (pull_request) Successful in 34s
driver / security (pull_request) Successful in 1m13s
CI / driver (pull_request) Failing after 3m4s
driver / standard (pull_request) Successful in 17s
driver / lint (pull_request) Successful in 20s
driver / types (pull_request) Failing after 1m10s
driver / test (3.12) (pull_request) Successful in 1m14s
driver / test (3.13) (pull_request) Successful in 1m4s
driver / publish (pull_request) Skipped
Devices ship self-signed certificates, so a driver either fails the CA check on every one of them or turns verification off and sends the login to whatever answers on the address. tls_certificates pins the certificate by its SHA-256 fingerprint instead, shaped like ssh_host_keys: the caller passes the fingerprint to expect by port (optional_args["tls_fingerprints"]), the driver refuses any other certificate before a request carries credentials, and every certificate seen goes to optional_args["tls_certificate_observer"]. Without a fingerprint the first certificate is accepted. CertificateCheck checks the certificate in a handshake of its own, then pins a requests session to it (urllib3's assert_fingerprint, direct and through a proxy), so no other host can step in between the check and the login. Refs NAPALM/napalm-hpe-aruba-procurve#17 |
||
|
|
bc17862a44 |
feat(fixes): configure_lldp_agent(interfaces) template
driver / lowest (pull_request) Successful in 30s
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 58s
CI / driver (pull_request) Successful in 2m32s
driver / standard (pull_request) Successful in 15s
driver / types (pull_request) Successful in 57s
driver / test (3.12) (pull_request) Successful in 1m7s
driver / test (3.13) (pull_request) Successful in 56s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 12s
LLDP getters used to install, start and reconfigure lldpd on their own, on every poll. Getters only read now, so starting the agent needs an action the application calls. The template installs the agent through ensure_package, has the driver write the interfaces it runs on, then enables and restarts it through manage_service. The caller names the interfaces: an agent on every interface also advertises on a WAN port. Refs NAPALM/napalm-openwrt#8 |
||
|
|
9f6ffa8a25 |
feat(snmp): let a health profile mark a value unknown
driver / lowest (pull_request) Successful in 35s
driver / build (pull_request) Successful in 27s
driver / security (pull_request) Successful in 1m1s
CI / driver (pull_request) Failing after 2m30s
driver / standard (pull_request) Failing after 15s
driver / lint (pull_request) Successful in 13s
driver / types (pull_request) Successful in 58s
driver / test (3.12) (pull_request) Successful in 1m3s
driver / test (3.13) (pull_request) Successful in 56s
driver / publish (pull_request) Skipped
SnmpValueSpec gains `unknown`. A driver whose device's agent answers a value wrongly says so in its SNMP_HEALTH_PROFILE, and the application reports no value for it instead of the standard reading or a default. OpenBSD's net-snmp reports the CPU as never idle, so a reading of ssCpuIdle shows every OpenBSD host at 100 % (NAPALM/napalm-bsd#7). |
||
|
|
4150570a94 |
feat: VMProvisionIncomplete names the VM a failed creation left behind
driver / lowest (pull_request) Successful in 37s
driver / build (pull_request) Successful in 35s
driver / security (pull_request) Successful in 1m15s
CI / driver (pull_request) Failing after 3m1s
driver / standard (pull_request) Failing after 17s
driver / lint (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m5s
driver / test (3.12) (pull_request) Successful in 1m13s
driver / test (3.13) (pull_request) Successful in 1m6s
driver / publish (pull_request) Skipped
create_vm_from_cloud_init raised a plain error once the VM existed, so the caller had no id to remove it by. The new RuntimeError carries vmid and node, with the failure as its cause; a failure before the VM exists raises as before. Refs NAPALM/napalm-proxmox#28 |
||
|
|
cb90fa9835 |
feat: SudoHistoryMixin, the sudo password left in shell histories (NetOrk/netork#1090)
driver / lowest (pull_request) Failing after 33s
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m8s
CI / driver (pull_request) Failing after 2m24s
driver / standard (pull_request) Failing after 7s
driver / types (pull_request) Successful in 1m8s
driver / test (3.12) (pull_request) Failing after 1m9s
driver / test (3.13) (pull_request) Failing after 1m3s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 20s
A driver that typed `echo '<password>' | sudo -S -p "" <command>` into an interactive shell left that line, password and all, in the login user's shell history once per command, and where only the part before the first `&&` ran as root, files root should own were left to the login user. get_history_sudo_lines() counts the lines per history file with grep -c, as the login user, without reading any back. remove_history_sudo_lines() deletes exactly those lines with sed -i, overwrites the backup with shred -u, and as root gives the driver's SUDO_ROOT_FILES back to root:root where each is a regular file, not a link, owned by the login user. It reports each file's lines before and after. Nothing goes to stdin. The driver names the marker and the files and supplies run_command. |
||
|
|
0dc1a598e2 |
Merge remote-tracking branch 'origin/main' into feat/network-target-uplinks
driver / lowest (pull_request) Successful in 32s
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Successful in 3m1s
driver / standard (pull_request) Successful in 24s
driver / lint (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m2s
driver / test (3.12) (pull_request) Successful in 1m9s
driver / test (3.13) (pull_request) Successful in 59s
driver / publish (pull_request) Skipped
# Conflicts: # CHANGELOG.md |
||
|
|
a5b7b540c6 |
feat: NetworkTargetDict.uplinks, the NICs a bridge leaves through (NetOrk/netork#1325)
driver / lowest (pull_request) Successful in 36s
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m12s
CI / driver (pull_request) Successful in 2m47s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 1m1s
driver / test (3.12) (pull_request) Successful in 1m3s
driver / test (3.13) (pull_request) Successful in 59s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
A VM on a VLAN-aware bridge without a VLAN tag only gets an address when the switch port behind the bridge carries an untagged network. To find that port, the caller needs the bridge's physical NICs: their LLDP neighbours name the switch and the port. uplinks lists them in groups, one per way out of the bridge: a bond's slaves together, a single NIC alone. A bond is one link, so a caller can let one slave's neighbour speak for the others when lldpd sees only one. Internal, VLAN and virtual ports are no uplinks. A missing key means the driver cannot tell; an empty list is a bridge without uplink. |
||
|
|
874c6c5a92 |
feat: ARP_AGE_UNKNOWN, the age of a neighbour the device does not report
driver / lowest (pull_request) Successful in 31s
driver / build (pull_request) Successful in 35s
driver / security (pull_request) Successful in 1m15s
CI / driver (pull_request) Successful in 3m3s
driver / standard (pull_request) Successful in 17s
driver / lint (pull_request) Successful in 18s
driver / types (pull_request) Successful in 1m12s
driver / test (3.12) (pull_request) Successful in 1m13s
driver / test (3.13) (pull_request) Successful in 1m8s
driver / publish (pull_request) Skipped
NAPALM requires an age on every entry of get_arp_table and get_ipv6_neighbors_table. Many devices do not report one, and drivers filled in 0.0, which means "confirmed just now". ARP_AGE_UNKNOWN (-1.0, as NAPALM's IOS driver reports) is the value for "not reported"; the README states the contract. NetOrk/netork#1327 |
||
|
|
fbd3cf0129 |
chore: Python 3.12 is the floor (NAPALM/driver-standard#6)
driver / build (pull_request) Successful in 31s
driver / security (pull_request) Successful in 1m13s
CI / driver (pull_request) Failing after 2m50s
driver / standard (pull_request) Successful in 21s
driver / types (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m2s
driver / lowest (pull_request) Failing after 30s
driver / test (3.13) (pull_request) Successful in 1m0s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
netOrk runs every driver in its own containers on Python 3.12, so 3.10 and 3.11 are no longer supported or tested. requires-python, mypy and ruff move to 3.12, along with what ruff's pyupgrade rules then rewrite. |
||
|
|
4d3574cd60 |
feat: shutdown_host and begin_stop_vm, shutting down without waiting
driver / test (3.10) (pull_request) Failing after 6s
driver / test (3.11) (pull_request) Successful in 1m13s
driver / lowest (pull_request) Successful in 43s
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m8s
CI / driver (pull_request) Failing after 2m41s
driver / lint (pull_request) Successful in 18s
driver / standard (pull_request) Successful in 20s
driver / types (pull_request) Successful in 1m4s
driver / test (3.12) (pull_request) Successful in 1m8s
driver / test (3.13) (pull_request) Successful in 1m1s
driver / publish (pull_request) Skipped
HostShutdownMixin.shutdown_host(), on DeviceTypeDriver: a device shuts itself down cleanly through its own means; declared, so hasattr says whether a driver can. There is no forced variant. VmStopRequestMixin.begin_stop_vm(name): ask for a VM's clean shutdown and return at once, for a caller that waits on a timer and reads get_vm_status instead of blocking in stop_vm. No role demands it. For netOrk's graph workflows, which switch a hypervisor off when CI has nothing for it (NetOrk/netork#1636). |
||
|
|
a07ced2df6 |
Merge branch 'main' into feat/apt-proxy-verify
driver / test (3.10) (pull_request) Successful in 50s
driver / test (3.11) (pull_request) Successful in 48s
driver / lowest (pull_request) Successful in 24s
driver / security (pull_request) Successful in 46s
driver / build (pull_request) Successful in 23s
CI / driver (pull_request) Successful in 7m2s
driver / standard (pull_request) Successful in 13s
driver / lint (pull_request) Successful in 1m24s
driver / types (pull_request) Successful in 44s
driver / test (3.12) (pull_request) Successful in 48s
driver / test (3.13) (pull_request) Successful in 41s
driver / publish (pull_request) Skipped
The NAPALM driver standard landed on main (#52, 4.21.1). apt_proxy follows it: builtin generics, strict mypy, complexity 10 at most (parse_apt_proxy, same_proxy_url and the comment-out step split into helpers), 100 % covered. Its TypedDicts live in apt_proxy.py, since models.py is over 1000 lines and may not grow. Version 4.22.0 with its CHANGELOG section. |
||
|
|
d7ec558933 |
feat: AptProxyMixin, what apt fetches through and pointing it at a proxy (NetOrk/netork#1397)
CI / test (3.10) (push) Successful in 31s
CI / test (3.11) (push) Successful in 30s
CI / test (3.13) (push) Successful in 33s
CI / test (3.10) (pull_request) Successful in 30s
CI / test (3.12) (pull_request) Successful in 29s
CI / test (3.13) (pull_request) Successful in 29s
CI / test (3.12) (push) Successful in 30s
CI / test (3.11) (pull_request) Successful in 28s
apt reads apt.conf.d in order and apt.conf last; the last value wins. The Debian installer writes its proxy into apt.conf, Ubuntu's into 90curtin-aptproxy: reading 00proxy alone missed both, and a fix that wrote 00proxy and read it back reported success while apt fetched elsewhere. - get_package_proxy_report(): apt-config dump's proxy, per-host overrides, auto-detect, every line of apt's files that sets it (in reading order, editable or inside a block), the http and https sources. - check_package_proxy(url, expect): a fetch with apt-helper, past any proxy; an HTTP error counts as an answer. - configure_package_proxy(url): write 00proxy, comment out other proxy lines, read apt's proxy back, fetch one InRelease through it. - same_proxy_url(): scheme, host and port, a trailing slash aside. A driver supplies _run_apt_command, _run_apt_root_command and _write_apt_file. Version 4.22.0. |
||
|
|
0475184684 |
chore: adopt the NAPALM driver standard
driver / test (3.10) (pull_request) Successful in 1m43s
driver / test (3.11) (pull_request) Failing after 9m18s
driver / lowest (pull_request) Failing after 1m38s
driver / security (pull_request) Failing after 4m33s
driver / build (pull_request) Failing after 1m29s
CI / driver (pull_request) Failing after 24m6s
driver / standard (pull_request) Successful in 54s
driver / lint (pull_request) Successful in 50s
driver / types (pull_request) Failing after 1m17s
driver / test (3.12) (pull_request) Failing after 1m20s
driver / test (3.13) (pull_request) Successful in 1m4s
driver / publish (pull_request) Skipped
- CI moves to .gitea/workflows/ci.yml and calls the shared driver workflow of NAPALM/driver-standard: conformance, ruff, strict mypy, tests on 3.10-3.13 and at the lowest declared versions, bandit, pip-audit, build, and on a release tag the upload to PyPI. - tests/quality_baseline.json records today's long and complex functions and the one file over 1000 lines; they may shrink, not grow. - Coverage floor 95 % (measured 95.15 %). - CHANGELOG.md starts here; project links point at git.netork.io; the license is the SPDX string PEP 639 wants. |
||
|
|
08296d0d2e |
style: ruff format and the lint rules of the driver standard
Mechanical: ruff format, and ruff check --fix with the rule set every NAPALM driver uses (E, F, I, UP, B at line length 100). typing.List/Dict/Optional become builtin generics and X | None, imports are sorted, the coding cookies are gone. Two tests that read the source text follow the new spelling. What ruff cannot fix comes in the next commit. |
||
|
|
f77091c489 |
feat: HostFirewallMixin, a Linux host's own netfilter rules (NetOrk/netork#1344)
CI / test (3.10) (push) Successful in 40s
CI / test (3.11) (push) Successful in 25s
CI / test (3.13) (push) Successful in 51s
CI / test (3.10) (pull_request) Successful in 24s
CI / test (3.12) (pull_request) Successful in 27s
CI / test (3.13) (pull_request) Successful in 25s
CI / test (3.12) (push) Successful in 25s
CI / test (3.11) (pull_request) Successful in 26s
get_host_firewall() reads `nft -j list ruleset` as root and returns every chain with its family, table, hook, priority and policy, and every rule as matches and a verdict. Rules iptables-nft wrote show their extensions in nft's JSON only as an opaque `xt`, so the tables iptables manages are taken from iptables-save instead; a legacy iptables is kept beside nft's tables, since both apply. A condition the parse does not model is an `unknown` match with its text, never left out. Without root neither tool can be read, and HostFirewallUnavailable is raised rather than a host without rules. A driver supplies only _run_host_firewall_command(command, privileged=). Version 4.21.0. |
||
|
|
cce26eff44 |
feat: ServicePackagesMixin, which packages a systemd service is (NetOrk/netork#1236)
CI / test (3.10) (push) Failing after 17s
CI / test (3.11) (push) Failing after 14s
CI / test (3.13) (push) Failing after 16s
CI / test (3.10) (pull_request) Failing after 17s
CI / test (3.12) (pull_request) Failing after 20s
CI / test (3.13) (pull_request) Failing after 26s
CI / test (3.12) (push) Failing after 15s
CI / test (3.11) (pull_request) Failing after 15s
get_service_packages() returns, per systemd service, the installed packages it is made of: the one shipping its unit file and the one shipping the binary its ExecStart runs -- not the libraries that binary links against. One read-only command: systemctl show for every loaded service unit, then one dpkg -S for all paths (each also across the /usr merge), or rpm -qf per path. The report is framed; one cut short raises. A driver supplies _run_service_packages_command, as for KernelFactsMixin. Version 4.20.0. |
||
|
|
94bf399d34 |
feat: ssh_host_keys.HostKeyCheck, trust on first use (NetOrk/netork#1167)
CI / test (3.10) (push) Successful in 35s
CI / test (3.11) (push) Successful in 41s
CI / test (3.13) (push) Successful in 33s
CI / test (3.10) (pull_request) Successful in 29s
CI / test (3.12) (pull_request) Successful in 33s
CI / test (3.13) (pull_request) Successful in 40s
CI / test (3.12) (push) Successful in 38s
CI / test (3.11) (pull_request) Successful in 28s
Drivers get the host keys to expect in optional_args["ssh_host_keys"] (by port) and report what they saw through optional_args["ssh_host_key_observer"]. With a known key, any other key is refused before authentication (SshHostKeyMismatch); without one, the first key is accepted. One implementation for paramiko (HostKeyCheck.connect) and netmiko (HostKeyCheck.netmiko + observe). A caller or driver that ignores both keys keeps working as before. Version 4.19.0. |
||
|
|
2bd7bcc77c |
feat: the configuration that says which services run together (4.17.0)
CI / test (3.10) (push) Successful in 29s
CI / test (3.11) (push) Successful in 24s
CI / test (3.13) (push) Successful in 27s
CI / test (3.10) (pull_request) Successful in 26s
CI / test (3.12) (pull_request) Successful in 27s
CI / test (3.13) (pull_request) Successful in 26s
CI / test (3.12) (push) Successful in 27s
CI / test (3.11) (pull_request) Successful in 25s
ServiceClustersMixin.get_service_clusters() -> ServiceClustersDict
{patroni, adguardhome_sync, bunkerweb}: per mechanism the clusters the
host's configuration says it belongs to, each with its members (address,
port, name, role as the mechanism words it, this_host, config_from) and the
unit or container it was read from (source).
- Patroni: scope, name and restapi.connect_address from its YAML, then the
members and roles /cluster lists from the DCS.
- adguardhome-sync: ORIGIN_URL and REPLICA*_URL; the origin pushes to each
replica.
- BunkerWeb: a worker's API_WHITELIST_IP names the manager it admits, a
manager's BUNKERWEB_INSTANCES its workers.
Two hosts answering at one virtual IP prove nothing; this is the evidence
that they run one service (NetOrk/netork#1125). One generic command for
every Linux host, filtered on the host like the virtual IPs' one:
allowlisted fields only, URLs without user:password@, DCS endpoints stay
there. Root first, then without it; None per mechanism is "did not look".
|
||
|
|
9324a5b8f1 |
feat: fix routines as templates with the caller's values; deprecate run_device_action (4.13.0)
CI / test (3.10) (push) Successful in 34s
CI / test (3.11) (push) Successful in 31s
CI / test (3.13) (push) Successful in 27s
CI / test (3.10) (pull_request) Successful in 27s
CI / test (3.12) (pull_request) Successful in 28s
CI / test (3.13) (pull_request) Successful in 27s
CI / test (3.12) (push) Successful in 31s
CI / test (3.11) (pull_request) Successful in 28s
run_device_action was a string dispatch drivers filled with an application's remediations, values hard-coded inside (community "public", the caller's address, a /24 firewall rule). napalm_device_types.fixes declares them as templates instead. A template runs declared steps in order and stops at the first failure (run_fix_steps); the driver implements the steps, or overrides the whole method where its device takes the change in one call; every value comes from the caller. - SnmpAgentMixin.configure_snmp_agent(settings): install, configure, firewall, start. The caller verifies with its own SNMP client. get_management_peer() (optional) says the address the device sees the management connection come from, for choosing allowed_sources. - EnsurePackageMixin.ensure_package(name): install only what is missing. - PackageProxyMixin.configure_package_proxy(url): declared. - ContainerEngineMixin.grant_container_engine_access(user): declared. None is mixed into a role base, so a capability check stays truthful. Closes #33 |
||
|
|
b4c4ec0b0b |
feat: SnmpHealthProfile, the OIDs a driver declares; deprecate HealthMetricsMixin (4.12.0)
CI / test (3.10) (push) Successful in 28s
CI / test (3.11) (push) Successful in 27s
CI / test (3.13) (push) Successful in 30s
CI / test (3.10) (pull_request) Successful in 29s
CI / test (3.12) (pull_request) Successful in 35s
CI / test (3.13) (pull_request) Successful in 33s
CI / test (3.12) (push) Successful in 29s
CI / test (3.11) (pull_request) Successful in 26s
Drivers no longer collect over SNMP (docs/STRUCTURE.md). A driver whose device publishes its health values under OIDs of its own declares them as SNMP_HEALTH_PROFILE: per value either scalars asked in order or a table folded by first, average or max, optionally with a pattern for text answers; memory as total with used or free, or a percentage, in KiB or bytes; and how to read the interfaces. The application polls and computes. HealthMetricsMixin.get_health_metrics now warns that it is deprecated; it goes in 5.0. Closes #32 |
||
|
|
90367c1370 |
feat: an HA pair's DHCP peers and config sync as facts (4.11.0)
CI / test (3.10) (push) Successful in 26s
CI / test (3.11) (push) Successful in 24s
CI / test (3.13) (push) Successful in 26s
CI / test (3.10) (pull_request) Successful in 26s
CI / test (3.12) (pull_request) Successful in 27s
CI / test (3.13) (pull_request) Successful in 25s
CI / test (3.12) (push) Successful in 27s
CI / test (3.11) (pull_request) Successful in 24s
get_dhcp_ha (declared on DhcpServerMixin, optional) is what a DHCP server's own HA configuration says: on or off, this server's peer name, each peer's name, role as the server words it, and HA URL. ConfigSyncMixin.get_config_sync is where a host pushes its configuration and for which services, by the names get_services reports; sync items without a service name stay visible under `unmapped`. A driver mixes it in, no role promises it. Both raise when they could not read. What the facts mean for a pair -- hot standby, which side to write to -- is the caller's (NetOrk/netork#1125). |
||
|
|
0330f17a67 |
fix: keep CARP state knowledge out of the base package (4.10.1)
CI / test (3.10) (push) Successful in 25s
CI / test (3.11) (push) Successful in 24s
CI / test (3.13) (push) Successful in 25s
CI / test (3.10) (pull_request) Successful in 26s
CI / test (3.12) (pull_request) Successful in 26s
CI / test (3.13) (pull_request) Successful in 26s
CI / test (3.12) (push) Successful in 26s
CI / test (3.11) (pull_request) Successful in 24s
carp_virtual_ip() and its state table are CARP protocol knowledge; under the agreed structure (PR #37, docs/STRUCTURE.md) the base package carries only contracts, data shapes and I/O-free reconcilers. They move to the driver that speaks CARP (napalm-opnsense). The contract stays: VirtualIpsDict.carp and VirtualIpDict.holds. Nothing used the helper yet; it was released in 4.10.0 an hour ago. netOrk #1121. |
||
|
|
4f3b88db0e |
feat: CARP addresses as virtual IPs, with their holder in the reading (4.10.0)
CI / test (3.10) (push) Successful in 27s
CI / test (3.11) (push) Successful in 24s
CI / test (3.13) (push) Successful in 25s
CI / test (3.10) (pull_request) Successful in 26s
CI / test (3.12) (pull_request) Successful in 26s
CI / test (3.13) (pull_request) Successful in 26s
CI / test (3.12) (push) Successful in 27s
CI / test (3.11) (pull_request) Successful in 24s
A firewall pair's CARP addresses are a third virtual IP mechanism. Unlike vip-manager and keepalived, a CARP reading says who holds the address: a firewall's interface list need not show it, but CARP's state names the MASTER. - VirtualIpsDict gains carp (NotRequired), VirtualIpDict gains holds (NotRequired; None leaves the holder to the interfaces). - carp_virtual_ip() shapes one address bound to a VHID: MASTER holds, BACKUP stands by, INIT and DISABLED neither run nor hold, an unknown state says nothing. The same for OPNsense and pfSense; a driver supplies the fields. netOrk #1121. |
||
|
|
fde6d717a8 |
feat: SystemIdentityMixin reads a host's SMBIOS identity (4.9.0)
What ties a server to its BMC: the BMC reports the server's serial number and system UUID, the host reads the same values from its DMI tables. Both drivers that read DMI (napalm-linux, napalm-proxmox) had a copy of the shell for it, and neither read the board serial. SystemIdentityMixin.get_system_identity() reads product_uuid, product_serial and board_serial in one framed command and returns them with vendor placeholders empty: a Supermicro board's product serial is 0123456789 on every one of them, others read "To be filled by O.E.M." or "Default string", and many cheap boards share the UUID 03000200-0400-0500-0006-000700080009. is_placeholder_identity() is the same filter for a BMC driver's side. A driver supplies only _run_system_identity_command(command, privileged=); the files are root's. |
||
|
|
a1da0337e2 |
feat: alternative fingerprint rules count once (4.8.0)
Discovery compares drivers by score divided by the most a driver could score, and that maximum summed every positive rule. Rules that never match together, such as one vendor's landing page or another's, made a driver that knows several vendors lose to one that knows none: napalm-redfish's Supermicro landing page scored 6 of 41 and lost to a bare "linux" in the same BMC's SNMP sysDescr, 5 of 18. FingerprintRule gets an optional group. rules_max_weight() sums the positive rules and counts each group once, with its strongest rule. Existing rules have no group and count as before. |
||
|
|
155b5bbbe4 |
feat!: settle the open review questions; release 4.7.0
## feat!: settle the open review questions on roles, diffs, SSH and SNMP - roles: a driver that sets ROLE itself replaces the role it inherits, so a Windows driver on OSDriver is "windows", not also "linux". - os: OSDriver's account listing is get_os_users; NAPALM's get_users has another shape and a runtime stub, so hasattr could not tell. - README: NAPALM's own getters must come from the driver or a mixin listed before the first role base; its stubs win the MRO otherwise. - firewall/DHCP diffs: an empty key, a key given twice, or one more than one live entry holds raises ValueError instead of overwriting by guess; live entries without a key are never matched. - ssh_server: only host key algorithms the host has a key for count as staying; when the keys cannot be read, the host key list is not touched. sshd_config and its copy keep their file mode (GNU and BSD stat), 644 only for a new file. - SNMP: 64-bit ifXTable octets and ifHighSpeed, with the 32-bit counters as fallback for agents without ifXTable. - pyproject: declare typing-extensions, which models.py imports. BREAKING CHANGE: OSDriver.get_users is now get_os_users; diffs raise ValueError on keys that cannot name one entry; plan_ssh_hardening removes no host key algorithm without host_keys. ## fix: tell "could not read" and "does not install" apart in update and VIP readers - package_updates: the dnf security reader records dnf's exit status and raises when it is missing or non-zero, as the apt reader does; a failed dnf no longer reads as "no security advisories". - host_status: an enabled dnf-automatic.timer counts as auto updates only with apply_updates = yes (dnf5's automatic.conf wins over dnf4's); dnf-automatic-install.timer always does. Unattended-upgrades counts only while the program is installed, not from a conffile left behind. - virtual_ips: a host with systemctl but without systemd as PID 1 reads as "did not look" (None), not as "has none". keepalived blocks whose brace is on the next line are read. BREAKING CHANGE: parse_dnf_security expects DNF_SECURITY_COMMAND's __DNF_RC marker and raises ValueError without it. |
||
|
|
e509445572 |
feat: add ManagementControllerDriver for server BMCs
A role base for baseboard management controllers (Supermicro, Dell iDRAC, HPE iLO, Lenovo XCC), reached over Redfish or IPMI, not SSH. It declares, under TYPE_CHECKING only: get_power_state, set_power_state (Redfish ResetType actions), get_hardware_inventory (CPUs, DIMMs, drives, PSUs, NICs, and the server's serial, system UUID and NIC MACs), get_event_log, get_firmware_inventory and get_management_protocols. reboot_host restarts the BMC itself (Manager.Reset), never the managed server, which goes through set_power_state. No HealthMetricsMixin and no command channel; sensors come through NAPALM's get_environment. |
||
|
|
dd8977750d |
chore: Python 3.13, mypy --strict in CI, eight bug fixes, docs
Squashes three changes: ## chore: support Python 3.13 and make mypy --strict pass in CI Add 3.13 to the CI matrix and classifiers, run mypy in CI, fix the 14 strict errors it reported, and correct the README's minimum Python. ## fix: eight bugs found in a full review, each with a regression test - channel: run_on_transport lost output sshd sent after the exit status; it now reads stdout and stderr to EOF before returning. - ssh_server: a failed way back (restore or reload) raised out of harden_ssh_server after the host was touched; it is now reported in the result, with rolled_back False. - host_status: a newer RPM kernel (RHEL, Fedora) was never seen, because its release, not its arch, followed the last "-". - package_updates: an apt line wrapped at a blank lost the blank, and with it the package. - kernel: an empty payload (gzip or base64 missing) read as a report. - listening: "[fe80::1]%eth0:546", as ss prints it, kept its brackets. - ping_sweep: a reply whose "success" was not a dict aborted the sweep. - lag: a member of unknown speed (-1) lowered the LAG's speed. ## docs: bring the README and docstrings in line with the code The firewall worked example showed the runtime stubs the README forbids; the class table missed PhoneDriver and MediaDriver; ConfigLifecycleMixin is mixed in by drivers, not by a role base; services, mac_acl and packages named a class, a key and an exception that do not exist. |
||
|
|
23c352aa8a |
feat: OpenSshServerMixin takes flagged algorithms out of what sshd offers
CI / test (3.10) (push) Successful in 23s
CI / test (3.11) (push) Successful in 22s
CI / test (3.10) (pull_request) Successful in 23s
CI / test (3.12) (pull_request) Successful in 23s
CI / test (3.12) (push) Successful in 23s
CI / test (3.11) (pull_request) Successful in 22s
ssh-audit names algorithms an SSH server should stop offering. Taking them out is the same on every OpenSSH host, so it lives here once: a driver mixes in OpenSshServerMixin and supplies run_command. harden_ssh_server reads the lists sshd really uses (sshd -T), removes the requested algorithms and writes the rest to /etc/ssh/sshd_config.d/00-netork-ssh-hardening.conf -- or, where sshd_config has no Include of that directory, rewrites sshd_config after a copy. It never removes the last algorithm of a list, nor, given the managing client's lists, the last one that client speaks. sshd -t must accept the result and sshd -T must show it; after the reload the caller's verify opens a new session, and if that fails the still-open one puts the previous state back and reloads again. Bumps to 4.5.0. NetOrk/netork#1027 |