You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
At the moment, there is no matchmaking involving GPU. The only logic implemented in SI so far is to request GPU pilots whenever jobs request GPUs, then jobs will match against those GPU pilots, which will advertise GPUs.
We need to define a matchmaking expression that will take into consideration the 3 mandatory GPU parameters, currently named as (will likely be renamed): GPUMemoryMB, CUDACapability and CUDARuntime
Describe the solution you'd like
This ticket requests mainly 2 changes:
rename the job GPU parameters to something like: GPUMemoryMB --> DESIRED_GPUMemoryMB CUDACapability --> DESIRED_GPUCapability CUDARuntime --> DESIRED_GPURuntime
define a requirement expression that takes into consideration the 3 job classads above, in addition to RequestGPUs, which says how many GPUs the job is looking for.
Describe alternatives you've considered
The job matchmaking expression can be defined in two places:
a) WMAgent
b) SI Frontend
I would love to hear pros/cons of those. From Marco M., he is fine either way.
Additional context
Further context is provided in this JIRA ticket: https://its.cern.ch/jira/browse/CMSSI-79
which talks about condor job classad renaming and heterogeneous StepChain requirements.
In addition, here is the current job requirements expression:
Impact of the new feature
WMAgent
Is your feature request related to a problem? Please describe.
At the moment, there is no matchmaking involving GPU. The only logic implemented in SI so far is to request GPU pilots whenever jobs request GPUs, then jobs will match against those GPU pilots, which will advertise GPUs.
We need to define a matchmaking expression that will take into consideration the 3 mandatory GPU parameters, currently named as (will likely be renamed): GPUMemoryMB, CUDACapability and CUDARuntime
Describe the solution you'd like
This ticket requests mainly 2 changes:
rename the job GPU parameters to something like:
GPUMemoryMB
-->DESIRED_GPUMemoryMB
CUDACapability
-->DESIRED_GPUCapability
CUDARuntime
-->DESIRED_GPURuntime
define a requirement expression that takes into consideration the 3 job classads above, in addition to
RequestGPUs
, which says how many GPUs the job is looking for.Describe alternatives you've considered
The job matchmaking expression can be defined in two places:
a) WMAgent
b) SI Frontend
I would love to hear pros/cons of those. From Marco M., he is fine either way.
Additional context
Further context is provided in this JIRA ticket: https://its.cern.ch/jira/browse/CMSSI-79
which talks about condor job classad renaming and heterogeneous StepChain requirements.
In addition, here is the current job requirements expression:
and this is the machine expression in place:
The text was updated successfully, but these errors were encountered: