Parallel NFS (pNFS) Flexible File Layout v2
draft-haynes-nfsv4-flex-filesv2-00

Document Type Active Internet-Draft (individual)
Last updated 2017-08-07
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
NFSv4                                                          T. Haynes
Internet-Draft                                              Primary Data
Intended status: Standards Track                         August 07, 2017
Expires: February 8, 2018

              Parallel NFS (pNFS) Flexible File Layout v2
                 draft-haynes-nfsv4-flex-filesv2-00.txt

Abstract

   The Parallel Network File System (pNFS) allows a separation between
   the metadata (onto a metadata server) and data (onto a storage
   device) for a file.  The flexible file layout type is an extension to
   pNFS which allows the use of storage devices in a fashion such that
   they require only a quite limited degree of interaction with the
   metadata server, using already existing protocols.  This document
   describes two extensions to the flexible file layout type to allow
   for multiple stateids for tightly coupled NFSv4 models and an
   additional security mechanism for loosely coupled models.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 8, 2018.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Haynes                  Expires February 8, 2018                [Page 1]
Internet-Draft             Flex File Layout v2               August 2017

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  XDR Description of the Flexible File Layout Type  . . . . . .   4
     2.1.  Code Components Licensing Notice  . . . . . . . . . . . .   5
   3.  Flexible File Layout Type v2  . . . . . . . . . . . . . . . .   6
     3.1.  ffv2_layout4  . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
     4.1.  RPCSEC_GSS and Security Services  . . . . . . . . . . . .   9
       4.1.1.  Loosely Coupled . . . . . . . . . . . . . . . . . . .   9
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     6.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  11
   Appendix B.  RFC Editor Notes . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   In the parallel Network File System (pNFS), the metadata server
   returns layout type structures that describe where file data is
   located.  There are different layout types for different storage
   systems and methods of arranging data on storage devices.
   [flexfiles] defines the flexible file layout type used with file-
   based data servers that are accessed using the Network File System
   (NFS) protocols: NFSv3 [RFC1813], NFSv4.0 [RFC7530], NFSv4.1
   [RFC5661], and NFSv4.2 [RFC7862].

   The first version of the flexible file layout type had two issues
   which could not be addressed in [flexfiles] because of existing
   implementations.  The first issue was that under the tightly coupled
   model for a NFSv4 implementation, either a global stateid or an
   anonymous stateid needed to be used.  The second issue was that under
   the loosely coupled model, for a secure Remote Procedural Call (RPC)
   ([RFC5531]) implementation, each of the client, metadata server, and
   storage devices needed to implement an RPC-application-defined
   structured privilege assertion with RPCSEC_GSS version 3
   (RPCSEC_GSSv3) [RFC7861].  The second version of the flexible file
Show full document text