On Thu, Sep 15, 2011 at 1:44 AM, Raffael Schmid <[email protected]> wrote:
> Hi everybody > > We would like to have the possibility to use definitions in an > external node classifier. > There is already a ticket about this with a possible solution: > https://projects.puppetlabs.com/issues/2408 . > > We are open for other solutions and your opinions about "naked > resources on site.pp level", so please give us some comments :) > > So to be clear, we're talking about assigning resources in general, not just definitions. The proposal is something like: classes: common: apt: resources: - "add local repo": type: "apt::repo" ensure: present content: "deb localrepo.magpie.lan/ubuntu lucid vendor" - "touch restart.txt": type: "exec" user: "root" command: "touch /var/www/rails/tmp/restart.txt" unless: "/var/www/rails/tmp/restart.txt" require: - file: "/var/www/" - file: "/var/www/rails" There are a few related questions to consider. Classes with parameters are much like resources at this level, and we don't want to end up having them be significantly second-class with an ENC compared to resources. Should a parameterized class be expressed as: classes: - common: param1: "value1" param2: "value2" or: resources: - common: type: class param1: "value1" param2: "value2" ? -- Nigel Kersten Product Manager, Puppet Labs *Join us for **PuppetConf * <http://www.bit.ly/puppetconfsig> Sept 22/23 Portland, Oregon, USA. * * -- 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.
