Happy new year! A new posting is way overdue after I set up the blog early last December.
Today, we surpassed 5,000 downloads. This is an important milestone for the project as it indicates the adoption of this powerful yet easy-to-use API has reached a new level.
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.
Moving forward, the API will continue to evolve with new vSphere releases. This is, of course, a very basic requirement. At the same time, it will support other VMware solutions like SRM, maybe LabManager, that have Web Services. VMware SRM QA team has done initial porting of the high performance Web Service engine to work with SRM in their testing framework, and observed 15 times performance boost over Apache AXIS engine.
As enterprises transforms to private cloud computing model, vSphere plays even more important role there. To simplify the learning curse of leveraging vSphere for the cloud, I will investigate a reduced version of VI Java API that matches the concept model of vCloud API. It means it will only expose DataCenter, VirtualMachine these basic types that a Cloud developer will care about, but not HostSystem and other types that only concern data center operators. This reduced API may require some pre-configuration, for example, the inventory tree is structured in a certain way that are best for faciliating cloud computing. This fits the trend “Convention over Configuration” that Ruby On Rail brought in years ago. This is investigative than anything else. I will update my finding along the way.