Puppet users - Nov 2008 - Can I store my configuration files in subversion or git and have puppet manage them?

Hi,

     We are looking to find something to manage our configuration
files.  Specifically our Apache web server farm configuration files.
We would like to store them in version control and have puppet push
them out or have the clients pull them making the necessary
customizations for each physical machine.  Is that something that
puppet can do?  Thanks in advance for any and all guidance

Thanks,
~Jet

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

Sure, you can have the puppet clients pull config files from the master.
This is the primary purpose of a configuration management system. Having
puppet pull stuff from subversion is also possible, if that is what you
prefer, but a method I would go by. What we do is having all our puppet
configuration in subversion and then have a working copy of that on the
master. You will find that a lot of users in the puppet community would
recommend git instead of subversion for various reasons. Puppet is very
flexible and can be utilized in a lot of different manners.

I would just make a apache module and have that making sure the clients get
the config files they are supposed to.

Regards
Bjørn Dyresen

2008/11/26 Jet <wildjetfu@gmail.com>
>
> Hi,
>
>     We are looking to find something to manage our configuration
> files.  Specifically our Apache web server farm configuration files.
> We would like to store them in version control and have puppet push
> them out or have the clients pull them making the necessary
> customizations for each physical machine.  Is that something that
> puppet can do?  Thanks in advance for any and all guidance
>
> Thanks,
> ~Jet
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Jet wrote:
> We are looking to find something to manage our configuration files.
> Specifically our Apache web server farm configuration files. We would
> like to store them in version control and have puppet push them out
> or have the clients pull them making the necessary customizations for
> each physical machine.
Not contradicting anything said before, but yes, puppet can handle that. 
Rather than keep a separate copy of each server''s configuration file in
version control, you''ll possibly want to keep a template of the 
configuration files in version control, and let the puppetmaster server 
customize those templates for each server as needed. Early on, you''ll 
probably want to switch from making piecemeal puppet classes to making 
self-contained modules that contain all the files, templates, and puppet 
manifests to configure a particular service.

Example of such a module for Amanda is at 
http://blogs.cae.tntech.edu/mwr/2007/08/02/the-new-file-server-puppet-and-modules/
-- not trivially simple, but not too complex, either.

-- 
Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
931 372-3601 / Tennessee Technological University -- renfro@tntech.edu

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

Are you saying rather then store the actual configuration files in
version control, store everything that is necessary to generate the
configuration file in version control?

Thanks,
~Jet

On Thu, Nov 27, 2008 at 9:11 AM, Mike Renfro <renfro@tntech.edu>
wrote:
>
> Jet wrote:
>
>> We are looking to find something to manage our configuration files.
>> Specifically our Apache web server farm configuration files. We would
>> like to store them in version control and have puppet push them out
>> or have the clients pull them making the necessary customizations for
>> each physical machine.
>
> Not contradicting anything said before, but yes, puppet can handle that.
> Rather than keep a separate copy of each server''s configuration
file in
> version control, you''ll possibly want to keep a template of the
> configuration files in version control, and let the puppetmaster server
> customize those templates for each server as needed. Early on,
you''ll
> probably want to switch from making piecemeal puppet classes to making
> self-contained modules that contain all the files, templates, and puppet
> manifests to configure a particular service.
>
> Example of such a module for Amanda is at
>
http://blogs.cae.tntech.edu/mwr/2007/08/02/the-new-file-server-puppet-and-modules/
> -- not trivially simple, but not too complex, either.
>
> --
> Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
> 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Yes,  with puppet you have a declarative language enabling you to do much
more than just storing config files in a version control system. The way
people do it around here is storing the code they write in puppets language
in a version control system, just like they would store any other source
code in a version control system.  It is a lot to get the head around and I
recommend you start here:

http://reductivelabs.com/trac/puppet/wiki/DocumentationStart





2008/11/30 Jet Wilda <wildjetfu@gmail.com>
>
> Are you saying rather then store the actual configuration files in
> version control, store everything that is necessary to generate the
> configuration file in version control?
>
> Thanks,
> ~Jet
>
> On Thu, Nov 27, 2008 at 9:11 AM, Mike Renfro <renfro@tntech.edu>
wrote:
> >
> > Jet wrote:
> >
> >> We are looking to find something to manage our configuration
files.
> >> Specifically our Apache web server farm configuration files. We
would
> >> like to store them in version control and have puppet push them
out
> >> or have the clients pull them making the necessary customizations
for
> >> each physical machine.
> >
> > Not contradicting anything said before, but yes, puppet can handle
that.
> > Rather than keep a separate copy of each server''s
configuration file in
> > version control, you''ll possibly want to keep a template of
the
> > configuration files in version control, and let the puppetmaster
server
> > customize those templates for each server as needed. Early on,
you''ll
> > probably want to switch from making piecemeal puppet classes to making
> > self-contained modules that contain all the files, templates, and
puppet
> > manifests to configure a particular service.
> >
> > Example of such a module for Amanda is at
> >
>
http://blogs.cae.tntech.edu/mwr/2007/08/02/the-new-file-server-puppet-and-modules/
> > -- not trivially simple, but not too complex, either.
> >
> > --
> > Mike Renfro  / R&D Engineer, Center for Manufacturing Research,
> > 931 372-3601 / Tennessee Technological University -- renfro@tntech.edu
> >
> > >
> >
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Thanks  I''ll do that.

On Sat, Nov 29, 2008 at 6:20 PM, Bjørn Dyre Dyresen <bjorn@dyresen.net>
wrote:
> Yes,  with puppet you have a declarative language enabling you to do much
> more than just storing config files in a version control system. The way
> people do it around here is storing the code they write in puppets language
> in a version control system, just like they would store any other source
> code in a version control system.  It is a lot to get the head around and I
> recommend you start here:
>
> http://reductivelabs.com/trac/puppet/wiki/DocumentationStart
>
>
>
>
>
> 2008/11/30 Jet Wilda <wildjetfu@gmail.com>
>>
>> Are you saying rather then store the actual configuration files in
>> version control, store everything that is necessary to generate the
>> configuration file in version control?
>>
>> Thanks,
>> ~Jet
>>
>> On Thu, Nov 27, 2008 at 9:11 AM, Mike Renfro <renfro@tntech.edu>
wrote:
>> >
>> > Jet wrote:
>> >
>> >> We are looking to find something to manage our configuration
files.
>> >> Specifically our Apache web server farm configuration files.
We would
>> >> like to store them in version control and have puppet push
them out
>> >> or have the clients pull them making the necessary
customizations for
>> >> each physical machine.
>> >
>> > Not contradicting anything said before, but yes, puppet can handle
that.
>> > Rather than keep a separate copy of each server''s
configuration file in
>> > version control, you''ll possibly want to keep a template
of the
>> > configuration files in version control, and let the puppetmaster
server
>> > customize those templates for each server as needed. Early on,
you''ll
>> > probably want to switch from making piecemeal puppet classes to
making
>> > self-contained modules that contain all the files, templates, and
puppet
>> > manifests to configure a particular service.
>> >
>> > Example of such a module for Amanda is at
>> >
>> >
http://blogs.cae.tntech.edu/mwr/2007/08/02/the-new-file-server-puppet-and-modules/
>> > -- not trivially simple, but not too complex, either.
>> >
>> > --
>> > Mike Renfro  / R&D Engineer, Center for Manufacturing
Research,
>> > 931 372-3601 / Tennessee Technological University --
renfro@tntech.edu
>> >
>> > >
>> >
>>
>>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---