IETF Logo Mail Archive

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

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Sat, 30 June 2018 09:08 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 5130D1292AD for <netconf@ietfa.amsl.com>; Sat, 30 Jun 2018 02:08:13 -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 l0e41eBpqfZA for <netconf@ietfa.amsl.com>; Sat, 30 Jun 2018 02:08:11 -0700 (PDT)
Received: from anna.localdomain (firewallix.jacobs-university.de [212.201.44.247]) by ietfa.amsl.com (Postfix) with ESMTP id 1682A124BE5 for <netconf@ietf.org>; Sat, 30 Jun 2018 02:08:11 -0700 (PDT)
Received: by anna.localdomain (Postfix, from userid 501) id BA3EA22BB41B; Sat, 30 Jun 2018 11:08:08 +0200 (CEST)
Date: Sat, 30 Jun 2018 11:08:08 +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: <20180630090808.5g232ydinkbsnddg@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9AEBD700@nkgeml513-mbx.china.huawei.com>
User-Agent: NeoMutt/20180622
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/phIM2cETTFHKVkXDHWg-_oUxw5s>
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: Sat, 30 Jun 2018 09:08:13 -0000

On Sat, Jun 30, 2018 at 07:05:23AM +0000, Qin Wu wrote:

> One point to add, we hope to support factory restore without
> reboot/restart and support factory restore with reboot, two cases,
> this make factory restore can be supported in the whole lifetime of
> the device.

So is the <factory> datastore conceptually copied into <startup> and
then you restart or is the the <factory> datastore conceptually copied
into <running>? Yes, <startup> is not mandatory to have, so there may
be multiple conceptual flows that are possible. I think it will be
helpful to be clear about the conceptual dataflow between the
datastores - and once this is clear, it should be relatively easy to
define the operations that are necessary.

/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