atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ATLAS-601) Ambari should apply host group substitution to entire Blueprint
Date Wed, 30 Mar 2016 05:46:25 GMT

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

Hemanth Yamijala resolved ATLAS-601.
------------------------------------
    Resolution: Invalid

Not an Atlas defect. Please file against right component - Ambari

> Ambari should apply host group substitution to entire Blueprint
> ---------------------------------------------------------------
>
>                 Key: ATLAS-601
>                 URL: https://issues.apache.org/jira/browse/ATLAS-601
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: Kyle R Dunn
>         Attachments: Screen Shot 2016-03-29 at 22.09.11.png
>
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message