Re: [Puppet-dev] Export and collect data, not just resources.

2012-07-04 Thread Luke Kanies
On Jun 29, 2012, at 12:54 AM, Stephen Gran wrote: > On Thu, 2012-06-28 at 08:40 -0700, Luke Kanies wrote: > > >> Do you have cases where you need to search for things other than host >> names? >> >> >> Both your use case and Andrew's seem to be about finding hosts in >> sets, which is quite di

Re: [Puppet-dev] Export and collect data, not just resources.

2012-07-01 Thread Stephen Gran
On Thu, 2012-06-28 at 08:40 -0700, Luke Kanies wrote: > Do you have cases where you need to search for things other than host > names? > > > Both your use case and Andrew's seem to be about finding hosts in > sets, which is quite different from arbitrary data. Hi, We have a wrapper around Use

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-29 Thread Luke Kanies
On Jun 29, 2012, at 10:31 AM, Daniel Pittman wrote: > On Thu, Jun 28, 2012 at 8:36 PM, Andrew Forgue > wrote: >> On Thursday, June 28, 2012 11:40:35 AM UTC-4, Luke Kanies wrote: >>> >>> Do you have cases where you need to search for things other than host >>> names? >> >> We also search for no

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-29 Thread Daniel Pittman
On Thu, Jun 28, 2012 at 8:36 PM, Andrew Forgue wrote: > On Thursday, June 28, 2012 11:40:35 AM UTC-4, Luke Kanies wrote: >> >> Do you have cases where you need to search for things other than host >> names? > > We also search for nodes with bind::slave class and then get the ipaddress > fact of th

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-28 Thread Andrew Forgue
On Thursday, June 28, 2012 11:40:35 AM UTC-4, Luke Kanies wrote: > > Do you have cases where you need to search for things other than host > names? > We also search for nodes with bind::slave class and then get the ipaddress fact of the node and use that for resolv.conf. I can't think of any ot

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-28 Thread Ryan Bowlby
> > Do you have cases where you need to search for things other than host > names? > > Both your use case and Andrew's seem to be about finding hosts in sets, > which is quite different from arbitrary data. > > -- > Luke Kanies | http://about.me/lak | http://puppetlabs.com/ | > +1-615-594-819

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-28 Thread R.I.Pienaar
- Original Message - > From: "R.I.Pienaar" > To: puppet-dev@googlegroups.com > Sent: Thursday, June 28, 2012 4:49:20 PM > Subject: Re: [Puppet-dev] Export and collect data, not just resources. > > > > - Original Message - > >

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-28 Thread R.I.Pienaar
- Original Message - > From: "Luke Kanies" > To: puppet-dev@googlegroups.com > Sent: Thursday, June 28, 2012 4:42:13 PM > Subject: Re: [Puppet-dev] Export and collect data, not just resources. > > > >> On Jun 22, 2012, at 12:48 PM, Andrew Forgue

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-28 Thread Luke Kanies
On Jun 22, 2012, at 12:48 PM, Andrew Forgue wrote: > On Wednesday, June 20, 2012 9:24:20 PM UTC-4, Ryan Bowlby wrote: > I imagine the common use case - and the one I had - is generation of a > configuration file where certain values must be dynamically derived based on > data that is beyond the

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-28 Thread Luke Kanies
On Jun 20, 2012, at 6:24 PM, Ryan Bowlby wrote: > I imagine the common use case - and the one I had - is generation of a > configuration file where certain values must be dynamically derived based on > data that is beyond the "node-scope". These values are inherently known to a > subset of node

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-22 Thread Andrew Forgue
On Wednesday, June 20, 2012 9:24:20 PM UTC-4, Ryan Bowlby wrote: > > I imagine the common use case - and the one I had - is generation of a > configuration file where certain values must be dynamically derived based > on data that is beyond the "node-scope". These values are inherently known > t

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-20 Thread Ryan Bowlby
I imagine the common use case - and the one I had - is generation of a configuration file where certain values must be dynamically derived based on data that is beyond the "node-scope". These values are inherently known to a subset of nodes who could provide them if given a means to do so. This

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-20 Thread Luke Kanies
On Jun 20, 2012, at 12:50 PM, Ryan Bowlby wrote: > Hi Jeff, > > That sounds great! If I could set and get in puppet manifests as well as from > a face that would be killer. Would this be in stdlib as a function or more > deeply embedded into the DSL? I'm assuming I can further filter a list of

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-20 Thread Zach Leslie
As was pointed out to me today, there is also https://github.com/dalen/puppet-puppetdbquery if you are running PuppetDB. I too have been looking for a way to just export data, since what you really care to export is the data thats used to create a given resource, not really to export the resource

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-20 Thread Ryan Bowlby
Hi Jeff, That sounds great! If I could set and get in puppet manifests as well as from a face that would be killer. Would this be in stdlib as a function or more deeply embedded into the DSL? I'm assuming I can further filter a list of hosts based on facter facts using Hiera (I honestly haven't

Re: [Puppet-dev] Export and collect data, not just resources.

2012-06-19 Thread Jeff McCune
Exported data as a concept and mental model is more important than exported resources IMHO. You've nailed it. Add me to the list of people who have passed hostnames through exported resources to a reverse proxy when all I really want is a variable containing an up to date list of worker hostn

[Puppet-dev] Export and collect data, not just resources.

2012-06-19 Thread Ryan Bowlby
I'm bumping up against the apparent limits of puppet. There appears to be a need for the ability to export data and not just resources. Then collecting this data and filtering based on specific values and or node facts. Nature will find a way Examples of exported resources being used to ove