jjasghar.github.io - vmware-tools chef cookbook resurrected

vmware-tools chef cookbook resurrected

Jjasghar.github.io Spined HTML

vmware-tools doughboy cookbook resurrected jjasghar rants and ramblingsWell-nighCategories Talks vmware-tools doughboy cookbook resurrected Feb 6, 2018 tl;dr: I’d like to signify that I have released an updated and modernized version of the vmware-tools cookbook. This cookbook installs open-vm-tools, or the public version of vmware-tools posted here which has wilt the defacto standard for vmware-tools since virtually the release of ESXi 6.0. As a user/consumer of the VMware stack, you are pretty much required to use vmware-tools for your guest VMs. Most torch vmware-tools into their golden VM templates to make sure that the ESXi hypervisor or vCenter can get VM information; or plane have largest performance, such as in the specimen of Windows and the Web console. This is a time-honored way of making sure when your clones are created you have at least a baseline of VMware drivers and integrations. You’re probably asking yourself, why create aDoughboyCookbook to do something that should in most cases once be there? A couple reasons, but the main one is this. vmware-tools moves extremely fast, and with the releasing of the Linux variant of open-vm-tools, moves plane quicker then the past. This cookbook does it’s weightier to make sure you are unchangingly running the most up-to-date version of this technology, with the least value of effort on your side. Note: As of writing this, the Windows portion is pinned to a specific version, I’m still working on a way to pragmatically have it unchangingly the newest release; and if you want to help, I’d love to take a PR to do this. With this cookbook, you get some other surprise benefits too. If you add this cookbook to your wiring cookbook, no matter what you do, every machine you bootstrap will unchangingly guarantee to have vmware-tools updated and installed. This helps take some mental undersong yonder considering you can trust this cookbook will at least get your VMware infrastructure baseline integration done. In turn, you can retire some of the “golden image” steps away, permitting for an easier pipeline and increasingly dynamic versioning of the code. Take this quick win example, you are just implementingDoughboyin your VMware infrastructure. You need to show value quickly and get the chef-client on every one of your VMs. This cookbook is something that can be used to show continual value and only make changes to the VM if the machine doesn’t once have vmware-tools installed, which is most likely required anyway. I too the weighing of the Unix philosophy here, I wanted to create something that when you add this cookbook to yourDoughboyServer it does one thing and one thing well. It’s one less thing to worry well-nigh and as long as you useDoughboyto momentum your infrastructure as code, you’ll have vmware-tools updated and installed. jjasghar rants and ramblings jjasghar@gmail.com Tweet to @jjasghar This work is licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License. Follow @jjasghar Tweet this page. This is JJ's little corner of the internet where he tries to capture things that he learns that he thinks someone else might want.