This looks promising! I should be able to create a fact on some
servers, then collect those servers in a template. I'm going to
upgrade to test this out.
Thanks,
puppetlurker
On Aug 22, 10:45 am, Nan Liu <n...@puppetlabs.com> wrote:
> On Mon, Aug 22, 2011 at 6:11 AM, puppetlurker
>
>
>
>
>
>
>
>
>
> <under.my.cont...@gmail.com> wrote:
> > Greetings,
>
> > I'm having an issue with my implementation of exported resources. I
> > have a memcache server pool, and want to update the /etc/php.d/
> > memcache.ini with the ips of all the servers. Previously, I hard coded
> > the $memcacheservers array in the node manifest and the template
> > collected and populated the template.
>
> > Now that I'm moving to exported resouces, how do I get it to set an
> > array in a way I can access it from a different scope? I tried moving
> > the file { "/etc/php.d/memcache.ini": content => template(memcache/
> > memcache.ini.erb) to the resource function (I understand exported
> > resources shoulld not define other resources), but it only populates
> > the first server collected, and complains about a duplicate resource
> > if I have more than 1 exported server.
>
> > I've tried defining the resource without the content the first time,
> > then override the define with the content, but that only picks up the
> > 2nd server. I've tried accessing the variable that gets populated
> > after the Memcache::Servers <<| |>> but it doesn't get populated in
> > this scope. I've tried looking up the
> > scope.lookupvar('memcached::servers::memcacheservers') but the
> > exported resource is a define not a class and I couldn't get it to
> > work. I've tried just using a script to populate the file with the
> > proper contents, but there is no way to ensure it is filled with all
> > the servers, for example the script is executed out of order,
> > replaced 3 times if there are 3 servers, and may contain 1, 2, or 3
> > servers after a puppet run.
>
> > Any suggestions?
>
> I was looking at a similar issue where I need to export data, not
> resource, and be able to lookup the data. It just happens that Dan has
> published a prototype along the line of what you are looking
> for:https://github.com/puppetlabs/puppetlabs-nodesearch
>
> Thanks,
>
> Nan
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
