I'm a pretty good candidate for a Puppet-fer-Windows guinea pig here
as I'd be able to get a lot of mileage out of just being able to use
the File, Service and Exec types on that platform ("Is game server
running?"  "Has configuration been updated?"  etc.) ... but I haven't
found much in puppet-users about what the current state is of Puppet
and Facter for Windows.

So here's what I've done so far on my Windows 7 desktop, just for fun:

*  Installed the latest version of Ruby via RubyInstaller:
http://files.rubyforge.vm.bytemark.co.uk/rubyinstaller/rubyinstaller-1.9.1-p429.exe
*  Added ruby to my default path.
*  Downloaded and expanded the puppet 2.6.0RC2 tarball.
*  Ran the rakefile, watched it die.  (oops)
*  Ran install.rb, watched it choke on the nonexistence of C:
\Ruby191\sbin ...
*  Created that directory, re-ran it, watched it choke on the
nonexistence of gzip.
*  Decided to give up on the installer and see how far I could get in
running Puppet.
*  Oh.  No Facter installed.
*  Pulled facter from github, latest revision so that maaaybe it'll
run on Windows: 
http://download.github.com/reductivelabs-facter-1.5.7-35-g1bd2ca2.zip
*  Expanded and ran facter's install.rb.  Hmmm, seems like it
worked...
*  Facter's not in my path.  Oh.  Maybe running this command will
work: ruby C:\Ruby191\bin\facter ...
*  OMG! :
Could not retrieve puppetversion: Cannot determine basic system
flavour
domain => myactualdomain.local
facterversion => 1.5.7
fqdn => zod.myactualdomain.local
hardwaremodel => i686
hostname => zod
ipaddress => myactualipaddress
kernel => windows
kernelmajversion => 6.1
kernelrelease => 6.1.7600
kernelversion => 6.1.7600
macaddress => myactualmacaddress
operatingsystem => windows
operatingsystemrelease => 6.1.7600
path => C:\Ruby191\bin;c:\Program Files (x86)\NVIDIA Corporation\PhysX
\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:
\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files
(x86)\QuickTime\QTSystem\;C:\Program Files\Windows Imaging\
ps => ps -ef
rubyversion => 1.9.1
timezone => Central Daylight Time

*  Tried to run Puppet in the same way:  ruby C:\Ruby191\bin\puppet
describe
*  Awww:

C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet/feature/base.rb:47:in `<top
(required)>': Cannot determine basic system flavour (Puppet::Error)
        from C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet.rb:53:in
`require'
        from C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet.rb:53:in
`<module:Puppet>'
        from C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet.rb:26:in `<top
(required)>'
        from C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet/application.rb:
292:in `require'
        from C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet/application.rb:
292:in `initialize'
        from C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet/util/
command_line.rb:55: in `new'
        from C:/Ruby191/lib/ruby/site_ruby/1.9.1/puppet/util/
command_line.rb:55: in `execute'
        from C:/ruby191/bin/puppet:4:in `<main>'

I'm assuming this is some kind of path problem and is therefore
inherent to my Ruby install, not so much a "Puppet is freaking out
because it's on Windows" problem.  I thought I'd share my experience
here to see how far other people have gotten ... I'm not in the habit
of developing or running Ruby on Windows at all, and I know there are
multiple flavors of installer.  I assume they behave differently.

Before I pour much more effort into this project -- I would LOVE to
bash my Windows game servers with the Puppet stick, it would make
pushing patches 2,415 times better -- I wanted to post and compare
notes with anyone else who was working on this.

And if *nobody's* trying this yet, and they're looking through The
Google ... I hope this helps you get it working.

-steve

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to