Recently I spent some time upgrading our corporate VMware environment from ESX4.1 to ESXi 5. Fun times I know. For most of the hosts, I was able to use the update manager to upgrade and only one host was short on space that required a full re-install from CD. The upgrades weren’t without incident. I had the unfortunate incident of running into an error of “The Unlicensed license for host does not include vSphere HA.

Logged into a Puppet master server today and noticed that I had some high CPU utilization happening. This is rather odd as the box usually just chugs along with no worries what-so-ever. Turns out, some others noticed this as well and some had suspicions that it was leap second related. Check out the full thread here. Looking back at my SAR records, I find that my CPU spiked right around June 30th at 7PM which is July 1, Midnight GMT.

Trying to keep myself on track here and the best way to do that is to make sure that I’m writing and checking in on my goals at various points throughout the year. So here is my mid-year goal checking. Goal #1: Sleep More! 6 months in and still tracking with the help of mercuryapp.com. My average is now 6.92 which is up slightly from my 3 month mark of 6.

We’re currently running a little in house beta at the office of vCloud 1.5.0. The testing has been going on for a while and recently I had to do something I didn’t want to do, but had a nice learning experience for me so I thought I would share. We have two UCS blades running in our vCloud environment giving us a nice healthy test bed to play in. For another maintenance in our VMware environment, I had to steal one of these blades to be used in another cluster to add some resources temporarily.

Today I came into work with the following messages in my logwatch emails: Last Status:    WARNING: Your ClamAV installation is OUTDATED!    WARNING: Local version: 0.97.4 Recommended version: 0.97.5    DON'T PANIC! Read http://www.clamav.net/support/faq    main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven)    daily.cld is up to date (version: 15042, sigs: 218148, f-level: 63, builder: mcichosz)    bytecode.cld is up to date (version: 185, sigs: 39, f-level: 63, builder: neo) Ah crap, time to touch all the boxes and make sure that the package is up to date right?