whirr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Buck (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WHIRR-746) Seperate Starting Nodes and bootstrapping from BootstrapCluster in java API
Date Wed, 11 Sep 2013 13:36:52 GMT

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

Werner Buck commented on WHIRR-746:

Yes I found it.

It's this thing here:

      final Template template = BootstrapTemplate.build(clusterSpec, computeService,
        statementBuilder, entry.getKey());

Is it possible to start nodes without Template with Jclouds? and then apply scripts in BootstrapClusterAction
to already existing Cluster?
> Seperate Starting Nodes and bootstrapping from BootstrapCluster in java API
> ---------------------------------------------------------------------------
>                 Key: WHIRR-746
>                 URL: https://issues.apache.org/jira/browse/WHIRR-746
>             Project: Whirr
>          Issue Type: Wish
>            Reporter: Werner Buck
>            Priority: Minor
> Instead of one function BootstrapCluster that both installs packages and starts nodes
I would like it separated to offer a more easy to use API and to increase reporting.
> I would like this separation because errors happening in the starting nodes-phase can
then be handled different than errors happening in bootstrap-phase.
> This can also reduce the amount of failures that can happen in the BootstrapCluster phase
further simplifying the code and making debugging easier during node starting fails.
> So the API calls would be:
> 1. Start nodes
> 2. Bootstrap Cluster
> 3. Configure Cluster
> 4. Start Cluster
> it would be sufficient just to add StartNodesCluster to ClusterDeployer and move the
starting-nodes logic from BootstrapClusterAction to StartNodesClusterAction.
> What do you think?

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