In broad terms, what are you trying to do?
A compute service operator should be able to weight different compute scopes to control the allocation of compute effort.
Briefly detail what you have already tried
Describe the new feature(s) that would help you to achieve this
I think two different methods would be nice to support for weighting different scopes.
One method would be weights, so like:
scopes: (mhenry-*-*, 0.1), (openfe-*-*, 0.1), (asap-*-* 0.2), (choderalab-*-*, 0.1), (asap-confidential-*, 0.5)
That would mean the compute worker would get a asap-confidential-* job 50% of the time, and a openfe-*-* job 10% of the time.
Another method that would be good to support is a simple rank order priority:
scopes: (mhenry-*-*, 5), (openfe-*-*, 4), (asap-*-* 2), (choderalab-*-*, 3), (asap-confidential-*, 1)
Where the compute service will only grab asap-*-* jobs if there are 0 asap-confidential-* jobs in the queue.
In broad terms, what are you trying to do?
A compute service operator should be able to weight different compute scopes to control the allocation of compute effort.
Briefly detail what you have already tried
Describe the new feature(s) that would help you to achieve this
I think two different methods would be nice to support for weighting different scopes.
One method would be weights, so like:
scopes: (mhenry-*-*, 0.1), (openfe-*-*, 0.1), (asap-*-* 0.2), (choderalab-*-*, 0.1), (asap-confidential-*, 0.5)That would mean the compute worker would get a
asap-confidential-*job 50% of the time, and aopenfe-*-*job 10% of the time.Another method that would be good to support is a simple rank order priority:
scopes: (mhenry-*-*, 5), (openfe-*-*, 4), (asap-*-* 2), (choderalab-*-*, 3), (asap-confidential-*, 1)Where the compute service will only grab
asap-*-*jobs if there are 0asap-confidential-*jobs in the queue.