The VMworld 2016 is coming in about two weeks. Although I’ve attended every single VMworld after 2007, it’s my first time as an exhibitor myself, to be exact, as a new innovator in the show. If you follow my blog and Twitter, you probably have know the company DoubleCloud that I had founded and the cool products/technologies we’ve been working on. This is the first year for us to promote our products in show. Please come to see our product demos, or simply stop by and say hi. Our booth is 841#4.
In my last post, I showed a sample with OAuth. It works well for application on others’ behalves. For the hello world program, it’s better to run without any user’s manual interaction. Google has provided “Service Account Key” for that purpose.
When you create a new credential, the console asks the type of key. You can select the service account key, and then select the “Compute engine default service account” with P12 as the key type. The generated key will be downloaded automatically. Save it safely and it cannot download again. You can then copy the key to the project home with a name as key.p12.
Google Cloud is the 3rd public cloud I tried after Amazon AWS and Microsoft Azure. I used its AppEngine before and it worked pretty well. Google started very early in the cloud game but it lost the opportunity to Amazon because it over-estimated the attractiveness of its own infrastructure that runs Google search.
After almost one year of intensive development, I am happy to announce the first release of DoubleCloud ICE. It’s an integrated tool for cloud management, in particular VMware vSphere with which you can do a lot of interactions easily and quickly.
The idea was inspired by the IDEs. Once upon a time, we all used editors like vi, Emacs to write code, then compile, link, and debug them using command lines. As time evolved, the IDE came out so we can do all these tasks (actually more) nicely and efficiently in one application. The result? Better user experience and higher productivity.
Last week I took a two day boot camp on OpenStack, which is increasingly popular these days. The project was initially created at Rackspace in answering Amazon Web Services, and open sourced to the community.
Not only service providers and software vendors showed interests in the project, but also hardware vendors tried to pre-install OpenStack as one of key differentiators (inside most, if not all, of hardware boxes are Intel therefore not much difference).
BusinessWeek recently published an article “In Silicon Valley, Hardware is Hot Again.” Almost all big names started to sell hardware now, Microsoft, Google, and Apple of course. Apple’s stellar success in iPhone and iPad disrupted the conventional wisdom that software is higher in margin compared to hardware. Also, Apple’s hardware and software combined devices posts a real risk for Microsoft and Google. To be exact, the hardware in the article title should really be software bundled hardware. That is why Google and Microsoft had to get into hardware business competing directly against Apple.
This past week was a busy one for Hadoop community with two Hadoop events in Silicon Valley. The first one was “what role will hadoop play in the enterprise” by Churchill Club which attracted about 300 attendees in a Palo Alto hotel. The second one was the much bigger conference Hadoop Summit in San Jose Convention Center. I will write a separate article on the second event soon.
As software professionals, we may still use the same programming languages and tools as 10 years ago. But there has been a fundamental shift in how we think of software, and make and consume software.
Traditionally software really means blueprints, which are used to construct running software instances. The blueprints include binary code, installer, and related documentations guiding the installation and configuration of the software. Software vendors make the software packages and sell them to customers who then deploy and run them.
While installing and configuring vCloud Director recently, I kept thinking how to simplify it by removing un-necessary concepts and steps. To be fair, vCloud Director as of version 1.5 does a decent job to provide a high level abstraction for cloud infrastructure. Still it can be significantly improved just like every other new technology. Note that I pick vCloud Director as an example for the following discussion simply because VMware is the leader in virtualization space and what it does has ripple effects on other vendors.
As I predicted for 2011, the cloud will be the ultimate powerhouse for mobile devices. The reason is simple: although fancy and stylish, the mobile devices typically do not have enough computing power and storage space for certain applications.
Several folks asked me about how to use vSphere(VI) Java API to connect to a VM running on vSphere. The quick answer is vSphere Java API is not designed for this. You will need VMware Remote Console, browser plug-in, remote desktop/VNC, SSH client etc. However, it can help you to get the information required by the console or plug-in. Tal Altman from CISCO suggested that it be a topic for doublecloud.org. Here it is.
There are 3 ways to connect to the VM from your client side outside the vSphere and Web Access which have built-in support for console access.
- Using VMware Remote Console which is a standalone application
- Using browser plug-in to either IE or Firefox (Note: this is NOT supported by VMware. Please don’t call the company tech support for this.)
- Using Remote Desktop, VNC or SSH
The first two connect to the ESX host, and work even there is no guest OS installed on the VM. The last one assumes you have guest OS installed, and have IP network and server components in place already.
Note that these 3 ways work for the VMs in the public cloud as well if the related ports are open in your firewall. It is, however, not the case for most enterprises, therefore I particularly say it’s for VMs in private cloud. If you don’t have firewall issue, feel free to give it a try with public cloud as well.
Let’s go over one by one in details and see how vSphere Java API helps.
Last week VMware released a news “VMware Expands VMware vCloud Developer Ecosystem With Open-Source Java and Python SDKs for VMware vCloud API”. It says,
VMware has also made a number of open-source contributions to the Cloud Tools project, which powers the SpringSource Cloud Foundry service, enabling Java developers to deploy, test, and manage applications for VMware environments via VMware vSphere(TM) and the VMware vCloud API.