I want to gather some ideas and/or best practice with the fine folks here in the group in terms of how you manage services in your environment.
For essential services like ssh, it's pretty much standard affair with the basic Package/Config/Service paradigm. Monitor the package info, make sure it away runs and refresh if new config files are pushed. Now, if you have something that's more application-oriented (ie. Apache, tomcat), how do you: 1. Maintain status-quo during 'normal' operation condition 2. Turn off services monitoring (i.e. Service ensure => running) during scheduled maintenance windows 3. Same as 2, for reasons that application is experiencing issue (outage) that causes by external means, and admin team need to debug on the node. In our environment right now, we defined different "application groups" via ENC, and we load different puppet modules based on that (with general service declaration ensure => running). One thing we keep running into is that if we want to work on a application setup on a specific node for whatever reason, we currently need to make sure that node does not load the said application module. We accomplish that currently by UNLOADING the module reference for the entire group. While this is serviceable, this clearly is not ideal. I have a couple ideas on improving our model, but I'm also interested to know how folks here would handle that. Thanks in advances. --KL This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
