On Monday, April 13, 2009 at 2:23:06 PM UTC-4, [email protected] wrote: > > Hello, > > Reading the doc I could not find if Puppet could help running system > updates. >
Help, yes. But I'd advise against trying to do them directly in puppet. > I would like to get started with several VMWare guests and few hosts, > all running CentOS. Some are 32bits, some 64bits. These are mostly > VMWare server installations; just starting ESXi with one system. They > are running different apps/configurations. > > Of course there are few issues with: > > 1- VMWare tools that want to be sometimes recompiled on Linux. There > is a trick to avoid the recompilation: > > http://vmetc.com/2008/08/31/automating-vmware-tools-installs-and-upgrades-in-linux-guests/ > > but maybe this could be taken care of with Puppet? > Switch to open-vm-tools. It's what VMWare reccomends now, and should be provided by your distro. https://kb.vmware.com/s/article/2073803 > 2- VMWare server on the host sometimes does not restart after a kernel > update. It also need to be recompiled. Of course the VM Guests are > down. > > 3- The host kernel updates might require reboot, shutting down guests. > I have a script for doing updates that I deploy via puppet, and schedule, via puppet. But the script is a bash script that grabs the time/date of the current kernel (well, the modification time of /boot, which is more aggressive), runs the yum update, and compares the new modification time of /boot. If they're different, it reboots. You can then set the guests to autostart at boot time-- or autostart puppet at boot time, if you're using that to manage guests. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/15a39c8a-fb17-4c4d-aad6-19f74cde1795%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
