An HTTP API (previously known as the “mariner installer”) to provision and control the deployment process of Ceph clusters.
The service allows you to install and configure ceph via a RestFul API that accepts and returns JSON responses along with meaningful error codes and messages.
Read the full documentation here: http://docs.ceph.com/ceph-installer/docs/
2 maintainers
Metadata
2 maintainers
Release files for ceph-installer 1.3.1
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 | |
|---|---|---|---|---|
| ceph-installer-1.3.1.tar.gz | 64.9 kB | Without provenance | Details |
Release files / ceph-installer-1.3.1.tar.gz
| Download URL | ceph-installer-1.3.1.tar.gz |
|---|---|
| Size | 64.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9588c58b4423163b052b537c4b45c7f56d8720cad420fd111a410660fdc87db4
|
|
BLAKE2b-256 checksum How to use checksums |
c74b9b1efb3fdb4b90b43512974da29cf68ec8472a441e111f02d74b850784e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ceph-installer 1.3.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.
