Skip to main content

OpenStack Swift object storage backend for zarr

Project description

zarr-swiftstore

OpenStack Swift object storage backend for zarr v3. Enables direct read/write access to zarr datasets stored in Swift containers using python-swiftclient — no S3 compatibility layer required.

Why this library exists

zarr v3 ships with FsspecStore, which supports many cloud backends (S3, GCS, Azure) through the fsspec ecosystem. For OpenStack Swift specifically, the standard recommendation is swiftspec + FsspecStore.

However, many OpenStack deployments — particularly HPC and research clusters — expose Swift through TempAuth only, without a full Keystone identity service. In those environments:

  • S3 compat (swift3/s3api) is unusable — signing S3 requests requires a username + password (ST_USER/ST_KEY), but TempAuth deployments typically hand out pre-authenticated tokens (OS_AUTH_TOKEN + OS_STORAGE_URL) that cannot sign S3 requests.
  • s3fs/boto3 do not work for the same reason.
  • swiftspec works in principle but has seen limited maintenance since 2022.

This library uses python-swiftclient directly, which speaks the native Swift API and accepts pre-auth tokens. It is the only actively-maintained, zarr-v3-native option for these deployments.

Known deployments where this matters:

  • DKRZ (swift.dkrz.de) — uses TempAuth, provides pre-auth tokens only; S3 compat middleware is present but not accessible without signing credentials.

If your OpenStack cluster provides full Keystone and EC2 credentials, you can use zarr.storage.FsspecStore with swiftspec or s3fs instead.

See ADR 001 for the full investigation behind this decision.

Install

pip install zarr-swiftstore

Or from source with uv:

git clone https://github.com/siligam/zarr-swiftstore.git
cd zarr-swiftstore
uv sync

Usage

Authentication

Provide credentials as a storage_options dict passed to SwiftStore.

Pre-authenticated token (most common in TempAuth deployments):

import os

storage_options = {
    "preauthurl": os.environ["OS_STORAGE_URL"],
    "preauthtoken": os.environ["OS_AUTH_TOKEN"],
}

Username + password (TempAuth v1.0):

storage_options = {
    "authurl": "https://swift.example.org/auth/v1.0",
    "user": "{account}:{user}",
    "key": "{password}",
}

zarr

import zarr
from zarrswift import SwiftStore

store = await SwiftStore.open(
    container="my-container",
    prefix="zarr-demo",
    storage_options=storage_options,
)

root = zarr.open_group(store=store, mode="w")
z = root.zeros("foo/bar", shape=(10, 10), chunks=(5, 5), dtype="i4")
z[:] = 42

xarray

import numpy as np
import xarray as xr
from zarrswift import SwiftStore

store = await SwiftStore.open(
    container="my-container",
    prefix="xarray-demo",
    storage_options=storage_options,
)

ds = xr.Dataset(
    {"foo": (("x", "y"), np.random.rand(4, 5))},
    coords={"x": [10, 20, 30, 40], "y": [1, 2, 3, 4, 5]},
)
ds.to_zarr(store=store, mode="w", consolidated=True)

# load
ds = xr.open_zarr(store=store, consolidated=True)

Container utilities (ACLs, TempURLs)

from zarrswift import SwiftStore
from zarrswift.utils import is_public, toggle_public, acquire_token

store = await SwiftStore.open("my-container", storage_options=storage_options)

# Check / toggle public read access
print(is_public(store))   # False
toggle_public(store)
print(is_public(store))   # True

Running the tests

Integration tests require a live Swift service. Set the environment variables for your deployment and enable the test suite with ZARR_TEST_SWIFT=1.

Pre-auth token:

export OS_STORAGE_URL="https://swift.example.org/v1/AUTH_..."
export OS_AUTH_TOKEN="..."
export ZARR_TEST_SWIFT=1
pytest -v zarrswift

Username + password:

export ST_AUTH="https://swift.example.org/auth/v1.0"
export ST_USER="{account}:{user}"
export ST_KEY="{password}"
export ZARR_TEST_SWIFT=1
pytest -v zarrswift

For local CI without a real Swift cluster, the tests run against openstackswift/saio:

docker run -d -p 8080:8080 openstackswift/saio
export ST_AUTH=http://localhost:8080/auth/v1.0
export ST_USER=test:tester
export ST_KEY=testing
export ZARR_TEST_SWIFT=1
pytest -v zarrswift

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

zarr_swiftstore-3.0.2.tar.gz (70.8 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

zarr_swiftstore-3.0.2-py3-none-any.whl (10.8 kB view details)

Uploaded Python 3

File details

Details for the file zarr_swiftstore-3.0.2.tar.gz.

File metadata

  • Download URL: zarr_swiftstore-3.0.2.tar.gz
  • Upload date:
  • Size: 70.8 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: uv/0.6.0

File hashes

Hashes for zarr_swiftstore-3.0.2.tar.gz
Algorithm Hash digest
SHA256 d720ef4db9138a334a4ecd27f037c93efb783cf2c2235d15837ad92932241adb
MD5 d39c524d4e0ee4a257bc8041e6224872
BLAKE2b-256 9709f76ad47675d685b48bb8104969fe197adf34557070c18e2175c63fcb7cc3

See more details on using hashes here.

File details

Details for the file zarr_swiftstore-3.0.2-py3-none-any.whl.

File metadata

File hashes

Hashes for zarr_swiftstore-3.0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 55c7213ec45102fe093d2156d0ea852ab94bf0e44165127a20fa3ab7a1c80835
MD5 23f975143764315a98ef275786384d54
BLAKE2b-256 794b577e2d5d147ab7ce40dc5613487df76f1f5d48ef8bf5081afedb7f73ba16

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page