On Friday 16 June 2006 21:06, Arno Lehmann wrote:
> Hi,
>
> On 6/13/2006 12:01 AM, Kern Sibbald wrote:
> > On Monday 12 June 2006 21:50, Arno Lehmann wrote:
>
> ...
>
> >>My personal preference would be the proliferation of directives... but
> >>then, I do get paid by people who don't want to work through the
> >>configuration themselves ;-)
> >
> > Yea, but you seem to be able to stock a lot more things in your head than
> > I can, so that is why I am tending toward non-proliferation :-)
>
> Thanks for the compliment... at least I decided it was one because I
> wouldn't like the other way ;-)
>
> >>Apart from that, trying to simplify the configuration seems a good goal
> >>to me, and linking pools with storage devices is even kind of logical.
> >>
> >>Anyway, having the necessary python hooks for all this sort of stuff
> >>would be really nice...
> >
> > Yes, I agree, and the hooks will eventually get implemented (I recently
> > slipped in a few more variables in a 1.38.x release), but for the moment,
> > the user interest in Python is almost non-existant.
>
> Personally, I'm quite sure that I will become very interested in python
> events once some *really* interesting tings are possible. Currently, the
> only real useful thing I can see is creating volume labels
> automatically... actually controlling jobs - modifying levels, pools,
> storage devices etc. - is much more appealing to me.
>
> > So until I start hearing
> > more complaints about adding more Python features,
>
> So I better start conmplaining.
>
> :-)
> :
> > it is not very high on my
> > priority list. I'm not worried about it though. In the early years of
> > Bacula I heard a lot of complaints about using SQL as the database, and
> > look what users are doing with it now (bacula-web, recover.pl, and
> > brestore.pl) !!! :-)
>
> Yup. Volume Location Management, too... I've got something more or less
> usable as a demonstration available soon, I think.
>
> > With a few more small hooks into Python, Eric and Marc could hook their
> > Perl GUI interface directly into Bacula via a Python call to Perl ---
> > hmmm.
> >
> > While I am wildly speculating, I should say that it seems to me that
> > adding a Python interpreter to bconsole could allow some really neat
> > scripting of Bacula commands -- even building "new intelligent" commands
> > that are in fact Python scripts.
>
> Interesting option... but please provide us with a good API for all
> sorts of status changes of jobs, volumes, and the catalog itself :-)
Why don't we start by implementing a number of new dot commands. Feed me a
couple of your most desired wishes. Please keep it short and sweet I
understand what is needed, but am so overloaded that a pointer to say the top
5-10 items would make it happen a lot faster ...
--
Best regards,
Kern
(">
/\
V_V
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
