I have posted a pdf containing an idea for a configuration management system, and would appreciate any extra peer review cycles you folks could spare:
http://www.tetrasec.net/data/itsyconfigurationmanagementsystem.pdf The basic concept is to take configruation management of LEAF routers to the enterprise level, while at the same time preserving the "SOHO" style of operation for routers that aren't part of an enterprise. By making "configuration management" its own package (its own lrp), it might make it easier to migrate to another package manager, such as Ipkg. Or, then again, its possible I've just completely lost it. The doc mentions ipkg, mainly because of wishful thinking; but it should be entirely possible to implement this system with the current .lrp based packages. (Translation - I don't want to start a holy war over package managers! This is just about /configuration/ management <smile>) For the Bering-uClibc folks - a version control client will be heavy. The core system should be implemented as shell scripts, so the base system still fits on floppy; The svn/cvs client would still be an "add on" for "enterprise" routers. Think " [ -e /bin/cvs ] && use cvs" Thanks! ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
