Hi-
I’m beginning to try Kerberos with NFS/RDMA. I get this complaint
from GSSD:
Oct 28 13:10:02 manet rpc.gssd[2549]: WARNING: unrecognized
protocol, 'rdma', requested for connection to server
klimt-ib.1015granger.net for user with uid 0
Should I change the kernel NFS client to tell GSSD it’s using
TCP, or should I change GSSD to recognize RDMA as another form
of TCP?
-—
Chuck Lever
On Wed, Oct 28, 2015 at 2:56 PM, Chuck Lever <[email protected]> wrote:
> Hi-
>
> I’m beginning to try Kerberos with NFS/RDMA. I get this complaint
> from GSSD:
>
> Oct 28 13:10:02 manet rpc.gssd[2549]: WARNING: unrecognized
> protocol, 'rdma', requested for connection to server
> klimt-ib.1015granger.net for user with uid 0
>
> Should I change the kernel NFS client to tell GSSD it’s using
> TCP, or should I change GSSD to recognize RDMA as another form
> of TCP?
>
gssd expects to be able to connect to the IP address that we pass in
the upcall. If we can guarantee that IP address can always be resolved
in a TCP connection attempt, then let's lie, and call it TCP.
Cheers
Trond
> On Oct 28, 2015, at 3:30 PM, Trond Myklebust <[email protected]> wrote:
>
> On Wed, Oct 28, 2015 at 2:56 PM, Chuck Lever <[email protected]> wrote:
>> Hi-
>>
>> I’m beginning to try Kerberos with NFS/RDMA. I get this complaint
>> from GSSD:
>>
>> Oct 28 13:10:02 manet rpc.gssd[2549]: WARNING: unrecognized
>> protocol, 'rdma', requested for connection to server
>> klimt-ib.1015granger.net for user with uid 0
>>
>> Should I change the kernel NFS client to tell GSSD it’s using
>> TCP, or should I change GSSD to recognize RDMA as another form
>> of TCP?
>>
>
> gssd expects to be able to connect to the IP address that we pass in
> the upcall. If we can guarantee that IP address can always be resolved
> in a TCP connection attempt, then let's lie, and call it TCP.
NFS/RDMA still requires IPoIB to provide IP addresses that
resolve to GUIDs, so I think we can make that guarantee.
Still, do you prefer the kernel to lie, or for GSSD to lie?
Changing GSSD might be more future-proof.
—-
Chuck Lever
On Wed, Oct 28, 2015 at 3:33 PM, Chuck Lever <[email protected]> wrote:
>
>> On Oct 28, 2015, at 3:30 PM, Trond Myklebust <[email protected]> wrote:
>>
>> On Wed, Oct 28, 2015 at 2:56 PM, Chuck Lever <[email protected]> wrote:
>>> Hi-
>>>
>>> I’m beginning to try Kerberos with NFS/RDMA. I get this complaint
>>> from GSSD:
>>>
>>> Oct 28 13:10:02 manet rpc.gssd[2549]: WARNING: unrecognized
>>> protocol, 'rdma', requested for connection to server
>>> klimt-ib.1015granger.net for user with uid 0
>>>
>>> Should I change the kernel NFS client to tell GSSD it’s using
>>> TCP, or should I change GSSD to recognize RDMA as another form
>>> of TCP?
>>>
>>
>> gssd expects to be able to connect to the IP address that we pass in
>> the upcall. If we can guarantee that IP address can always be resolved
>> in a TCP connection attempt, then let's lie, and call it TCP.
>
> NFS/RDMA still requires IPoIB to provide IP addresses that
> resolve to GUIDs, so I think we can make that guarantee.
>
> Still, do you prefer the kernel to lie, or for GSSD to lie?
> Changing GSSD might be more future-proof.
OK.