Puppet users - May 2007 - RFC - file population and basic configuration script

Hi,

Since I''m about to deploy puppet on a large number of hosts, I got a
little tired of inputing configuration files which basically held very
similar information.

I wrote a small script where I intended the following:

- when you encounter a file that you realize should be handled by
  puppet, you run my script with the filename as argument. The script
  looks at the mode, user, group, etc and then places it in subversion
  in the right place
- it creates a basic class file for the file in subversion, today with
  multiple sources which is good when you''re managing many sites.
  Ie, first it looks for the file in the node:s private space, then
  under another class (currently site but it can be configured for
  anything) and lastly it looks at a "common" place.
- I realize the same goal can be achieved by templating, but if that
  isn''t the way for you for some reason, perhaps this may be of use.

It''s not a very good looking script, I made it for myself. I will
publish an url to the script tomorrow, perhaps someone else about to
deploy puppet will find it useful. Input, comments and ideas are all
welcome.

//Andreas Loong

-- 
CES 1984 - "The Lorraine''s graphics are a whole step ahead of any
personal computer now on the market. This computer is potentially powerful
enough to make an IBM-PC look like a four-function calculator."

On May 15, 2007, at 11:26 AM, Andreas Loong wrote:
>
> Hi,
>
> Since I''m about to deploy puppet on a large number of hosts, I got
a
> little tired of inputing configuration files which basically held very
> similar information.
>
> I wrote a small script where I intended the following:
>
> - when you encounter a file that you realize should be handled by
>   puppet, you run my script with the filename as argument. The script
>   looks at the mode, user, group, etc and then places it in subversion
>   in the right place
> - it creates a basic class file for the file in subversion, today with
>   multiple sources which is good when you''re managing many sites.
>   Ie, first it looks for the file in the node:s private space, then
>   under another class (currently site but it can be configured for
>   anything) and lastly it looks at a "common" place.
> - I realize the same goal can be achieved by templating, but if that
>   isn''t the way for you for some reason, perhaps this may be of
use.
>
> It''s not a very good looking script, I made it for myself. I will
> publish an url to the script tomorrow, perhaps someone else about to
> deploy puppet will find it useful. Input, comments and ideas are all
> welcome.
I wholly applaud this kind of work -- I''m always looking for great  
ways to build a process around using Puppet.  I''d love to see people  
publish how they use Puppet, including the tools they write and use,  
and if you have any feature requests that can streamline your  
process, please add them to the ticket db.

  --
  Wear the old coat and buy the new book.     -- Austin Phelps
  ---------------------------------------------------------------------
  Luke Kanies | http://reductivelabs.com | http://madstop.com

On Tue, May 15, 2007 at 12:01:51PM -0500, Luke Kanies
wrote:
> > It''s not a very good looking script, I made it for myself. I
will
> > publish an url to the script tomorrow, perhaps someone else about to
> > deploy puppet will find it useful. Input, comments and ideas are all
> > welcome.
> 
> I wholly applaud this kind of work -- I''m always looking for great
> ways to build a process around using Puppet.  I''d love to see
people
> publish how they use Puppet, including the tools they write and use,  
> and if you have any feature requests that can streamline your  
> process, please add them to the ticket db.
Thank you for the endorsement. I''ve cleaned it up a little now, and
I''m
ready to share it with others.

http://developer.acggbg.org/scripts/ is where you''ll find PupIt. Again,
suggestions for improvements, enhancements and bugreports welcome.
However, send them directly to me, and not to this list.

//Andreas Loong

-- 
CES 1984 - "The Lorraine''s graphics are a whole step ahead of any
personal computer now on the market. This computer is potentially powerful
enough to make an IBM-PC look like a four-function calculator."