you should be able to use Fabric from within Chef or Puppet for deployment if you prefer. While the steps for doing automated deployment can be implemented via Chef/Puppet, there may not be any value in doing that if other options already exist.
I recently implemented a puppet solution for managing 4 env's ( dev, qa, stage & prod) x 2 hosts/per env and around 12 tomcat instances per host. A total of about 100 tomcat instances across all env's .. and perhaps about 15 apache web servers fronting the tomcat instances. This was for infrastructure for a dev organization on the JVM stack. Puppet was used to manage the boxes ( accounts, etc), provision the tomcat instances with settings unique to each instance, make sure the services are running etc. Worked like a charm for getting everything setup. For the deployment bits we plan to leverage puppet as much as we can and use shell scripts where appropriate. So as already mentioned, use puppet/chef for managing env's, services, etc. While they can be used to implemented automated continuous deployments also, you may want to keep alternatives in mind. as usual technology choices come down to personal preference and the path of least resistance ;) cheers, -- Nimret Sandhu http://www.nimret.org On Thu, Jun 14, 2012 at 10:28 AM, John DeRosa <[email protected]> wrote: > I don't understand using Fabric, Chef, and Puppet in the same sentence... > Fabric is automated deployment, the latter two are continuous configuration > management. > >
