I just recently learned about Puppet and was wondering if someone could tell me if this would be a good fit for our environment.
We have 3 web servers (and will soon have 4). Here's the steps I currently use to deploy: # log on to production web server 1 > service httpd stop > service tomcat5 stop # log on to QA server > scp ROOT.war [email protected]:/usr/share/tomcat5/webapps/ Sometimes it is more complex, though, and I may need to copy any of the following: /etc/httpd/conf.d/mod_jk.conf /etc/tomcat5/context.xml But I can't just copy over context.xml from QA, since the connection strings are different in QA and production. # restart everything (after ROOT.war has transferred) > service tomcat5 start > service httpd start Usually, I deploy to server1, test, and then deploy to server2 and server3. I like to wait until server 2 is completed ready before I start deploying to server 3 -- can Puppet do this (check for the HTTP status of /)? So, can I have Puppet deploy server1 and then have it do the deploy and wait to server2, server3, and soon to be server4? Thanks, Bradford -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
