<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>Re: [hobbit] Configuration database backend.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I like the idea of a database for the trends and status. I think once you getinto using a database for that you will look for other parts of hobbit to put there too. One thing that comes to mind is some uer authentication for whatever config editing front-end you do. And I denfinately want to see a front-end for the configs so that the hobbit server admin is not overly burdened with config setup/changes for a growing client population.<BR>
<BR>
<BR>
--------------------------<BR>
Thomas Kern<BR>
301-903-2211<BR>
<BR>
<BR>
----- Original Message -----<BR>
From: Stef Coene <stef.coene@docum.org><BR>
To: hobbit@hswn.dk <hobbit@hswn.dk><BR>
Sent: Thu Dec 07 17:27:08 2006<BR>
Subject: Re: [hobbit] Configuration database backend.<BR>
<BR>
On Thursday 07 December 2006 23:01, Trent Melcher wrote:<BR>
> Has anyone thought about or implemented a configuration database backend<BR>
> for hobbit, primarily a database replacement for the hobbit-clients.cfg<BR>
> and hobbit-alerts.cfg to start....these are a couple that I would like<BR>
> to buils a webfront to and be able to give limited access to users so<BR>
> they could modify thresholds and alerting capabilities when needed.<BR>
><BR>
> I did this about 4 years back for Big Brother using Informix, I was<BR>
> able to setup thresholds and a replacement for the bb-host file inside a<BR>
> couple tables in a database. However back then Big Brother was mostly<BR>
> shell scripts and flat files for all its configuration. So adding hooks<BR>
> into it for talking to a databse was easy. With hobbit its all compiled<BR>
> code and Im not sure where to start, plus I don't have access to an<BR>
> Informix database or the API's for it anymore so Im looking at mysql and<BR>
> its api's for writing code in C.<BR>
We are thinking about using mysql for storing trends and status messages.<BR>
<BR>
For the configuration, I think mysql is overkill and makes it too complex. I<BR>
love the simplicity of the config files. I'm more thinking about making a<BR>
web-based frontend for the config files. The config files can be parsed as<BR>
ini-files. And for parsing ini-files, perl is perfect. So writing a<BR>
web-based frontend for the config files in perl, is not that hard.<BR>
<BR>
<BR>
Stef<BR>
<BR>
To unsubscribe from the hobbit list, send an e-mail to<BR>
hobbit-unsubscribe@hswn.dk<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>