<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 22 Nov 2019, 5:03 Xie Changlong <<a href="mailto:zgrep@139.com">zgrep@139.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<p><br>
</p>
<div>在 2019/11/22 5:14, Kaleb Keithley 写道:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">I personally wouldn't call three years ago — when
we started to deprecate it, in glusterfs-3.9 — a recent
change.
<div><br>
</div>
<div>As a community the decision was made to move to
NFS-Ganesha as the preferred NFS solution, but it was agreed
to keep the old code in the tree for those who wanted it.
There have been plans to drop it from the community packages
for most of those three years, but we didn't follow through
across the board until fairly recently. Perhaps the most
telling piece of data is that it's been gone from the
packages in the CentOS Storage SIG in glusterfs-4.0, -4.1,
-5, -6, and -7 with no complaints ever, that I can recall.</div>
<div><br>
</div>
<div>Ganesha is a preferable solution because it supports
NFSv4, NFSv4.1, NFSv4.2, and pNFS, in addition to legacy
NFSv3. More importantly, it is actively developed,
maintained, and supported, both in the community and
commercially. There are several vendors selling it, or
support for it; and there are community packages for it for
all the same distributions that Gluster packages are
available for.</div>
<div><br>
</div>
<div>Out in the world, the default these days is NFSv4.
Specifically v4.2 or v4.1 depending on how recent your linux
kernel is. In the linux kernel, client mounts start
negotiating for v4.2 and work down to v4.1, v4.0, and only
as a last resort v3. NFSv3 client support in the linux
kernel largely exists at this point only because of the
large number of legacy servers still running that can't do
anything higher than v3. The linux NFS developers would drop
the v3 support in a heartbeat if they could.</div>
<div><br>
</div>
<div>IMO, providing it, and calling it maintained, only
encourages people to keep using a dead end solution. Anyone
in favor of bringing back NFSv2, SSHv1, or X10R4? No? I
didn't think so.</div>
<div><br>
</div>
<div>The recent issue[1] where someone built gnfs in
glusterfs-7.0 on CentOS7 strongly suggests to me that gnfs
is not actually working well. Three years of no maintenance
seems to have taken its toll.</div>
<div><br>
</div>
<div>Other people are more than welcome to build their own
packages from the src.rpms and/or tarballs that are
available from gluster — and support them. It's still in the
source and there are no plans to remove it. (Unlike most of
the other deprecated features which were recently removed in
glusterfs-7.)</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div>
<div>[1] <a href="https://github.com/gluster/glusterfs/issues/764" target="_blank" rel="noreferrer">https://github.com/gluster/glusterfs/issues/764</a></div>
</div>
</div>
</div>
<br>
</div>
</blockquote>
<br>
<p>It seems <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1727248" target="_blank" rel="noreferrer">https://bugzilla.redhat.com/show_bug.cgi?id=1727248</a>
has resolved this issue. <br>
</p>
<p>Here i'll talk about something from commerical company view. For
security reasons most government procurement projects only allow
universal storage protocol(nfs, cifs etc) what means fuse will be
excluded. Consindering performance requirements, the only option
is nfs. <br></p></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I don't see how NFSv3 is more secure than newer NFS versions. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p>
</p>
<p>Nfsv4 is stateful protocol, but i see on performance improvement.
Trust me, nfs-ganesha(v3, v4) shows ~30% performance degradation
versus gnfs for either small or big files r/w in practice.
Further, many customers prefer nfs client than cifs in windows,
because the poor cifs performance, AFAIK nfs-ganesha is not going
well with windows nfs client.<br></p></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Interesting - we've seen far better performance with Ganesha v4.1 vs. gnfs. </div><div dir="auto">Would be great if you could share the details. </div><div dir="auto">Same for NFS Ganesha and Windows support.</div><div dir="auto"><br></div><div dir="auto">It's difficult to counterpart without referring to specific issues. It's eveb to harder to fix them ;-) </div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p>
</p>
<p>Gnfs is stable enough, we have about ~1000 servers, 4~24 servers
for a gluster cluster, about ~2000 nfs clients, all works fine
till the last two years expect some memleak issue. <br></p></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">Nice! Would be great for the Gluster community to learn more about the use case! </div><div dir="auto">Y. </div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><p>
</p>
<p>Thanks</p>
<p> -Xie<br>
</p>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Nov 21, 2019 at 5:31
AM Amar Tumballi <<a href="mailto:amarts@gmail.com" target="_blank" rel="noreferrer">amarts@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Hi All,
<div><br>
</div>
<div>As per the discussion on <a href="https://review.gluster.org/23645" target="_blank" rel="noreferrer">https://review.gluster.org/23645</a>,
recently we changed the status of gNFS (gluster's native
NFSv3 support) feature to 'Depricated / Orphan' state.
(ref: <a href="https://github.com/gluster/glusterfs/blob/master/MAINTAINERS#L185..L189" target="_blank" rel="noreferrer">https://github.com/gluster/glusterfs/blob/master/MAINTAINERS#L185..L189</a>).
With this email, I am proposing to change the status
again to 'Odd Fixes' (ref: <a href="https://github.com/gluster/glusterfs/blob/master/MAINTAINERS#L22" target="_blank" rel="noreferrer">https://github.com/gluster/glusterfs/blob/master/MAINTAINERS#L22</a>) </div>
<div><br>
</div>
<div>TL;DR;</div>
<div><br>
</div>
<div>
<div>I understand the current maintainers are not able
to focus on maintaining it as the focus of the
project, as earlier described, is keeping NFS-Ganesha
based integration with glusterfs. But, I am
volunteering along with Xie Changlong (currently
working at Chinamobile), to keep the feature running
as it used to in previous versions. Hence the status
of 'Odd Fixes'. </div>
<div><br>
</div>
<div>Before sending the patch to make these changes, I
am proposing it here now, as gNFS is not even shipped
with latest glusterfs-7.0 releases. I have heard from
some users that it was working great for them with
earlier releases, as all they wanted was NFS v3
support, and not much of features from gNFS. Also note
that, even though the packages are not built, none of
the regression tests using gNFS are stopped with
latest master, so it is working same from at least
last 2 years. </div>
</div>
<div><br>
</div>
<div>I request the package maintainers to please add
'--with gnfs' (or --enable-gnfs) back to their release
script through this email, so those users wanting to use
gNFS happily can continue to use it. Also points to
users/admins is that, the status is 'Odd Fixes', so
don't expect any 'enhancements' on the features provided
by gNFS.</div>
<div><br>
</div>
<div>Happy to hear feedback, if any.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Amar</div>
<div><br>
</div>
</div>
_______________________________________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org" target="_blank" rel="noreferrer">maintainers@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/maintainers</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Community Meeting Calendar:
APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: <a href="https://bluejeans.com/441850968" target="_blank" rel="noreferrer">https://bluejeans.com/441850968</a>
NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: <a href="https://bluejeans.com/441850968" target="_blank" rel="noreferrer">https://bluejeans.com/441850968</a>
Gluster-devel mailing list
<a href="mailto:Gluster-devel@gluster.org" target="_blank" rel="noreferrer">Gluster-devel@gluster.org</a>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" target="_blank" rel="noreferrer">https://lists.gluster.org/mailman/listinfo/gluster-devel</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
<br>
Community Meeting Calendar:<br>
<br>
APAC Schedule -<br>
Every 2nd and 4th Tuesday at 11:30 AM IST<br>
Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer noreferrer" target="_blank">https://bluejeans.com/441850968</a><br>
<br>
<br>
NA/EMEA Schedule -<br>
Every 1st and 3rd Tuesday at 01:00 PM EDT<br>
Bridge: <a href="https://bluejeans.com/441850968" rel="noreferrer noreferrer" target="_blank">https://bluejeans.com/441850968</a><br>
<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank" rel="noreferrer">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
</blockquote></div></div></div>