Usually I do not read requirements that deeply as I should, and I run into several problems and spent like two hours with troubleshooting my python environment until I realized that it requires Python 3.6 but in my CentOS server I had version 2.6.5. Working with the script is quite easy, although the installation of the environment was a bit pain in the ass for me.
Well, I did not (it was released roughly two weeks before the on-site training and I must say it is a wonderful script.īasically, what it does is, that it will check your ESXi servers against HCL automatically and gives you report of all components, supported versions of ESXi you can upgrade to and much more information. He was quite upset that he has to validate all components against HCL to be on supported level and after few days he said like “Hey, I have found this fling, do you know about it?”. I said its quite straight forward process but warned him about Hardware Compatibility List and supported hardware. I was doing on-site training two weeks ago and one of my students asked me about upgrade procedure of the vSphere environment. It’s a wonderful collection of various scripts or extended functionality for your vSphere environment and sometimes those projects make it to the production state as a part of VCSA. If you never heard about flings, you must visit. Many of you might be considering upgrading to Vmware vSphere 6.7 but what about your underlaying hardware of ESXi? Is it capable of running ESXi 6.7? I have found this great fling by absolute coincidence.