Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Restconf does not handle startup datastore according to the RFC #74

Closed
olofhagsand opened this issue Feb 22, 2019 · 1 comment
Closed

Restconf does not handle startup datastore according to the RFC #74

olofhagsand opened this issue Feb 22, 2019 · 1 comment
Labels
bug

Comments

@olofhagsand
Copy link
Member

RFC8040 Section 1.4 Co-existence with Netconf
If the NETCONF server supports :startup, the RESTCONF server MUST
automatically update the non-volatile startup configuration
datastore, after the "running" datastore has been altered as a
consequence of a RESTCONF edit operation.
thanks @mgsmith1000
olofhagsand added a commit that referenced this issue Apr 26, 2019
@olofhagsand
* Restconf with startup feature will now copy all edit changes to sta…
6bf2a74 
…rtup db (as it should according to RFC 8040)

  * See [Restconf does not handle startup datastore according to the RFC](#74)
* Netconf Startup feature is no longer hardcoded, you need to explicitly enable it (See RFC 6241, Section 8.7)
  * Enable in config file with: `<CLICON_FEATURE>ietf-netconf:startup</CLICON_FEATURE>`, or use `*:*`
@olofhagsand
Copy link
Member Author

Fixed. Note, you need to explicitly enable feature: ietf-netconf:startup. And it causes some worse performance since every edit operation results in a copy frm running db to startup.

@ihrasko ihrasko mentioned this issue Jun 9, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@olofhagsand