Explicit resources allocation

[ocherfas]

Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature

Description:
Allocate explicit resources to a queue (instead of allocating weights)

I would like to be able to define queues like this for example:

Name: Sample queue
Number of GPUs: 4
CPUs: 20
Memory: 4G

Anything else we need to know?:

[k82cn]

@ocherfas , that's the max or min resources of the queue?

[ocherfas]

@k82cn This is the deserved resources of the queue

[hzxuzhonghu]

https://github.com/kubernetes-sigs/kube-batch/blob/60060fd95abcbc4656d9733b8c10a313f07b6f17/pkg/apis/scheduling/v1alpha2/types.go#L196-L200

Currently, queue has Weight indicate a relative resource limit. And Capability indicates the maximum resources the queue can occupy.

I think it is reasonable to have an optional deserved resources field, which should be mutually exclusive with existing fields.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.