EXTENSIONS
Lima
One dedicated Linux VM on a Mac, owned and driven through Lima. Renders the whole configuration from pinned inputs instead of inheriting Lima's default template, so the guest gets no host home, no agent or X11 forwarding, no host keys, no proxy environment, and no port that was not listed. Ownership is a marker this model wrote; a VM that merely shares the name is left alone. Drift is reported as replacement-required and never repaired in place, a failed create deletes nothing, and destroy is a separate door that wants the exact name, a stopped VM, and a preservation decision.
Xen Orchestra
Xen Orchestra (XO) / XCP-NG VM lifecycle model over the REST API (/rest/v0): create a VM from a template with cloud-init, start, stop (clean/hard), snapshot, migrate (cross-host/pool with SR + VIF remap), clone, and destroy, plus VM/host/template/pool/SR/network discovery so UUIDs are resolved rather than hardcoded. Disk provisioning: createVdi creates a blank VDI on an SR (POST /vdis), importFromUrl imports a disk image from a URL into an SR as a new VDI, and attachVdi/detachVdi attach/detach an existing VDI to a VM as a VBD — so a cloud image can be seeded onto a pool that lacks it and booted (import the disk, create a diskless VM with cloud-init, attach the VDI as the bootable boot disk, start), or a dedicated data disk stood up (createVdi then attachVdi). Registers XCP-NG hosts with XO (addServer/listServers) so new pools become migrate targets. Token auth via the `authenticationToken` cookie (vaulted); plain HTTPS through one injectable fetch seam, TLS verification always on (optional private-CA trust via caCert).
Exe Dev/vm
exe.dev VM lifecycle model. Wraps the exe.dev HTTPS API to manage VMs as
Libvirt
Comprehensive libvirt/virsh management — VMs, networks, storage pools,
Firecracker
Firecracker microVM lifecycle management via SSH + the Unix-socket REST API.
Kubevirt
Install and upgrade KubeVirt on an existing Kubernetes cluster from a SHA-256-pinned operator manifest, and manage one VirtualMachine from a digest-pinned containerDisk image or a CDI DataVolume. Two model types over kubectl, with the kubeconfig supplied as a vault reference and never placed on a command line.
Azure
Azure infrastructure management via az CLI — 43 model types covering compute, networking, data, security, RBAC, Azure Policy, Defender for Cloud, Entra directory, monitoring, DNS, DevOps, Azure AI Foundry (accounts, model deployments, projects, quota), AI Search, Cosmos DB, PostgreSQL Flexible Server, Static Web Apps, Service Bus, Event Grid, Recovery Services, Log Analytics, subscription-wide topology with Mermaid diagrams and cost estimation, actual-spend cost analysis and waste auditing via Cost Management/Resource Graph/Advisor, and the Azure AI Vision Face REST API for identity-aware room services.
Libvirt Vm Pool
Desired-state local libvirt VM pool reconciler for Swamp. Defines, starts, removes, and publishes per-VM connection facts for downstream SSH/config models.
Colima
Lifecycle management for a Colima VM (macOS container runtime, https://github.com/abiosoft/colima) via the local colima CLI: start and provision, stop, restart, delete, sync VM status, and exec commands inside the VM. One model instance targets one Colima profile.
Arch Cloud Init
Convenience Arch Linux VM image preparer for Swamp: downloads the Arch cloud image, creates a qcow2 overlay, and writes a NoCloud seed ISO.
Qcow2 Overlay Prep
Generic qcow2 base image downloader and overlay disk preparer for Swamp.
Cloud Init Nocloud
Generic cloud-init NoCloud seed ISO generator for Swamp. Renders user-data, meta-data, and optional network-config into an ISO 9660 image with CIDATA volume label, optionally writing the ISO to a host filesystem path.
Phenix
Full sceptre-phenix control via the HTTP API, split into six models — config, experiment, scorch, vm, cluster and user: config CRUD (Topology/Scenario/Experiment/Image/User), the experiment lifecycle (create/start/stop/delete, schedule, apps, topology, files, trigger), scorch run control (start, poll-to-completion, status, cancel, output tarballs), VM control (inventory, reconfigure, power, snapshots, captures, commit), and cluster/server reads (hosts, disks, apps, topologies, version, features, settings) plus identity (users, roles, long-lived tokens).
Minimega
Full minimega control via its command socket (or `minimega -e`), split into eight models — vm, vmconfig, namespace, network, cc, disk, mesh and host: VM lifecycle (launch/start/stop/kill, info, tags, net, screenshots), the launch config template, namespaces and the scheduler, networking (bridges, taps, VLANs, QoS, captures, router, dnsmasq), command-and-control (miniccc), disk images, the mesh/deploy fabric, and host/system ops (host, check, version, files, vnc, logging) plus a generic command passthrough.