openstack-image-manager
Easily manage and keep up to date a large number of images on an OpenStack environment
Upstream checksum fields
Image versions using the latest pointer must specify where to find the
upstream checksum, using exactly one of these two fields:
checksums_url— URL of a checksums file that contains the image filename, e.g. theSHA256SUMSmanifest published by Ubuntu. Lines have the form<digest> <filename>; the line matching the image filename is used.checksum_url— URL of a checksum file that contains a single bare digest and nothing else, e.g. the.sha512sidecar files published by Alpine. Use this when the checksum file does not contain the image filename.
Supported digests are MD5, SHA-1, SHA-256 and SHA-512 (hex-encoded). The checksum URLs must be HTTP(S).
Import path (--prefetch)
By default images are imported with Glance's web-download method, where
glance-api fetches the image from its URL itself. When that fetch is slow or
flaky, the import can stall and revert to queued. As an alternative the image
can be downloaded locally with aria2c (robust multi-connection download with
retry and resume) and uploaded via the glance-direct import method, which runs
the same decompress/convert/store taskflow as web-download.
--prefetch selects the behaviour:
never— always useweb-download(previous default behaviour).on-stuck— default; useweb-downloadfirst, and fall back toaria2c+glance-directonce if the web-download attempts fail.always— skipweb-downloadand usearia2c+glance-directdirectly.
--import-timeout (default 1800) bounds the overall per-image wait, shared
across all attempts. When a definition carries a checksum, it is passed to
aria2c for verification.
The aria2c binary must be installed for the prefetch path, and the target
cloud must have the glance-direct import method enabled.
Unlike web-download (where glance-api fetches the image directly), the prefetch
path downloads the image to a temporary directory on the host running
openstack-image-manager, so that filesystem needs room for the full image
(e.g. ~345 MB for the octavia amphora image). A free-space preflight aborts before
downloading if the temporary filesystem is too small.
Metadata
Release files for openstack-image-manager 0.20261007.0
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 |
|---|---|---|---|---|
| openstack_image_manager-0.20261007.0.tar.gz | 39.9 kB | Without provenance | Details for openstack_image_manager-0.20261007.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openstack_image_manager-0.20261007.0-py3-none-any.whl | Python 3 | none | any | Details for openstack_image_manager-0.20261007.0-py3-none-any.whl |
Total release size: 84.8 kB
Release files / openstack_image_manager-0.20261007.0.tar.gz
| Download URL | openstack_image_manager-0.20261007.0.tar.gz |
|---|---|
| Size | 39.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4df3909ed87e34623fff8896c0bc6069871ab9b9c7d484f9c46b33bfe9fc8a61
|
|
BLAKE2b-256 checksum How to use checksums |
b9b800336f3b53863ba22c4e71162cfa752ca570171add621925ccf678d992b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / openstack_image_manager-0.20261007.0-py3-none-any.whl
| Download URL | openstack_image_manager-0.20261007.0-py3-none-any.whl |
|---|---|
| Size | 44.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db3fbd71d40de8591778eb1ccd50f12f0375cd6a526cb531fe50f112de54cb56
|
|
BLAKE2b-256 checksum How to use checksums |
576c977cb3768e8ca34389288905d69c2702b1d6e477df77b70932fcb0096f28
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Security for openstack-image-manager 0.20261007.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.