[jira] [Commented] (BIGTOP-1773) Add option for starting services and monitoring their lifecycle via Upstart to puppet deploy

["Nate DAmico (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BIGTOP-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378723#comment-14378723 ] 

Nate DAmico commented on BIGTOP-1773:
-------------------------------------

Seems like a good idea, also would be good starting point for future optional use of something like monit for more advanced service monitoring/alerts/etc

On upstart setup side of things, is mindset to use puppet or embed the upstart cfg file in the package so something installed via package alone would need no outside help/dependency on puppet if user chooses?  Or leave packages alone and have smarts pushed into puppet and users would choose during config/deploy time?

> Add option for starting services and monitoring their lifecycle via Upstart to puppet deploy
> --------------------------------------------------------------------------------------------
>
>                 Key: BIGTOP-1773
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1773
>             Project: Bigtop
>          Issue Type: Bug
>          Components: deployment
>    Affects Versions: 0.8.0
>            Reporter: Rob Leidle
>            Priority: Minor
>             Fix For: backlog
>
>
> Wanted to get a JIRA open for this to see what thoughts people had for where this should be implemented. I would like to add an option for configuring all the various services to be started and monitored by upstart and restarted in the case of the service exiting to the puppet manifests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)