For several years now Eric Siebert has held voting for the top Virtualization Bloggers. This is a huge undertaking, and this year he has over 300 blogs listed. You should keep in mind several factors when voting, such as longevity, length of content, frequency, and quality. Voting is now open, and will continue through 3/17/2014. Last year I was ranked in the Top 25, at #24. I really appreciated the votes, and was thrilled to be one of the top rated.
In Part 1 of this two part VMware VCDX journey series I accounted for the first 120 days of my VCP5 to VCDX #125 journey. This post will cover the final 60 days, which were just as important, if not more so, than the first 120. In my last post we left off with my completed design package, application form, and a sacrificial payment of $300 was submitted to the VMware Gods. Would my application be chopped in half and sent back in pieces, or spared to live another day?
This is Part 1 of my tale of the last 180 days of my life, my adventure from VCP5 to becoming …drum roll… VMware VCDX #125. Yes, I successfully defended my design at VMware PEX 2014 in San Francisco this past week, which was for VCDX5-Datacenter Virtualization (DCV)! It was a fun, educational, and a surprisingly pleasant experience. I’m blogging about this experience because I know if I can become a VCDX, then anyone can do it with enough experience and dedication. Do keep in mind that prior to starting my 180 day adventure, I had approximately 4 years of VMware architecture experience for Government and commercial enterprise systems. Years of architecture-level experience is key, however VMware does not require a specific number of years or job title to apply for the VCDX certification.
Now that vSphere 5.5 has been out for a few months, if you haven’t already started working with it in your test environment, you should! A lot of great new features, and major improvements to the SSO experience. However, you still may find it a bit challenging to secure vCenter and ESXi hosts with trusted SSL certificates. So hot off the press is a minor bug fix version of my vSphere 5.5 Toolkit script. You can download the new version here. In case you aren’t familiar with it, here are some of the features:
Yes, time to update my vSphere 5.5 Toolkit with a few more features and bug fixes. For those of you that need to replace your vSphere 5.5 SSL certificates, the process can be somewhat cumbersome and time consuming. While VMware has a tool to help you replace the certificates once you create them (SSL certificate automation tool), it has limited functionality in helping you create all the files needed as pre-reqs to running the tool.
After a bit of a delay, I’m finally publishing how to update your ESXi SSL certificate. The process is pretty much unchanged from the 4.x era, but what is new is my Toolkit script. It has been updated to include ESXi certificate support. This is accomplished all in PowerShell, and does NOT require SSH be enabled on the host. It uses the HTTP PUT command to upload the two required files. This should also run successfully against older ESXi hosts, but I haven’t tested it.