You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2013/11/30 07:12:35 UTC

[jira] [Updated] (AMBARI-3937) Revise Config Group Management copy to be more descriptive

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

Yusaku Sako updated AMBARI-3937:
--------------------------------

    Description: 
The Config Group Management popup is currently showing:
"Manage configuration groups of this service. Groups can be created, renamed and deleted and from here. Host memberships can also be changed. A host can belong to only one configuration group."

A bit of rewording to:
* remove redundancy with the header
* explicitly state that the configuration group being referred to is specific to the service in question
* explicitly state that hosts in a service config group have the same set of configs for the service in question

"You can apply different sets of <service-name> configurations to groups of hosts by managing <service-name> Configuration Groups and their host membership.  Hosts belonging to a <service-name> Configuration Group have the same set of configurations for <service-name>.  Each host belongs to one <service-name> Configuration Group."

> Revise Config Group Management copy to be more descriptive
> ----------------------------------------------------------
>
>                 Key: AMBARI-3937
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3937
>             Project: Ambari
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.4.3
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>             Fix For: 1.4.3
>
>
> The Config Group Management popup is currently showing:
> "Manage configuration groups of this service. Groups can be created, renamed and deleted and from here. Host memberships can also be changed. A host can belong to only one configuration group."
> A bit of rewording to:
> * remove redundancy with the header
> * explicitly state that the configuration group being referred to is specific to the service in question
> * explicitly state that hosts in a service config group have the same set of configs for the service in question
> "You can apply different sets of <service-name> configurations to groups of hosts by managing <service-name> Configuration Groups and their host membership.  Hosts belonging to a <service-name> Configuration Group have the same set of configurations for <service-name>.  Each host belongs to one <service-name> Configuration Group."



--
This message was sent by Atlassian JIRA
(v6.1#6144)