Hi, Stanislav, everyone -- On 11 Oct 2010, at 19:34, Stanislav Sinyagin <[email protected]> wrote: > I'm currently working on a new open-source project. Many of you > know the imperfections of RANCID software, and this project is made to > dramatically change this.
This is great news, we use rancid all of the time, and find that adding functionality and bespoke behaviour is quite hard work, further when we deviate our custom changes to the scripts it makes it harder to track mainline rancid releases. I love your idea to make the custom behaviour work as pure configuration and via a plugin architecture. Please do preserve the best features of rancid, the main is that configuration is backed up into a version control system, so inspecting former config dating back months or years is possible. Using svn rather than cvs would be nice so that we can run it alongside our codebase. A choice of version control back ends would make a lot of people happy I think. :-) Also, make sure there is an option to 'blank out' passwords in the stored configuration. Some way to import the former rancid cvs database might be a neat feature, but we can probably survive without this by running rancid in parallel with your software for six months or a year. It's really important that a community grows around this software, so that we can both contribute and download plugins for many vendors and config dialects. I'd be delighted to volunteer mailing list hosting. I also would really like to follow development in an rss format so that I can tune our noc guys in and we can start to help with testing and building the community when the features we really need are in the software. Congratulations on getting this far, good luck, and ask for help before you need it :-) Andy _______________________________________________ swinog mailing list [email protected] http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
