Hi Arno, Lucas and Frank,
Thanks for your replies. I didn't realise the Bacula-Python API wasn't that
well used. Sounds like a useful feature to me, but...
I'll take a look and report back regarding any findings and what I end up
doing, and thanks for the pointers. Thankfully what we need to achieve
shouldn't be that difficult, and the tests are pretty basic too, so am hoping
it shouldn't be too difficult and I am a firm believer in keeping things as
simple as possible :)
WRT maintaining the API, am not much of a hacker, much more a systems guy who
just ends up tapping code when required. However if during my attempts to
create something that does what I am after, I can add anything to the project,
by all means will do so.
Thanks again
Dan
________________________________________
From: ext Arno Lehmann [al AT its-lehmann DOT de]
Sent: 28 November 2009 14:29
To: bacula-users AT lists.sourceforge DOT net
Subject: Re: [Bacula-users] Automated Test Suite
Hello,
27.11.2009 21:47, Lucas B. Cohen wrote:
> Hi Dan,
>
> I'm not up to date on this point, but IIRC there had been some
> discussion on whether to continue providing the Python API in Bacula,
> due to lack of maintainership a while ago. It might not be wise to rely
> on Python in Bacula for your project.
Indeed... I was about to write essentially the same thing.
BUT, Daniel, if you imagine you could work on the Bacula python stuff,
and you like it, and you decide that you could maintain and improve
it, you might be a good help for the developers there!
In the end, we all would get python scripting improvements, you might
get the features we want, and everybody is happy :-)
>
> ext-daniel.hawker AT nokia DOT com wrote:
>> I could integrate this somewhat, by using a separate Verify Job followed by a
>> *Run after Job* script. This script could then use Python and the
>> Bacula-Python hooks
>> to run a restore job and then the rest of the required tests.
>
> If you intened to schedule a separate Verify Job after the Backup job,
> why not simply schedule a Restore job after that as well ? This third
> job would make use of the RunAfterJob directive, and whichever
> additional data integrity/usability tests you wish to run could then be
> implemented in the scripting language you prefer.
Actually, I'd do it even simpler... Just feed the necessary commands
to bconsole (like 'run job=whatever ...' and 'wait') and do all the
other steps in a script ouside of Bacula. Mostly because scheduling
restore jobs doesn't work very well...
To get integrated into Baculas scheduling, you could run your script
as a run script inside Bacula... for example, to run after the
successful verify job.
Cheers,
Arno
> Best,
>
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
