The fundamental problem is that such information is only going to be accurate to the last Puppet run, it's not realtime. Hence the need for some sort of external orchestration (which you'd get for free with DNS/DHCP data). Other options are of course available.
On 21 January 2014 07:25, Jose Luis Ledesma <joseluis.lede...@gmail.com> wrote: > I think this could be accomplished with exported resources, on every node > export a file with his IP, and collect the other ones. Then with a custom > script you could verify if the entry is on the hosts file. > > > About the offtopic dhcp vs hosts file, most clusters like to have the ips > defined on the hosts file, f.e. in Hacmp cluster it is mandatory. Also, imho, > it is not a good idea to have dhcp for cluster nodes. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/e83ff07a-0cbf-440d-a8bd-646b4d23f0ca%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAK5eLPSQCNzRX%2B8FhOFKDY%3DK4LfF-NGeHUxEkoZwXuoSzw%2BW%2Bw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
