NFSv4 migration: Implementation Experience and Specification Issues
draft-ietf-nfsv4-migration-issues-11

Document Type Active Internet-Draft (nfsv4 WG)
Last updated 2017-02-08
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state AD is watching
Consensus Boilerplate Unknown
Telechat date
Responsible AD Spencer Dawkins
Send notices to (None)
NFSv4                                                     D. Noveck, Ed.
Internet-Draft
Intended status: Informational                                 P. Shivam
Expires: August 12, 2017                                        C. Lever
                                                                B. Baker
                                                                  ORACLE
                                                        February 8, 2017

  NFSv4 migration: Implementation Experience and Specification Issues
                  draft-ietf-nfsv4-migration-issues-11

Abstract

   The migration feature of NFSv4 provides for moving responsibility for
   a single filesystem from one server to another, without disruption to
   clients.  Implementation experience has shown problems in
   specification for this feature in RFC7530.  This document explains
   the choices made to address these issues by updating the NFSv4.0
   specification in RFC7931 and those to be made with regard to the
   NFSv4.1 specification, in order to properly address migration.

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 August 12, 2017.

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

Noveck, et al.           Expires August 12, 2017                [Page 1]
Internet-Draft              nfsv4-migr-issues              February 2017

   carefully, as they describe your rights and restrictions with respect
   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
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  NFSv4.0 Implementation Experience . . . . . . . . . . . . . .   3
     3.1.  Implementation Issues . . . . . . . . . . . . . . . . . .   3
       3.1.1.  Failure to Free Migrated State on Client Reboot . . .   4
       3.1.2.  Server Reboots Resulting in a Confused Lease
               Situation . . . . . . . . . . . . . . . . . . . . . .   4
       3.1.3.  Client Complexity Issues  . . . . . . . . . . . . . .   5
     3.2.  Sources of Protocol Difficulties  . . . . . . . . . . . .   7
       3.2.1.  Issues with nfs_client_id4 Generation and Use . . . .   7
       3.2.2.  Issues with Lease Proliferation . . . . . . . . . . .   9
   4.  Resolution of NFSv4.0 Protocol Difficulties . . . . . . . . .   9
     4.1.  Changes Regarding nfs_client_id4 Client-string  . . . . .   9
     4.2.  Changes Regarding Merged (vs. Synchronized) Leases  . . .  10
     4.3.  Other Changes to Migration-state Sections . . . . . . . .  11
       4.3.1.  Changes Regarding Client ID Migration . . . . . . . .  12
       4.3.2.  Changes Regarding Callback Re-establishment . . . . .  12
       4.3.3.  NFS4ERR_LEASE_MOVED Rework  . . . . . . . . . . . . .  13
     4.4.  Changes to Other Sections . . . . . . . . . . . . . . . .  13
       4.4.1.  Need for Additional Changes . . . . . . . . . . . . .  13
       4.4.2.  Callback Update . . . . . . . . . . . . . . . . . . .  14
       4.4.3.  clientid4 Handling  . . . . . . . . . . . . . . . . .  14
       4.4.4.  Handling of NFS4ERR_CLID_INUSE  . . . . . . . . . . .  16
   5.  Issues for NFSv4.1  . . . . . . . . . . . . . . . . . . . . .  17
     5.1.  Addressing state merger in NFSv4.1  . . . . . . . . . . .  17
     5.2.  Addressing pNFS relationship with migration . . . . . . .  18
     5.3.  Addressing server owner changes in NFSv4.1  . . . . . . .  18
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  19
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  20
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  20
Show full document text