swift-bench 1.2.0-5 source package in Ubuntu
Changelog
swift-bench (1.2.0-5) unstable; urgency=medium [ Ondřej Nový ] * Running wrap-and-sort -bast. * d/copyright: Bump my copyright year. * Use debhelper-compat instead of debian/compat. * Use pybuild for building package. * Bump debhelper compat level to 12. * Bump standards version to 4.4.0 (no changes). [ Thomas Goirand ] * Convert the package to Python 3. -- Ondřej Nový <email address hidden> Mon, 05 Aug 2019 13:13:07 +0200
Upload details
- Uploaded by:
- Debian OpenStack
- Uploaded to:
- Sid
- Original maintainer:
- Debian OpenStack
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Mantic | release | universe | python | |
Lunar | release | universe | python | |
Jammy | release | universe | python | |
Focal | release | universe | python |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
swift-bench_1.2.0-5.dsc | 2.2 KiB | 6fcd193f1f8f28a949d5fcc877a93f4127109857d5bc20aea0308fcdb5c61098 |
swift-bench_1.2.0.orig.tar.xz | 15.2 KiB | 6e4f8d2a911e3fbb83d3770f7ff55020f993cc2e8347f0004f44a4223ff50109 |
swift-bench_1.2.0-5.debian.tar.xz | 4.3 KiB | 9524fe074f0e155512c17be880eb63bb457f586f0990b1d1c0285ce50d921644 |
Available diffs
- diff from 1.2.0-4 to 1.2.0-5 (3.1 KiB)
No changes file available.
Binary packages built by this source
- swift-bench: benchmarking tool for Swift
Swift Bench is simple tool for benchmarking OpenStack Swift cluster
.
OpenStack Object Storage (code-named Swift) creates redundant, scalable object
storage using clusters of standardized servers to store petabytes of
accessible data. It is not a file system or real-time data storage system, but
rather a long-term storage system for a more permanent type of static data
that can be retrieved, leveraged, and then updated if necessary. Primary
examples of data that best fit this type of storage model are virtual machine
images, photo storage, email storage and backup archiving. Having no central
"brain" or master point of control provides greater scalability, redundancy
and permanence.