On 01/04/2012 04:18 AM, Dan White wrote: >> Have you tried importing that very file instead of *.pp? > I could, but I plan to add more node files.
I'd still like you to try. Moreover, what does a 'grep -r ^node manifests/' yield? It appears as though your puppt apply was using an empty node definition. It's unclear to me where this definition might be. What's the output of 'facter fqdn'? > > Am I doing it wrong by having the import inside the scope of basenode ? I've never thought highly of node inheritance. I prefer classes and including instead. It doesn't strike me as wrong, though. However, it's not safe to assume that import statements inside classes/nodes are only honored when compiling catalogs for those nodes. In fact, I've seen 0.25.5 import everything it found in all node definitions (but that's knowledge from the Dark Ages). > Should I do the importing outside the basenode ? You should not import anything besides your nodes*.pp. > Like where I say (import "modules") ? Or do I even need to import ? import modules still looks horribly wrong to me. Under normal circumstances the autoloader should suffice. Does the module autoloader take care of that ? Please note that this is for puppet 2.6.12 Yes, it does. When you include foo::bar, puppet will try and find this class in the foo module. That's how you should be naming classes in your modules. Using import is (afaik) considered bad practice. Cheers, Felix -- 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.
