Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 13 Sep 2017 04:53:00 +0000 (UTC)
From: "Yussuf Shaikh (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13092934.1502124087000.98422.1505278380197@Atlassian.JIRA>
In-Reply-To: <JIRA.13092934.1502124087000@Atlassian.JIRA>
References: <JIRA.13092934.1502124087000@Atlassian.JIRA> <JIRA.13092934.1502124087136@jira-lw-us.apache.org>
Subject: [jira] [Commented] (AMBARI-21674) Ambari to support Hybrid cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 13 Sep 2017 04:53:06 -0000


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

Yussuf Shaikh commented on AMBARI-21674:
----------------------------------------

Hi Nate,

Thanks for your inputs.

We have done some investigations and code changes for supporting Hybrid cluster. I would like to discuss on the points you mentioned above. I would share the design information in next couple of days.

* Agent Registration. We need changes to the bootstrap code (python) to change the ambari.repo url contents as per the OS arch type.
* JDK Install option. UI changes have been done for specifying JAVA_HOME path for Power specific hosts. We are planning to add a new key called JAVA_HOME_PPC in ambari.properties for storing this value. The User prompt will appear in step3 controller during Add/Install Hosts wizard if the host added is Power. Subsequent JDK validations and Service install on the agent hosts will be done depending on the OS architecture of each host added.
* Repository Versions. This area have been tested and works fine with minimal code changes with the help of new commits to include os_type specific to ppc. Eg: redhat-ppc7. Since the repo_info.xml already have the Power specific HDP and HDP-UTILS URLs we do not need much efforts. Ambari would pass on the proper HDP* URLs to the agent hosts to create the repo files. However, it may hold true for public repositories, we need more discussions for setting up offline repo for each OS type.

The changes you mentioned for 3.0.0 may need rework for repo settings in later phase.

> Ambari to support Hybrid cluster 
> ---------------------------------
>
>                 Key: AMBARI-21674
>                 URL: https://issues.apache.org/jira/browse/AMBARI-21674
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-agent, ambari-server
>            Reporter: Ayappan
>
> We have been exploring Hybrid hadoop cluster recently. By hybrid, i mean the nodes in the cluster have different platform architectures. Some nodes are intel x86_64 , some are IBM Power ppc64le., and so on. Right now Ambari doesn't have this hybrid support. It selects the repo based on the machine where it is installed and then ask the users to add the nodes. I think this order has to be changed as the first step to provide hybrid support in Ambari.
> We were actually able to bring up a hybrid cluster using some hacks (not so good) like manually configuring the yum repos according to the arch, installing the rpms before ambari does and also manipulating the JAVA_HOME variable. We also ran some examples like terasort without any issues.
> So the thing here is we kind of starting to work on making Ambari provide a smooth hybrid support which requires some design changes. We very much welcome Ambari community to provide some ideas, patch contributions, or whatever way you can help us on. 


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)