[chef] Re: Re: Dependency between nodes

[Stuart Cracraft < >]

Can’t this be done with Chef alone?

Just make a recipe to roll it back and make it dependent on a simple flag.

Avoid having to support all the disparate systems of antiquity.

Go Chef!

Go!

On May 18, 2015, at 9:23 PM, Vikas Roonwal < " class=""> > wrote:

Hello all,
Thanks for all the input.
I am currently using an SSH + SCP option to move and deploy builds and rollback in case there are startup or other issues. For configuration changes and copy ANT tasks are called using SSH.
Will look at Capistrano for sure.

~Vikas

On May 19, 2015 7:55 AM, "Joseph Hammerman" < " class=""> > wrote:

I’d recommend Capistrano for a multistage transactional deploy.

From: Vikas Roonwal < " target="_blank" class=""> >
Reply-To: " " target="_blank" class=""> " < " target="_blank" class=""> >
Date: Monday, May 18, 2015 at 2:16 AM
To: " " target="_blank" class=""> " < " target="_blank" class=""> >
Subject: [chef] Dependency between nodes

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

---------------------------------------------------------------------------

This message is intended only for the addressee. Please notify sender by e-mail if you are not the intended recipient. If you are not the intended recipient, you may not copy, disclose, or distribute this message or its contents to any other person and any such actions may be unlawful.
SecondMarket, Inc. (Member FINRA/SIPC, MSRB Registered) ("SecondMarket") does
not accept time sensitive, action-oriented messages or transaction orders, including orders to purchase or sell securities, via e-mail.
SecondMarket reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the SecondMarket e-mail system and archived in accordance with FINRA and SEC regulations.
This message is intended for those with an in-depth understanding of the high risk and illiquid nature of alternative assets and these assets may not be suitable for you. This message is not a solicitation for an order, and there is not enough information contained in this message in which to make an investment decision and any information contained herein should not be used as a basis for this purpose. SecondMarket does not produce in-house research, make recommendations to purchase or sell specific securities, provide investment advisory services, or conduct a general retail business.