ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frode Halvorsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-2852) Ambari installation and configuration to manage an existing deployed hadoop Cluster
Date Mon, 02 Nov 2015 10:55:27 GMT

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

Frode Halvorsen commented on AMBARI-2852:
-----------------------------------------

One year later .... Still no plans for this ?
I suspect this affect the latest version as well ?

> Ambari installation and configuration to manage an existing deployed hadoop Cluster
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-2852
>                 URL: https://issues.apache.org/jira/browse/AMBARI-2852
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-web
>    Affects Versions: 1.4.0
>            Reporter: Anisha Agarwal
>
> In case you want to use Ambari for management of a live Hadoop cluster (including monitoring
and eco-system services), without deployment. Ambari assumes it has the control of Hadoop
installation. Suppose there is an existing HDP Hadoop cluster and one wants to install Ambari
to start managing/monitoring Hadoop. The proposal is to allow Ambari installation on the cluster
but bypass the Hadoop (and eco-system) deployment. We should provide the ability to import
the existing configuration without over writing existing setup. 
>  
> Proposed phases:
> 1. Provide on Ambari wiki documentation, leveraging Ambari API, all manual steps to configure
Ambari without redeploying Hadoop and its eco-system
> 2. Provide a template configuration file and one Utility (leaning toward Python script)
that automates the process of important an existing configuration
> 3. Provide User interface to allow step above via UI



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

Mime
View raw message