It’s a known bug in VI Java API that it did not escape strings to be included within a XML tag. The potential risk, although very very rare, is that it can blow the de-serialization of a request on the server side. I did get one or two reports on failing on login, which turned out to be caused by special characters like < or > in passwords. As a quick fix, an escaping logic has been added to escape the special characters in passwords.
In my previous articles, I mainly cover server virtualization and cloud computing. Client computing, although less enterprise focused, is also a very important part of whole story. In this article, I am going to share some thoughts on this topic, mostly about the future development of how users will use computers and what it takes to get there. I know it’s a big topic, but let’s give a try.
After the vSphere Java API 5.0 beta was released, I got a very interesting bug that I think is worthwhile to share with the community. Note that I used the word “interesting.” It turned out to have no solution logically, but quite easy to work around and patch up. The workaround addresses only particular issue but does not prevent similar bugs from happening in the future.
Confused? Let’s take a quick look at the bug report:
As a developer, I’m always interested in latest development of middleware platforms. Yesterday came a big news from VMware: the vFabric 5 Cloud Application Platform reached GA. For those who might not be familiar with vFabric, it is an integrated suite of middleware for deploying and managing applications.
Note that despite the version number, this is the first release of the vFabric platform. I guess the version 5 may be just for aligning with vSphere 5. Also, this is a suite of products that have been there for a while.
Among all the new features vSphere API exposes, I think VIX integration is very important. All of sudden, the vSphere API gets a boost on manageability of guest OS, and you can do many more with single set of APIs.
In his keynote at VMworld last week, VMware CTO Steve Herrod showed a very interesting project called AppBlast. According to this news release thereafter, “Project AppBlast will provide the universal delivery of any application, including Windows-based applications, to any device supporting HTML5, enabling instant remote access to applications without the heavy footprint of the underlying operating system.”
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.
Today is day two of VMworld 2011 in Las Vegas. VMware CTO Steve Herrod got on stage with his technology deep dives into various products and new projects around the cloud story – “your cloud, own it.” Again this is based on my note and memory, and has not reviewed by anyone. Mistakes are all mine.
Today is day one of VMworld 2011 in Las Vegas. The most important part is of course the keynotes by CEO Paul Maritz and Co-President Carl Eschenbach. The following is based on my personal note and has not reviewed by anyone. All the mistakes and errors are mine and only mine.
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.
There are many programming languages today, sometimes too many to choose from for a new project. The good thing is that there aren’t many main stream programming languages, so picking one is not a daunting task. And almost all main stream languages can achieve similar things, meaning any one of them will work. So in the end it’s really a matter of team preference and sometimes company policy.
As part of the VMworld #vMeetups in the Community Lounge, this developer/administrator (a.k.a. devops) meet up will take place on August 30th from 12PM to 1PM at VMworld Community Louge, located just outside the entrance to the solution exchange. Because it’s lunch hour, please feel free to bring your lunch.
This event offers you a unique opportunity to meet and network with other professionals who create or use VMware APIs and CLIs for integration and automation.
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.
Cloud bursting means workload moves from one cloud to another on the fly. With differentiation of public cloud and private cloud, you can have 4 different permutations: private to public, private to private, public to public, and public to private.
What people talk about the most is the case of private to public cloud. Think about the case in which
It’s probably fair to say anyone working in software knows a term called platform. It’s a term borrowed from transportation industry, where a raised and flat space on which passengers trains in a station. In software, it means something you can leverage, either an environment for running your software or a development library for building your applications.
Like many things in software, platform has never had a clear definition. Different people basically have their own versions of definitions. That is not necessarily a bad thing – at least it helped
As cloud computing gains momentum, more mega data centers are constructed or to be constructed. You can find cool videos on how companies like Google, Microsoft build and run their state-of-the-art data centers.
In these data centers, computers/storage/switches are packed and wired inside containers in factory before being shipped to a data center. After hooking up power, networking, and cooling, a container of servers are ready to go. These advances have
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,