Look into Oxidized as a possible replacement

[mattpascoe]

Not that I dont love maintaining code and such but hey, if there is better maintained tool to leverage, great! The https://github.com/ytti/oxidized project looks to be pretty well done and seems to cover most of the things I care about.

Check into viability of using it as the configuration archive method and integrate ONA to it using its API.

There may be a few areas to tweak and or give PRs for to mesh up with my desires and how I use archives.

Things to consider:

• password management
• user management
• host lists based on ONA
• snmptrap based triggers
• other methods of triggering (touching a file)
• other methods of loading into the system.. direct file, post to endpoint etc
• git as a backend
• types
• 'hiding'/ deleting text from the config.. seems to be there, how is it done?
• is there an untouched version of the config that can be used for restore?
• other security implications... encryption, ssl, blah d blah

@ytti Cool stuff by the way, hopefully I find time to dig in.

[ytti]

Thanks. I've been slacking lately on issues in Oxidized, but hope to clear the backlog soon.

SNMPTrap based triggers would essentially be writing daemon which monitors for SNMPTrap then lauches HTTP GET. We have in /extras directory example how to do this for udp syslog or syslog file, should be fairly straightforward to do it for SNMPTrap also.
Added bonus for doing it triggered instead of periodic, that we we can extract configuration commit user and message, which we can then pass to git, so 'git blame' would show actual user who made the change.

[mattpascoe]

I hear ya on the backlog! :)

As an idea I would look at my trapscript method that I've been using (located in this repo under cfg_archive/bin/cfg_archive_cisco_trapscript).. The methodology is to use snmptrapd as the daemon (no need to rewrite what is already there). I configured mine to be aware of the various states of how Cisco does things. For example when you do a 'copy run start' operation that will trigger a refresh of the config, so will a reboot of the device. I'm sure this could be adapted to cover more than just Cisco.

My current version simply touches a file on the file system and that gets picked up later by another process. The trapscript could easily be updated to do the HTTP operations within oxidized.

I also liked the ability to use any other means to touch the file to invoke a config archive update. I would assume you have methods for that already (I've not yet looked!? :)

Well, I've hijacked your attention over here. I mainly wanted to get a note into my project to investigate yours as a possible replacement for what I'm doing, as I rarely find time to keep this one up to date. I've had lots of ideas that it seems you have implemented (like GIT backend) so I would love to dig into this more and offer ideas and help with what you are doing. My end goal for me would be to get rid of my archival method, use yours and integrate it directly into my OpenNetAdmin project.

Thanks again and keep up the good work!