[
https://issues.apache.org/jira/browse/AMBARI-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121577#comment-14121577
]
Robert Levas commented on AMBARI-7150:
--------------------------------------
I am currently working on something where we are proposing to set "visibility"
properties on a service to limit it exposure via the Ambari UI and Ambari
monitoring facility. The idea we are poking at is to add a {{properties}}
block to services and under that adding (at least) the following two Boolean
properties {{installable}} and {{managed}}. For example:
{code:xml}
<metainfo>
…
<services>
<service>
…
<properties>
<property>
<name>installable</name>
<value>false</name>
</property>
<property>
<name>managed</name>
<value>true</name>
</property>
</properties>
…
</service>
</services>
</metainfo>
{code}
If a service is not installable ({{installable=false}}), Ambari shouldn't allow
it to be visible in any UI to create or add to a cluster. Also it shouldn't be
allowed to be specified in a Blueprint. The idea is that it would only be
installed by some other facility - maybe as a dependency.
If a service is not managed ({{managed=false}}), Ambari should show it in
monitoring dashboards. We are still working through this one.
> Wondering if there is a way to disable a checkbox for a service in step 4
> choose services, but still utilize the service for any built in dependencies?
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-7150
> URL: https://issues.apache.org/jira/browse/AMBARI-7150
> Project: Ambari
> Issue Type: Improvement
> Reporter: Scott Creeley
>
> Wondering if there is a way to disable a checkbox for a service in step 4
> choose services, but still utilize the service for any built in dependencies?
> Example, if we are using 2.1.GlusterFS stack, we still need the scripts and
> some dependencies on HDFS, but don't want it selected in step4 by default AND
> would also like it disabled so it can't be selected?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
