<HTML dir=ltr><HEAD><TITLE>Re: [rancid] Re: RANCID as an Element of a CMDB System</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText85120 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Lance</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Quite true. Thanks for this advice, a number of those points are worth looking at. It suggests I should look at first creating a set of scripts to generate a schema (or an approximate schema) given standard configs from cisco/juniper, and then creating code generic enough to handle new schema adjustments.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Time to hit that drawing board :-)</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Regards,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Traiano</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> lavermil@gheek.net on behalf of Lance Vermilion<BR><B>Sent:</B> Tue 2008/09/23 06:42 PM<BR><B>To:</B> Traiano Welcome<BR><B>Cc:</B> Oliver Gorwits; rancid-discuss@shrubbery.net<BR><B>Subject:</B> Re: [rancid] Re: RANCID as an Element of a CMDB System<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Traniano,<BR><BR>I don't think it should be that hard. It will for sure take a little<BR>bit of research to come up with a set of common commands between all<BR>the systems that rancid supports. I would look at the commandtable and<BR>then create a table for each vendor that way it can remain fairly<BR>consistent and all your fields would match what you have in your<BR>rancid file. You could create a table for each general command and<BR>then just reference it via the nodeid. Different thoughts for sure one<BR>is more relational while one is more flat. Anyway you layout the<BR>database it is still going to be a result of what is captured from the<BR>commandtable.<BR><BR>The above statement is the easy part, the not so fun part is changing<BR>up rancid to use that database. Writting it isn't tough, it will be<BR>getting it added to the distro so many can use all the hard work.<BR><BR>On Tue, Sep 23, 2008 at 1:19 AM, Traiano Welcome <twelcome@tenet.ac.za> wrote:<BR>><BR>> How easy would it be to use the database schema and backend code, possibly<BR>> with a different UI, do you think?<BR>> Well, it's worth a try, it's one of those ymmv things :-)<BR>><BR>><BR>><BR>> -----Original Message-----<BR>> From: Lance Vermilion [<A href="mailto:lavermil@gheek.net">mailto:lavermil@gheek.net</A>]<BR>> Sent: Mon 9/22/2008 6:47 PM<BR>> To: Traiano Welcome<BR>> Cc: Oliver Gorwits; rancid-discuss@shrubbery.net<BR>> Subject: Re: [rancid] Re: RANCID as an Element of a CMDB System<BR>><BR>> Traiano,<BR>><BR>> The biggest downfall to Netdisco is that it is not a simple install. I<BR>> think that is what has plagued the project. The UI could use a little<BR>> updating, but it gets the job done.<BR>><BR>> On Mon, Sep 22, 2008 at 1:47 AM, Traiano Welcome <twelcome@tenet.ac.za><BR>> wrote:<BR>>> Hi Oliver<BR>>><BR>>> I've gone some way towards building the router schema based on ENTITY-MIB<BR>>> and others (quite labour intensive :-)). Netdisco seems to overlap a lot<BR>>> of<BR>>> what I've done, and offer a number of better features, so it might be<BR>>> worth<BR>>> looking at integrating it into the CMDB system I'm trying to build, as<BR>>> opposed to the custom stuff I've scripted.<BR>>><BR>>> Many Thanks!<BR>>> Traiano<BR>>><BR>>><BR>>> -----Original Message-----<BR>>> From: rancid-discuss-bounces@shrubbery.net on behalf of Oliver Gorwits<BR>>> Sent: Fri 9/19/2008 3:46 PM<BR>>> To: rancid-discuss@shrubbery.net<BR>>> Subject: [rancid] Re: RANCID as an Element of a CMDB System<BR>>><BR>>> -----BEGIN PGP SIGNED MESSAGE-----<BR>>> Hash: SHA1<BR>>><BR>>> Hi Traiano,<BR>>><BR>>> Traiano Welcome wrote:<BR>>> | what I want is a pre-canned sql schema for each<BR>>> | model router config (or a single generic one!) which would allow me<BR>>> | to easily import a router config into a database.<BR>>><BR>>> If you were using SNMP, you could poll the ENTITY-MIB on the network<BR>>> devices. This would reveal their hardware configuration, and it uses a<BR>>> standardized language as described in section 3 of RFC 2737.<BR>>><BR>>> Some systems such as Netdisco will do this, and insert it into an SQL<BR>>> database. The database schema is quite simple; the RFC uses a strict<BR>>> hierachical model for the physical entities.<BR>>><BR>>> You could look at the Netdisco or SNMP::Info code for some ideas,<BR>>> perhaps, and translate them for your RANCID-based system.<BR>>><BR>>> regards,<BR>>> oliver.<BR>>> - --<BR>>> Oliver Gorwits, Network and Telecommunications Group,<BR>>> Oxford University Computing Services<BR>>><BR>>> -----BEGIN PGP SIGNATURE-----<BR>>> Version: GnuPG v1.4.6 (GNU/Linux)<BR>>> Comment: Using GnuPG with Mozilla - <A href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org</A><BR>>><BR>>> iD8DBQFI061B2NPq7pwWBt4RAi52AJ93VHcMrSvg5JBCNTkW1H7Kbh2wDACfUVmu<BR>>> h2KgL6cIfWtD7yfzw8x1rMI=<BR>>> =7Yay<BR>>> -----END PGP SIGNATURE-----<BR>>> _______________________________________________<BR>>> Rancid-discuss mailing list<BR>>> Rancid-discuss@shrubbery.net<BR>>> <A href="http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss">http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss</A><BR>>><BR>>><BR>>> _______________________________________________<BR>>> Rancid-discuss mailing list<BR>>> Rancid-discuss@shrubbery.net<BR>>> <A href="http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss">http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss</A><BR>>><BR>><BR>><BR></FONT></P></DIV></BODY></HTML>