> puppet is a steady-state management system, where you specify the target > and puppet works out how to get there. Installing and removing packages > in a single step doesn't fit into that model at all.
I've actually been thinking about doing this in a multistage fashion using the current state as the steady state: state 1: PSP not installed, no support tools installed - puppet action: install support tools state 2: PSP not installed, support tools installed - puppet action: install PSP state 3: PSP installed - puppet action: check server class, uninstall support tools based on server class It may take several hours to install the PSP, but I'm looking at thousands of servers so that doesn't concern me. It just seemed to be to shoe-horning the problem to fit the solution. > > If there is no possibility at all to pre-compile packages from the PSP > (e.g. by re-using an imaging server or stow or something similar) then I > would a) hate the vendor and b) create a single script doing an > unattended PSP install which is called by puppet when needed. Oh, we got all KINDS of HP hate going on over here over this :) We have tried the pre-compilation route, and the issue is that it loads kernel modules that are minor rev sensitive. We have to have i386, x86_64, x86_64 largesmp, and ia64 versions built for every flavor of kernel in the environment. It became unmanageable very quickly. We currently are using an unattended PSP install script too but that's what I'm trying to get away from. It's becoming woefully unweildy because of differences in the way RHEL4 and RHEL5 do package installation, and different package dependencies between different flavors of RHEL. That's why I was hoping to use puppet to resolve those dependencies and install the appropriate tools without having to figure it out on every single variation of server. > If you really want to force this into puppet proper, you need a list of > all packages needed by the installation, and -- for each server -- a > list of packages out of this set that should be always installed. We have both of those. The first list is the same across all platforms and environments. The second list will vary based on the server environment, but I think I can get around that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---