Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.2.1
-
None
-
None
Description
When deploying Ambari Blueprints with extensive configuration (i.e. those generated from known-working clusters) Ambari should allow for the Blueprint to be generalized to the extent that no hostnames/FQDNs are necessary in a Blueprint. This requires host group substitution across the entire Blueprint. A few known locations lacking this support are Knox topology.xml, host-group specific YARN configuration overrides, and initial HA namenode standby.
This was also previously mentioned in the mailing list here: http://mail-archives.apache.org/mod_mbox/ambari-user/201508.mbox/%3C1B9E7CC6-E5EB-4853-92F2-0404FF358DD0@hortonworks.com%3E