You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@metron.apache.org by "Ali Nazemian (JIRA)" <ji...@apache.org> on 2017/07/12 05:58:00 UTC
[jira] [Created] (METRON-1032) Metron Ambari mpack is not blueprint
friendly
Ali Nazemian created METRON-1032:
------------------------------------
Summary: Metron Ambari mpack is not blueprint friendly
Key: METRON-1032
URL: https://issues.apache.org/jira/browse/METRON-1032
Project: Metron
Issue Type: Bug
Affects Versions: 0.4.0
Reporter: Ali Nazemian
Priority: Minor
In order to deploy a platform using Ambari blueprint, one can divide generic and non-generic parts to two different files. In this case, the generic parts should go to the main blueprint and the non-generic parts like passwords or the fields that come with hostnames should go to the host-group mapping file. This is the way that all HDP and HDF components have been implemented. However, it is not right for Metron and all the components that come with HCP. All the following fields should be included in the main blueprint. Otherwise, you cannot kick start the blueprint.
{
metron-env= [
storm_rest_addr,
es_hosts,
zeppelin_server_url,
metron_jdbc_url
]
},
{
kibana-env= [
kibana_es_url
]
}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)