whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-676) Convert CDH services to use Bigtop artifacts
Date Thu, 15 Nov 2012 10:48:12 GMT

    [ https://issues.apache.org/jira/browse/WHIRR-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497920#comment-13497920

Steve Loughran commented on WHIRR-676:

Here are some things I'd like to see from a new service, one which I could subclass in Java
to add some specific features

# ability for service to specify preferred OS family for installation (deb, yum), maybe some
other params.
# a specific preflight script that does pre-deployment checks of system (network state &c)
# explicit register_repositories script
# explicit checks for NN in the HDFS layer, JT in the MR layer, rather than just stack traces
on the lookups
# make it possible to select a different set of default properties from {{"whirr-hadoop-default.properties";}}

What I'd really, really like is to be able to chain together two or more in-JAR .properties
files, so that the default hadoop one was read in, then the installation specific one. This
would let the vendor one provide a different set of default action (repos, scripts, default
config options) that don't need to be set up correctly by everyone in their own local .properties
file in order to use that installation.

The current two-level installer forces everyone to override the scripts in their target properties
file, and keep in sync with any other cluster options.
> Convert CDH services to use Bigtop artifacts
> --------------------------------------------
>                 Key: WHIRR-676
>                 URL: https://issues.apache.org/jira/browse/WHIRR-676
>             Project: Whirr
>          Issue Type: Sub-task
>            Reporter: Tom White
>             Fix For: 0.9.0
> The CDH services predate Bigtop, but now that it's available we should change them to
use Bigtop artifacts, and then vendor distributions can extend these as needed (and should
be hosted outside Apache).

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