On Wed, Aug 3, 2011 at 11:38 AM, Aleksey Tsalolikhin < [email protected]> wrote:
> RANCID might help too. Brent has a great summary of it at > http://www.netomata.com/blog/brent_chapman/2010/03/26/120 > Thanks for the compliment! One of the things that I dislike about RANCID is that it's very crufty code. Andrew Fort <[email protected]> let me know about some tools that he had written to replace RANCID. I haven't checked them out myself, but I thought I'd send the pointers along for anybody who is interested. Here are Andrew's descriptions of the 3 tools (all of which are open source): * Notch: Think RANCID *login scripts but running on a JSON-RPC > backend you can run any number of tasks of (which can be load-balanced > from a client and sharded so that you can build a low-latency > worldwide service. This is an open version of one of the things I > wrote for Google). http://code.google.com/p/notch > > * Mr. CLI: A multi-router CLI using Notch. > http://code.google.com/p/mr-cli * PUNC: A RANCID config backup thing, again using Notch (again based > on what I wrote for Google. It occured to me later that writing *login > scripts that made the necessary RPC calls would be suitable so that > you got all the Perl goodness of RANCID). http://code.google.com/p/punc Again, I haven't used any of these tools myself, but I'm passing the pointer along for anybody who is looking for stuff like this. Check it out and let us know how it goes! -Brent
_______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
