Now that vSphere 5 just GAed today, I am happy to announce the public beta of VI Java API Crescendo release. Based on the feedbacks I got from the community, especially William Lam, I decided the new version to be 5.0 beta so that we can sync up with the vSphere 5.0.
This beta code has been used internally and externally in various projects for months. Still, I would like to have one month or so beta phase for your feedbacks. Please feel free to file a bug here. As always, we strive for the best quality, because I know you rely on this API for managing your mission critical infrastructures.
Bothered by SLOW Web UI to manage vSphere? Want to manage ALL your VMware vCenters, AWS, Azure, Openstack, container behind a SINGLE pane of glass? Want to search, analyze, report, visualize VMs, hosts, networks, datastores, events as easily as Google the Web? Find out more about vSearch 3.0: the search engine for all your private and public clouds.
The biggest change in this new release is the vSphere 5.0 support. If you haven’t read what’s new in vSphere API 5.0, it’s time to do so. The overall structure of the API is the same as before and 100% compatible with previous versions. As a user of the API, you won’t feel much difference except that you find more managed object types and additional methods on existing ones.
There are several hundreds of new files and changes to existing ones. While I was committing them to the repository, I found the Subversion plugin for Eclipse broke with confusing error messages about .svn\tmp\tempfile.tmp file. After searching Web and experimenting by myself, it turned out to a limit on the number of files to be committed at one batch. With several trials, I found the magic number to be 100. Sometimes it’s lower, which made me think McAfee antivirus may had contributed to the problem one way or the other.