Another VMworld is upon us and its time for my VMworld 2013 predictions. I’m going to leave out some of the gimme predictions of NSX being released and a new vSphere / ESXi / vCloud. But I’ll go into the some of the features that I think they’ll have. It should be noted, the company I work for is not a part of any beta trials at the moment nor have I had any preview as a vExpert (though one would be nice!

For those that are interested in learning a little bit more about Puppet, join me at the KC VMUG Meeting on August 15th from 1:30 – 4. I’ll be giving a talk on how we use Puppet at LightEdge and a few cool things you can do to automate your server deployments. Should be a good (and informative) time.

Finally dug out of the past couple of weeks to do some writing and I have a bunch of stuff to talk about. Hoping to have several posts here in the next week or so. One of the big events that has happened over the last week is that I was selected as one of the vExperts for 2013. I’m honored to be one of the selected members for this year and truly grateful for the recognition.

With the latest and greatest VMware Tools updates, you may have noticed a change to the VMware Tools Toolbox. Mainly, the inability to do anything that you used to be able to do. Now you are simply greeted with the version, some copyright information and a status that tells you if the service is running or not. This change is outlined in the ESXi 5.1u1 notes as follows: VMware Toolbox. vSphere 5.

Recently while patching some CentOS boxes in my lab, I noticed the following error. May  5 13:48:38 puppet-agent[19924]: Could not run Puppet configuration client: Could not retrieve local facts: undefined method  `kernel_fact_value' for Facter::Util::Processor:Module This was a bit odd as one of the things that I will typically do when I see puppet or facter updates in my update list is to run the agent manually with a puppet agent -t Since that came back clean, I was a little surprised when I checked into the dashboard later in the day to see nodes failing on me.