I've got a question post puppet camp. I'm not sure I understand the > benefit of external nodes and storeconfigs. > > If you put node data or other puppet configuration in external > sources, it would seem to me that: > > 1. Your complicating your configuration by essentially putting your > puppet config in two different locations, and >
You get rid of the node definitions that are not programmatic. So you only have one place. (not doing that is madness) 2. Most importantly, your losing the ability to version control your > configuration. It would seem to me that of utmost importance in any > prod environment is the ability to diff incremental config pushes, and > maybe roll them back where necessary. > You still version control everything. The classes are all versioned, in addition to the node assignment logic. The ability to diff config pushes is equivalent. > Am I missing a benefit that over rides disadvantages 2 and 3? > There is not a disadvantage IMHO. External nodes and storeconfigs are totally different things. The main advantage of external nodes is it provides more flexibility and scalability on how you assign nodes and classes. The benefit of storeconfigs is configuring resources with inter-host dependencies. My 0.02 Regards, Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
