cradox
Python libraries for the Ceph librados library with use cython instead of ctypes
This a standalone library identical to this Ceph PR https://github.com/ceph/ceph/pull/7621
But this can be used with older version of Ceph from 0.80.X (firefly) to 10.0.X (perhaps more not tested)
This is designed for application that only want to use the Rados API, this can’t be used with the ceph rbd.py or librbdpy
The API of this python lib is identical to the Ceph rados.py API. More detail can be found on https://github.com/ceph/ceph/pull/7621.
Free software: LGPL 2.1
Documentation: http://docs.ceph.com/docs/master/rados/api/python/
Installation
Pre-requires:
$ sudo apt-get install cython librados2 librados-dev
Then, at the command line:
$ pip install cradox
Or, if you have virtualenvwrapper installed:
$ mkvirtualenv cradox $ pip install cradox
Usage
import cradox as rados
Functionnal Tests
A running ceph cluster is needed, the authentification must be disabled or done automatically with the configuration in /etc/ceph/ceph.conf.
For python 2.X:
$ ./test_rados.sh
For python 3.X:
$ ./test_rados.sh -3
For python2-dbg + gdb:
$ ./test_rados.sh -b
For python2-dbg + cygdb:
$ ./test_rados.sh -d
Release files for cradox 1.0.5
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 | Actions |
|---|---|---|---|---|
| cradox-1.0.5.tar.gz | 37.4 kB | Without provenance | Details for cradox-1.0.5.tar.gz |
Release files / cradox-1.0.5.tar.gz
| Download URL | cradox-1.0.5.tar.gz |
|---|---|
| Size | 37.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ec79713ec7043627e65a14c04488f42ec33c797a22b2696cae40653c024b90b
|
|
BLAKE2b-256 checksum How to use checksums |
80716b2ae52cd210db8dc408ce0011c1ab342a39baa9e1cbf24c90b8bb248401
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cradox 1.0.5
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.
