On 6/10/2010 3:36 AM, Daniel Pittman wrote:
Luke Kanies<[email protected]> writes:1) Easy way to force updates when a required catalog has been changed. (This doesn't automatically fix the problem of new data showing up, only changed data.)2) With good graph viewing, a straightforward way to view the whole architecture, with cross-host dependencies visible. This is why I'm so focused on getting export/collect to work - when you're sharing rich data, this kind of information is possible, but if you're just doing db queries, it's all invisible.*nod* I think my conceptualization is that the "db queries" bit is an implementation detail of the actual solution you have in mind; you could transparently let your graph of cross-machine relationships handle that. (OTOH, I also think that the whole "storeconfigs" thing is probably a proxy for an mcollective "live query" type operation across the infrastructure, so my ideas may be completely crazy :)
There is an overlap between the two, but both provide things the other one can't. Live queries can (probably?) answer questions about unmanaged resources, which are not stored in the database. Exported resources on the other hand do provide an added value that cannot be directly achieved with live queries.
Best Regards, David -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg -- 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.
