Re: [Bacula-devel] Volume Location Management

[Eric B. <er...@eb...>]

Hi,

I have started an other bacula web interface some weeks ago.=20
At this time, i can display useful informations like=20
 - media (with pool, location, name, etc filter)
 - pool
 - jobs
 - running jobs (with realtime information ie : "status client=3Dxxx")
 - jobs log (per job)
 - location
 - clients
 - backup statistics (like bacula-web)
 - autochanger (sort of graphic mtx)
 - ...

You can also insert/remove tape from your autochanger easly
(the selection is made by my tool, just say : "i want remove 10 cartiges fr=
om=20
Autochanger1, give me best candidates")

It works with mysql and postgresql.

So, i have implemented a volume management system to, you can update locati=
on=20
with a simple workflow. (you can see screenshot on=20
http://brestore.webhop.info/web)

it's unlucky we've been working on the same thing at the same time. I'd lik=
e=20
to propose merging those two projects now so we can stop duplicating effort=
s.

It's not finish, but you can test bweb on http://bweb.mine.nu/bweb=20
user devel, pass Devel

(it's on my pc, so it's could be slow or down some time)

Best regards.

Le Jeudi 6 Juillet 2006 23:51, Arno Lehmann a =E9crit=A0:
> Hi,
>
> as promised, but later than I wanted, I have some sort of a preview of
> the Volume Location Management I'm implementing.
>
> Basic outline:
> - Tag each volume with a Location.
> - The Location assigned to a volume can be changed in a web interface.
> - A volume can be (temporarily) disabled. This is intended for loading /
> unloading operations, so you can have a catalog representing the actual
> autochanger inventory and still swap volumes without Bacula stumbling.
> - Bacula, as of version 1.40 (or the current development version) will
> respect the Volume disabling AFAIK.
> - Bacula does *not* respect Location tags, for example it will requests
> volumes tagges as "off-site storage".
> - A very basic configuration page is implemented, but it's still lacking
> lots of features.
> - User authentication is implemented through LDAP, different roles can
> be defined. Currently, the user setup itself can only be done manually.
> - Locations can be defined in the web frontend, but needs work.
> - Volume locations can be modified, and the Enabled/Disabled status can
> be set.
> - The appearance of the web front-end could be improved.
>
> Some screenshots are attached.
>
> Two questions regarding interaction with Bacula itself:
>
> I intended the volume disabling / enabling as a temporary setting for
> use during changing the volumes in an autochanger. As such, I intended
> to automatically enable volumes when changing locations, and would have
> suggested to have the Bacula-internal 'update slots' command to
> automatically enable the volumes it finds, too. So, whenever a volume
> status is changed, it would be enabled.
>
> Does this sound right to you all, or should volume enabling / disabling
> be done purely manually?
>
> Then, I implemented a logging function so each volumes life-cycle can be
> tracked. This would be most useful if Bacula itself, when finding a
> volume during 'update slots', logged this event, too.
>
> This would obviously require a new feature in Bacula, but I would
> suggest to handle it by always writing the log entries to the
> corresponding catalog table, but simply ignoring errors. Thus, if you
> don't want the log, simply don't create the table. If the table exists,
> the log will be written.
>
> Does this sound reasonable?
>
> Thanks for your consideration,
>
> Arno