Hello, > But none of that is going to solve your particular problem, because > even if you instantiate your defines virtually, you still can provide > only one set of parameters for each title within the scope of each > node. Basically, this part of your design concept (define "bar") does > not fit the Puppet model.
That's what I suspected: My brain has not yet been able to comprehend the Puppet model completely. > I think the bar / hadoop_sub_directory define needs to be removed > altogether. You may be able to replace some or all of its intended > function with ordinary File resources in conjunction with suitably- > scoped File property defaults. You may simply need to be a little > more verbose and / or repetitious in your manifests. You may need or > want to refactor some of the classes that use these defines. This is the part I don't understand. The more verbose I've been the more errors I got because of duplicate definitions etc. Which only supports the point that I still don't "get" the Puppet model :) > HTH, I really do appreciate that you took the time to write such a detailed response. I will try once more to understand what I'm doing wrong and I'll re-read your mail a few times but I've spent so much time on this seemingly simple directory issue that I might just have to revert to a simple script or fabric to do this job. But as I said: Thank you for the help - I'll try to learn something from it now. Cheers, Lars -- 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.
