On Wed, Apr 15, 2009 at 8:29 AM, Joe McDonagh
<[email protected]> wrote:
>
> James Richardson wrote:
>> Hi,
>>
>> I am just starting to try to learn/use puppet. The problem I am trying
>> to overcome now it how to make a client reboot after a kernel upgrade.
>>
>> Alternatively, what is the best practice for managing kernels on a
>> debian system.
>>
>> Thanks
>>
>
> I manage upgrades through scripts, but you can have an exec like this:
>
> exec { "/sbin/reboot":
>   refreshonly => "true"
> }
>
> Then in your kernel package def set the attribute notify =>
> Exec["/sbin/reboot"]. This means when your kernel package gets changed,
> the system reboots. It will be unpredictable however, unless your nodes
> are in LDAP and you can run puppetrun on all of them at once...
>
This brings you to the really question. Do you really want the servers
rebooting in a semi random manner? Some as disruptive as a system
reboot really need to be set to happen at pre-scheduled time, not
really whenever there is a kernel update. I would suggest using a
'notify =>' to a cron type that sets up a pre-scheduled reboot window.

Evan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to