Thanks everyone for the pointers. I've gone with the Virtual
Resources approach because (a) the description of them more or less
exactly matches my use case, and (b) because from a class perspective
I'm trying to follow the "is a web server" type of paradigm, and "is a
jre-jce" doesn't really work in that context - it's too granular, and
not a description of the role of the node.
Paul
On Dec 17, 4:32 pm, Stefan Schulte <stefan.schu...@taunusstein.net>
wrote:
> On Fri, Dec 17, 2010 at 07:46:29AM -0800, luke.bigum wrote:
> > Nigel's Virtual Resources is one way, this is another using only
> > classes.
>
> > You can put the base software in classes of their own and include
> > these in your 'server classes'. Classes can be included multiple times
> > on a node without causing errors.
>
> Hm personally, I don't really like that because you can include the class in
> different scopes:
>
> One example:
>
> class common {
> file { '/tmp/test':
> content => $tempvar,
> ensure => file,
> }
> }
> class foo {
> $tempvar = "foo"
> include common
> }
> class bar {
> $tempvar = "bar"
> include common
> }
> node default {
> include foo
> include bar
> }
>
> This does not throw a compile error but it really depends on ordering if
> "foo" or "bar" will be in your file. If you define a virtual resource in
> one place then everything depends on the scope where you defined that
> resource and not where you realize it.
>
> -Stefan
>
> application_pgp-signature_part
> < 1KViewDownload
--
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.
