I agree. I doubt that the efficiencies that might arise from a backend database would offset the extra complexity. Most Hobbit implementations are pretty small. The only reason why the host-file-like configuration is getting cumbersome is that so many features have crept into Hobbit that old folks like me can't remember them all...
GLH
-----Original Message----- From: Stef Coene [mailto:stef.coene at docum.org] Sent: Thursday, December 07, 2006 4:27 PM To: hobbit at hswn.dk 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