Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4C457FD44 for ; Fri, 31 May 2013 00:43:20 +0000 (UTC) Received: (qmail 43053 invoked by uid 500); 31 May 2013 00:43:20 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 42954 invoked by uid 500); 31 May 2013 00:43:20 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 42887 invoked by uid 99); 31 May 2013 00:43:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 May 2013 00:43:20 +0000 Date: Fri, 31 May 2013 00:43:20 +0000 (UTC) From: "Yusaku Sako (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-2118) ambari-web modifications to allow for Hadoop Compatible Filesystems (HCFS) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671010#comment-13671010 ] Yusaku Sako commented on AMBARI-2118: ------------------------------------- Hello [~croberts], here's my feedback so far. Sorry for the delay: * /app/assets/data/wizard/deploy/5_hosts/poll_6.json: Please don't include the changes to this file, as this is used for testing scenarios where the server returns a response for the start API. It might be a good idea to introduce another set of mock data for which the step for start API is empty. * /app/controllers/wizard/step8_controller.js: {code} + case 'HCFS': + return {config: {'global': 'version1', 'core-site': 'version1'}}; {code} The above does not apply because getConfigForService function has been removed (this function is no longer used). * /app/controllers/wizard/step9_controller.js: This needs further review. This step needs to handle various edge cases (retry upon installation failure, page refreshes, etc). * /app/data/config_mapping.js: fs.default.name definition is duplicated. We should remove the redundant entry and manage the value in code (e.g., hdfs://namenode_host:8020 for HDFS and whatever is appropriate for glusterfs). * /app/data/config_properties.js: the newly added glusterfs properties have the "filename" attribute. These should be removed. * /app/data/service_configs.js: For the newly added HCFS object, "configs" should be an empty array, and "sites" should be added (see others) * /app/config.js: Skip this file from the patch * /app/messages/js: installer.step4.multileDFS.popup.header and installer.step4.multileDFS.popup.body are misspelled. > ambari-web modifications to allow for Hadoop Compatible Filesystems (HCFS) > -------------------------------------------------------------------------- > > Key: AMBARI-2118 > URL: https://issues.apache.org/jira/browse/AMBARI-2118 > Project: Ambari > Issue Type: Improvement > Components: controller > Affects Versions: 1.2.2 > Environment: all supported platforms > Reporter: Chad Roberts > Assignee: Chad Roberts > Labels: patch > Attachments: trunk_with_hcfs_new_files.patch, trunk_with_hcfs.patch > > Original Estimate: 72h > Remaining Estimate: 72h > > Make modifications to ambari-web that will allow for the selection of a Hadoop Compatible Filesystem. These changes include allowing HDFS to be unselected (either HDFS or HCFS must be selected). If HCFS is chosen, push appropriate configuration (site-conf.xml) files during the install so that systems will work with HCFS as the underlying filesystem rather than HDFS. -- 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