As reported by the open source VI Java API community, a bug came to my attention. It’s related to the Client REST API which is a powerful hack with vSphere MOB based on a little secret. Started in vSphere 4.1 update 1, things started to break if you want to call a method with the REST API while retrieving properties continues to work.
After the vSphere 5.0 was released, I checked the vSphere Web Services SDK documentation page. Upon clicking the vSphere API Reference link, I got into the vSphere 5.0 Documentation Center as follows:
It’s a bit surprise to me. First of all, I like the integrated approach where you can find all the information related to vSphere 5.0: from user manual to SDK/CLIs, and even links to communities/blogs. Also, you have nice features like bookmark, search and printing, etc.
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.
Because vSphere 5.0 is now released, I can talk about the changes of the API in public. As you may have heard me saying many times, management APIs are the “view” to the product. New features can be exposed via APIs. Understanding the changes in APIs helps you understand the product itself.
The API Reference 5.0 has the first page “New and Changed Managed Object Elements in 5.0” summarizing all the changes. To support vSphere 5.0 in new VIJava API , I’ve gone through all these changes. I will write a separate article on VIJava new release soon.
A question was recently posted at the open source VI Java API forum regarding the uniqueness of MOIDs. The developer who raised the question wanted to build a caching on the client side so as to avoid getting back to the server for the name of a virtual machine with its MOID. If MOID doesn’t resonate with you, you may want to read this post before reading on.
If you are using, or intend to use, the open source vijava API with Java Web start, you want to read this article carefully.
A community user recently reported an issue in this scenario. His test application was launched via Web Start jnlp. “First, when run a single test thread everything is fine and the VM tasks operate normally. However as soon as we kick off a second test thread while the first test thread
I got an interesting question on how to find out WSDL files are used by vSphere Web Services at the VI Java API forum. After some clarification, it turns out the questioner just wanted to know what methods are called, so that the proxy between client and vCenter server can decide whether it should be allowed to go through.
Although a rare use case, but it’s a valid and sophisticated one. In general, you can use vSphere built in feature for security, for example,
There was recently a question in VMware vSphere Web Service SDK forum regarding gzip compression in vSphere API. I understand where the user came from – some of the SOAP responses could be pretty big. If they can be compressed, performance could be improved and network bandwidth reduced.
The case can be a little tricky. On one hand, compressing big data definitely saves bandwidth; on the other hand,
Today I got an email from Louis Jia who is a Sr. Development manager at Cisco. He told me that the product his team has been working on had been rebranded as Cisco Data Center Network Manager (DCNM) and is formally released. Congratulations to Louis and team!
I don’t normally cover products from vendors, be it an established company or a startup. But this one is different
I saw a new bug (Intermittent ManagedObjectNotFound on VirtualMachine.getConf) filed in the open source VI Java API project today:
It looks like sometimes VirtualMachine.getConfig() returns null, but other times it throws:
Caused by: java.lang.RuntimeException: com.vmware.vim25.ManagedObjectNotFound
at com.vmware.vim25.mo.ManagedObject.retrieveObjectProperties(ManagedObject.java:158)
at com.vmware.vim25.mo.ManagedObject.getCurrentProperty(ManagedObject.java:179)
at com.vmware.vim25.mo.VirtualMachine.getConfig(VirtualMachine.java:55)
As the vSphere API reference points out,
English
Recent Comments