Re: [netmod] schema-mount pre09 branch

Ladislav Lhotka <lhotka@nic.cz> Wed, 07 February 2018 10:29 UTC

Return-Path: <lhotka@nic.cz>
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 7444B120727 for <netmod@ietfa.amsl.com>; Wed, 7 Feb 2018 02:29:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.01
X-Spam-Level:
X-Spam-Status: No, score=-7.01 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, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
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 FP3_N_niSs6Z for <netmod@ietfa.amsl.com>; Wed, 7 Feb 2018 02:29:23 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [IPv6:2001:1488:800:400::400]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9774A126C19 for <netmod@ietf.org>; Wed, 7 Feb 2018 02:29:23 -0800 (PST)
Received: from birdie (unknown [IPv6:2001:1488:fffe:6:9001:c4ff:fe87:6c8]) by mail.nic.cz (Postfix) with ESMTPSA id F3371620CF for <netmod@ietf.org>; Wed, 7 Feb 2018 11:29:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1517999362; bh=47rzlMnzSCQW7omCrMe+ggpunIvVd3mL3GuKTNToIls=; h=From:To:Date; b=RAaw2SahMbUfUbhgmpYkveTKjT+I+yElFLnITjyrWAXulWsfCcKMyMhgxF7W93fwU F+fKT+6RhM/tfHPWv5bJjcVRSUjzM65Q2mG2XJaAFqkQ356HHFOC/mhY0reB8NJZ09 Kk+t+yy6gr080DfN11BV4owXg9Hu7cS0at8wWREs=
Message-ID: <1517999361.22328.33.camel@nic.cz>
From: Ladislav Lhotka <lhotka@nic.cz>
To: netmod@ietf.org
Date: Wed, 07 Feb 2018 11:29:21 +0100
In-Reply-To: <20180207.111441.1066018064701748797.mbj@tail-f.com>
References: <20180206141655.6iast3lbhubk6rk5@elstar.local> <3f3f9984-0797-1ded-ded4-17543382f628@cisco.com> <20180207094845.ift6vhoomsp4d7kk@elstar.local> <20180207.111441.1066018064701748797.mbj@tail-f.com>
Organization: CZ.NIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.26.5
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/f7a0h43tdVhC2NW7TpPfeW4xUB8>
Subject: Re: [netmod] schema-mount pre09 branch
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
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, 07 Feb 2018 10:29:27 -0000

On Wed, 2018-02-07 at 11:14 +0100, Martin Bjorklund wrote:
> Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> wrote:
> > On Tue, Feb 06, 2018 at 03:25:52PM +0000, Robert Wilton wrote:
> > > 
> > > I think that the term "external" could also be confusing, since I think
> > > that
> > > sort of implies peer mount like semantics.
> > 
> > The "inline" mount concept seems to subsume peer mounts. From the
> > model perspective, is there a difference whether the mounted data is
> > local or remote (and what does local/remove mean for a VM)?
> >  
> > > I would suggest the term "dynamic" instead of "inline " but that could
> > > easily be confused with dynamic datastores.
> > 
> > Yes, I think this is not a good word either.
> > 
> > > Perhaps rather than "inline" another choice could be "discoverable", i.e.
> > > the schema is not known, and is dynamically discoverable inline at the
> > > mount
> > > point.
> > > Equally, rather than "use-schema", perhaps a better choice would be
> > > "known",
> > > i.e. the schema is already known, and made available as part of YANG
> > > library.
> > 
> > Perhaps integrated schema vs. mounted schema.
> 
> I like the term "integrated" better than "use-schema".  But both cases
> are mounted, so we need another term than "mounted" for "inline".
> "segregated" doesn't sound quite right ;-)

I would prefer to use the term "mount" only for the inline case and find
something else for the use-schema case. The term "mount" evokes that some
*instance* data being added, which is what happens in the "inline" case but not
for "use-schema".

Lada

> 
> 
> /martin
> 
> > 
> > > Whether it would be right to change these at this time, I've no idea ...
> > 
> > Yep.
> > 
> > /js
> > 
> > -- 
> > Juergen Schoenwaelder           Jacobs University Bremen gGmbH
> > Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
> > Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>
> > 
> 
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod
-- 
Ladislav Lhotka
Head, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67