On Tue, Feb 16, 2010 at 3:00 PM, Rob McBroom <mailingli...@skurfer.com> wrote: > On Feb 11, 2010, at 7:10 AM, Marc Fournier wrote: > >> [²] http://github.com/camptocamp/puppet-openvmtools > > Pardon my ignorance, but why run the `install-open-vm-tools.sh` or > `vmware-config-tools.pl` at all? > > My manifests for VMWare guests (running RHEL5) just do this: > > 1. set up a yumrepo for > http://packages.vmware.com/tools/esx/4.0/rhel5/$architecture/ > 2. make sure the “vmware-tools” package is installed > 3. make sure the "vmware-tools” service runs > > The only problems I’ve had are that the GPG key for that repo doesn’t seem to > work (last I checked) and it doesn’t support RHEL4. What am I missing?
We had issues with certain modules (vmmemctl) not loading until we'd run vmware-config-tools.pl. Running the service might have helped, but at the time there were some widespread performance issues on our ESX hosts and I wanted to be as blameless as possible - so I chickened out and went for the 'official' RPMs :) We install the (official) RPM with Puppet, and do the tools install on the vmware console when we patch the kernel. I'm not adventurous enough to have Puppet patch kernels and bounce systems (yet). -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
