IETF Logo Mail Archive

Re: [netmod] Differentiating the types of Mount

"Alexander Clemm (alex)" <alex@cisco.com> Wed, 16 March 2016 15:34 UTC

Return-Path: <alex@cisco.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6015012D9E9 for <netmod@ietfa.amsl.com>; Wed, 16 Mar 2016 08:34:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 KXvujOlXz7Ns for <netmod@ietfa.amsl.com>; Wed, 16 Mar 2016 08:34:10 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40B9112D78A for <netmod@ietf.org>; Wed, 16 Mar 2016 08:33:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=928; q=dns/txt; s=iport; t=1458142394; x=1459351994; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ZRAT/60il/+Ur/9143TZrFvdCDxwstXEKtAHXBjFAqg=; b=e875+xVcnenHY6ns8vy2kIYnY8zpu66BUNnMaMJ72aGdvM8MBVsvHDR5 TxQTtwKOl6cPo5a/xtF38Il1N3wcZsm2EMAmcvFYu/cVdGXrq0MXy09yW nj5PwAyQtHeA9xP95U7JtMdpL/0840PJqvxEfurrrk1zS8s/O2avD/w04 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D5AQCUe+lW/4oNJK1eg0aBR7l9AQ2Bb4YNAoE9OBQBAQEBAQEBZCeEQQEBAQMBOj8QAgEINhAyJQEBBAENDYgXCL9pAQEBAQEBAQEBAQEBAQEBAQEBAQEBFYpihCSEUgEEl1EBjXmBbIdvhTGOfgEeAQFCg2WKT34BAQE
X-IronPort-AV: E=Sophos;i="5.24,345,1454976000"; d="scan'208";a="250190541"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 16 Mar 2016 15:33:13 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u2GFXCDQ024286 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 16 Mar 2016 15:33:12 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 16 Mar 2016 11:33:11 -0400
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1104.009; Wed, 16 Mar 2016 11:33:12 -0400
From: "Alexander Clemm (alex)" <alex@cisco.com>
To: "Eric Voit (evoit)" <evoit@cisco.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Thread-Topic: [netmod] Differentiating the types of Mount
Thread-Index: AdF/OD2NJ3Cq4cCSQLyujReGzdHIoQAX41GAAAGL/6AAAV8hMA==
Date: Wed, 16 Mar 2016 15:33:11 +0000
Message-ID: <3db0d2e918eb41cfab310c24aba9f619@XCH-RTP-001.cisco.com>
References: <84d0c3c5331c4b5e9d0883f890a87a40@XCH-RTP-013.cisco.com> <20160316112329.GB39598@elstar.local> <21332d7a3dfd41009fb5023ca94baa94@XCH-RTP-013.cisco.com>
In-Reply-To: <21332d7a3dfd41009fb5023ca94baa94@XCH-RTP-013.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.92.187]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/netmod/9h92VzmVEFdFHasNJc_k03R-p3c>
Cc: "netmod@ietf.org" <netmod@ietf.org>, "Martin Bjorklund (mbjorklu)" <mbjorklu@cisco.com>
Subject: Re: [netmod] Differentiating the types of Mount
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2016 15:34:11 -0000

Hi,

I have one addition on top of Eric's response

--- Alex

> 
> Is your alias mount simply a special case of a peer mount where the 
> peer is local? Or is there more to it?

>From a syntax standpoint, peer mount is more general.  But underneath, things get more complicated.

For example, many of the initial concerns about peer mount were on the implications of synchronizing objects across distributed systems.  (I.e., Eventual consistency is not appropriate when attempting to manage some type of objects.)  Alias mount shouldn't have this issue.

<ALEX> So, yes, alias mount is a special and simple case.  Perhaps the most relevant aspect to characterize this is that the authoritative owner in alias mount is the same Netconf server, whereas in peer mount authoritative owners will be different.  For this reason, peer mount will be better suited for read-only views.  </ALEX>

v2.23.0 | Report a Bug | By Email