[
https://issues.apache.org/jira/browse/AMBARI-10306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391793#comment-14391793
]
Hudson commented on AMBARI-10306:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2172 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2172/])
AMBARI-10306 - Views: Ability for a view instance to be associated to a cluster
for configuration (tbeerbower) (tbeerbower:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=acdaae986b428b09310c06f08ec42fc98b93d3b4)
* ambari-server/src/main/java/org/apache/ambari/server/view/ClusterImpl.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewVersionResourceProvider.java
* ambari-server/src/main/resources/Ambari-DDL-SQLServer-CREATE.sql
* ambari-views/src/main/java/org/apache/ambari/view/ViewContext.java
*
ambari-server/src/test/java/org/apache/ambari/server/view/ViewRegistryTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ViewEntity.java
*
ambari-server/src/test/java/org/apache/ambari/server/view/configuration/ParameterConfigTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/view/configuration/ViewConfigTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ViewInstanceEntity.java
* ambari-server/src/main/java/org/apache/ambari/server/view/ViewContextImpl.java
*
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/ViewInstanceResourceProviderTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog210Test.java
* ambari-views/src/main/java/org/apache/ambari/view/cluster/Cluster.java
* ambari-server/src/main/resources/Ambari-DDL-Postgres-EMBEDDED-CREATE.sql
* ambari-server/src/main/java/org/apache/ambari/server/view/ViewRegistry.java
* ambari-server/src/test/java/org/apache/ambari/server/view/ClusterImplTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/controller/internal/ViewInstanceResourceProvider.java
*
ambari-server/src/main/java/org/apache/ambari/server/orm/entities/ViewParameterEntity.java
* ambari-server/src/main/resources/Ambari-DDL-Oracle-CREATE.sql
*
ambari-server/src/main/java/org/apache/ambari/server/view/configuration/ParameterConfig.java
* ambari-views/src/main/java/org/apache/ambari/view/ViewInstanceDefinition.java
* ambari-server/src/main/resources/Ambari-DDL-MySQL-CREATE.sql
* ambari-server/src/main/resources/Ambari-DDL-Postgres-CREATE.sql
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog210.java
* ambari-views/src/main/resources/view.xsd
*
ambari-server/src/test/java/org/apache/ambari/server/orm/entities/ViewEntityTest.java
*
ambari-server/src/test/java/org/apache/ambari/server/view/ViewContextImplTest.java
> 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)
