General discussion about Chef

[chef] LWRPs as containers


Chronological Thread 
  • From: "Mark J. Reed" < >
  • To:
  • Subject: [chef] LWRPs as containers
  • Date: Tue, 19 Apr 2011 11:13:14 -0400
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=OzDDTKp4Q0E8tOVd2BsUJS6ejlX29cBsWq5dBJ8qyf6Y0sqSCye+QVZ7Yt/EK1ZKlr ewd+dVsfqm9UPF/gZhaesf3QyRZfcDFqOMO3mXdv4uU/08go3XVWqI7rSGEhRGeVcqsK 8M2LXjfIklekdTbIqvDAgG9cavv8hwItgXLvE=
I have an LWRP that fundamentally just creates a bunch of other
resources dynamically.  I had some issues getting notifies to work, so
I have some questions.

1. Is an LWRP the best way to create a resource that is really a
collection of other resources?

2. If not, what is?  A define?  A straight-up non-lightweight resource
definition?  It's definitely not a recipe, as I need to be able to
call/include it multiple times with different parameters.

3. If it's at least a reasonable way to do it, where in the provider
does that logic belong?  Creating more resources once you're already
running the action seems a bit late; I wind up having to call
run_action on them as I create them in order to get the behavior I
want.

4. As far as notifies go, is there a way from the provider to access
the set of notifications requested?

Any thoughts and recommendations appreciated. Thanks!

-- 
Mark J. Reed 
< >

Archive powered by MHonArc 2.6.16.

§