I''m working on controlling Glassfish from Puppet, and I''ve run
into a
problem that I''m not sure how to solve.
Our EJBs rely on various JMS connectors to be set up before they can
be deployed. This is easy - call asadmin for each JMS connector
required.
However, I''d like to be able to say ''Before running the EJB
deployments, ensure that all of the defined JMS connections exist'',
and I''ve love to be able to do that without going require => [
Glassfish_jms[''foo''], ... ] and filling in all of the JMS
entries
(especially since it''s yet another thing to keep updated as JMS queues
are added).
I suppose one way around it is to use a define in the per-node
manifest file, something like:
define myfoo() {
glassfish_jms { "fred" ...}
glassfish_jms { "bar" ...}
...
}
and just require => Myfoo[name].
Any failures in the wrapped _jms calls should propagate up, so it might work.
Any other concepts I should be thinking of? I suppose I could define
for each EJB deployment, which JMS queues it needs (which is, I guess,
the ''proper'' way to maintain the dependency chain).
--~--~---------~--~----~------------~-------~--~----~
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-unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---