Redfish Tacklebox
Copyright 2019-2026 DMTF. All rights reserved.
About
Redfish Tacklebox contains a set of Python3 utilities to perform common management operations with a Redfish service. The utilities can be used as part of larger management applications, or be used as standalone command line tools.
Installation
Only one installation method is required to use Redfish Tacklebox.
From PyPI
pip install redfish_utilities
Building from Source
git clone https://github.com/DMTF/Redfish-Tacklebox.git
cd Redfish-Tacklebox
python setup.py sdist
pip install dist/redfish_utilities-x.x.x.tar.gz
Building Docker
-
Pull the container from Docker Hub:
docker pull dmtf/redfish-tacklebox:latest
-
Build a container from local source:
docker build -t dmtf/redfish-tacklebox:latest .
-
Build a container from GitHub:
docker build -t dmtf/redfish-tacklebox:latest https://github.com/DMTF/Redfish-Tacklebox.git
Requirements
External modules:
- redfish: https://pypi.python.org/pypi/redfish
- XlsxWriter: https://pypi.org/project/XlsxWriter
You may install the external modules by running:
pip install -r requirements.txt
Utilities
- Discover (rf_discover.py)
- Sensor List (rf_sensor_list.py)
- System Inventory (rf_sys_inventory.py)
- Logs (rf_logs.py)
- SEL (rf_sel.py)
- Power/Reset (rf_power_reset.py)
- Boot Override (rf_boot_override.py)
- Virtual Media (rf_virtual_media.py)
- BIOS Settings (rf_bios_settings.py)
- Manager Configuration (rf_manager_config.py)
- Accounts (rf_accounts.py)
- Update (rf_update.py)
- Firmware Inventory (rf_firmware_inventory.py)
- Event Service (rf_event_service.py)
- Licenses (rf_licenses.py)
- Certificates (rf_certificates.py)
- Diagnostic Data (rf_diagnostic_data.py)
- Assembly (rf_assembly.py)
- Power Equipment (rf_power_equipment.py)
- Thermal Equipment (rf_thermal_equipment.py)
- Component Integrity (rf_component_integrity.py)
- Raw Request (rf_raw_request.py)
- Test Event Listener (rf_test_event_listener.py)
Release Process
- Go to the "Actions" page
- Select the "Release and Publish" workflow
- Click "Run workflow"
- Fill out the form
- Click "Run workflow"
2 maintainers
Metadata
2 maintainers
Release files for redfish-utilities 3.5.2
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 | |
|---|---|---|---|---|
| redfish_utilities-3.5.2.tar.gz | 71.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| redfish_utilities-3.5.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 179.7 kB
Release files / redfish_utilities-3.5.2.tar.gz
| Download URL | redfish_utilities-3.5.2.tar.gz |
|---|---|
| Size | 71.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
469ee4aa22b54ea74c36553077640f0b4f1bdf028df741f237c42a816fd3d344
|
|
BLAKE2b-256 checksum How to use checksums |
5f5c0acc6b3a487e045b12475861a10eca7f6bdd6fbf9f0bfcd44d8e9e260ea8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / redfish_utilities-3.5.2-py3-none-any.whl
| Download URL | redfish_utilities-3.5.2-py3-none-any.whl |
|---|---|
| Size | 108.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b84e8aea2bcf55a4d0b257495fa26efd7d86bf53fb82ee098fcdb7af7faa845d
|
|
BLAKE2b-256 checksum How to use checksums |
a3d4038d0255425b0b68da96727948d7c9d0731831548f4517f9d7e1386e5866
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for redfish-utilities 3.5.2
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.
