Dave Disser created AMBARI-12416:
------------------------------------
Summary: Aggregation of config groups across services
Key: AMBARI-12416
URL: https://issues.apache.org/jira/browse/AMBARI-12416
Project: Ambari
Issue Type: Wish
Components: ambari-server
Affects Versions: 2.1.0
Reporter: Dave Disser
Priority: Minor
Configuration groups in Ambari currently enable, among other things,
configuration of heterogeneous hosts in the same cluster (eg. different numbers
of disks or different amounts of memory). However, these configuration groups
exist only on a service-by-service basis, which makes the management of a
cluster which may have only a small number of distinct node configurations by
requiring each distinct node type to have several configuration groups
associated with it.
It would be much easier to have an abstraction for a node type which would
encompass multiple configuration groups, as well as stack-specific features
such as rack id or YARN node label. This abstraction could be expressed in a
form such as:
{
"href" : "http://mycluster1.blah.blah:8080/blah/blah";,
"HostTemplate": {
"cluster_name" : "HIPERF",
"description" : "Nodes with 24 drives and 512 GB RAM",
"ConfigGroups": [
"ConfigGroup": {
"group_name": "HIPERF",
"tag": "YARN"
},
"ConfigGroup": {
"group_name": "HIPERF",
"tag": "HDFS"
},
],
}
}
It's tempting to enumerate a host list in this structure as well, but such a
list would be in conflict with existing hosts list in the group definitions; I
don't know if it would make more sense to have config groups which delegate
their hosts list only to the configuration groups or to have the ConfigGroups
be a template which is applied in a one-time fashion to a particular host which
would then cause the underlying groups to be modified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
