Denis,
Take a look at the "application" cookbooks folder on github* for an
idea of managing in-house application configurations. We're using chef
to manage things like log4j.xml files, spring properties files and
other things. The benefit you get from using the same tool to manage
your application configuration that you use for system configuration
is that your application configurations are now infrastructure aware.
Take database servers:
If you have a node in Chef tagged as your master db server, you can
now refer to that information in your application configuration. If
the role of db master moves to another box, your application
configuration will be updated on next run.
* https://github.com/opscode/cookbooks/tree/master/application
On Fri, Feb 25, 2011 at 8:51 AM, Denis Haskin < "> > wrote:
> (apologies if this has been previously asked & answered; the mailing list
> archives are sort of hard to use.)
> We're investigating using chef, among other purposes to better manage
> cross-system "application" configuration. Specifically, we have services
> from multiple projects running on multiple servers, and at the moment each
> project has their own configuration file, despite the fact that there is
> configuration that would be best shared among them.
> I'm quite sure this could be helped by chef but I'm having a little trouble
> completely wrapping my head around how we would do this with chef. Seems
> like all of the chef docs & tutorials are focused on provisioning and
> configuring services like apache, mysql, etc. (And, as I've read elsewhere,
> a lot of the chef doc seems somewhat abstract and doesn't always relate
> these abstract concepts to concrete usage.)
> Does anybody have any samples/suggestions/etc?
> Thanks!
> dwh
>
Archive powered by MHonArc 2.6.16.