Automatic push to git

[afourmy]

Let the user configure GIT parameters for automatically pushing to gitlab/github the results of the script. => compare scripts results like configs, pings, traceroutes directly on git.

[ryanmerolle]

For configs, would you think about automated snapshots pulled from devices and pushed to git based on: schedul

• e in calendar
• syslog "configured by user x messages" (after NAPALM logs integration and possibly committed on behalf user in syslog message)
• as a part of automation workflow (committed by user kicking off workflow)

i.e. rancid/oxidized for netbox and focused on automation.

Did not want to hit you with a ton of features, just adding to the foundational feature & get your view.

[afourmy]

• Based on schedule in calendar: once the feature is completed, you will be able to push the results of a script to git, so the config in particular via the get_config NAPALM getter. Actually, I already implemented it in a standalone project called "napalm-git": https://github.com/afourmy/napalm-git . All I have left to do is to integrate this in eNMS now.
• Based on syslog configuration messages: yes, that can be done. There could be an option so that, every time the "configuration committed" message is received via syslog, eNMS uses NAPALM get_config to retrieve the new configuration and push it to git. Pushing the config on behalf of the user is also possible, but we cannot reasonnably expect to have an exact mapping between the git credentials and network credentials. The solution is that in eNMS, there would be only one git account with the credentials, and eNMS will use the --name git option upon committing with the name that's in the syslog message (if there is one).
• Point 3: I don't understand the difference with the first point. What exactly do you call an "automation workflow" ?

Anyway these points are all very important, so I will implement them as part of the first version of the logging system and they will be in the next release. Thanks !

[ryanmerolle]

• Having an audit trail would be helpful. Even adding the userid as a comment for the push would be good enough for version 1 of the feature.
• A handy feature I have seen implemented is setting a timer after logging change made per user in order to group other config changes together in one commit. In an ideal scenario I have seen:
  • group all config changes implemented by a user after some timer initiated by first config change
  • prompt user (chatops & web prompt) to extend timer, manually add devices to commit (to address syslog connectivity or log parsing limitations for said device), add a comment, force commit
• I think I was thinking out loud about the workflow. Creating some function to allow for x automation tool to make a API call to eNMS to pull configs on devices post some push might be nice depending on the tool. IE it would enhance the automation workflow.

[afourmy]

Done: Docs:

• https://enms.readthedocs.io/en/latest/services/service_system.html#gitlab-export
• https://enms.readthedocs.io/en/latest/services/default_services.html