On Wed, Feb 17, 2010 at 10:42:18AM -0500, Phil Shafer wrote:
> That said, we could make [transfer-on-commit] run a command, like:
>
> [edit system archival configuration]
> transfer-on-commit;
> archive-sites {
> scp://m...@my-server/whatever;
> }
> archive-command "ssh %A incoming-config-file --host %H --date %D --file %F";
What happens to this if you commit a change that breaks management
access or causes the control plane to go insane due to idiotic config,
bug, or whatever?
If the router doesn't retry those uploads, the above solution fails to
record precisely the change that you're most interested in! That's
why I want it to commit to a local database first - so it can be
replayed later to a central repo exactly as happened.
What VC system is used is immaterial - I mentioned git because if I
could install software on my router, there's easy and obvious ways to
do implement the idea.
--
Ross Vandegrift
r...@kallisti.us
"If the fight gets hot, the songs get hotter. If the going gets tough,
the songs get tougher."
--Woody Guthrie
signature.asc
Description: Digital signature
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
