[
https://issues.apache.org/jira/browse/AMBARI-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389903#comment-14389903
]
Hadoop QA commented on AMBARI-10306:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12708591/AMBARI-10306.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/2205//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/2205//console
This message is automatically generated.
> Views: Ability for a view instance to be associated to 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
>
> Attachments: AMBARI-10306.patch
>
>
> 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 context).
> 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
> available 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 cluster in same ambari, or picking remote ambari server to
> "auto-configure". Based on the configuration option the user chooses, the
> way the user gets configuration changes. If the user chooses today mode of
> config, they can use the same ViewContext.getProperties() as they do today.
> If they choose a local cluster, they need a way to get access to all cluster
> configurations. For 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 (custom, local or remote), and have a way to get access via
> ViewContext. Also, need ability to flag properties as cluster "configuration"
> or "setting" so the UI can organize properties that can be derived from
> cluster configuration properties vs. settings props related to the view
> itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
