Hi, it might be possible to get this to work. You would basically create a profiles module per affiliate.
Putting all data into params.pp might be possible, but not ideal. Consider implementing Hiera instead. Your hierarchy can dynamically adapt to select appropriate data for each affiliate. HTH, Felix On 05/16/2015 01:17 AM, Rafael Tomelin wrote: > Hi people, > > My name is Rafael, i working with puppet, but in small environment. > > I will implement the puppet in large environment. The company has 45 > affiliates and each unit have 1 firewall, 1 proxy, 1 AD, 1 VMWARE, > Zabbix proxy, .... > > I would like the create module with all information the units > (affiliates) e after using dependencie the others modules. > > My idea create the example module: > puppet module generate client-affiliates > > /etc/puppet/modules/client-affiliates/manifests/params.pp > > The params.pp, have all informations: > ip dns > domain > network > ip proxy > ip firewall > ip ntp > .... > > or > /etc/puppet/modules/client-affiliates/manifests/network.pp > /etc/puppet/modules/client-affiliates/manifests/proxy.pp > > > the archives, the information by service. > > And with using the others modules these with variables? -- 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/5558CC0B.5000902%40Alumni.TU-Berlin.de. For more options, visit https://groups.google.com/d/optout.
