napalm-qnap-qts

4 Commits

Include renames

Author	SHA1	Message	Date
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	b4fe7c7a91	docs: point repository URLs at the NAPALM organisation	2026-09-24 09:05:24 +02:00
christianmanivong	35c47bdb24	docs: do not claim hardware testing that has not happened yet	2026-08-21 09:55:20 +07: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