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.

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

YANG model update/upgrade procedure #287

Closed
rastislavs opened this issue Aug 17, 2016 · 4 comments
Closed

YANG model update/upgrade procedure #287

rastislavs opened this issue Aug 17, 2016 · 4 comments
Labels
is:enhancement Request for adding new feature or enahncing functionality.

Comments

@rastislavs
Copy link
Contributor

Implement the YANG model update/upgrade procedure: When there is a new version of a YANG model (with the same revision date or with a newer revision date), the datastore should allow to switch to the new model while preserving existing startup (or even running?) datastore data - if possible. If it is not possible, the incompatible data leaves should be either removed, or whole operation should be skipped.

For this we should implement a new operation of sysrepoctl, e.g. sysrepoctl --upgrade.

In the simplest case, it should do the equivalent of:

sysrepocfg --export
sysrepoctl --uninstall
sysrepoctl --install
sysrepocfg --import
@rastislavs rastislavs added the is:enhancement Request for adding new feature or enahncing functionality. label Aug 17, 2016
@rkrejci
Copy link
Contributor

rkrejci commented Jan 2, 2017

support for this (or very similar) functionality is also requested from libyang, see CESNET/libyang#231

@liuaifinch
Copy link

@rkrejci

Hi rkrejci,

Does this feature have been implemented?

@michalvasko
Copy link
Collaborator

Hi,
no, it has not yet been implemented.

Regards,
Michal

@michalvasko
Copy link
Collaborator

Latest sysrepo supports this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:enhancement Request for adding new feature or enahncing functionality.
Projects
None yet
Development

No branches or pull requests

4 participants