[
https://issues.apache.org/jira/browse/AMBARI-14981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139814#comment-15139814
]
jun aoki commented on AMBARI-14981:
-----------------------------------
[~aonishuk], I thought we would like to separate stack/service definitions from
ambari core, as described in AMBARI-14854 "Completely Decouple Ambari's cluster
management and monitoring functions from stack management and definition",
which will get Ambari to more generic platform and open up to much winder user
base/audience/developers. [~swagle][~u39kun]?
If it is right, I think the patch does the opposite way as
should_install_ams_grafana() (which is specific to grafana) is in
package_conditions.py(which is in ambari core ambari-common)
On the other hand, if we could set this way
{code}
<condition>common-servies/AMBARI_METRICS/0.1.0/package/scripts/condition.py#should_install_ams_grafana<condition>
{code}
many other service plugin providers can benefit it by dropping their scripts
under common-services/THEIR_SERVICE/1.0.0/ without touching apache-common code.
> Move service specific exclude packages logic from resource management to
> stack.
> -------------------------------------------------------------------------------
>
> Key: AMBARI-14981
> URL: https://issues.apache.org/jira/browse/AMBARI-14981
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.4.0
> Reporter: Aravindan Vijayan
> Assignee: Andrew Onischuk
> Priority: Critical
> Fix For: 2.4.0
>
>
> Based on recommendations from [~jaoki], [~sumitmohanty], [~swagle]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)