-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Two new features for the napalm configuration management: commit_in and commit_at #48779
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
Two new features for the napalm configuration management: commit_in and commit_at #48779
Conversation
|
Hi @mirceaulinic - this is causing some related tests to fail. Can you take a look? https://jenkinsci.saltstack.com/job/pr-kitchen-ubuntu1604-py2/job/PR-48779/1/ |
11620cb to
9538445
Compare
rallytime
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, pending tests.
gtmanfred
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks awesome!
|
@mirceaulinic There are 2 tests failing with this change: https://jenkinsci.saltstack.com/job/pr-kitchen-ubuntu1604-py2/job/PR-48779/1/ |
9538445 to
74a0b9b
Compare
|
Hi @rallytime - I have corrected that error, please let me know if there's anything else. Thanks! |
|
Looks good now! Thanks @mirceaulinic! |
What does this PR do?
In the networking world, there are a very small number of platforms that allow you to commit a specific configuration change at a desired time. Although this is not particularly one of the best practices, turns out to be important sometimes (very rarely though). Nevertheless it is and will forever be optional.
With these changes, I am adding support for
commit_inandcommit_atto commit the config changes later. This simply leverages the abilities of the Salt scheduler, by adding a job to be executed once, at the time requested by the user. Therefore, this is available for any network platform managed through NAPALM, regardless if they do or don't support scheduled commit capabilities.For safety reasons, I am adding the
net.cancel_commitcounterpart execution function to discard a scheduled commit.Example: