IETF Logo Mail Archive

Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 02 July 2018 12:22 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DCB130F1D for <netconf@ietfa.amsl.com>; Mon, 2 Jul 2018 05:22:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 v7cV9nt_tU-w for <netconf@ietfa.amsl.com>; Mon, 2 Jul 2018 05:22:57 -0700 (PDT)
Received: from anna.localdomain (anna.eecs.jacobs-university.de [IPv6:2001:638:709:5::7]) by ietfa.amsl.com (Postfix) with ESMTP id 1A42D130F76 for <netconf@ietf.org>; Mon, 2 Jul 2018 05:22:57 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id 3D6C422BF24C; Mon, 2 Jul 2018 14:22:54 +0200 (CEST)
Date: Mon, 02 Jul 2018 14:22:54 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Qin Wu <bill.wu@huawei.com>
Cc: Kent Watsen <kwatsen@juniper.net>, Ladislav Lhotka <lhotka@nic.cz>, "netconf@ietf.org" <netconf@ietf.org>
Message-ID: <20180702122254.hrws4cneranwwm3w@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Qin Wu <bill.wu@huawei.com>, Kent Watsen <kwatsen@juniper.net>, Ladislav Lhotka <lhotka@nic.cz>, "netconf@ietf.org" <netconf@ietf.org>
References: <B8F9A780D330094D99AF023C5877DABA9AEB9E31@nkgeml513-mbx.china.huawei.com> <87a7rfjdcx.fsf@nic.cz> <B8F9A780D330094D99AF023C5877DABA9AEBAF17@nkgeml513-mbx.china.huawei.com> <2A66E046-CE29-42B5-A60C-1313357378DE@juniper.net> <B8F9A780D330094D99AF023C5877DABA9AEBD689@nkgeml513-mbx.china.huawei.com> <B8F9A780D330094D99AF023C5877DABA9AEBD700@nkgeml513-mbx.china.huawei.com> <20180630090808.5g232ydinkbsnddg@anna.jacobs.jacobs-university.de> <B8F9A780D330094D99AF023C5877DABA9AEBED1A@nkgeml513-mbx.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9AEBED1A@nkgeml513-mbx.china.huawei.com>
User-Agent: NeoMutt/20180622
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/c6oY24dysFMjTBTg6vCaywTp1Os>
Subject: Re: [Netconf] I-D Action: draft-wu-netconf-restconf-factory-restore-00.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Network Configuration WG mailing list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Jul 2018 12:23:09 -0000

On Mon, Jul 02, 2018 at 12:16:27PM +0000, Qin Wu wrote:
> Good point and suggestion. Here is my thought:
> In case :startup capability is supported, the factory datastore can be copied into <startup>, restart is not needed since we have loaded content of factory datastore into startup. Startup will be updated with running each time the running is altered. In case of system fatal error, we will consider copy factgory datatore into <startup> again for restore.

I doubt this will work. If you copy <factory> to startup> and
subsequently <running> to <startup>, there is a copy of <running> left
in <startup>, i.e., the copy of <factory> to startup> had no effect.

> In case the restart is needed or device power on is needed, the factory datastore as source may not be set, instead, URL is set as source, the content of source identified by URL can be loaded into target datastore during restart or device repower on. In this case, the proposed factory datastore
> and new operation can work together with zero touch bootstrapping procedure proposed in draft-ietf-netconf-zerotouch.

URLs are an optional capability so far and I do not know what "URL is
set as source" means to me. What is target datastore here? I am not
sure how data flows.

> In case :writable-running capability is supported, the factory datastore can be directly copied into <running>, in case of multiple conceptual flows, we can consider to copy one factory datastore into multiple <running> targets.
> In case :candidate capability is supported, the factory datastore can be first copied into <candiate> and then the <candidate> is committed into <running>, in this case, startup is not touched.

What are multiple <running> targets? What are "multiple conceptual flows"?
I am confused.

/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/>

v2.23.0 | Report a Bug | By Email