Hi, Thank you Manula for prompt reply.
On Wed, Nov 26, 2014 at 6:51 AM, Manula Waidyanatha <[email protected]> wrote: > The easiest way is to send a kill signal (SIGTERM) to the process since > you can get the Process ID from carbon home. > If not, you can run the Application server as a Linux service (init or > upstart). Then you can use the Mcollective service plugin to stop the > service in a cluster. > I think Mcollective approach is better as we have the server starting requirement as well. Regards, Malintha Adikari > > On Wed, Nov 26, 2014 at 12:06 PM, Suhan Dharmasuriya <[email protected]> > wrote: > >> Hi, >> >> Currently Malintha and I are in to R&D of deployment automation. >> >> We have a requirement to shutdown a application server temporarily in a >> cluster node. >> For that we are thinking of pushing a configuration from puppet master to >> agent node. >> >> Can we use puppet kick or mCollective commands to perform this task? >> Is there a better alternative other than using puppet? >> >> Thanks, >> Suhan >> -- >> Suhan Dharmasuriya >> Software Engineer - Test Automation >> >> *WSO2, Inc. * >> >> lean . enterprise . middleware >> Tel: +94 112 145345 >> Mob: +94 779 869138 >> Blog: http://suhan-opensource.blogspot.com/ >> > > > > -- > Regards, > Manula Waidyanatha > Systems Engineer, WSO2, Inc. > Phone: +94 774 195853 > Blog: blog.manula.org > -- *Malintha Adikari* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mobile: +94 71 2312958 Blog: http://malinthas.blogspot.com Page: http://about.me/malintha
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
