IETF Logo Mail Archive

Re: [nfsv4] Fwd: New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt

"tigran.mkrtchyan@desy.de" <tigran.mkrtchyan@desy.de> Sun, 19 February 2023 23:53 UTC

Return-Path: <tigran.mkrtchyan@desy.de>
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 84C1CC14CF17 for <nfsv4@ietfa.amsl.com>; Sun, 19 Feb 2023 15:53:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.095
X-Spam-Level:
X-Spam-Status: No, score=-6.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=desy.de
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DFZLoybqtuWv for <nfsv4@ietfa.amsl.com>; Sun, 19 Feb 2023 15:53:39 -0800 (PST)
Received: from smtp-o-3.desy.de (smtp-o-3.desy.de [IPv6:2001:638:700:1038::1:9c]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57149C14EB17 for <nfsv4@ietf.org>; Sun, 19 Feb 2023 15:53:38 -0800 (PST)
Received: from smtp-buf-3.desy.de (smtp-buf-3.desy.de [IPv6:2001:638:700:1038::1:a6]) by smtp-o-3.desy.de (Postfix) with ESMTP id 569196082A for <nfsv4@ietf.org>; Mon, 20 Feb 2023 00:53:34 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp-o-3.desy.de 569196082A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=desy.de; s=default; t=1676850814; bh=dadQdWm1DiAlxPMYeE6TfVKpQKIM5SoAYRo8hv/11SA=; h=Date:Subject:References:From:To:In-Reply-To:From; b=M90iq21WugBtaPjFPyj8KN+eH82wOSOSy97wGPuBHw2fG1myWEIFajseGKG0iv5P/ 0+ytvGNsFNw9F48ZrHfZsbgFhYmXIjHym1teCleW2Vrd/HHLRjVR0TDTVwez3E0zJe oYjraVr3mCIC+yPToZnzVT/AXqHTbpznA/7MG9jA=
Received: from smtp-m-3.desy.de (smtp-m-3.desy.de [131.169.56.131]) by smtp-buf-3.desy.de (Postfix) with ESMTP id 46EC7A00B3; Mon, 20 Feb 2023 00:53:34 +0100 (CET)
Received: from smtp-intra-3.desy.de (smtp-intra-3.desy.de [IPv6:2001:638:700:1038::1:45]) by smtp-m-3.desy.de (Postfix) with ESMTP id 3E8606008C; Mon, 20 Feb 2023 00:53:34 +0100 (CET)
Received: from z-mbx-2.desy.de (z-mbx-2.desy.de [131.169.55.140]) by smtp-intra-3.desy.de (Postfix) with ESMTP id 39A788003A; Mon, 20 Feb 2023 00:53:34 +0100 (CET)
Date: Mon, 20 Feb 2023 00:53:34 +0100
Importance: Normal
Message-ID: <1049929229.37471841.1676850814102.JavaMail.zimbra@z-mbx-2>
References: <167650188094.35471.12073867230641500375@ietfa.amsl.com> <8A2593C7-1A1F-455D-B2CC-9084EC9EA1B2@hammerspace.com>
From: "tigran.mkrtchyan@desy.de" <tigran.mkrtchyan@desy.de>
To: Thomas Haynes <loghyr@hammerspace.com>, NFSv4 <nfsv4@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_37471837_404337414.1676850814087"
X-ZxMobile-Command: SmartReply
X-ZxMobile-Version: 3.14.0
X-Mailer: Zimbra 9.0.0_GA_4485
In-Reply-To: <8A2593C7-1A1F-455D-B2CC-9084EC9EA1B2@hammerspace.com>
Thread-Topic: New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt
Thread-Index: AQHZQZD2qcNUINm21k+BsUawoiPkFyodkOmY
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/mC1ooeAVSiRYDuM2KBmzQs5QJHc>
Subject: Re: [nfsv4] Fwd: New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 19 Feb 2023 23:53:43 -0000

Hi Tom, 

I like the idea. It looks like that the draft is limited only to NFSv3 based flexfiles layouts. Neither nfsv41_files nor flexfiles layouts allow GETATTR requests to be sent to data servers. Thus only in responses to READ or WRITE over v3 clients will get the wcc information. However the draft position itself to be more generic. 


Do I miss something? 


Best regards, 

- Tigran


-------- Original message --------
From: Thomas Haynes <loghyr@hammerspace.com>
Date: Thu, Feb 16, 2023, 00:02
To: NFSv4 <nfsv4@ietf.org>
Subject: [nfsv4] Fwd: New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt

Hi,

As part of the review of delstid, it was suggested that I pull this part out of that document and create a new draft.

This then is that result.

I ask the working group to adopt this draft was a WG one. This is work that had previously been accepted as part of the delstid one.

Thanks,
Tom

Begin forwarded message:

Subject: New Version Notification for draft-haynes-nfsv4-layoutwcc-00.txt
Date: February 15, 2023 at 2:58:00 PM PST
To: "Thomas Haynes" <loghyr@hammerspace.com>, "Trond Myklebust" <trondmy@hammerspace.com>


A new version of I-D, draft-haynes-nfsv4-layoutwcc-00.txt
has been successfully submitted by Thomas Haynes and posted to the
IETF repository.

Name: draft-haynes-nfsv4-layoutwcc
Revision: 00
Title: Add LAYOUT_WCC to NFSv4.2
Document date: 2023-02-15
Group: Individual Submission
Pages: 9
URL:            https://www.ietf.org/archive/id/draft-haynes-nfsv4-layoutwcc-00.txt
Status:         https://datatracker.ietf.org/doc/draft-haynes-nfsv4-layoutwcc/
Html:           https://www.ietf.org/archive/id/draft-haynes-nfsv4-layoutwcc-00.html
Htmlized:       https://datatracker.ietf.org/doc/html/draft-haynes-nfsv4-layoutwcc


Abstract:
  The Parallel Network File System (pNFS) allows for a file's metadata
  (MDS) and data (DS) to be on different servers.  It does not provide
  a mechanism for the data server to update the metadata server of
  changes to the data part of the file.  The client has knowledge of
  such updates, but lacks the ability to update the metadata server.
  This document presents several refinements to both RFC8881 and
  RFC8434 to allow the client to update the metadata server to changes
  on the data server.




The IETF Secretariat



v2.23.0 | Report a Bug | By Email