I thought of this also a while ago, but thought the efforts would be too
much.

Here is what I came up with:

Use a shell/perl/php script to retrieve values from sql-DB into the conf
file for
Each deamon before it starts up (minimizes sw changes to bacula) All that
needs to
Be know then is the DB credentials on each host.

(would be nice to have a perl script to go the other way too [conf ->
sql])

Then a gui could be a simple php/perl (lamp) application manipulating the
DB.

If the web lives on the bacula director host, simple commands allow to
either
Restart, apply (get from sql  into conf files), and reload the config

I don't think one would get a complete interactive gui yet, and that was
not my goal.
Dealing with the ever complex backup schedules in graphical manner is.


-sww



-----Original Message-----
From: David Boyes [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 26, 2007 8:02 AM
To: Erich Prinz; Stephan Wendl
Cc: bacula-devel Development; Bacula Mailing List
Subject: RE: [Bacula-devel] [Bacula-users] Bacula GUI

> > The design of a GUI for bacula may revolve arround interfacing with
> > the dameons.  I was wondering
> > if just designing a  GUI for config file modification might simply
> > suffice, i.e. a config file editor with
> > the smarts of syntax checking and linking of all the resources in
> > the main bacula-dir.conf file.
> > Most of the cfg files do not change much or at all.  The file most
> > often modified is the bacula-dir.conf
> > It would much easier to just concentrate on that task rather than
> > designing a GUI which interacts with the
> > dir daemon.

I'd rather see a majority of the configuration moved into database
tables. 

As more organizations move towards a configuration management database
approach (CMDB), controlling configuration is going to be more important
and more complex. 

Flat files are nice from a simplicity point of view, but the syntax is
becoming complex enough that it might be smarter (and easier to maintain
across multiple systems) to normalize it and move it into a RDBMS. It
would also allow real-time updates more easily. 

Maybe the easy approach would be to write a tool to maintain the
configuration in the database, and then auto-generate the appropriate
files from the database tables. 



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to