General discussion about Chef

[chef] Re: Re: Re: Re: Re: Re: Chef handler to reboot windows machine


Chronological Thread 
  • From: Todd Pigram < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Chef handler to reboot windows machine
  • Date: Tue, 25 Nov 2014 06:52:38 -0500
Sachin, 

I guess it depends on how you are installing the chef client? If you have a bare bone image with Chef Client installed, you can install the Chef Service using the MSI. If you are using Knife, then you have a couple of options:
1. Using windows_task as Greg mentioned
2. or create a batch recipe that runs the following to install the service and start it -  chef-service-manager -a install & chef-service-manager -a start

I do both as starting with 11.16.2 + , after a RDSH install the service doesn't start even though I have it automatic(delayed) and recover - restart service 3 times and set 0days 1 minute, it doesn't start. 

Once you have the this set.

In my previous response, you see that I have 

not_if {reboot_pending?} this tells chef if there is a pending reboot, don't run until next time.

So in my example for a RDSH install:

# install RDS
powershell node['w2k8']['rds'] do
  code <<-EOH
  Import-Module ServerManager
  Add-WindowsFeature RDS-RD-Server
  EOH
  not_if {reboot_pending?}
end    --    This reboots


# Install desktop experience
powershell node['w2k8']['deskexp'] do
  code <<-EOH
  Import-Module ServerManager
  Add-WindowsFeature Desktop-Experience
  EOH
  not_if {reboot_pending?}
end --- Restarts the run, then reboots

powershell node['w2k8']['xps'] do
  code <<-EOH
  Import-Module ServerManager
  Add-WindowsFeature XPS-Viewer
  EOH
  not_if {reboot_pending?}
end - restarts next run no reboot. 

windows_reboot 30 do 
  reason 'Chef said to'
  only_if {reboot_pending?}
end

Here is an example of a complete run list that I use.


​
usually completes without intervention. 

I use the bare bone image method as my Chef workstation is not on the same network as the instances, so I spin the image, put in the client.rb, and validation.pem, run chef-client locally once, then use the UI to assign the runlist. I wish I could just use knife, but I can't at the moment. Plus this makes it easier for my teammates to use as they aren't totally up on Chef, but they understand Windows. 

Hope this helps

Todd


On Mon, Nov 24, 2014 at 8:21 AM, Greg Zapp < " target="_blank"> > wrote:
Hi Sachin,

I build my AMI's using Chef and I have also split them into two parts(before and after reboot).  Before boot adds a windows task to run Chef on the next boot: https://github.com/opscode-cookbooks/windows#windows_task .  It needs to run as SYSTEM without a password to work without login(IIRC).  After boot recipe removes the task.

Cheers,
   -Greg

On Tue, Nov 25, 2014 at 2:03 AM, Sachin Gupta < " target="_blank"> > wrote:
Thanks James/Todd for sharing this info.

Do you know when chef 12 will be released??

In the meantime, I also tried to add the following code for reboot at the end of Apache installation.

windows_reboot 60 do
reason "Installed a new Apache package"
action:request
end

At the top of the Apache recipe, I had also added the line ( include_recipe 'windows::reboot_handler' and 'include_recipe 'chef_handler::default') and also added (depends  "windows" and chef_handler)in apache metadata.rb.

I am able to get the reboot message and system gets rebooted after a period of 60 sec. From this use case it is clear that reboot is done only at the end of the chef client.

Now if I want to do a reboot at the middle of execution, then will this approach work??

a) will break the recipe into two parts, first part will installed the required package and second part will do the remaining stuff.

Now the biggest challenge is how to start the chef client again after reboot. 
I have to make a reboot.txt file before the reboot in first recipe and after that system will be rebooted.  during the startup script if I pass the chef-solo command to run the chef client with the second recipe and in that recipe it will check whether the reboot.txt file is present or not. if reboot.txt is present then only second recipe will move forward otherwise it will not do anything and exit.


James/Todd   Is this making any sense and would like to know whether I am moving on a correct  path??


Thanks & Regards,
Sachin Kumar






On Mon, Nov 17, 2014 at 11:11 PM, Todd Pigram < " target="_blank"> > wrote:
James,

That is awesome!!!!

On Mon, Nov 17, 2014 at 11:46 AM, James Scott < " target="_blank"> > wrote:
Also, Chef 12 adds a new resource that moves the cookbook-based reboot resource into core Chef:


On Mon, Nov 17, 2014 at 7:20 AM, Todd Pigram < " target="_blank"> > wrote:
Sachin,

make sure that the 'windows::reboot_handler 'is at the top of your run list as well as putting ('depends     'windows') in your metadata.rb.

The install what you want and Chef will reboot and continue. 

here is an example of installing RDSH for preparation for Citrix XenApp install. It will starts the RDSH, reboot and then come back and do the desktop experience, and so on.... As long as you installed the chef service during client install or created a scheduled task. 

# install RDS
powershell node['w2k8']['rds'] do
  code <<-EOH
  Import-Module ServerManager
  Add-WindowsFeature RDS-RD-Server
  EOH
  not_if {reboot_pending?}
end


# Install desktop experience
powershell node['w2k8']['deskexp'] do
  code <<-EOH
  Import-Module ServerManager
  Add-WindowsFeature Desktop-Experience
  EOH
  not_if {reboot_pending?}
end

powershell node['w2k8']['xps'] do
  code <<-EOH
  Import-Module ServerManager
  Add-WindowsFeature XPS-Viewer
  EOH
  not_if {reboot_pending?}
end

windows_reboot 30 do 
  reason 'Chef said to'
  only_if {reboot_pending?}
end

if you still have issues, create a library file called reboot_pending.rb in you cookbook - I was given this by Alex Vinyar from Chef. This was added to Chef Client back in version 11.12...But I still use it

reboot_pending.rb

class Chef
  class Resource
    # include Chef::Mixin::ShellOut

    def reboot_pending?
      # Any files listed here means reboot needed
      (Registry.key_exists?('HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations') &&
        Registry.get_value('HKLM\SYSTEM\CurrentControlSet\Control\Session Manager','PendingFileRenameOperations').any?) ||
      # 1 for any value means reboot pending
      # "9306cdfc-c4a1-4a22-9996-848cb67eddc3"=1
      (Registry.key_exists?('HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired') &&
        Registry.get_values('HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired').select{|v| v[2] == 1 }.any?) ||
      # 1 or 2 for 'Flags' value means reboot pending
      (Registry.key_exists?('HKLM\SOFTWARE\Microsoft\Updates\UpdateExeVolatile') &&
        [1,2].include?(Registry::get_value('HKLM\SOFTWARE\Microsoft\Updates\UpdateExeVolatile','Flags'))) ||
      # added by Alex
      Registry.key_exists?('HKLM\Software\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending')
    end

  end
end

 

On Mon, Nov 17, 2014 at 8:30 AM, Sachin Gupta < " target="_blank"> > wrote:
Hi All,

I have a use case where I need to reboot windows machine after some package installation.

would like to know the possible best practice to implement this use case;

a)  Make a single recipe that will do the package installation and product installation and then at last      call chef handler to reboot the machine

a)   make two different chef recipe, the first recipe will install packages and then reboot the machine,
       the second recipe will do the remaining stuff. I don't know this will work or not.    
       Is there a way, we can return the chef client to run the same cookbook after reboot??
    

I also gone through some documentation but nothing is useful.

Any help would the useful .


Thanks & Regards,
Sachin Kumar



--




--





--

Archive powered by MHonArc 2.6.16.

§