5 Commits

Include renames

Author	SHA1	Message	Date
Christian Manivong	ecff2b430d	feat(vm-provision): provision FreeBSD and OpenBSD guests ... create_vm_from_cloud_init(guest_os=...) with GUEST_AGENTS from napalm-device-types 3.0 (QEMU_GUEST_AGENTS: Linux, FreeBSD, OpenBSD). An unknown guest_os is refused before anything is created. Found on FreeBSD 15.1 and OpenBSD 7.9 cloud images (NetOrk/netork#793): - OS type `other` for the BSDs. OpenBSD's qemu-ga only works over ISA serial, and only as the second port: the image keeps its console on com0, so the VM gets `serial0: socket` next to `agent: 1,type=isa`. - A BSD guest gets a network-config v2 snippet of its own (`cicustom: user=...,network=...`, MAC read back from net0). FreeBSD's nuageinit fails on the v1 Proxmox generates and then skips runcmd, which starts the guest agent. Linux keeps Proxmox's own. - Packed images (FreeBSD's .qcow2.xz) are unpacked on the node after the packed file's checksum is verified; only the unpacked file is cached. download-url unpacks ISOs only, so they always take the SSH path. Fixed on the way: - get_vm_status skipped loopback only when it was called `lo`; OpenBSD's agent lists `lo0` first, so 127.0.0.1 would have been the VM's IP. Loopback is now recognised by its address. - destroy_vm read cicustom after deleting the VM, when its config was gone, so snippets stayed on the node; it now reads them first and removes all of them (#15).	2026-10-08 07:53:58 +02:00
Christian Manivong	a13af149d9	feat(vm-provision): let Proxmox download cloud images into an import storage ... Provisioning downloaded every cloud image over SSH into /var/lib/vz/template/netork-images, on the node's root filesystem. On a small root that fills up and takes Proxmox down with it (netOrk #480). When the node has an active storage with content type "import" (Proxmox 8.2+), Proxmox now does it itself: download-url with checksum verification into that storage, then import-from as the root disk. The file is named after a hash of the full URL and reused when present. Proxmox takes the format from the extension and has no ".img", so Ubuntu's qcow2 .img is stored as .qcow2 -- a wrong guess fails at import instead of attaching a qcow2 container as a raw disk. Without an import storage, or for an image type Proxmox cannot import, the SSH download is used as before.	2026-10-02 08:59:17 +02:00
Christian Manivong	08bfb5c1c0	feat: VM snapshots and reboot_host through the API ... get_vm_snapshots, create_vm_snapshot, delete_vm_snapshot and rollback_vm_snapshot for VMs and containers, so netOrk's snapshot view works on Proxmox as it does on VMware. Proxmox lists the live state as a pseudo-snapshot named "current"; it is never reported or addressable. Containers have no RAM state, so include_memory is ignored for them. reboot_host() restarts the node with POST /nodes/{node}/status command=reboot instead of /sbin/reboot over SSH.	2026-09-24 10:00:12 +02:00
Christian Manivong	dd48d3c1e5	feat: implement the HypervisorDriver VM contract ... start_vm, stop_vm, reboot_vm, suspend_vm and get_vm_config existed only as declarations. netOrk called Proxmox's own power_vm and read a VM's raw config through _node_api(), so no other hypervisor could serve the same endpoints. These let netOrk talk to every hypervisor alike. The power methods accept a VM's name or vmid, wait for the Proxmox task, and raise ValueError/RuntimeError as the contract says instead of returning a result dict. A forced reboot of a container is stop + start, since LXC has no reset; suspending a container is refused. power_vm is unchanged for existing callers. get_vm_config moves the config parsing netOrk did in _parse_proxmox_hw_config into the driver and returns a VMConfigDict: disks with storage and size, NICs with model, MAC, bridge and VLAN, CPU topology, firmware, machine type and PCI/USB passthrough. get_vms reports vmid as a string ("100"), following napalm-device-types 2.0, still ordered numerically.	2026-09-24 09:06:59 +02:00
Christian Manivong	f3ecf14c8d	initial commit	2026-05-29 09:24:39 +02:00