[chef] Re: Dependency between nodes

[niristotle okram < >]

There have been discussions around about Chef being used as a deployment mechanism or not. From what i have analysed and reviewed based on the community feedbacks + some of my experience, Chef should not be used for deployments. Chef is a configuration management tool i.e you use Chef to set up your servers where the applications are deployed/hosted. Depending of Chef for deployment is just leaving more room for failures. Are you gonna do a chef-run for a production deploy? If you so, what happens if the chef run fails due to say, may be any silly reasons? And how are you going to put a gate on the deployment (although this can be archived using branches in your repo). 

The mentioned type of deployment can to achieve best with a combination of capistrano  + ssh (in my opinion). Check out capistrano 2 / 3 (many suggest to use 3, + me :) ) . But i still use cap2. And this have tied me down to an older Version of chef.  

A .war can be deployed to a say Tomcat cointainer using ssh from the repository via the jenkins servers (if you use jenkins). & the DB related deploys are done mostly via the capistrano. Not sure on the other 2 apps on what they are though.

hope this gives some to think and possibly a solution. 

 

On Sun, May 17, 2015 at 11:16 PM, Vikas Roonwal < " target="_blank"> > wrote:

Hi,
I wanted to know if chef is suitable for the following scenari, if yes then what would be the best way to achieve it.
We need to deploy a web-application which contains 3 components
1. A WAR file - portal
2. An application - A module which interacts with the portal for different tasks
3. DB
4. Active MQ - To facilitate the communication b/w Portal and App

If the above 4 components are on different machines/nodes, can the deployment be made atomic i.e. either all nodes get upgraded or none does.
I have an ANT script which can handle the deploy-all or none on a sinle node, is chef a possible solution if we need to suppprt the same across nodes?

Thanks,
~Vikas

--

Regards
nirish okram