Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2B0FC200CAD for ; Mon, 5 Jun 2017 18:35:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 29FB1160BBB; Mon, 5 Jun 2017 16:35:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 72218160BD4 for ; Mon, 5 Jun 2017 18:35:07 +0200 (CEST) Received: (qmail 4851 invoked by uid 500); 5 Jun 2017 16:35:06 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 4842 invoked by uid 99); 5 Jun 2017 16:35:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jun 2017 16:35:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 35923CF559 for ; Mon, 5 Jun 2017 16:35:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id H4kO2GiJrnOp for ; Mon, 5 Jun 2017 16:35:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 69E485F342 for ; Mon, 5 Jun 2017 16:35:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AF09FE02F7 for ; Mon, 5 Jun 2017 16:35:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 4913420DF5 for ; Mon, 5 Jun 2017 16:35:04 +0000 (UTC) Date: Mon, 5 Jun 2017 16:35:04 +0000 (UTC) From: "Hari Sekhon (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-21178) Config revision log view across all cluster services MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 05 Jun 2017 16:35:08 -0000 Hari Sekhon created AMBARI-21178: ------------------------------------ Summary: Config revision log view across all cluster services Key: AMBARI-21178 URL: https://issues.apache.org/jira/browse/AMBARI-21178 Project: Ambari Issue Type: New Feature Components: ambari-server Affects Versions: 2.5.0 Environment: HDP 2.5 Reporter: Hari Sekhon Feature request for a global view of all service configuration revision history. When there are changes to multiple services pending restarts for a change maintenance window it would be nice to be able to see the global log of revision control changes so we can see what will be applied until cluster restart. This is especially important when more than one person has scheduled changes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)