Code Craft AI Interop - libvirt / KVM
The codecraftai-interop-libvirt package is the venue-specific client for libvirt-managed hypervisors (KVM/QEMU primarily, with Xen, LXC, and VirtualBox reachable through the same binding). libvirt’s wire protocol is a custom binary RPC accessed through the official libvirt-python bindings, so RestClientBase does not apply — this package is the canonical example of the “native bindings only when the protocol has no other option” branch of the cross-cutting usability commitments.
Highlights
LibvirtClient — the venue client speaking libvirt-native RPC; connection lifecycle plus host capability and node-info queries.
Network and storage management — NAT/bridged/isolated networks, storage pools, and volumes.
Domain lifecycle — define/create/start/shutdown/destroy/undefine, domain XML templating with safe parameterisation, and disk/NIC attach-detach.
Snapshots — snapshot management. (The libvirt operations exposed here are synchronous via the native binding; no asynchronous task-handle surface is provided.)
Aspects-driven transport — authentication uses the libvirt connection URI plus an ILibvirtAuthCallback; every behaviour-bearing call accepts aspects: AspectsNative = DEFAULT_LIBVIRT_ASPECTS (a libvirt-flavoured Aspects object, not AspectsRest).
Repository Structure
development/ - Runtime environment scripts.
repository-setup/ - Repository homing and setup scripts.
source/packages/ccai/interop/libvirt/ - Package source code.
source/testroots/testbase/ccai/tests/interop/libvirt/ - TestBase test roots.
specs/ - Requirements, design, and task documentation (Kiro-style).
userguide/ - Standards, conventions, and documentation.
Environment Setup
When working in a Codex container:
./development/setup-agent-container
For local development:
./repository-setup/rehome-repository
./development/setup-environment
Running Tests
source .venv/bin/activate
testbase testing run --root ./source/testroots/testbase --includes=testbase.ccai.tests
Standards and Conventions
Naming conventions: userguide/10-02-naming-conventions.rst
Code organization: userguide/10-01-code-organization.rst
Coding standards: userguide/10-00-coding-standards.rst
Additional Resources
User guide entry point: userguide/userguide.rst
Metadata
Release files for codecraftai-interop-libvirt 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| codecraftai_interop_libvirt-1.2.0.tar.gz | 30.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codecraftai_interop_libvirt-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 81.7 kB
Release files / codecraftai_interop_libvirt-1.2.0.tar.gz
| Download URL | codecraftai_interop_libvirt-1.2.0.tar.gz |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
962f782530b5cb10bcb96ba0b3fa5cdb3120c5b171b254a06e2f5b89708b9855
|
|
BLAKE2b-256 checksum How to use checksums |
b593b0a5603f58aa5730331ab443bad8c31e56cc47bfbc9c4b2a4e68bc58f4c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / codecraftai_interop_libvirt-1.2.0-py3-none-any.whl
| Download URL | codecraftai_interop_libvirt-1.2.0-py3-none-any.whl |
|---|---|
| Size | 51.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8717d91d16b7ac5d7d6114410f8f30793fe01eb72cc37bd614b02eca6fd9915f
|
|
BLAKE2b-256 checksum How to use checksums |
328d18963149e2536ee48626396b480d5e6a4c4491e7ce2561cd60ac0509f39d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for codecraftai-interop-libvirt 1.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for codecraftai_interop_libvirt-1.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.