Details
-
Feature
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Current Situation
- If you want that a job is executed on a JobScheduler Agent then you have to assign a process class to the job where the process class specifies the Agent in the remote_scheduler attribute.
- So you have a fix allocation between job and Agent..
Desired Behavior
- The JobScheduler should provide "dynamic Agent assignment" by an order parameter.
- The order parameter has the name scheduler.remote_scheduler
- This order parameter beats the remote_scheduler attribute of an assigned process class for the current task when a task is started.
- The value of this order parameter has to be the same form like the remote_scheduler attribute in a process class otherwise an error is raised.
Maintainer Note
- The order parameter scheduler.remote_scheduler affects only "shell" jobs.
- "API" jobs ignore this order parameter and the task logs a SCHEDULER-484 warning.
Attachments
Issue Links
- mentioned in
-
Page Loading...