metron-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (METRON-1615) Fill in some endpoint details from Ambari info
Date Tue, 02 Oct 2018 02:08:00 GMT


ASF GitHub Bot commented on METRON-1615:

Github user simonellistonball commented on the issue:
    Turns out this is (in theory) done by the service advisor at   
which doesn't look to have been significantly tested (doesn't for example work on a real cluster,
and only works with overrides to blueprint templates to force application of settings (since
the required field insists you enter a custom value). That therefore doesn't fire in default
Ambari blueprint installs. 
    You won't see that on full dev, or a platform that explicitly sets storm_rest_addr in
blueprints to a correct value, but on something like a cloudbreak install (where you can't
change the ambari configStrategy) it is impossible to get the service advisor to run. Since
the fields in question are marked required, the service advisor cannot override them, and
the blueprint cannot be submitted without setting them, so you're in a catch 22 if you do
not know the host names upfront prior to install (the cloud install case).
    In any case, this is probably not a good Apache fix, since from the Apache point of view
this already 'works as designed'. Maybe I should file a separate ticket on the removing the
required attribute from the settings which are not actually required, or it should be handled
by rewriting the automation engine elsewhere, which would allow the service advisor to set

> Fill in some endpoint details from Ambari info
> ----------------------------------------------
>                 Key: METRON-1615
>                 URL:
>             Project: Metron
>          Issue Type: Improvement
>    Affects Versions: 0.5.0
>            Reporter: Simon Elliston Ball
>            Priority: Trivial
> When installing a metron cluster, users are required to fill in values that Ambari should
already know: 
>  * location of storm ui
>  * location of elastic search
>  * location of zeppelin notebook server
> While it is useful to be able to override the ES location if you're using a non-metron
managed ES, the others are absolutely a function of the Metron cluster, whose locations are
known to Ambari, so users should not be expected to fill them in.
> If the ES hosts settings is left blank, it should be calculated from info in the ES mpack.
> The kibana service in the elastic mpack should also automatically set the url for ES

This message was sent by Atlassian JIRA

View raw message