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 D2266C4BC for ; Thu, 27 Jun 2013 12:54:23 +0000 (UTC) Received: (qmail 27192 invoked by uid 500); 27 Jun 2013 12:54:23 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 27090 invoked by uid 500); 27 Jun 2013 12:54:22 -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 27037 invoked by uid 99); 27 Jun 2013 12:54:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jun 2013 12:54:21 +0000 Date: Thu, 27 Jun 2013 12:54:20 +0000 (UTC) From: "Yusaku Sako (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (AMBARI-2506) Host Check UI: Issues should be grouped by Issue Type 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-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yusaku Sako reassigned AMBARI-2506: ----------------------------------- Assignee: Aleksandr Kovalenko > Host Check UI: Issues should be grouped by Issue Type > ----------------------------------------------------- > > Key: AMBARI-2506 > URL: https://issues.apache.org/jira/browse/AMBARI-2506 > Project: Ambari > Issue Type: Task > Components: client > Affects Versions: 1.2.5 > Reporter: Aleksandr Kovalenko > Assignee: Aleksandr Kovalenko > Fix For: 1.2.5 > > Attachments: AMBARI-2506_branch-1.2.5.patch, AMBARI-2506.patch, Screen Shot 2013-06-20 at 5.38.23 PM.png > > > Attached is an image about how the sections in Hosts check dialog should look like. There should be 5 major sections (more to come later): > Example: > * 3 file or folder issue > * 2 process issues > * 1 service issues > * 0 user issues > * 3 package issues > Each of the above should have the following labels in them respectively > * The following files or folders should not exist > * The following processes should not be running > * The following services should be up > * The following users should be removed > * The following packages should be uninstalled > Currently we model host->issue-type->issues. We should reverse that map in code to be issue-type->issues->hosts. Generally an issue might exist in multiple hosts (like /etc/hadoop/conf existing in 10 hosts). So in that case we need to have the 10 hosts in an array for the issue of /etc/hadoop/conf path. -- 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