On Mar 19, 3:05 am, Nikhil Mulley <mnik...@gmail.com> wrote:
> Hi,
>
> In my puppet configuration, to deploy certain files to group of nodes,
> everytime either a new class of node is being used or the node class has to
> typically extended to many other machines and is likely more typing. The
> more typing can generally result in anomalies/errors in hosts.
>
> For example:
>
> node x1.y.z x2.y.z x3.y.z x4.y.z{
> ...
> ...
>
> }
>
> What I am trying to formulate this into is use the netgroup information
> available from /etc/netgroup and get this grouped as [...]That's backwards. The contents of /etc/netgroup should be managed by Puppet if you rely on it for anything. If it already is managed then Puppet already has the information you want, though you probably need to refactor. If /etc/netgroup is *not* already managed by Puppet then it's a poor idea to set it up as a supplemental source of truth. An ENC would provide what you need, though whether it would be any better in practice depends on how it's implemented. You might find that a simple script would suit you, or else that hiera's ENC features do everything you need. Your description of the problem is rather abstract, however. If you want more specific advice then it would help to provide a little more detail about how your node definitions are set up, and an example or two of the kind of error-prone operation you want to avoid. John -- 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.
