Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 1 Apr 2015 01:51:53 +0000 (UTC)
From: "Tom Beerbower (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12787224.1427853078000.88260.1427853113560@Atlassian.JIRA>
In-Reply-To: <JIRA.12787224.1427853078000@Atlassian.JIRA>
References: <JIRA.12787224.1427853078000@Atlassian.JIRA>
 <JIRA.12787224.1427853078045@arcas>
Subject: [jira] [Created] (AMBARI-10306) Views: Ability for a view instance
 to be associated to a cluster for configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Tom Beerbower created AMBARI-10306:
--------------------------------------

             Summary: Views: Ability for a view instance to be associated t=
o a cluster for configuration
                 Key: AMBARI-10306
                 URL: https://issues.apache.org/jira/browse/AMBARI-10306
             Project: Ambari
          Issue Type: Task
            Reporter: Tom Beerbower
            Assignee: Tom Beerbower
             Fix For: 2.1.0


Ability for a view instance to be associated to a cluster for configuration=
 (so the view can have access to cluster config information via view contex=
t). This enables the view instance to be configured w/o the admin having to=
 wire-up properties. Whether the view is auto instantiated or instantiated =
manually, the Ambari Admin should have an option to relate an instance of a=
 cluster to the view instance. This make the cluster config information ava=
ilable to the view so the view can "auto-configure". Therefore, in addition=
 to today's manual configure option, need to add options for picking a clus=
ter in same ambari, or picking remote ambari server to "auto-configure".  B=
ased on the configuration option the user chooses, the way the user gets co=
nfiguration changes. If the user chooses today mode of config, they can use=
 the same ViewContext.getProperties() as they do today. If they choose a lo=
cal cluster, they need a way to get access to all cluster configurations. F=
or remote cluster, maybe we just provide convenient method way to get rest =
endpoint to the cluster resource to limit scope? In any of the three cases,=
 the view developer needs to know how he is to get his configurations (cust=
om, local or remote), and have a way to get access via ViewContext. Also, n=
eed ability to flag properties as cluster "configuration" or "setting" so t=
he UI can organize properties that can be derived from cluster configuratio=
n properties vs. settings props related to the view itself.=20


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