On Tue, Jan 27, 2009 at 4:45 PM, Jason Dobies <[email protected]> wrote: > Just a quick followup, from my reading Quartz does seem to support a lot > of these needs, including thread pooling and canceling tasks. I'm > willing to bet they support timeouts too. > > I'm not sure how much of this we expose in Taskomatic, such as the > ability to schedule a task without having it pre-defined in the rhn conf > files, so I'd still like to hear back from our resident taskomatic guru > on initial thoughts of how feasible this would be.
Right now taskomatic doesn't allow on demand scheduling. It reads the tasks defined in the config only. But it wouldn't be hard to add say a XMLRPC server to Taskomatic (like we did with search server) to send jobs to Taskomatic or adding the entries to a task table. Partha brings up a good point about trying to reuse the rhnServerActions, something to look into. I think I like the idea of adding an api to taskomatic (for doing things on demand) and combining that with a database. The api allows you to do it NOW versus waiting for taskomatic to poll for jobs. jesus _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
