So, I was following the thread "how to conditionally add users to a virtualized group?" and had a bit of a realization that I'm not quite sure why Hiera is a better backend than LDAP.
Hiera: - Stores hierarchical data locally on your system - Uses YAML - Integrates with puppet LDAP - Stores hierarchical data across potentially multiple systems (think puppet master scaling and data sync) - Uses LDIFs - Needs some glue code written However, both are hierarchical databases based on 'read often/write rarely' principals. Besides the glue code to make LDAP do Hiera-like things, what are the issues? It also seems that using a well known and supported system, such as LDAP, would foster greater enterprise support (except in those places where you have to spawn your own due to insane directory admins). And, yes, I know that a hiera back-end could be written to support LDAP but that would just be an unnecessary data transference if I'm reading it right. If you wanted local "fast" copies of the data on all of your puppet masters (and you do) then a simple LDAP slave would be spawned on each master. Thanks, Trevor -- Trevor Vaughan Vice President, Onyx Point, Inc (410) 541-6699 tvaug...@onyxpoint.com -- This account not approved for unencrypted proprietary information -- -- 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.
