On Jun 4, 2010, at 1:19 AM, David Schmitt wrote:
On 6/4/2010 3:45 AM, Daniel Pittman wrote:
Well, my use case pretty much always comes down to "do something
for this data
about this host", and hasn't ever gotten more than two levels deep:
backuppc::server needs a per-client configuration
per-client configuration needs this clients mount-points and
excludes
the load-balancer needs the hostname and ip of every app-server
Just as another "data point", I cover those things also with export/
collect, but do not need an ERB template, by actually creating the
needed file fragments (usable for volcane's concat) on the source
hosts. Collection can then use the <<||>> query language to select
what's needed, in my cases always by tag.
That approach has great flexibility, without the pain of accessing
the DB myself.
To me, we need to be focusing on fixing Collection so it actually
works well for this purpose. It sounds like most of Daniel Pittman's
needs would be solved by better resource collection.
I am open to adding support for pulling attributes from the database
in general, I just don't think that's actually the right long-term
answer.
--
You've achieved success in your field when you don't know whether what
you're doing is work or play. -- Warren Beatty
---------------------------------------------------------------------
Luke Kanies -|- http://puppetlabs.com -|- +1(615)594-8199
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
