Re: [netmod] New Version Notification for draft-wu-netmod-factory-default-01.txt

[Rohit R Ranade <[e-mail]>]

6.       Since we have scenario of copy to multiple targets, whether we can add a leaf called the error-option with possible values of “stop-on-error/continue-on-error/rollback-on-error”   ?

   [Qin]: Same as above. Should these error-option values be part of rpc-reply or part of operation request? By reading edit-config,it is also not clear to me whether

       Error-option should be part of edit-config operation that is sent in rpc-request message.


[Rohit] <error-option> is an input to the edit-config rpc-request.   So I suggested to have a similar approach. But this multi-datastore copy will be tricky because if we give two targets say <running> / <startup> and if after copy to <running>, copy to <startup> fails,  then how to handle this ?  Revert <running> config ?

I suggest to restrict the copy of factory datastore to a single target datastore for now.
With Regards,
Rohit R


From: Qin Wu
Sent: 22 October 2018 12:25
To: Rohit R Ranade <[e-mail]>; Balázs Lengyel <[e-mail]>; [e-mail]
Subject: RE: New Version Notification for draft-wu-netmod-factory-default-01.txt

Thanks Rohit, see reply inline below.

发件人: netmod [mailto:[e-mail]] 代表 Rohit R Ranade
发送时间: 2018年10月22日 12:59
收件人: Balázs Lengyel; [e-mail]<mailto:[e-mail]>
主题: Re: [netmod] New Version Notification for draft-wu-netmod-factory-default-01.txt

Some suggestions,



1.       In YANG module, the identity has name as “factory-default”, but many places  the name "factory-default-running" is used. I suggest we used “factory-default”in all places.

[Qin]: works for me.

2.       This YANG module is importing ietf-netconf module. I suggest that this import should be removed as this module should not have dependencies on NETCONF.

[Qin]: Good catch, thanks.

3.       The description of this YANG module, still has the reference to <copy-config>.  Whether this can be removed ?

[Qin]: Good catch, thanks.

4.       The description of the indentity “factory-default”, suggest to describe the identity rather than tell “how” it can be used.

[Qin]: Okay.

5.       Whether we can also add the statement that if the “target-datastore”, have been locked , then the reset-datastore will fail with the <error-tag> value as “in-use” ?

[Qin]: I think we can reuse <error-tag> in the rpc-error element, similar to example in section 7.5 of RFC6241.

6.       Since we have scenario of copy to multiple targets, whether we can add a leaf called the error-option with possible values of “stop-on-error/continue-on-error/rollback-on-error”   ?

   [Qin]: Same as above. Should these error-option values be part of rpc-reply or part of operation request? By reading edit-config,it is also not clear to me whether

       Error-option should be part of edit-config operation that is sent in rpc-request message.

With Regards,

Rohit R

From: netmod [mailto:[e-mail]] On Behalf Of Balázs Lengyel
Sent: 19 October 2018 18:17
To: [e-mail]<mailto:[e-mail]>
Subject: [netmod] Fwd: New Version Notification for draft-wu-netmod-factory-default-01.txt


Hello,

A new version of I-D, draft-wu-netmod-factory-default-01.txt has been uploaded. Changes include:
Removed impacts to <copy-config> as the reset-datastore  RPC can anyway do the same thing.
Explained the difference between startup and factory-default datastores
Small corrections.

regards Balazs

-------- Forwarded Message --------
Subject:

New Version Notification for draft-wu-netmod-factory-default-01.txt

Date:

Fri, 19 Oct 2018 05:30:05 -0700

From:

[e-mail]<mailto:[e-mail]>

To:

Ye Niu <[e-mail]><mailto:[e-mail]>, Qin Wu <[e-mail]><mailto:[e-mail]>, Balazs Lengyel <[e-mail]><mailto:[e-mail]>




A new version of I-D, draft-wu-netmod-factory-default-01.txt
has been successfully submitted by Balazs Lengyel and posted to the
IETF repository.

Name: draft-wu-netmod-factory-default
Revision: 01
Title: Factory default Setting
Document date: 2018-10-19
Group: Individual Submission
Pages: 10
URL: https://www.ietf.org/internet-drafts/draft-wu-netmod-factory-default-01.txt
Status: https://datatracker.ietf.org/doc/draft-wu-netmod-factory-default/
Htmlized: https://tools.ietf.org/html/draft-wu-netmod-factory-default-01
Htmlized: https://datatracker.ietf.org/doc/html/draft-wu-netmod-factory-default
Diff: https://www.ietf.org/rfcdiff?url2=draft-wu-netmod-factory-default-01

Abstract:
This document defines a method to reset a YANG datastore to its
factory-default content. The reset operation may be used e.g. during
initial zero-touch configuration or when the existing configuration
has major errors, so re-starting the configuration process from
scratch is the best option.

A new reset-datastore RPC is defined. Several methods of documenting
the factory-default content are specified.

Optionally a new "factory-default-running" read-only datastore is
defined, that contains the data that will be copied over to the
running datastore at reset.



Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--

Balazs Lengyel                       Ericsson Hungary Ltd.

Senior Specialist

Mobile: [phone]              email: [e-mail]<mailto:[e-mail]>