EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: Standard RTEMS NFSv3 client
From: Joel Sherrill via Tech-talk <tech-talk at aps.anl.gov>
To: Matt Rippa <mrippa at gemini.edu>, Talk EPICS Tech <tech-talk at aps.anl.gov>
Date: Wed, 12 Feb 2020 00:20:36 +0000
On 2/11/2020 1:46 PM, Matt Rippa wrote:
Hello EPICS/RTEMS users,

Back in 2017 there were some emails in the EPICS and RTEMS community about requesting support for an RTEMS NFSv3 client . We're getting increasing requests from our IT department to support this but don't see an easy way forward. We're running RTEMS 4.10.2 and NFSv2 is currently working and supported by default with a CentOS 6 file server. Moving to CentOS 7 we're getting push back supporting NFSv2. It's not enabled by default and we have to configure it. Our IT department believes the ability to enable NFS v2 on CentOS7 is a bug and it may not function properly after routine maintenance on a CentOS7 machine. This may be related to [1] below.

I know we (like you) have used NFSv2 RTEMS client with an CentOS 7 server.

The issue you cite seems to be related to documentation so I don't see a particular concern with that.

A few questions:

1. Is there any risk manually configuring a CentOS7 nfs server to use version 2 via /etc/sysconfig/nfs ?:

Config changes to /etc/sysconfig/nfs: 
MOUNTD_NFS_V2="yes"
RPCNFSDARGS="-V 2"
RPCMOUNTDOPTS="-V 2"

2. Do you know if CentOS 8 continues to support NFSv2, even if you have to configure it?

Based on this, it appears to still be there.

https://linuxize.com/post/how-to-install-and-configure-an-nfs-server-on-centos-8/

I couldn't quickly find anything about NFSv2 on a recent version of Fedora which would be a hint of even longer term point of view.

3. Do you know if/when we'll hit a hard stop with NFS v2 support on CentOS?

4. Gemini may be able to find some funding for the development of an NFSv3 client on RTEMS. Are other sites interested in pursuing this and sharing the cost?

I can't help with the funding but I can say that the RTEMS Project would love to see this as well. One requirement to consider is whether to support both the legacy and libbsd TCP/IP stacks.

One option for a libbsd only solution is to focus on adding the FreeBSD NFS client to libbsd. That would provide a solid base for the future and it would get updated with the rest of the libbsd code base.

But it would leave BSPs which don't have drivers in the new stack out in the cold. The path for them might be focused on improvements to the existing NFS client (if v2->v3/4 is possible that way).  AFAIK this is the TCP/IP stack supported by many of the BSPs the EPICS community uses. 

Providing solutions for both stacks is likely necessary because some of the older boards may not have the RAM to support libbsd and there is always the issue of making sure there are drivers. Solving this the best way for both TCP/IP stacks upgrades the capability for all boards in use without touching any BSP or device driver specifics.

I am happy to chat about this in more detail or investigate the amount of work required.

In case you all never hear it, the RTEMS developers are proud RTEMS is used by the EPICS community.  You all do great work and contribute to increasing humanity's understanding of the universe.

And as a final aside, we would really like to get EPICS integrated into the RTEMS testing cycle so we all can be confident that EPICS and RTEMS work together properly with no unexpected breakages.

Thanks.

--joel sherrill
RTEMS/OAR






Replies:
Re: Standard RTEMS NFSv3 client Matt Newville via Tech-talk
References:
Standard RTEMS NFSv3 client Matt Rippa via Tech-talk
Navigate by Date:
Prev: RE: Standard RTEMS NFSv3 client Zhou, Jingchen via Tech-talk
Next: Re: Standard RTEMS NFSv3 client Matt Newville via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: Standard RTEMS NFSv3 client Zhou, Jingchen via Tech-talk
Next: Re: Standard RTEMS NFSv3 client Matt Newville via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024 
ANJ, 11 Feb 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·