Re: [Nfs-ganesha-devel] nss_getpwnam: name 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'

2018-03-07 Thread Malahal Naineni 
>> Tried identical ifmapd.conf files on client and server but rpcidmapd
tries to start the local copy of nfsd on the nfs Ganesha servers but that
competes with

NFS Ganesha doesn't need rpcidmapd daemon running. So refrain from running
the idmapd daemon. Ganesha uses idmapd libraries, so you should be good as
long as you have the libraries installed (part of the nfs-utils package on
RHEL, I think).

Regards, Malahal.

On Tue, Mar 6, 2018 at 9:15 PM, Tom  wrote:

> t...@my.dom is an ad user.   Nix.my.dom is a subdomain managed freeipa.
>
> Tried identical ifmapd.conf files on client and server but rpcidmapd tries
> to start the local copy of nfsd on the nfs Ganesha servers but that
> competes with nfs-Ganesha and won’t bind on port 2049.  So I need to change
> the port for the old nfs to 12049 etc to get the old nfs started so
> rpcidmapd can start on the Ganesha nfs servers.  They made it a dependency.
>
> That’s when things get messy.   I may try to uninstall the built in nfs
> packages but not sure if they will also pull out the rpcidmapd ones too.
>
> Cheers,
> Tom
>
> Sent from my iPhone
>
> > On Mar 6, 2018, at 9:00 AM, Daniel Gryniewicz  wrote:
> >
> > Based on the error messages, you client is not sending t...@nix.my.dom
> but is sending t...@my.dom@localdomain.  Something is mis-configured on
> the client.  Have you tried having identical (including case) idmapd.conf
> files on both the client and server?
> >
> > Idmap configuration has historically be very picky and hard to set up,
> and I'm far from an expert on it.
> >
> > Daniel
> >
> >> On 03/06/2018 08:24 AM, TomK wrote:
> >> Hey Guy's,
> >> Getting below message which in turn fails to list proper UID / GID on
> NFSv4 mounts from within an unprivileged account. All files show up with
> owner and group as nobody / nobody when viewed from the client.
> >> Wondering if anyone saw this and what the solution could be here?
> >> If not the right list, let me know please.
> >> [root@client01 etc]# cat /etc/idmapd.conf|grep -v "#"| sed -e "/^$/d"
> >> [General]
> >> Verbosity = 7
> >> Domain = nix.my.dom
> >> [Mapping]
> >> [Translation]
> >> [Static]
> >> [UMICH_SCHEMA]
> >> LDAP_server = ldap-server.local.domain.edu
> >> LDAP_base = dc=local,dc=domain,dc=edu
> >> [root@client01 etc]#
> >> Mount looks like this:
> >> nfs-c01.nix.my.dom:/n/my.dom on /n/my.dom type nfs4
> (rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,
> hard,proto=tcp,port=0,timeo=10,retrans=2,sec=sys,clientaddr=192.168.0.236,
> local_lock=none,addr=192.168.0.80) /var/log/messages
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: key: 0x3f2c257b type: uid
> value: t...@my.dom@localdomain timeout 600
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid: calling
> nsswitch->name_to_uid
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nss_getpwnam: name 
> >> 't...@my.dom@localdomain'
> domain 'nix.my.dom': resulting localname '(null)'
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nss_getpwnam: name 
> >> 't...@my.dom@localdomain'
> does not map into domain 'nix.my.dom'
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid:
> nsswitch->name_to_uid returned -22
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid: final
> return value is -22
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid: calling
> nsswitch->name_to_uid
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nss_getpwnam: name
> 'nob...@nix.my.dom' domain 'nix.my.dom': resulting localname 'nobody'
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid:
> nsswitch->name_to_uid returned 0
> >> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid: final
> return value is 0
> >> Mar  6 00:17:27 client01 nfsidmap[14398]: key: 0x324b0048 type: gid
> value: t...@my.dom@localdomain timeout 600
> >> Mar  6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid: calling
> nsswitch->name_to_gid
> >> Mar  6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid:
> nsswitch->name_to_gid returned -22
> >> Mar  6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid: final
> return value is -22
> >> Mar  6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid: calling
> nsswitch->name_to_gid
> >> Mar  6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid:
> nsswitch->name_to_gid returned 0
> >> Mar  6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid: final
> return value is 0
> >> Mar  6 00:17:31 client01 systemd-logind: Removed session 23.
> >> Result of:
> >> systemctl restart rpcidmapd
> >> /var/log/messages
> >> ---
> >> Mar  5 23:46:12 client01 systemd: Stopping Automounts filesystems on
> demand...
> >> Mar  5 23:46:13 client01 systemd: Stopped Automounts filesystems on
> demand.
> >> Mar  5 23:48:51 client01 systemd: Stopping NFSv4 ID-name mapping
> service...
> >> Mar  5 23:48:51 client01 systemd: Starting Preprocess NFS
> configuration...
> >> Mar  5 23:48:51 client01 systemd: Started Preprocess NFS configuration.
> >> Mar

Re: [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

2018-03-07 Thread Kinglong Mee 
On 2018/3/7 21:10, Daniel Gryniewicz wrote:
> On 03/06/2018 10:10 PM, Kinglong Mee wrote:
>> On 2018/3/7 10:59, Kinglong Mee wrote:
>>> When using nfsv3 on glusterfs-3.13.1-1.el7.x86_64 and 
>>> nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64,
>>> I gets strange "Invalid argument" when writing file.
>>>
>>> 1. With quota disabled;
>>> nfs client mount nfs-ganesha share, and do 'll' in the testing directory.
>>>
>>> 2. Enable quota;
>>> # getfattr -d -m . -e hex /root/rpmbuild/gvtest/nfs-ganesha/testfile92
>>> getfattr: Removing leading '/' from absolute path names
>>> # file: root/rpmbuild/gvtest/nfs-ganesha/testfile92
>>> trusted.gfid=0xe2edaac0eca8420ebbbcba7e56bbd240
>>> trusted.gfid2path.b3250af8fa558e66=0x3966313434352d653530332d343831352d396635312d3236633565366332633137642f7465737466696c653932
>>> trusted.glusterfs.quota.9f1445ff-e503-4815-9f51-26c5e6c2c17d.contri.3=0x0201
>>>
>>> Notice: testfile92 without trusted.pgfid xattr.
>>
>> The trusted.pgfid will be created by the next name lookup; nameless lookup 
>> don't create it.
>>
>>> 3. restart glusterfs volume by "gluster volume stop/start gvtest"
>>
>> Restarting glusterfsd here cleanup all inode cache from memory;
>> after starting, inode of testfile92's parent is NULL.
>>
>>> 4. echo somedata > testfile92
>>
>> Because, nfs-ganesha and nfs client has cache for testfile92,
>> before write fops, no name lookup happens that trusted.pgfid is not created 
>> for testfile92.
>>
>> Quota_writev call quota_build_ancestry building the ancestry in 
>> quota_check_limit,
>> but testfile92 doesn't contain trusted.pgfid, so that write fops failed with 
>> Invalid argument.
>>
>> I have no idea of fixing this problem, any comments are welcome.
>>
> 
> I think, ideally, Gluster would send an invalidate upcall under the 
> circumstances, causing Ganesha do drop it's cached entry.

It doesn't work.
I try to restarting nfs-ganesha, and echo data to testfile92, the problem also 
exists.

After nfs-ganesha restart, 
1. A GETATTR is send from nfs-client for the testfile92, ganesha translates it 
to nameless lookup.
2. A ACCESS gets attributes from nfs-ganesha's cache (cached by #1).
3. A SETATTR sets the testfile92's size to 0, ganesha translates it to setattr 
fop.
4. A WRITE also get Invalid argument error.

If ganesha drops its cache, nfs client may write file by filehandle;
ganesha lookup it by nameless lookup from glusterfs,
so that, trusted.pgfid isn't created too.

I think, a name lookup is needed for testfile92 after quota enable.

thanks,
Kinglong Mee

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Multiprotocol support in ganesha

2018-03-07 Thread Frank Filz 
Unfortunately out in the real world, people want to mix POSIX and Microsoft 
semantics…

 

So we do the best we can.

 

I wonder how much of the multi-protocol use falls into two camps:

 

1.  Simple file sharing, for example, I run Virtual Box on a Windows 
machine to get Linux VMs. I mount my Windows “My Documents” into the Linux VM 
so I can easily pass files back and forth. Share reservations work and prevent 
Linux from trampling things if Microsoft Word happens to have a file open.

2.  Some kind of database application with clients on multiple platforms. 
Such application will use appropriate synchronizing operations including byte 
range locks in a way that does not depend on any of the peculiarities of POSIX 
or Microsoft semantics.

 

Yea, we can try to make things like delete of open files work as best as 
possible, but either of those two use cases won’t have any really big surprises 
if the integration for a peculiarity like deleting an open file isn’t perfect.

 

Now one use case that may not go so well is an application that uses lock files 
to indicate which client or process is active…

 

I’ve seen folks paranoid that POSIX byte range locks are only advisory, but 
outside of a program bug, if a POSIX app and a Windows app are both using byte 
range locks to protect records they are changing, it doesn’t matter that POSIX 
thinks they are only advisory… Of course a server CAN enforce the range locks 
(and NFS v4 even supports this idea), and yea, that will break a POSIX app that 
thought it didn’t actually need to respect the locks.

 

I think overall Ganesha does a pretty good job. There are places where it can 
do better.

 

While talk of having an SMB front end to Ganesha are fun, I doubt we will ever 
do that, and I don’t think it’s necessary to have sufficiently good integration 
to cover 99.9% of the possible multi-protocol use cases.

 

Frank

 

From: DENIEL Philippe [mailto:philippe.den...@cea.fr] 
Sent: Wednesday, March 7, 2018 6:28 AM
To: Pradeep ; nfs-ganesha-devel 

Subject: Re: [Nfs-ganesha-devel] Multiprotocol support in ganesha

 

Hi,

from a "stratospheric" point of view, I see a potentially big issue ahead for 
such a feature : FSAL has been designed to be quite close to POSIX behavior, 
CIFS follows the Microsoft File System semantics, which is pretty different 
from POSIX.
My experience with 9p integration in Ganesha shows some issues in POSIX corner 
cases (like "delete on close" situations), I can't imagine what integrating a 
CIFS support would mean. 
Years ago, Tom Tapley came to bake-a-thon (this was a few months after he 
joined Microsoft Research) and he talked about issues met by Microsoft to 
implement a NFSv4 support, because of Microsoft semantics. He found many, but 
was quite optimistic. Current state : Windows has no NFS support and code 
developed at CITI (e.g. NFSv4 clients for Windos) were not pushed to Windows.
Microsoft is not POSIX and POSIX is not Microsoft. They live in two very 
different worlds, and it's probably better so ;-)

Regards

Philippe

On 03/06/18 18:20, Pradeep wrote:

Hello,

 

Is there plans to implement multiprotocol (NFS and CIFS accessing same 
export/share) in ganesha? I believe current FD cache will need changes to 
support that.

 

Thanks,

Pradeep






--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot






___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net 
 
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] Multiprotocol support in ganesha

2018-03-07 Thread DENIEL Philippe 

Hi,

from a "stratospheric" point of view, I see a potentially big issue 
ahead for such a feature : FSAL has been designed to be quite close to 
POSIX behavior, CIFS follows the Microsoft File System semantics, which 
is pretty different from POSIX.
My experience with 9p integration in Ganesha shows some issues in POSIX 
corner cases (like "delete on close" situations), I can't imagine what 
integrating a CIFS support would mean.
Years ago, Tom Tapley came to bake-a-thon (this was a few months after 
he joined Microsoft Research) and he talked about issues met by 
Microsoft to implement a NFSv4 support, because of Microsoft semantics. 
He found many, but was quite optimistic. Current state : Windows has no 
NFS support and code developed at CITI (e.g. NFSv4 clients for Windos) 
were not pushed to Windows.
Microsoft is not POSIX and POSIX is not Microsoft. They live in two very 
different worlds, and it's probably better so ;-)


    Regards

        Philippe

On 03/06/18 18:20, Pradeep wrote:

Hello,

Is there plans to implement multiprotocol (NFS and CIFS accessing same 
export/share) in ganesha? I believe current FD cache will need changes 
to support that.


Thanks,
Pradeep


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] nss_getpwnam: name 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'

2018-03-07 Thread Frank Filz 
> On 3/6/2018 10:45 AM, Tom wrote:> t...@my.dom is an ad user.   Nix.my.dom
> is a subdomain managed freeipa.

So you have two domains visible on your client? That may be causing confusion.

The client sending t...@my.dom@localdomain makes me think idmapd thinks 
localdomain is the domain to use for ids, and it doesn't recognize @my.dom, so 
it's treating "t...@my.dom" as an opaque username, and appending @localdomain 
to turn it into a fully qualified username.

Frank

> > Tried identical ifmapd.conf files on client and server but rpcidmapd tries 
> > to
> start the local copy of nfsd on the nfs Ganesha servers but that competes with
> nfs-Ganesha and won’t bind on port 2049.  So I need to change the port for the
> old nfs to 12049 etc to get the old nfs started so rpcidmapd can start on the
> Ganesha nfs servers.  They made it a dependency.
> >
> > That’s when things get messy.   I may try to uninstall the built in nfs 
> > packages
> but not sure if they will also pull out the rpcidmapd ones too.
> >
> > Cheers,
> > Tom
> >
> > Sent from my iPhone
> >
> >> On Mar 6, 2018, at 9:00 AM, Daniel Gryniewicz  wrote:
> >>
> >> Based on the error messages, you client is not sending t...@nix.my.dom but
> is sending t...@my.dom@localdomain.  Something is mis-configured on the
> client.  Have you tried having identical (including case) idmapd.conf files 
> on both
> the client and server?
> >>
> >> Idmap configuration has historically be very picky and hard to set up, and 
> >> I'm
> far from an expert on it.
> >>
> >> Daniel
> >>
> >>> On 03/06/2018 08:24 AM, TomK wrote:
> >>> Hey Guy's,
> >>> Getting below message which in turn fails to list proper UID / GID on 
> >>> NFSv4
> mounts from within an unprivileged account. All files show up with owner and
> group as nobody / nobody when viewed from the client.
> >>> Wondering if anyone saw this and what the solution could be here?
> >>> If not the right list, let me know please.
> >>> [root@client01 etc]# cat /etc/idmapd.conf|grep -v "#"| sed -e "/^$/d"
> >>> [General]
> >>> Verbosity = 7
> >>> Domain = nix.my.dom
> >>> [Mapping]
> >>> [Translation]
> >>> [Static]
> >>> [UMICH_SCHEMA]
> >>> LDAP_server = ldap-server.local.domain.edu LDAP_base =
> >>> dc=local,dc=domain,dc=edu
> >>> [root@client01 etc]#
> >>> Mount looks like this:
> >>> nfs-c01.nix.my.dom:/n/my.dom on /n/my.dom type nfs4
> >>> (rw,relatime,vers=4.0,rsize=8192,wsize=8192,namlen=255,hard,proto=tc
> >>> p,port=0,timeo=10,retrans=2,sec=sys,clientaddr=192.168.0.236,local_l
> >>> ock=none,addr=192.168.0.80) /var/log/messages Mar  6 00:17:27 client01
> nfsidmap[14396]: key: 0x3f2c257b type: uid value: t...@my.dom@localdomain
> timeout 600 Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid:
> calling nsswitch->name_to_uid Mar  6 00:17:27 client01 nfsidmap[14396]:
> nss_getpwnam: name 't...@my.dom@localdomain' domain 'nix.my.dom':
> resulting localname '(null)'
> >>> Mar  6 00:17:27 client01 nfsidmap[14396]: nss_getpwnam: name
> 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'
> >>> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid:
> >>> nsswitch->name_to_uid returned -22 Mar  6 00:17:27 client01
> >>> nfsidmap[14396]: nfs4_name_to_uid: final return value is -22 Mar  6
> >>> 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid: calling nsswitch-
> >name_to_uid Mar  6 00:17:27 client01 nfsidmap[14396]: nss_getpwnam: name
> 'nob...@nix.my.dom' domain 'nix.my.dom': resulting localname 'nobody'
> >>> Mar  6 00:17:27 client01 nfsidmap[14396]: nfs4_name_to_uid:
> >>> nsswitch->name_to_uid returned 0 Mar  6 00:17:27 client01
> >>> nfsidmap[14396]: nfs4_name_to_uid: final return value is 0 Mar  6
> >>> 00:17:27 client01 nfsidmap[14398]: key: 0x324b0048 type: gid value:
> >>> t...@my.dom@localdomain timeout 600 Mar  6 00:17:27 client01
> >>> nfsidmap[14398]: nfs4_name_to_gid: calling nsswitch->name_to_gid Mar
> >>> 6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid:
> >>> nsswitch->name_to_gid returned -22 Mar  6 00:17:27 client01
> >>> nfsidmap[14398]: nfs4_name_to_gid: final return value is -22 Mar  6
> >>> 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid: calling nsswitch-
> >name_to_gid Mar  6 00:17:27 client01 nfsidmap[14398]: nfs4_name_to_gid:
> nsswitch->name_to_gid returned 0 Mar  6 00:17:27 client01 nfsidmap[14398]:
> nfs4_name_to_gid: final return value is 0 Mar  6 00:17:31 client01 systemd-
> logind: Removed session 23.
> >>> Result of:
> >>> systemctl restart rpcidmapd
> >>> /var/log/messages
> >>> ---
> >>> Mar  5 23:46:12 client01 systemd: Stopping Automounts filesystems on
> demand...
> >>> Mar  5 23:46:13 client01 systemd: Stopped Automounts filesystems on
> demand.
> >>> Mar  5 23:48:51 client01 systemd: Stopping NFSv4 ID-name mapping
> service...
> >>> Mar  5 23:48:51 client01 systemd: Starting Preprocess NFS configuration...
> >>> Mar  5 23:48:51 client01 systemd: Started Preprocess NFS configuration.
> >>> Mar  5 23:48:51

Re: [Nfs-ganesha-devel] nfsv3 client writing file gets Invalid argument on glusterfs with quota on

2018-03-07 Thread Daniel Gryniewicz 

On 03/06/2018 10:10 PM, Kinglong Mee wrote:

On 2018/3/7 10:59, Kinglong Mee wrote:

When using nfsv3 on glusterfs-3.13.1-1.el7.x86_64 and 
nfs-ganesha-2.6.0-0.2rc3.el7.centos.x86_64,
I gets strange "Invalid argument" when writing file.

1. With quota disabled;
nfs client mount nfs-ganesha share, and do 'll' in the testing directory.

2. Enable quota;
# getfattr -d -m . -e hex /root/rpmbuild/gvtest/nfs-ganesha/testfile92
getfattr: Removing leading '/' from absolute path names
# file: root/rpmbuild/gvtest/nfs-ganesha/testfile92
trusted.gfid=0xe2edaac0eca8420ebbbcba7e56bbd240
trusted.gfid2path.b3250af8fa558e66=0x3966313434352d653530332d343831352d396635312d3236633565366332633137642f7465737466696c653932
trusted.glusterfs.quota.9f1445ff-e503-4815-9f51-26c5e6c2c17d.contri.3=0x0201

Notice: testfile92 without trusted.pgfid xattr.


The trusted.pgfid will be created by the next name lookup; nameless lookup 
don't create it.


3. restart glusterfs volume by "gluster volume stop/start gvtest"


Restarting glusterfsd here cleanup all inode cache from memory;
after starting, inode of testfile92's parent is NULL.


4. echo somedata > testfile92


Because, nfs-ganesha and nfs client has cache for testfile92,
before write fops, no name lookup happens that trusted.pgfid is not created for 
testfile92.

Quota_writev call quota_build_ancestry building the ancestry in 
quota_check_limit,
but testfile92 doesn't contain trusted.pgfid, so that write fops failed with 
Invalid argument.

I have no idea of fixing this problem, any comments are welcome.



I think, ideally, Gluster would send an invalidate upcall under the 
circumstances, causing Ganesha do drop it's cached entry.


Daniel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel

Re: [Nfs-ganesha-devel] submitting LizardFS FSAL to nfs-ganesha

2018-03-07 Thread Kaleb S. KEITHLEY 
On 03/07/2018 06:07 AM, Szymon Haly wrote:
> Hi Kaleb,
> 
> Hope you are well.
> We are planning on releasing new version on Monday 26/03/2018.
> It will also include some fixes in our implementation of Ganesha. The
> guys told me that it should be pretty easy to add to your project.
> 
> Will let you know.

Excellent.

I actually thought you had done that once already. I thought DanG told
me he was working on merging your FSAL.

Regardless, it's good to have more contributions and contributors.

Thanks and regards,

--

Kaelb


> 
> On Thu, Feb 15, 2018 at 6:36 PM, Szymon Haly
> > wrote:
> 
> Hey Kaleb,
> Hope you are well.
> 
> Sorry for delay - we are working on the patch to make it perfect to
> save us time during testing.
> It should be ready some day next week - will keep you posted.
> 
> On Mon, Feb 5, 2018 at 3:33 AM, Szymon Haly
> >
> wrote:
> 
> Hi Kaleb,
> 
> Thanks so much for an awesome time. I forwarded your email to
> the team and we will proceed.
> 
> On Feb 5, 2018 10:50, "Kaleb S. KEITHLEY"  > wrote:
> 
> Hi,
> 
> Here's process for submitting your code via gerrithub.
> 
> 
> https://github.com/nfs-ganesha/nfs-ganesha/wiki/DevPolicy#Pushing_to_gerrit
> 
> 
> 
> Good talking with you at FOSDEM.
> 
> Regards,
> 
> --
> 
> Kaleb
> 
> 
> 
> 
> -- 
> Szymon Haly
> CSO
> P: +48221120519
> M: +48 793 983 133
> 
> 
> 
> 
> -- 
> Szymon Haly
> CSO
> P: +48221120519
> M: +48 793 983 133
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel