You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2013/10/17 22:50:50 UTC
[jira] [Commented] (AMBARI-3531) Provide configuration host
overrides capability in Ambari
[ https://issues.apache.org/jira/browse/AMBARI-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798394#comment-13798394 ]
Srimanth Gunturi commented on AMBARI-3531:
------------------------------------------
Feedback given about UI
* Default group name should be {{Default}}
* Restart indicator on configs page should have action to restart stale host-components
* Host page should have restart indicator beside components
* On hosts page find hosts which have overrides, or override a property
* On hosts page, restart in host components in bulk
> Provide configuration host overrides capability in Ambari
> ---------------------------------------------------------
>
> Key: AMBARI-3531
> URL: https://issues.apache.org/jira/browse/AMBARI-3531
> Project: Ambari
> Issue Type: New Feature
> Components: controller
> Affects Versions: 1.4.1
> Reporter: Srimanth Gunturi
> Assignee: Siddharth Wagle
> Fix For: 1.4.2
>
> Attachments: AmbariConfigGroupManagement.pdf, AmbariConfigGroupsUI.pptx
>
>
> Ambari currently provides cluster level service configurations.
> This is a problem when the cluster has a mix of different hardwares requiring different configurations for a group of hosts of a service. For example, some DataNodes having bigger disks might need extra mount points in {{dfs_datanode_data_dir}}.
> Ambari needs to provide configuration override capability for a group of hosts per service.
> The primary use cases from UI perspective are the ability to
> # Override 3 properties for 500 hosts
> # Go to host and see effective configurations
> # Save configuration without restarting
> # Indicate which services/components need restarting
--
This message was sent by Atlassian JIRA
(v6.1#6144)