whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (WHIRR-266) Separate tasks of both install and configuration scripts into more generic and detailed functions
Date Tue, 09 Oct 2012 10:02:09 GMT

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

Tom White updated WHIRR-266:

    Fix Version/s:     (was: 0.8.0)
> Separate tasks of both install and configuration scripts into more generic and detailed
> -------------------------------------------------------------------------------------------------
>                 Key: WHIRR-266
>                 URL: https://issues.apache.org/jira/browse/WHIRR-266
>             Project: Whirr
>          Issue Type: New Feature
>          Components: core
>            Reporter: Hyunsik Choi
>            Priority: Blocker
>             Fix For: 0.8.1
> Using whirr, I experimented some problems. Especially, if at least one of the steps for
installing and configuring a service meets some exception or error, whirr cannot construct
the running cluster. In another case, some of entire clusters do not startup by whirr due
to unknown reasons. In both cases, users have to recover them manually. It may be really burden
for users.
> However, the current implementation does not support any recovery ways. In addition,
service scripts (install and post-configure) bundles up too many tasks. For example, for hadoop
service the configuration script mounts devices, configures *-site.xml files, and executes
the service start script. It makes users hard to reuse that scripts.
> Thus, I propose that we separate both scripts (i.e., install and post-configure) into
more normalized and detailed functions, such as *service-clean, service-install, service-configuration,
service-start, and service-stop*. In addition, they should be executable individually by a
> I expect that it will give us many benefits: 1) it makes debugging easier 2) when an
exception or error occurs during starting a service, a user can recover easily the cluster
by using appropriate functions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message