Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 61E6610E69 for ; Mon, 13 Jan 2014 19:33:49 +0000 (UTC) Received: (qmail 40255 invoked by uid 500); 13 Jan 2014 18:19:33 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 35859 invoked by uid 500); 13 Jan 2014 18:08:12 -0000 Mailing-List: contact dev-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 dev@ambari.apache.org Received: (qmail 34313 invoked by uid 99); 13 Jan 2014 18:04:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jan 2014 18:04:50 +0000 Date: Mon, 13 Jan 2014 18:04:50 +0000 (UTC) From: "Antonenko Alexander (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-4276) Falcon initial implementation 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-4276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonenko Alexander updated AMBARI-4276: ---------------------------------------- Attachment: AMBARI-4276_additional.patch > Falcon initial implementation > ----------------------------- > > Key: AMBARI-4276 > URL: https://issues.apache.org/jira/browse/AMBARI-4276 > Project: Ambari > Issue Type: Task > Components: client > Affects Versions: 1.5.0 > Reporter: Mikhail Bayuk > Assignee: Mikhail Bayuk > Fix For: 1.5.0 > > Attachments: AMBARI-4276.patch, AMBARI-4276_additional.patch > > > Add ability to install and manage Falcon via Ambari Web. > This is for 2.x stack only. > h3. Install Wizard: > * Select Services page: Falcon will be shown as an installable service, with one master component FALCON_SERVER. TBD: Will we need to install Falcon Client? > * Assign Masters page: There will be a new drop down for "Falcon Server". > * Assign Slaves page: The Falcon Server host will be shown with a red asterisk. > * Customize Services page: There will be a new "Falcon" tab and a "Falcon Server" section. In "Misc" tab, add "Falcon user" (default "falcon"). TBD: name of the configuration resource, params to expose, etc. > * Review page: show the Falcon server host. > h3. Dashboard: > * Left nav: show "Falcon". > h3. Services: > * Left nav: show "Falcon" > * Summary panel > ** Show Falcon Server host and link > ** Show heap usage? > ** TBD: metrics of interest > * Quick Links > ** Show Falcon Server UI link > * Actions > * "Start", "Stop", "Run Service Check" > h3. Hosts: > * Add "Falcon Server" to the component filter > h3. Host Details: > * Show Falcon alerts for the host > * Show "Falcon Server" component with the capability to "Start" and "Stop" > h3. Mirroring > * Mirroring tab shows up if and only if Falcon is installed -- This message was sent by Atlassian JIRA (v6.1.5#6160)