Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Add way to upload and schedule periodic maintenance scripts|
|Product:||[Other] RHQ Project||Reporter:||Elias Ross <genman>|
|Component:||Core Server||Assignee:||Lukas Krejci <lkrejci>|
|Status:||NEW ---||QA Contact:||Mike Foley <mfoley>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Elias Ross 2012-10-31 17:45:44 EDT
Comment 1 Heiko W. Rupp 2013-07-01 05:08:20 EDT
Lukas, we already have the possibility for server side plugins to be scheduled by cron expressions. Could our facility to run alerting cli scripts be extended for general purpose scripts, as we already have the upload and content side of things and also the "container" to run the scripts? Elias' proposal looks like a great addition to me.
Comment 2 Lukas Krejci 2013-07-01 06:40:32 EDT
This has been on my mind from basically the day one of scripting on the server. Unfortunately other things have had higher priorities. The ability to run individual scripts on a schedule unfortunately doesn't play well with server-plugins "control" schedules. The controls of the server plugins are statically defined in the descriptor whereas the scripts are user-defined. So we'd probably have to create a new UI/remote API to manage the script schedules (we could still store them in the repos, but the schedule is something we don't have a place for yet. Also, the scripts could be "tied" to a number of "entities" - system wide, individual resources, groups, users, which adds to the complexity of the API/UI (but that could be alleviated to some extent by supporting passing "arguments" to the scripts, which is also an RFE for the scripted notifications ;) ). One of the other things I had in mind was to have the ability to define script-driven "wizards" that an admin could define for the users to then run - but I'm not sure this is of much importance as this is basically an UI only thing - basically such user-defined wizard would provide the configuration for a script to run with.