[
https://issues.apache.org/jira/browse/AMBARI-7150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141221#comment-14141221
]
Scott Creeley commented on AMBARI-7150:
---------------------------------------
[~rlevas] [~jaimin] [~mahadev] [~u39kun] [~erinaboyd] [~subin11]
I think it is reasonable, even if it's not the long term strategy and
direction, it would be useful short-term at least. With the architectural
changes have taken place recently, maybe there is a better way to accomplish
this per stack, but right now, many services depend on HDFS for example and if
we simply do not include it, the installer and deployment of glusterfs and
associated stack services will fail. So I like the idea of having the
dependencies in the stack as they exist today but being able to hide them on
the interface so users are not confused.
I will have to defer to the more experienced committers on the team to weigh in
on this, but from my perspective it seems like a +1. If everyone agrees, then
you can use this JIRA to document status. Let me know what you think.
thanks,
Scott
> 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)
