[
https://issues.apache.org/jira/browse/AMBARI-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484228#comment-14484228
]
Brandon Li commented on AMBARI-10389:
-------------------------------------
[~jaimin] recommended to move NFS component along with the following properties
to HDP 2.3 which is the product supporting NFS officially through Ambari:
nfs.dump.dir
nfs.exports.allowed.hosts
nfsgateway_heapsize
> NFS Gateway breaks Windows installation
> ---------------------------------------
>
> Key: AMBARI-10389
> URL: https://issues.apache.org/jira/browse/AMBARI-10389
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Brandon Li
> Assignee: Brandon Li
> Fix For: 2.1.0
>
>
> [~jluniya] pointed out:
> {quote}
> NFS Gateway is not supported for Windows. Hence I removed NFS Gateway
> component from the HDPWIN stack definition.
> However the current ambari-web changes are very tightly integrated and do not
> check for the case where NFS Gateway component is present in the selected
> stack. Hence
> 1. During Customize Services, I see a section for "NFS Gateway" config
> properties to be displayed for Windows
> 2. During Review step in the installation wizard, the wizard is looking for
> NFS Gateway component and throws a null exception.
> Can you add additional checks in the ambari-web to handle the scenario of NFS
> Gateway component not being present more gracefully. Apart from Windows, this
> potentially might be a valid scenario for other vendors who dont have to
> support an NFS Gateway.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
