On 2012-05-25 19:44, Chris Price wrote:
I'm surveying the landscape of existing puppet modules that have to do
with relational database functionality. I've talked with a few folks
now and it seems like there is a fairly broad range of opinions on what
"ideal" would look like w/rt managing rdbms with puppet.
Hi,
I believe that rdbms are complex enough they warrant implementing both
layers separately: One module for each implementation that provides for
fine-grained control over all available features and tunings, as well as
a common integration module that provides a simple, unified interface.
The first is needed because I need all the knobs for tuning my system.
The second is needed because I just want to say "class { 'zenoss':
database => 'postgres' }" and have it work.
Using the first set of module in the common integration module ensures
that tuning is still possible.
Common code can always be placed into a base module, used by everyone.
Best Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
