nessie-backend-mem
The in-memory reference backend for
nessie-store — a
HashMap-backed implementation of the full VolumeBackend ⊂ SnapshotBackend ⊂ CloneBackend stack. It passes the full conformance suite and needs no privileges
or external services, so it's the zero-dependency way to script against an
ONTAP-shaped backend.
Install
pip install nessie-backend-mem # Python
cargo add nessie-backend-mem # Rust
Usage (Python)
from nessie_backend_mem import MemBackend
b = MemBackend()
vol = b.create_volume("build-cache", size_bytes=50 * 2**30)
snap = b.create_snapshot(vol["uuid"], "pre-build")
clone = b.create_clone(vol["uuid"], snap["uuid"], "build-cache-pr1234")
assert clone["clone"]["parent_volume"] == "build-cache"
Methods return plain dicts in the substrate-neutral domain shape (size_bytes,
vol_type, clone={parent_volume, parent_snapshot}) and raise NessieError on
failure. The ONTAP wire shape (size, type, clone.is_flexclone, HAL
_links) is produced by nessie-ontap-protocol.
Usage (Rust)
use nessie_backend_core::{VolumeBackend, VolumeSpec};
use nessie_backend_mem::MemBackend;
let b = MemBackend::new();
let vol = b.create_volume(VolumeSpec::named("build-cache")).unwrap();
Dual-licensed MIT OR Apache-2.0.
Metadata
Release files for nessie-backend-mem 0.4.1
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_mem-0.4.1-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for nessie_backend_mem-0.4.1-cp310-abi3-win_amd64.whl |
| nessie_backend_mem-0.4.1-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_mem-0.4.1-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
| nessie_backend_mem-0.4.1-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details for nessie_backend_mem-0.4.1-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
Total release size: 787.3 kB
Release files / nessie_backend_mem-0.4.1-cp310-abi3-win_amd64.whl
| Download URL | nessie_backend_mem-0.4.1-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 176.7 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c33997b3d6a5b7e9f1fdc202e5745ec544643d7383711b11d9d4219237cbbb85
|
|
BLAKE2b-256 checksum How to use checksums |
d8c5f7a07aaea81f2e111f65e5b5136c7bc47e33bca184ea25c2d0daba63647b
|
| 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_mem-0.4.1-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | nessie_backend_mem-0.4.1-cp310-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 305.0 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
79045fec471abe409c1afe8f7f552083db92ca77562c27d1f5b09804bd7de307
|
|
BLAKE2b-256 checksum How to use checksums |
0ecf471fd4bbc64ddaa6f16d962298587cd7f6427a5235382d7aee75692f35f0
|
| 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_mem-0.4.1-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | nessie_backend_mem-0.4.1-cp310-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 305.5 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
cb5e6a0886bf7ae65585e8be3441e1cf72a3eec4c4641a57ef199c694f6169de
|
|
BLAKE2b-256 checksum How to use checksums |
183bf3c3b0df5b76c2abc3de8b0f613b4e2ab88136c1bf68dd21fc4156d5ebed
|
| 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-mem 0.4.1
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.