You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Andrei Savu (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/28 19:40:30 UTC

[jira] [Resolved] (WHIRR-421) Handle more role / service lifecycle events as part of the core functionality

     [ https://issues.apache.org/jira/browse/WHIRR-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Savu resolved WHIRR-421.
-------------------------------

    Resolution: Fixed

Committed. Thanks for reviewing! 
                
> Handle more role / service lifecycle events as part of the core functionality
> -----------------------------------------------------------------------------
>
>                 Key: WHIRR-421
>                 URL: https://issues.apache.org/jira/browse/WHIRR-421
>             Project: Whirr
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-421.patch, WHIRR-421.patch
>
>
> Right now each role can define event handlers for bootstrap and configure. I suggest that the Whirr core should be aware of more service lifecycle events like: start, stop & cleanup. This semantic improvement should allow us to add more features like: cluster reconfiguration (e.g. update Hadoop settings and restart all the nodes - rolling restart), add / remove nodes etc. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira