New knife "windows bootstrap" subcommand

Available at: http://github.com/dougm/chef/tree/CHEF-1569

Tested against:
Windows 2003 Server standard
Windows 2008 Server standard
Windows Vista Ultimate
Windows 7 Pro

Poll - How would you like to have the chef config files, etc., laid out by default when using the windows bootstrap command?

1) unix-like

c:/etc/chef/client.rb
c:/etc/chef/client.pem
c:/etc/chef/validation.pem
c:/var/chef/backup/
c:/var/chef/cache/
c:/var/log/chef/client.log
c:/bin/chef-client.exe

2) all under c:/chef + somewhat unix-like

c:/chef/etc/client.rb
c:/chef/etc/client.pem
c:/chef/etc/validation.pem
c:/chef/var/backup/
c:/chef/var/cache/
c:/chef/log/client.log
c:/chef/bin/chef-client.exe

3) all under c:/chef - flat

c:/chef/client.rb
c:/chef/client.pem
c:/chef/validation.pem
c:/chef/backup/
c:/chef/cache/
c:/chef/client.log
c:/chef/chef-client.exe

4) other?

In addition to client.log, the winsw service wrapper creates the following log files, which would site along side client.log:

chef-client.err.log
chef-client.out.log
chef-client.wrapper.log

Hi Doug!

First, thanks for this. Totally awesome to improve Windows support :-D.

In my observation, when people port Unix/Linux tools to Windows, they use the strategy like #2 in your poll. There's a top-level directory that contains the unix-like structure. Personally this makes the most sense to me.

Thanks Josh! I agree on #2 and have pushed the changes to my branch:

To git@github.com:dougm/chef.git
   99b763c..d00b3c4  CHEF-1569 -> CHEF-1569

Everything is under c:\chef now:

C:\chef\etc\validation.pem [+]
C:\chef\etc\config.rb [+]
C:\chef\etc\first-boot.json [+]
C:\chef\etc\client.pem [~]

C:\chef\tmp\bootstrap.bat [+]
C:\chef\tmp\client-install.vbs [+]
C:\chef\tmp\rubyinstaller-1.8.7-p249-rc2.exe [+]

C:\chef\var\cache\checksums\...  [~]
C:\chef\var\cache\cookbooks\... [~]
C:\chef\var\backup\... [~]

C:\chef\bin\chef-client.exe [*]
C:\chef\bin\chef-client.xml [*]

C:\chef\log\client.log [*]
C:\chef\log\chef-client.err.log [*]
C:\chef\log\chef-client.out.log [*]
C:\chef\log\chef-client.wrapper.log [*]

+ == created by "knife windows bootstrap"
* == created by windows::chef_client cookbook and the service it runs
~ == created by chef-client run

ok to delete C:\chef\tmp\ after bootstrap

Note that to bootstrap Windows 7 and Vista you either need to disable UAC on the remote machine or from http://support.microsoft.com/kb/942817 do the following in cmd.exe run as Administrator:

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f

Also pushed 118f0fa to dougm/chef/CHEF-1569:
add -h flag to psexec: If the target system is Vista or higher, has the process run with the account's elevated token, if available.

When trying to fetch to source for CHEF-1569 using git command like,

git clone http://github.com/dougm/chef/tree/CHEF-1569

An error message was return,

Cloning into CHEF-1569...
fatal: http://github.com/dougm/chef/tree/CHEF-1569/info/refs not found: did you run git update-server-info on the server?

Any idea why this is happening?

When trying to fetch to source for CHEF-1569 using git command like,

git clone http://github.com/dougm/chef/tree/CHEF-1569

An error message was return,

Cloning into CHEF-1569...
fatal: http://github.com/dougm/chef/tree/CHEF-1569/info/refs not found: did you run git update-server-info on the server?

Any idea why this is happening?

That's just the github url. If you want to get the source via git, you should start with the opscode/chef master branch. Either with your own fork, or:

git clone git://github.com/opscode/chef.git
cd chef

Then you can create a local branch with the CHEF-1569 changes like so:

git remote add dougm git://github.com/dougm/chef.git
git remote update
git checkout -b CHEF-1569
git merge dougm/CHEF-1569

Or, less commands but you'll be out of sync with the opscode/chef master branch:
git clone git://github.com/dougm/chef.git
cd chef/
git checkout --track -b CHEF-1569 origin/CHEF-1569

Thanks for answering the question quickly. I actually download the knife code directly from github download button. But it's nice to learn some git command line tricks.

Here's another question, I was able to run knife windows brootstrap fqdn -r windows:chef_client, but

1. Is there a way to install ruby-1.8.7.p-302.exe rather than the hard code rubyinstaller-1.8.7-p249-rc2.exe. I modify the vb script, but it brows away on ADO.stream ...
2. Although bootstrap can successfully install ruby binary, but it failed to find first-boot.json. Looking at the code from the knife folder, a lot of place refer to this json file, but I cannot find it anywhere! Is this file generated dynamically or we have to create one for ourself?

Paste the error message here:

[Fri 10/01/2010 14:42:49.25]
d:\ > knife-start windows bootstrap chefclient-vm1.hq.daptiv.com -r windows::chef_client
INFO: Bootstrapping Chef on chefclient-vm1.hq.daptiv.com

PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com

c:\chef\tmp>cscript /nologo client-install.vbs
Using existing rubyinstaller-1.8.7-p249-rc2.exe
C:\Ruby exists
C:\Ruby\bin\ruby.exe C:\Ruby\bin\gem install --no-ri --no-rdoc chef ruby-wmi windows-pr win32-open3 rubyzip
ERROR: While executing gem ... (Errno::ENOENT)
No such file or directory - Z:/

c:\chef\tmp>(

c:/ruby/bin/ruby
:
No such file or directory – c:/ruby/bin/chef-client
(
LoadErro

r)

) 1>c:/chef/etc/client.rb

c:\chef\tmp>() 1>c:/chef/etc/first-boot.json

c:\chef\tmp>c:/ruby/bin/ruby c:/ruby/bin/chef-client -c c:/chef/etc/client.rb -j c:/chef/etc/first-boot.json -l info"
cmd.exe exited on chefclient-vm1.hq.daptiv.com with error code 1.

If you change the script to point at the new .exe, make sure you also change the Url variable.

The ENOENT error sounds like an issue with 'gem', not the windows bootstrap command. Do you get the same error if you run the gem install ... command manually? Try add --verbose to the gem command and see if that sheds any light. Do you have a drive mapped to Z: ?

Wow, this is pretty awesome stuff (as usual), thanks Doug!

If you want to bootstrap a windows 2008 - 64 bits machine you need to modify the source code of a couple of files:

#chef/chef/lib/chef/knife/bootstrap/windows-gems.erb
> c:/chef/etc/client.rb (
@echo.require 'win32ole'
@echo.WIN32OLE.codepage = WIN32OLE::CP_UTF8
@echo.log_level :info

#To bootstrap in win2008 add -s option to psexec
#chef/chef/lib/chef/knife/windows_bootstrap.rb
        cmd = ['psexec', @unc_path, "-h", "-s", "-w", 'c:\chef\tmp']

I've taken the chef-client cookbook portion of Doug's work and integrated it with the current chef-client cookbook here: http://tickets.opscode.com/browse/COOK-795