What techniques are people using to do particular tasks once in a great while? For example, usually you don''t want to automatically upgrade the kernel until it''s fully tested but, of course one day you will. How do you work through Puppet to perform this activity on an on-demand basis instead of a periodic job. Are you using state files like "if file X exists do Y" or are you doing something more sophisticated? Thanks, Trevor _______________________________________________ Puppet-users mailing list Puppet-users@madstop.com https://mail.madstop.com/mailman/listinfo/puppet-users
> What techniques are people using to do particular tasks once in a great > while? > > For example, usually you don''t want to automatically upgrade the kernel > until it''s fully tested but, of course one day you will. > > How do you work through Puppet to perform this activity on an on-demand > basis instead of a periodic job. > > Are you using state files like "if file X exists do Y" or are you doing > something more sophisticated?That''s a good question. Unfortunately, we don''t use puppet to do things like that. But we have a really cool tool that you might want to look at: <http://www.eyrie.org/~eagle/software/remctl/> -- Digant C Kasundra <digant@stanford.edu> Technical Lead, ITS Unix Systems and Applications, Stanford University
On 3/7/07, Trevor Vaughan <peiriannydd@gmail.com> wrote:> How do you work through Puppet to perform this activity on an on-demand > basis instead of a periodic job.Sorry for the late answer, but we''re using a simple hack for a system upgrade (apt-get dist-upgrade), which we first want to check. Actually, we''re looking for a way to create a "I want to update these on 7836 machines, am I allowed?" thingy, so we can checklist each item. For now, we''re simply doing: configfile { "/etc/update_initiator": source => "update_initiator", } exec { "/usr/bin/apt-get -y dist-upgrade": refreshonly => true, subscribe => File["/etc/update_initiator"], } When we authorise an update, we simply edit the update_initiator file. It''s actually kind of convenient, since it allows us to keep track of the updates we apply. A sample entry in update_initiator would be: 20070226 -- Tim (debian-archive-keyring, libldap, mysql) But any chance to the file would be enough. -- Gegroet, Tim