[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Configuration database backend.
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Configuration database backend.
- From: "Kern, Thomas" <Thomas.Kern (at) hq.doe.gov>
- Date: Thu, 7 Dec 2006 18:33:34 -0500
- Thread-index: AccaTxMeEaCQ05q/QkGmpwBzp+pl6wACQnJ2
- Thread-topic: [hobbit] Configuration database backend.
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.
--------------------------
Thomas Kern
301-903-2211
----- Original Message -----
From: Stef Coene <stef.coene (at) docum.org>
To: hobbit (at) hswn.dk <hobbit (at) hswn.dk>
Sent: Thu Dec 07 17:27:08 2006
Subject: Re: [hobbit] Configuration database backend.
On Thursday 07 December 2006 23:01, Trent Melcher wrote:
> Has anyone thought about or implemented a configuration database backend
> for hobbit, primarily a database replacement for the hobbit-clients.cfg
> and hobbit-alerts.cfg to start....these are a couple that I would like
> to buils a webfront to and be able to give limited access to users so
> they could modify thresholds and alerting capabilities when needed.
>
> I did this about 4 years back for Big Brother using Informix, I was
> able to setup thresholds and a replacement for the bb-host file inside a
> couple tables in a database. However back then Big Brother was mostly
> shell scripts and flat files for all its configuration. So adding hooks
> into it for talking to a databse was easy. With hobbit its all compiled
> code and Im not sure where to start, plus I don't have access to an
> Informix database or the API's for it anymore so Im looking at mysql and
> its api's for writing code in C.
We are thinking about using mysql for storing trends and status messages.
For the configuration, I think mysql is overkill and makes it too complex. I
love the simplicity of the config files. I'm more thinking about making a
web-based frontend for the config files. The config files can be parsed as
ini-files. And for parsing ini-files, perl is perfect. So writing a
web-based frontend for the config files in perl, is not that hard.
Stef
To unsubscribe from the hobbit list, send an e-mail to
hobbit-unsubscribe (at) hswn.dk