Weeks ago I had a great conversation with Vanessa Alvarez (@VanessaAlvarez1) who is an analyst with Forrest Research. Among other topics, we discussed datacenter automation because we’re both interested in it. After Vanessa tweeted about her automation dream, several follow-up tweets came up.
In general, I think automation is a vague word in IT world, and it mostly means different things to different people. This is especially true when we talk about automation together with integration. This article tries to define automation from my understanding and perspective. Please feel free to share your thoughts in comments.
My colleague John Troyer (@jtroyer), who hosts VMware Communities Roundtable, has posted an interview with Alan Renouf (@alanrenouf) and me about our thoughts on VMware SDKs, APIs, and CLIs on May 18. During the interview, I answered questions about the open source vSphere Java APIs, the themes of my blogs (why it’s called doubecloud), what I am doing now at VMware, and of course our first community meetup event on the same day. If you have missed the session, you can listen to it now: , or here. Read more...
Our first community meetup event on Wednesday night was a great success. It attracted about 200 developers/QAs and administrators globally either on site or online with live streaming. An EMC development team flied all the way from Irvine to join us; so did Huawei Symantec from Chengdu of China.
At the end of the meetup, we gave way 20 copies of these books: VMware VI and vSphere SDK by me, VMware vSphere 4.1 HA and DRS Technical deepdive (Volume 1) by Duncan Epping, VMware vSphere PowerCLI Reference: Automating vSphere Administration by Luc Dekens and Alan Renouf, andVMware ESX and ESXi in the Enterprise: Planning Deployment of Virtualization Servers (2nd Edition) by Edward Haletky; and many gadgets.
We know our attendees took their personal time mainly not Read more...
After preparing the event for almost two months, we are finally ready. If you join us onsite, here is direction to our venue. We have free food/drinks, and many books/gifts waiting for you, thanks to our sponsors and 12 volunteers.
If you join us online, we have a great news for you. Instead of WebEx, we will have a live broadcasting. Here is the URL: http://bit.ly/osvimeetup, courtesy of @lkilpatrick. You can enter as a Guest on 7PM (Pacific Time) for tech talks.
Here are the 8 tech talks we pulled together. A bit long but Read more...
Yesterday the VMware community noticed that the direct ESX download links were removed from vSphere download page. When I checked the download page, the ESX link is not with the bundles but at the end of the page in its own section.
To my own curiosity, I wonder what the adoption ratio of these two hypervisors is today. As an engineer, I don’t have sales data in front of me. Even I have, I am sure if I can share it here.
It’s been a while since I checked the VI Java API fling at VMware Lab last time. When I checked it again yesterday, I found something new and exciting – VI Java API on Google Android. The following comment was posted there by a gentleman called Bob:
Great framework, I used it on a recently published android application (avmcontrol – vsphere client for android), I had to tweak it a bit, however developing for android using vijava was much easier then the same for iOS4 devices.
You may be wondering why anyone would do this. This is in fact not a typical use case. You probably know that vSphere Client does not treat license keys like passwords which are not visually displayed as dots or asterisks. As a result, anyone who can access a vSphere Client can write down license keys and use them elsewhere.
Normally this is not an issue at all. What about Read more...
A new feature called vCenter Linked Mode has been introduced in vSphere 4. It allows several vCenter servers to form a linked mode group. When you connect to any of the vCenter server via vSphere Client, you see all of them behind a single pane of glass.
I got questions from time to time, “what does it mean for vSphere API?” More specifically, if you connect to one vCenter in a linked mode group, will you “see” all of them? If not, how can vSphere Client achieve that? Read more...
In my previous blog, I introduced the new licensing APIs since vSphere 4. As promised, I will write samples showing how to use the APIs.
Here is the first sample (stay tuned to next one, coming soon). What it does is to check the licenses in vCenter server for their expiration dates, and print them out in the console. You can of course save them into other format, say an CSV file so that you can use Excel to further analyze it. To run the sample, you must change the IP address to the vCenter server, the username/password, as would with most VI Java API samples.
There has been a total change in vSphere licensing model since version 4. Before that, you need a special/dedicated licensing server which may be more flexible/powerful but also cause many troubles in production environment which made licensing related issues one of the top categories in tech support.
vSphere 4 has dramatically simplified the whole licensing model, and removed the licensing server. To find out how the new licensing model works, check out the VMware vSphere 4 Licensing Guide. It covers both the vSphere side and the portal with which you can easily manage your license keys: splitting/combining, etc. This article does not cover the portal part but related APIs only.
Management APIs reflect product features. If you check the latest API reference, you will find out Read more...
After I touted the idea to have a meetup last week, I got quite positive feedbacks from the community. More importantly, I secured sponsorship from my employer VMware so that we can have the event at VMware headquarter. Due to a little time conflict, we will have it on May 18, instead of May 25 as I planned before. It’s still a Wednesday and food/drinks will be served with no charge.
This event was designed for professionals like developers, system administrators. Even if you are not but interested in virtualization and cloud computing in general, you are still very welcome to join us.
The first 100 registers for onsite will have chance to win Read more...
If you want to read information about a virtual machine from the guest OS running on it, the vSphere Guest API is for you. It’s a C library coming with VMware Tools. Unlike the vSphere API which can be used anywhere, the vSphere Guest API is only available in the guest OS.
If you think vSphere Client exposes everything, you are wrong. The vSphere APIs actually expose more features than the vSphere Client, which is a great product. This is one reason why system administrators should learn vSphere APIs.
While writing my book, for example, I noticed that vSphere APIs actually allow you to change guest OS screen size with a simple call setScreenResolution(int width, int height).
Given the time pressure, I didn’t summarize these API only features at that time. To be honest, Read more...
If you have a mobile phone and travel to other areas or countries, you can still use it to make and receive a call. Your phone number does not change. This is called roaming in the wireless telecommunications.
In the cloud environment, your virtual machine can “travel” around as well, maybe from one datacenter to another, from your enterprise to one of your service providers or the other way around, or from one service provider to another.
Chargeback is an important feature for computing infrastructures. Even inside an enterprise where IT users are not charged with real money, it’s still nice to see the usage patterns and sometimes avoid wasting resources. As I mentioned in IBM RC2, applying chargeback reduced unnecessary usage overnight.
VMware vCenter Chargeback is a component for this purpose. It can run standalone with Web GUI, and surface to vSphere Client as a plug-in. Although its name includes vCenter, it can also work with vCloud Director (see Using vCenter Chargeback with VMware Cloud Director).
VMware ESX and ESXi (a.k.a. vSphere Hypervisor) support the most guest operating systems among all the hypervisors. From the vSphere API, you can determine what operating system is installed on a virtual machine.
The related managed object is the VirtualMachine and there are multiple ways to Read more...
To empower developers, we got to figure out who the developers are and what they want. It’s hard, if ever possible, to identify every developer in VMware community. But it’s normally easy to find out the types of the developers. In my observation, there are two types of developers (The title of this article is not that accurate, but Read more...
After working on this for weeks, I am pleased to announce the first release of VMware vSphere API and SDK Frequently Asked Questions. It includes 70+ questions and trustable answers in 6 different categories: General, Getting Started, Language Bindings, VI Java API, API Usage, Troubleshooting.
From now on, before posting any question to any forum please read this FAQ page. For the best readability, I decided not to allow comments on that page. But your feedbacks and suggestions are always important. Please feel free to use this post for comments and discussions. Based on your inputs, I will continue to enhance the FAQs.
The open source VI Java API has implemented typing which makes it much easier to use and possible to catch errors in compile time. To use these types, you have to get hold of these objects. Normally you don’t need to worry about this because you navigate the system from the top ServiceInstance and get the managed objects through VI Java API calls.
There are some rare cases in which you get the object id first, for example, a task id as asked in the VI Java API forum. A bit more common case is when you develop vSphere Client plug-ins. The URL string your web application gets has object id and type for a virtual machine or host, etc.
My company has created products like vSearch ("Super vCenter"), vijavaNG APIs, EAM APIs, ICE tool. We also help clients with virtualization and cloud computing on customized development, training. Should you, or someone you know, need these products and services, please feel free to contact me: steve __AT__ doublecloud.org.
Me: Steve Jin, VMware vExpert who authored the VMware VI and vSphere SDK by Prentice Hall, and created the de factor open source vSphere Java API while working at VMware engineering. Companies like Cisco, EMC, NetApp, HP, Dell, VMware, are among the users of the API and other tools I developed for their products, internal IT orchestration, and test automation.