RvCrunch- RVTools reporter
RvCrunch is a simple CLI tool that provides a report with relevant information from a RvTools export. The main function is to save an Excel report with this information.
The report includes a 'Agg Cap' figure which uses the vPartitions tab to calculate a more accurate used capacity figure. Where VMs are missing because they are powered off or VMware tools is not working, the allocated capacity will be shown in that column.
RvCrunch relies on the excellent work done by Rob de Veij of RvTools fame.
There are also mini reports that provide quick reports on key information from the RvTools report.
The tool accepts RvTools files in excel format (.xlsx), vInfo and vPartition tabs are required.
Installation
You can install RvCrunch from PyPi via:
pip install rvcrunch
Updates
Now works with the latest version of RvTools which changed the capacity units from MB to MiB.
Usage
Run the tool via the command line via:
rvcrunch [OPTIONS] path
Specifying the file path as the first argument will run the main Excel "Crunch" report.
rvcrunch "C:\path\to\rvtools\rvtools.xlsx"
-po or --poweredon modifies the report to display only Powered On virtual machine info.
-sn or --savename allows you to specify the exported file name, otherwise the default 'report.xlsx' will be used.
-sr or --skipreport stops the main report being exported to excel, this can be used with the mini reports below.
There are also several mini reports that provide certain key info, these are shown in the command line.
-vm : Provides the total VM count by Powered-On and Off
-dc : Provides the Data center names
-cl : Provides the Cluster names
-dc_cl : Groups the clusters by the Data center and provides vm, disk and vInfo capacity breakdowns.
-rdm : Checks if report has RDMs and optionally exports to Excel. The vDisk tab is required for this to work.
These can be run alongside the main report or instead. To prevent the main report being run when using mini reports use the -sr flag.
Example:
rvcrunch -sr -vm "C:\path\to\rvtools\rvtools.xlsx"
Note: RDM report is allocated capacity, mapping the disks in vDisk to the partitions in vPartition isn't precise enough to be practical.
Metadata
Release files for rvcrunch 1.2.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 | |
|---|---|---|---|---|
| rvcrunch-1.2.0.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rvcrunch-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.9 kB
Release files / rvcrunch-1.2.0.tar.gz
| Download URL | rvcrunch-1.2.0.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e55c07b4abc37ca6e82bb928d2fc0ae4bbc4015bbd9d07c893fd711e3e64039
|
|
BLAKE2b-256 checksum How to use checksums |
14f6f6999fa723d4df67d1dbc843d418b807afd3bb2c3ec2e0b4039121224371
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Release files / rvcrunch-1.2.0-py3-none-any.whl
| Download URL | rvcrunch-1.2.0-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f1355f9a8033e036e0caf06dbd7bac925711a1ab154c755aa6bd9053fb0525e
|
|
BLAKE2b-256 checksum How to use checksums |
1e0f3d907aa2d18a04edfe16042c92236faa28139afd3a48e2da314ec8a421b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.0
|
Security for rvcrunch 1.2.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.