Re: [netmod] Question on draft-wu-netmod-factory-default

Andy Bierman <andy@yumaworks.com> Tue, 26 March 2019 16:14 UTC

Return-Path: <andy@yumaworks.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 736531204EC for <netmod@ietfa.amsl.com>; Tue, 26 Mar 2019 09:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 ojolCdwNFNiC for <netmod@ietfa.amsl.com>; Tue, 26 Mar 2019 09:14:08 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1E5C12052F for <netmod@ietf.org>; Tue, 26 Mar 2019 09:14:07 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id l7so11653248ljg.6 for <netmod@ietf.org>; Tue, 26 Mar 2019 09:14:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=I1Rhpx5mjOTPR1UCqFmqDHJNE/Vesr5YybrWuPmc6GA=; b=IcCqk63/xas/lB7KX5WPdRGDKuDT5fH0ucTGCn7QLpgqCvyz7VQ4q1bQJbtX0b8QgS P8rDjH0YcHaylOh7m+EQ0Q/z5Fy9xlMXl+eceAtm8jMR0cFR0goL7akfKNDHXzpGFdQ0 pFh+gX0m1YrTLhzIyBTSCjyTTgLS3SWh9vHjNIo3P6yTZpMLY+cfwUCWfiRM05YsEyu4 +ojUZGPkufE9/GEQpafoFRD9yZ23FO0vVur7OhHxrCfUPhJlw7fjpAbHgOYpmFMwWGD7 XcPNhqb/AknRjPfp7iptJes6ZBV4Z3UVAlnLn54yQ8HeEXkcn9jD5RzRiN3S1srdvTPo OKRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=I1Rhpx5mjOTPR1UCqFmqDHJNE/Vesr5YybrWuPmc6GA=; b=jhWYjO95dq6RPTgYbKyYu2KmBwnOX30bZQXszjwxvOGUmEMs0cPGvKMtNvAIWw1pt+ a1zTc4BIN7JuKBCv6SlaxMvwSxCci42c+5BIvzj0mwItKHsusfAT+GGsdgxheu+N1/V7 r1Y8TmxcOWiA8AngNNTkjLFxfy9qBp6rYxsECEasaPexst5rNFKBDVinOsNbM9XL4wq2 KzCIxj+ZU8m3mBslZhp8QhX/DloBFPBhb/hbSIGsE2GfnQBtvoMcsG3d0bCK1Yye3f68 ClfclhViWO9PdykxShQGtLlpkD7BBQVvTGoblddLlz6kC0f9IPvgi7a+zJAkBp/qKpQG D7eQ==
X-Gm-Message-State: APjAAAXFUzX/Zm1AbIhuaDjozAx/2xUedhpIpdgDg+M7ZPbIHvEcNnRc 09K9H/hxD4qSn5Wo4cS0plnsZwxcgpteOz0oHmfa1w==
X-Google-Smtp-Source: APXvYqwoRGTnIWgao5TmJnb/OP+pq7W/ZIRzjN4FfdOmEUuFGQ+aBXeXk9PmYG20stxLG8a11ozibwJmYyUf//Kl5/M=
X-Received: by 2002:a2e:12c4:: with SMTP id 65mr17070743ljs.141.1553616845943; Tue, 26 Mar 2019 09:14:05 -0700 (PDT)
MIME-Version: 1.0
References: <B8F9A780D330094D99AF023C5877DABAA487E4BE@nkgeml513-mbx.china.huawei.com> <20190326055118.nhm27b3gsivthi37@anna.jacobs.jacobs-university.de>
In-Reply-To: <20190326055118.nhm27b3gsivthi37@anna.jacobs.jacobs-university.de>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 26 Mar 2019 09:13:54 -0700
Message-ID: <CABCOCHSG7i+meArUHGCGxiOKs_vjysxqnKT7q7Q=jK0GCkTDaw@mail.gmail.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, Qin Wu <bill.wu@huawei.com>, Joe Clarke <jclarke@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003849040585019ce0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/ryXeDApQeVLnWUDTEET_qFeR02w>
Subject: Re: [netmod] Question on draft-wu-netmod-factory-default
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 26 Mar 2019 16:14:11 -0000

On Mon, Mar 25, 2019 at 10:51 PM Juergen Schoenwaelder <
j.schoenwaelder@jacobs-university.de> wrote:

> Qin,
>
> the idea should be to make things simpler, not more complex. Perhaps
> it is not necessary to expose N options to reset a device. Perhaps a
> simple "factory-reset" RPC which resets all relevant datastores in an
> implementation specific manner is sufficient. Why expose more details
> to the management client?
>
>
+1

Some of us have not consumed the NMDA kool-aid ;-)
We still manage servers, not datastores.
You can reset the server so it comes back with the factory-default config.
I have never heard of resetting specific datastores to factory-default.

>From the client POV, why would I even want to know the
implementation-specific
details and have to provide reset contents for each datastore and the order
to reset them?
No customers are asking for this!

/js
>

Andy


>
> On Tue, Mar 26, 2019 at 05:25:45AM +0000, Qin Wu wrote:
> > Joe,
> >
> >
> > -----邮件原件-----
> > 发件人: netmod [mailto:netmod-bounces@ietf.org] 代表 Joe Clarke
> > 发送时间: 2019年3月25日 22:14
> > 收件人: netmod@ietf.org
> > 主题: [netmod] Question on draft-wu-netmod-factory-default
> >
> > I support the need for being able to reset a DS to its factory default.
> > However, I have a question on the current design of the model and the
> "factory-default" DS.
> >
> > It seems to me that this is a single DS that might have been intended to
> reset running or startup.  However, what if I have different DSes that each
> have unique factory default data?
> >
> > [Qin]:We start with a simple case, you case could be addressed by
> invoking multiple rpc with each rpc to allow reset a set of datastores.
> >  If I choose to extend factory-default with a new identity of my other
> DS, how can I indicate that the target DS will be reset to _that_ DS?  Does
> that make sense?
> >
> > [Qin]: In simple case, target DS will only be reset by a single factory
> datastore. If there is a new factory datastore could be derived from that
> DS, I think target DS should be changed to reset that new factory datastore.
> >
> > Or if I do a <get-data> on a factory-default DS, how do I know what
> other DSes does this DS pertain?  Perhaps the server will use this to reset
> a given DS, but how would a user know that (other than perhaps naming of
> the factory-default DS)?
> >
> > Maybe the module needs a mapping to let the client know what DS will be
> used to reset what other DS?
> > [Qin]: So your point is should we allow multiple source, multiple target
> in the same RPC, will think it over. Thanks.
> > Joe
> >
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
> > _______________________________________________
> > netmod mailing list
> > netmod@ietf.org
> > https://www.ietf.org/mailman/listinfo/netmod
>
> --
> 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
>