VMware

We’ve recently been setting up vCloud 1.5 in the office and so far we like what we’ve been seeing. During the install, we did run into a bit of an issue when we set the API urls. On our first attempt we didn’t set them and had issues uploading media. You’d think that the two would be unrelated. You’d first think that you had a permissions issue on the file system somewhere right? Wrong-o-bucko! What you need to do is set the API url in Administration > Public Addresses. Uploading media apparently uses it.

Hardware issues have forced a lack of blog updates this week. look for a recap next week when I have a chance to decompress.

Ah yeah, its finally here! Next week is the infamous VMworld conference in Las Vegas. Couldn’t come at a better time as we’re knee deep in vCloud at work and very excited to get our hands on the new bits coming out of VMware. Looking forward to a great conference and hopefully I’ll have some time to post some content of things we’re seeing. If not a blog post, definitely some tweets (@usrlocal for those that don’t follow me).

A few months back I had a little bit of trouble with an upgrade in our corporate VMware cluster that I thought I would share. The details of this upgrade was to add a new host to the mix and bring everything up to vSphere 4.1 update 1. It seemed pretty straight forward at the time but there were a few unexpected issues that sucked up more time than expected.

As I wrapped up the migration from vSphere 4.0 to 4.1, I had one host that for the life of me wouldn’t upgrade. It kept giving me the following error:

I can see the ESX host just fine. Nothing out of the ordinary there. The firewall ports look exactly the same as the other 6 hosts in this particular cluster. Why the hell won’t it download the updates.