Whitespace: due to discovery from an email thread, the detail of “the parameter in the properties file” slipped below an expert’s radar.
I therefore changed ~.vmware.servers.exclude to ~.vmware.discovery.exclude in the output of –dump-config=esx.csv output. Dion has indicated that this parameter is not length-limited, and has been tested with over 2000 entries.
This change is merely whitespace in the commentary of the generated file.
Vitoo recognized that the order of the CSV is incorrectly noted in the –dump-config=esx.csv output. Dion has indicated that engineering confirms this does now work, but is limited to 256 characters.
This change merely whitespace-corrected the order of the text in the comments for the exported text.
Completed the VM Estimator but need to ensure it will deliver via JNLP. The VM Estimator is a simple GUI that can reach out and discover the ESX count on a vCenter. Currently only tested with https:// on a local 5.1 vCenter, seems to function. The key goal is to provide a quick estimate of the ESX counts of a number of vCenters in an organization to better estimate a rate-based cost where the number of ESX servers relates to a recurring license/usage/permit cost.
I’ll post a URL when it’s available.
In revision 521, I added the ability to dump out the esx hbas as esxhbas.csv, esxhbas.xml, vminventoryraw.csv, or vminventoryraw.xml similar to dumping roving.xml and roving.csv. The outputs are self-documenting in #comments in the CSV, or as XML self-documents already. The benefit of this function is that when the PHC seems to miscalculate the HBA speeds in phc-vm.csv, the raw data can be debugged. Note that the XML has no whitespace, so “xmllint -format esxhbas.xml” is your friend.
For example:
(typically running locally: the MySQL is configured to only accept local connections)
java -jar vict.jar -D esxhbas.csv
or
java -jar vict.jar -D esxhbas.xml
…and in long-options too:
java -jar vict.jar --dump-config esxhbas.xml
…but since the JRE is typically hidden below the VirtualWisdom directory, use vict.bat:
VICT.BAT -D esxhbas.xml
VICT.BAT --dump-config esxhbas.xml
In revision 424, similar to 423 wherein I added the ability to dump out detected ESXs, I added the ability to dump out the virtualserver table as vm.csv or vm.xml. The outputs are self-documenting in #comments in the CSV, or as XML self-documents already. Note that the XML has no whitespace, so “xmllint -format vm.xml” is your friend.
For example:
(typically running locally: the MySQL is configured to only accept local connections)
java -jar vict.jar -D vm.csv
or
java -jar vict.jar -D vm.xml
…and in long-options too:
java -jar vict.jar --dump-config vm.xml
…but since the JRE is typically hidden below the VirtualWisdom directory, use vict.bat:
VICT.BAT -D vm.xml