Re: [nfsv4] [PATCH nfs-utils v3 00/14] add NFS over AF_VSOCK support

David Noveck <davenoveck@gmail.com> Wed, 13 September 2017 18:18 UTC

Return-Path: <davenoveck@gmail.com>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B8841200F3 for <nfsv4@ietfa.amsl.com>; Wed, 13 Sep 2017 11:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJNolpngmnYs for <nfsv4@ietfa.amsl.com>; Wed, 13 Sep 2017 11:18:11 -0700 (PDT)
Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F254132A05 for <nfsv4@ietf.org>; Wed, 13 Sep 2017 11:18:11 -0700 (PDT)
Received: by mail-it0-x22a.google.com with SMTP id v19so4686315ite.0 for <nfsv4@ietf.org>; Wed, 13 Sep 2017 11:18:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dyVm9QTJYTTNw9qLLeNjtfGOAxk6EPt3o/w2LP/I2U0=; b=E5l1rP1mmkwI3HBztaZCMt98IR35UXhc31FqJ3J+cgAGKYW/DYot+C13uzcYIK8n/w ddkYjmNcNAeGfbK49Y/xQZx1JivncSACiHROmxm58vV2Ed2cRZqgVo9WGCy/GGtFFWRY kSa+KNenjcknjfmgjKJByRMStlcUA3iEdq/HWfbWfFVpxVr4hNtT85LD+zUjZabr28TY 7gapX1BFpDHh5jHT64Y7WR5bByxTLnXnzdhyrFgco0XZun0sBblvxwoMS/u3P976S3mM fb8DxyX9N43pLwRKft1VW2BbiAjj9DpabWrjbAyOhd1aNfPDTDLtG7ozHpPWToMKItrX EkHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dyVm9QTJYTTNw9qLLeNjtfGOAxk6EPt3o/w2LP/I2U0=; b=De+I9tXiu2CEA4U7BvKYZXtss9istDyONIBiML327ZM3O/WRR95tMhGivGyhBQEOjQ 4AhyAcs7DlKaVbm++fZ/GNq2SaOiOzzO9NxuvYA+V4txMm0H61YZnPzER+9gkYMsmDEI rfajCw7+WvzTShK3M9JS263el40D0sLFUOl/qX730Iwb1fM74dzM0pPRpnGZtdKNHn2i VLOmcI9QwcSDyVREjKYdAPDK2d3QZGAf9YKvAwh8w0gU3ILLotucul/kQSAZ0B9BwntF asRTH/KreMtmoGBhyGVgf7/3viNQMPk0hCkgZDSUeUfDKfdfWeZSfC8fTSuOC0an+U39 vWaQ==
X-Gm-Message-State: AHPjjUiMSR28WBEuGlriJax0aL++f1gGpI8vB8S9XUdkpauQQlRUsQl3 t9PeMPKX00vasIw1oPTyVlkqLEf330FqZ29b1yg=
X-Google-Smtp-Source: AOwi7QCGz3i/aznOZpSCxzdBUGjmhn0rgli2scN8XKzPYOVKez5tzZkh4aXsbGVgbQ8JD5fcpqCxtBsv4oCiI99mDlg=
X-Received: by 10.36.83.146 with SMTP id n140mr6733497itb.104.1505326690745; Wed, 13 Sep 2017 11:18:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.4.194 with HTTP; Wed, 13 Sep 2017 11:18:09 -0700 (PDT)
In-Reply-To: <20170913162111.GA14389@infradead.org>
References: <20170913102650.10377-1-stefanha@redhat.com> <20170913162111.GA14389@infradead.org>
From: David Noveck <davenoveck@gmail.com>
Date: Wed, 13 Sep 2017 14:18:09 -0400
Message-ID: <CADaq8jd2VaHUX=9rVbG41tTPj+9R8Grkjnaoh1hfKv8sVn5-GA@mail.gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stefan Hajnoczi <stefanha@redhat.com>, "nfsv4@ietf.org" <nfsv4@ietf.org>, linux-nfs@vger.kernel.org, Jeff Layton <jlayton@redhat.com>, NeilBrown <neilb@suse.com>, Steve Dickson <steved@redhat.com>, "J . Bruce Fields" <bfields@fieldses.org>, Matt Benjamin <mbenjami@redhat.com>
Content-Type: multipart/alternative; boundary="001a114052dcac647b0559162e35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/lhBQ2t-OBxnbhfYdtc92_7iHNEQ>
Subject: Re: [nfsv4] [PATCH nfs-utils v3 00/14] add NFS over AF_VSOCK support
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Sep 2017 18:18:15 -0000

> and how to ask IESG to assign it?

The way to get the IESG to assign it would be to write an RFC and get it
approved as a Proposed Standard but I don't think you need to do that.
There is a portion of the netid registry that is assigned on a
first-come-first-served basis (see RFCs 5665 and 5226) and if you are OK
with that, the IESG doesn't have to be involved.  You simply have to ask
IANA to assign it, providing the information (pretty limited) mentioned in
those RFCs.

On Wed, Sep 13, 2017 at 12:21 PM, Christoph Hellwig <hch@infradead.org>
wrote:

> Please get your VSOCK NFS transport into the ietf NFSv4 working group
> first before moving forward with Linux support - we should not implement
> non-standardized extensions.
>
> On Wed, Sep 13, 2017 at 11:26:36AM +0100, Stefan Hajnoczi wrote:
> >  * The last revision was somewhat controversial because it's already
> possible
> >    to share files between a hypervisor and virtual machine using TCP/IP,
> so why
> >    add AF_VSOCK support to the stack?  TCP/IP based solutions require the
> >    virtual machine administrator to be involved in the configuration and
> are
> >    therefore not suitable for automatic management by OpenStack, oVirt,
> etc.
> >    Maintainers, is this feature acceptable?
> >
> >  * Need advice on netid: is there agreement to use "tcpv" instead of
> "vsock" as
> >    Chuck Lever suggested and how to ask IESG to assign it?
> >
> > The AF_VSOCK address family allows virtual machines to communicate with
> the
> > hypervisor using a zero-configuration transport.  KVM, VMware, and
> Hyper-V
> > hypervisors support AF_VSOCK and it was first introduced in Linux 3.9.
> >
> > This patch series adds AF_VSOCK support to mount.nfs(8) and
> rpc.nfsd(8).  To
> > mount an export from the hypervisor (CID 2):
> >
> >   # mount.nfs 2:/srv/vm01 /mnt -o proto=vsock
> >
> > To serve exports over vsock port 2049:
> >
> >   # nfsd ... --vsock 2049
> >
> > This series extends exports(5) syntax to handle vsock:<CID> or vsock:*.
> For
> > example, the guest with CID 3 can be given access using vsock:3.
> >
> > nfsd can export over IPv4/IPv6 and vsock at the same time.  See the
> changes to
> > exports.man, nfs.man, and nfsd.man in the patches for syntax details.
> >
> > NFSv4 and later are supported.
> >
> > The code is also available here:
> > https://github.com/stefanha/nfs-utils/tree/vsock-nfsd
> >
> > The latest kernel patches are available here:
> > https://github.com/stefanha/linux/tree/vsock-nfsd
> >
> > Stefan Hajnoczi (14):
> >   mount: don't use IPPROTO_UDP for address resolution
> >   nfs-utils: add vsock.h
> >   nfs-utils: add AF_VSOCK support to sockaddr.h
> >   mount: present AF_VSOCK addresses
> >   mount: accept AF_VSOCK in nfs_verify_family()
> >   mount: generate AF_VSOCK clientaddr
> >   getport: recognize "vsock" netid
> >   mount: AF_VSOCK address parsing
> >   exportfs: introduce host_freeaddrinfo()
> >   exportfs: add AF_VSOCK address parsing and printing
> >   exportfs: add AF_VSOCK support to set_addrlist()
> >   exportfs: add support for "vsock:" exports(5) syntax
> >   nfsd: add --vsock (-v) option to nfsd
> >   tests: add "vsock:" exports(5) test case
> >
> >  tests/Makefile.am          |   3 +-
> >  support/include/exportfs.h |   4 ++
> >  support/include/sockaddr.h |  18 +++++
> >  support/include/vsock.h    |  59 +++++++++++++++++
> >  utils/nfsd/nfssvc.h        |   1 +
> >  support/export/client.c    |   8 +--
> >  support/export/hostname.c  | 161 ++++++++++++++++++++++++++++++
> +++++++++++++--
> >  support/nfs/getport.c      |  16 +++--
> >  utils/exportfs/exportfs.c  |  42 ++++++++++--
> >  utils/mount/network.c      |  37 ++++++++++-
> >  utils/mount/stropts.c      |  61 ++++++++++++++---
> >  utils/mountd/auth.c        |   2 +-
> >  utils/mountd/cache.c       |  10 +--
> >  utils/mountd/mountd.c      |   4 +-
> >  utils/mountd/rmtab.c       |   2 +-
> >  utils/nfsd/nfsd.c          |  18 ++++-
> >  utils/nfsd/nfssvc.c        |  62 +++++++++++++++++
> >  configure.ac               |   3 +
> >  tests/t0002-vsock-basic.sh |  53 +++++++++++++++
> >  utils/exportfs/exports.man |  12 +++-
> >  utils/mount/nfs.man        |  20 ++++--
> >  utils/nfsd/nfsd.man        |   4 ++
> >  22 files changed, 552 insertions(+), 48 deletions(-)
> >  create mode 100644 support/include/vsock.h
> >  create mode 100755 tests/t0002-vsock-basic.sh
> >
> > --
> > 2.13.5
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> ---end quoted text---
>
> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4
>