Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 22 Apr 2016 10:50:12 +0000 (UTC)
From: "Gaurav Nagar (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12961594.1461318810000.7256.1461322212810@Atlassian.JIRA>
In-Reply-To: <JIRA.12961594.1461318810000@Atlassian.JIRA>
References: <JIRA.12961594.1461318810000@Atlassian.JIRA>
 <JIRA.12961594.1461318810417@arcas>
Subject: [jira] [Updated] (AMBARI-16037) View Configuration Simplification
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-16037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gaurav Nagar updated AMBARI-16037:
----------------------------------
    Description: 
Scope
The current implementation scope is limited to improving the ease of creation of View Instances, and reduce creation time issues. Also, this design leaves enough extension points to be extended further on the availability of subsequent centrally shared services in the case of non-Ambari managed custom Clusters.
 
Custom Configuration for non-Ambari managed Cluster
Cluster level configurations will be setup once to define underlying data services and end-points for subsequent usage at the time of View Instance creation. 
These cluster level configurations will be maintained as references in the respective View instances. 


> View Configuration Simplification
> ---------------------------------
>
>                 Key: AMBARI-16037
>                 URL: https://issues.apache.org/jira/browse/AMBARI-16037
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.2.2
>            Reporter: Gaurav Nagar
>            Assignee: Gaurav Nagar
>             Fix For: 2.4.0
>
>
> Scope
> The current implementation scope is limited to improving the ease of creation of View Instances, and reduce creation time issues. Also, this design leaves enough extension points to be extended further on the availability of subsequent centrally shared services in the case of non-Ambari managed custom Clusters.
>  
> Custom Configuration for non-Ambari managed Cluster
> Cluster level configurations will be setup once to define underlying data services and end-points for subsequent usage at the time of View Instance creation. 
> These cluster level configurations will be maintained as references in the respective View instances. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)