nessie-backend-core
Core domain vocabulary for nessie-store
— a cheap ONTAP on-ramp. This crate defines the substrate-neutral types and the
VolumeBackend ⊂ SnapshotBackend ⊂ CloneBackend supertrait stack that every
storage backend implements. The PyO3 bindings expose the domain vocabulary to
Python so you can script against the system (the "outside" extension surface).
Install
pip install nessie-backend-core # Python
cargo add nessie-backend-core # Rust
Usage (Python)
import nessie_backend_core as core
# A request to create a 50 GiB volume.
spec = core.VolumeSpec("build-cache", size_bytes=50 * 2**30)
print(spec) # VolumeSpec(name="build-cache", size_bytes=...)
# Declare what a backend can do — and check the tiers are self-consistent.
caps = core.Capabilities(snapshots=True, clones=True)
assert caps.is_consistent()
assert caps.snapshots and caps.clones
# A sparse PATCH (resize + set the NFS junction).
patch = core.VolumePatch(size_bytes=100 * 2**30, junction_path="/build")
assert not patch.is_empty()
Usage (Rust)
use nessie_backend_core::{Capabilities, VolumeSpec};
let spec = VolumeSpec::named("build-cache");
assert!(Capabilities::clones().is_consistent());
Dual-licensed MIT OR Apache-2.0.
Metadata
Release files for nessie-backend-core 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nessie_backend_core-0.4.0-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for nessie_backend_core-0.4.0-cp310-abi3-win_amd64.whl |
| nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details for nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
| nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details for nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
Total release size: 710.7 kB
Release files / nessie_backend_core-0.4.0-cp310-abi3-win_amd64.whl
| Download URL | nessie_backend_core-0.4.0-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 150.4 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
d98ddacf5195703b7fa1a20cd1cf7bde1ff0087dae1fadae7d36a609680ce838
|
|
BLAKE2b-256 checksum How to use checksums |
3411c71c1b10f1da377a63976ddb4ce864dbefb229d8f32b9172ad78d5697d0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 278.7 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
633d8978d74f24a95907663ac900d5a86aeca0eccb8a86387f2dd067fdbefdfc
|
|
BLAKE2b-256 checksum How to use checksums |
6d1f32ec109e9c48990d210d08afc2621fa0092de081ba3a90fc75aa82e7dafe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | nessie_backend_core-0.4.0-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 281.5 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
394ecafbec345919ac60114d1debcd9f8daa7298c30f69b21140e6cad89e891c
|
|
BLAKE2b-256 checksum How to use checksums |
88c68389b7284cd3ad48d4cb28dd9f3b81da20080ddf669652acf952e87e39a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for nessie-backend-core 0.4.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.