Bruce Richardson wrote:
On Wed, Apr 07, 2010 at 12:10:07PM -0700, Dmitry V'yal wrote:
Hello,
I'm currently administering a vps running a dozen of php-sites. I use
several scripts for deploying new sites, updating them, taking the
backups and so on. All the system is quite fragile and error-prone.
I'm thinking about some more integrated solution. Can puppet be useful
in my situation? Or is it primarily intended for managing big number
of similarly configured hosts?
The latter, but that doesn't necessarily mean puppet couldn't be useful
to you. After all, puppet lets you define dependencies so that you can
specify that action A is triggered when file B is modified, action C
happens if acion A is successful and so on, which must describe half of
what your scripts do. It also lets you define templates and then create
multiple instances based on those templates and different
configurations, which must be the other half of what you do. So I think
it can help you. And you may find other things about your vps that it
can configure for you.
I would create a definition that describes your site layout. Each time
you invoke that definition in your script, with different parameters,
it'll create the site for you and trigger any necessary actions (like
restarting apache). You can also have the directory hierarchy that
contains your sites managed by puppet in such a way that it will delete
any files that weren't created by your current puppet config. That way,
all you have to do is remove the description of a site from your config
and all the files previously generated for it will be removed the next
time puppet is run.
Looks very promising to me :)
One of the problems with my current setup, is what there is no central
storage of configuration After one ran the script, the only way to see
what's is currently served is to manually look at all these config files
and site directories.
Another problem, is what from time to time after I made some
enhancements all the configs must be modified a bit. For example, I
setup a log analyzing utility and now it must be enabled for all the
sites. Such an operation is extremely painful right now.
You don't need a puppetmaster to run puppet, you can run it on a single
host from local standalone scripts. So you don't need to incur the
overhead of running puppetmaster and puppet daemons just for your sites.
Great )
Some time ago I looked at Chef, but even in it's minimal configuration
it looked like an overkill for my needs.
Of course, you can do this yourself by choosing your own templating
system and writing scripts to manipulate it, but puppet can make it much
simpler.
Yeah, I'm already fed up with my current sed-based templates and wanted
to move to ERB, but it reminded my reinventing the wheel the second time
in a row :)
Thank you very much for all the suggestions
--
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.
