On Mon, Nov 17, 2008 at 7:56 AM, Arnau Bria <[EMAIL PROTECTED]> wrote: > Is this correct? or is better to just include all *pp files in manifest > dir?
It is a really good idea to start using modules from the very beginning. > My other question, is posible to add some "dependencies" between > imports? You can't define dependencies between imports. Import is a function, not a type. > I need some order between groups/user/yaim and packages/pbs, for > exmaple. > > Do I have to define dependencies in classes? You must define dependencies at the "resource" level (though you can also define dependencies on defined types and classes; in this way you are using them as resources). > If yes, may I call a resource defined in a module from another > diferntet? Resources are essentially global; you may refer to them from any module. I think you might want to take a step back and really think about how you want to make the best use of puppet. Make sure your modules represent logical chunks of configuration, rather than just grouping together all the resources that are similar. Why have a 'packages' module? If I were trying to configure an LDAP server, I wouldn't want to have the user in a 'system_users' module, the package(s) in 'packages' and the startup scripts in 'init.d_stuff' modules; I'd want an 'ldap' module that contained all of these resources. Try thinking in terms of services; in the long run this will allow you to get the most out of Puppet. --Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
