Support or Workarounds for hook scripts, custom GUI jobs or manual scheduling

[riedel]

Hi, we need to do some stuff that is not possible via the GUI (we have access to a large external tape backup infrastructure, that we want to trigger syncing to for off-site backup eg. after a specific GC&pruning job ).

We can do this via cron. However, it would be great if this could be transparently scheduled via the GUI and actually to be synced with some other jobs.

In PVE jobs there is a script option to add hook-scripts? I see such thing is missing in PBS.

Is there any work around except for polling the running tasks?

Would it make sense to try to develop a patch set?

PS: generally we are struggling a bit with our rather slow HDD machine with scheduling only based on time. Hook scripts that e.g. could also delay a scheduled task via a waiting or cancel logic would be very welcome to not trigger tons of overlapping jobs that actually trigger a bit of IO hell on the machine). Work around would be to totally move to cron I guess, but there isn't even manual scheduling for jobs, so that we lose all traces/history in the GUI. Any best practices for gaining more control over jobs in general?

As said the PVE mechanisms with scripts really works for many cases.

 

[riedel]

BTW: remotely related: https://forum.proxmox.com/threads/shutdown-des-pbs-nachdem-alle-vms-gesichert-wurden.104263/

An importan thing, that I maybe did not clearly mention, why we would want to do this stuff inside the "official" job api actually would be notfications and error reporting

 

[dcsapak]

see the discussions at https://bugzilla.proxmox.com/show_bug.cgi?id=4639 and https://bugzilla.proxmox.com/show_bug.cgi?id=4893

 

[riedel]

Thanks. Related post in the forum: https://forum.proxmox.com/threads/s...ter-performance-disk-life.125065/#post-545230 , which I also did not find yesterday (my original motivation is actually a bit different)

I could not quite follow unfortunately the won't fix decision from the discussion (which had to do with the coupling of of PVE / PBS and other things I guess). I added a comment and link to my question to the second bug that is still alive. I will also continue adding to the other thread. Thanks again for pointing out (I did not look into the closed bugzilla bugs, next time I will)