[
https://issues.apache.org/jira/browse/HDFS-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725940#comment-13725940
]
Brandon Li commented on HDFS-4947:
----------------------------------
{quote}Another question I have is whether there may be multiple hostnames
associated with the client's IP address. I'm pretty sure this is allowable, so
we may have to deal with that case here.{quote}
Yes. it could happen.
One way I can think to deal with this situation is to match each one with the
access rules, and then use the minimum access permission. For example, one IP
has two hostnames. According to exports table, one name has rw access and one
has ro access. We may want to give ro access to this IP.
What do you think?
> Add NFS server export table to control export by hostname or IP range
> ---------------------------------------------------------------------
>
> Key: HDFS-4947
> URL: https://issues.apache.org/jira/browse/HDFS-4947
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: nfs
> Affects Versions: 3.0.0
> Reporter: Brandon Li
> Assignee: Jing Zhao
> Attachments: HDFS-4947.000.patch, HDFS-4947.001.patch,
> HDFS-4947.002.patch, HDFS-4947.003.patch
>
>
> This jira adds NFS server export table (hostname or IP range) to control
> export. Specifically, it
> 1. adds two new classes AccessPrivilege and ClientHostsMatcher for loading
> and checking the mapping between client hosts and their access privileges.
> These two classes are directly copied from Brock Noland's NFS4 implementation.
> 2. adds the access check (based on the export) to NFS3 procedures.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
