I'm using puppet 0.25.2 in a RHEL5 environment and Glassfish is one of the
resources under management. Managing the Glassfish configuration is proving
troublesome.
I have a glassfish module with a glassfish class which has the following
file resource definition:
"/opt/glassfish/domains/pulse/config/domain.xml":
content => template("glassfish/domain-$environment.xml.erb"),
owner => pulse,
group => pulse,
mode => 644,
checksum => md5,
require => Exec["ConfigureGlassfish"];
Glassfish has an annoying behavior where it writes out a cached version of
the config file when it shuts down so I can't push the file while Glassfish
is running otherwise my changes get overwritten. So I need to ensure
Glassfish is shut down before puppet pulls the updated file from the
puppetmaster and then after the new version of the domain.xml config file is
distributed Glassfish needs to be restarted. I can manage Glassfish as a
service but I'm not sure how to trigger these actions pre and post update.
Does anyone have any insights into how I might accomplish this?
Is this a task better suited for something like ControlTier than Puppet? It
isn't specific to application building and deployment and seems to be a part
of managing my infrastructure and how it is configured.
thanks,
chuck
--
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.
