Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support extended resource in NodeResourcesBalancedAllocation plugin #101946

Merged
merged 1 commit into from
Jul 6, 2021

Conversation

chendave
Copy link
Member

@chendave chendave commented May 12, 2021

Per the design https://docs.google.com/document/d/1MT0KVnyeAc4QcKqUsmk-4OvmBhOy6PvBQOGnjugrJ9k/edit?ts=60942305# and the discussion in the scheduler meeting.

Signed-off-by: Dave Chen dave.chen@arm.com

What type of PR is this?

/kind feature

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Scheduler could be configured  to consider new resources beside CPU and memory,  GPU for example, for the score plugin of `NodeResourcesBalancedAllocation`.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/feature Categorizes issue or PR as related to a new feature. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 12, 2021
@k8s-ci-robot
Copy link
Contributor

@chendave: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label May 12, 2021
@k8s-ci-robot k8s-ci-robot added kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 12, 2021
@fejta-bot
Copy link

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

@chendave
Copy link
Member Author

This is ready for review.

cc more maintainers in case any of you have some bandwidth to review this change, thanks in the advance!

@Huang-Wei @ahg-g @alculquicondor

@alculquicondor
Copy link
Member

The release note is not accurate. It kind of implies that, by default, kube-scheduler will start considering new resources. It should say that it can be configured to consider new resources.

Copy link
Member

@Huang-Wei Huang-Wei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you retitle to "Support extended resource in NodeResourcesBalancedAllocation plugin"?

@chendave
Copy link
Member Author

/retitle: Support extended resource in NodeResourcesBalancedAllocation plugin

@k8s-ci-robot k8s-ci-robot changed the title Extent NodeResourcesBalancedAllocation plugin to cover more resources : Support extended resource in NodeResourcesBalancedAllocation plugin May 14, 2021
@chendave
Copy link
Member Author

Thanks guys for your great suggestion!

Couple of them are pending on discussion, will update soon when it is get clear.

@chendave chendave changed the title : Support extended resource in NodeResourcesBalancedAllocation plugin Support extended resource in NodeResourcesBalancedAllocation plugin May 14, 2021
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 14, 2021
@chendave
Copy link
Member Author

chendave commented May 19, 2021

/hold

TODO

  • update testcase
  • rebase

@Huang-Wei
Copy link
Member

@Huang-Wei, this is compatible with your proposal in #103169, right?

@alculquicondor it's compatible and UTed properly.

Copy link
Member Author

@chendave chendave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks guys for the review and those great suggestion, I hope all those comments have been addressed.

@chendave chendave force-pushed the balance_allocation branch 2 times, most recently from 137d21d to 2bfa67f Compare June 29, 2021 12:38
@@ -381,6 +381,82 @@ profiles:
},
},
},
{
name: "v1beta1 NodeResourcesBalancedAllocation resource weights are set properly",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is kind of too much, I would just reuse one of the existing "custom configs" test cases.
As it is, it will add toil for the maintenance of this file.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

squeezed this test into "...all plugin args in default profile".

…ources

Signed-off-by: Dave Chen <dave.chen@arm.com>
@chendave
Copy link
Member Author

squashed the commits since it will easier for me to rebase on the head of master.

@chendave
Copy link
Member Author

chendave commented Jul 1, 2021

@alculquicondor any more comments, or can we get this in 1.22? thanks!

@Huang-Wei
Copy link
Member

/lgtm

Leaving /approve to @alculquicondor .

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 1, 2021
Copy link
Member

@alculquicondor alculquicondor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

Sorry, I was out on vacation.

@alculquicondor
Copy link
Member

/label api-review

@k8s-ci-robot k8s-ci-robot added the api-review Categorizes an issue or PR as actively needing an API review. label Jul 5, 2021
@chendave
Copy link
Member Author

chendave commented Jul 5, 2021

thanks @alculquicondor , hope you've had a good vacation!

I guess this needs the approval from api review, @liggitt would you pls take the final review?

@chendave
Copy link
Member Author

chendave commented Jul 5, 2021

/cc @liggitt for api review, thanks!

@liggitt
Copy link
Member

liggitt commented Jul 6, 2021

/approve

@liggitt liggitt added this to API review completed, 1.22 in API Reviews Jul 6, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, chendave, liggitt

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 6, 2021
@k8s-ci-robot k8s-ci-robot merged commit ea3bcbc into kubernetes:master Jul 6, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.22 milestone Jul 6, 2021
@chendave chendave deleted the balance_allocation branch July 11, 2021 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api-review Categorizes an issue or PR as actively needing an API review. approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
Status: API review completed, 1.22
Development

Successfully merging this pull request may close these issues.

None yet

7 participants