Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Thu, 8 Aug 2013 23:47:48 +0000 (UTC)
From: "Anisha Agarwal (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12662742.1376005585588.29230.1376005668633@arcas>
In-Reply-To: <JIRA.12662742.1376005585588@arcas>
References: <JIRA.12662742.1376005585588@arcas>
Subject: [jira] [Created] (AMBARI-2852) Ambari installation and
 configuration to manage an existing deployed hadoop Cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Anisha Agarwal created AMBARI-2852:
--------------------------------------

             Summary: 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: client
    Affects Versions: 1.4.0
            Reporter: Anisha Agarwal
            Priority: Minor


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 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