search

usegalaxy-eu / tpv-metascheduler-api

Metascheduler for TPV as Service
MIT License
0 stars 5 forks source link

Additional attributes for an API request #3

Closed abdulrahmanazab closed 8 months ago

abdulrahmanazab commented 11 months ago

Would be great to add these attributes for the matchmaking to be implemented (example values):

"selected_objectstore": "object_store_italy_S3_01", "cores" : 8, "mem" : 20, "Platform" : "Debian", "prefered dest" : "condor-tpv"

pauldg commented 10 months ago

@abdulrahmanazab Can you remind me, are these job related attributes?

abdulrahmanazab commented 9 months ago

@pauldg Yepp, as mentioned in the chat. In order to do the actual matchmaking, we need to add job attributes (requirements) to match them against the destination attributes (resource specifications), in addition to the consideration of locality, i.e. where are the input datasets stored (and if relevant, where the should the results be stored)

pauldg commented 8 months ago

Discussed during the meetings, tpv handles the matchmaking based on job requirements.