> What you gain is truly node-scoped variables (AWESOME). Contrary to > Ken's assertion about global variables, instead you have your external > node script place variables into the output YAML; these variables are > then available to all the classes and resources that apply to that > node.
I apologise for the semantic confusion :-). I meant 'variables of global scope' in the sense you have stated here - ie. scoped to the node and its imported classes/resources. My use of Puppet DSL was to show the functional equivalent of what effect you get in external nodes - I was hoping with an example it would explain what I meant :-). Although I believe using external nodes places class/variables at 'top scope' which is one level above a node ... kind of like stuffing your imported external node config into site.pp for each node run dynamically (hehehe - I hope that makes sense). > External nodes is 100% awesome, I think you just haven't taken the > time to really understand it. Agreed. Douglas - further to the spirit of what Paul is getting at - you shouldn't abandon the idea of using external nodes until you give it a go. I believe it is possible to mix your existing config with external nodes so you can try it out and see if you like it. We are moving to external nodes due to the sheer number of nodes we have to support. Using a text file with puppet DSL is no longer viable - large changes are slow to perform - and even with some performance tuning the files take half a minute to parse. ken. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
