napalm-qnap-qts

6 Commits

Include renames

Author	SHA1	Message	Date
Christian Manivong	a97c460cc3	feat: name no warnings and report no package proxy (0.5.0) CI / test (3.10) (push) Failing after 19s Details CI / test (3.11) (push) Failing after 17s Details CI / test (3.12) (push) Failing after 18s Details CI / test (3.10) (pull_request) Failing after 18s Details CI / test (3.11) (pull_request) Failing after 17s Details CI / test (3.12) (pull_request) Failing after 19s Details napalm-linux 0.9.0 names no warnings (netOrk #1111), so the override that kept the inherited get_device_warnings from asking for updates goes. The package proxy it now reports is switched off with the template that sets it: QTS has no apt. Requires napalm-linux 0.9.0.	2026-10-17 09:44:51 +02:00
Christian Manivong	95ec6ad33b	feat: switch off the fix templates QTS cannot take (0.4.0) CI / test (3.10) (push) Successful in 38s Details CI / test (3.11) (push) Successful in 35s Details CI / test (3.12) (push) Successful in 35s Details CI / test (3.10) (pull_request) Successful in 31s Details CI / test (3.11) (pull_request) Successful in 30s Details CI / test (3.12) (pull_request) Successful in 32s Details napalm-linux 0.8 implements napalm-device-types' fix templates. QTS has no apt, dnf or opkg and sets its SNMP agent in its own UI, so configure_snmp_agent, configure_package_proxy and ensure_package are None here: a capability check answers no instead of offering a fix that fails, as the inherited fix_snmp and fix_apt_proxy did. get_device_warnings returns nothing: the inherited one asked for updates, which is None here, and logged a TypeError on every poll. The role test follows napalm-linux's get_os_users. Closes #6. Part of #7.	2026-10-17 01:17:37 +02:00
Christian Manivong	912469bdc0	refactor!: drop the _docker_bin override CI / test (3.10) (pull_request) Successful in 29s Details CI / test (3.11) (pull_request) Successful in 27s Details CI / test (3.12) (pull_request) Successful in 29s Details CI / test (3.10) (push) Successful in 28s Details CI / test (3.11) (push) Successful in 26s Details CI / test (3.12) (push) Successful in 28s Details napalm-linux 0.3.0 drops the Docker CLI methods the override served. _container_engine_binary("docker") returns Container Station's path itself, which is all netOrk needs: it reaches the engine through open_container_engine (NetOrk/netork#765, phase 9). Requires napalm-linux >= 0.3.0. Version 0.3.0.	2026-10-08 08:43:57 +02:00
Christian Manivong	5838685690	feat: hand the container engine connection Container Station's docker CI / test (3.11) (pull_request) Successful in 27s Details CI / test (3.12) (pull_request) Successful in 30s Details CI / test (3.10) (push) Successful in 29s Details CI / test (3.11) (push) Successful in 27s Details CI / test (3.12) (push) Successful in 28s Details CI / test (3.10) (pull_request) Successful in 29s Details napalm-device-types 2.6.0 opens a host's container engine through `open_container_engine()`, and asks the driver for the binary through `_container_engine_binary()`. Under QTS docker is not on PATH; the hook now returns the path `open()` already discovers, so the Engine API stream (`<path> system dial-stdio`) and the CLI reach Container Station while callers only pass arguments (NetOrk/netork#765). Version 0.2.0, requires napalm-device-types >= 2.6.0 and napalm-linux >= 0.2.0. Refs NAPALM/napalm-device-types#17	2026-10-07 17:59:55 +02:00
Christian Manivong	b4fe7c7a91	docs: point repository URLs at the NAPALM organisation	2026-09-24 09:05:24 +02:00
christianmanivong	26d723f417	feat: initial QNAP QTS driver scaffold QTS is a Linux distribution, so the driver inherits the OS surface from LinuxDriver and adds QNAP's storage, QPKG and virtualisation layers. What is here: the class with its discovery fingerprints, per-session detection of the QTS major version and of the QPKG-local docker and virsh binaries, and explicit resolution of the MRO collisions that StorageDriver creates over LinuxDriver. What is not: the storage, QPKG and VM parsers. Those need real command output from QTS 4 and QTS 5 hardware to be written against, which is what tools/harvest.sh collects and tools/sanitize.py anonymises. Two tests are marked xfail(strict) as the specification for that work.	2026-08-21 09:53:13 +07:00