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

update comment with EnqueueExtensions #103686

Conversation

kerthcet
Copy link
Member

Signed-off-by: kerthcet kerthcet@gmail.com

What type of PR is this?

/sig scheduling
/kind documentation

What this PR does / why we need it:

add comment for EnqueueExtensions

Which issue(s) this PR refs:

Refs #103633

Special notes for your reviewer:

New to community, hope to hear as much advices as better.

Does this PR introduce a user-facing change?

NONE

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


@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note-none Denotes a PR that doesn't merit a release note. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. kind/documentation Categorizes issue or PR as related to documentation. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 14, 2021
@k8s-ci-robot
Copy link
Contributor

@kerthcet: 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 Jul 14, 2021
@k8s-ci-robot
Copy link
Contributor

Hi @kerthcet. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jul 14, 2021
@pacoxu
Copy link
Member

pacoxu commented Jul 14, 2021

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jul 14, 2021
@kerthcet
Copy link
Member Author

/retest

@kerthcet kerthcet marked this pull request as ready for review July 14, 2021 15:17
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 14, 2021
Comment on lines 310 to 312
// move unschedulable Pods in internal scheduling queues. It's recommended for
// plugins may impacting scheduling, other implemented plugins are useless and
// harmless.
Copy link
Member

Choose a reason for hiding this comment

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

The statement "It's recommended..." doesn't seem to provide extra information. Correct me if you intend to emphasize something here. If no, I'd suggest removing it.

Comment on lines 313 to 315
// When setting up a new scheduler, it will load events registered by
// EventsToRegister(), and convert them to gvks to build dynamic event handlers
// with.
Copy link
Member

Choose a reason for hiding this comment

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

It's redundant with the comments of EventsToRegister(). Prefer to remove it.

// EventsToRegister returns a series of interested events that
// will be registered when instantiating the internal scheduling queue.
// EventsToRegister returns a series of possible events that may cause a Pod
// scheduling failed by this plugin.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
// scheduling failed by this plugin.
// failed by this plugin schedulable.

Comment on lines 319 to 320
// EventsToRegister() is called to fill ClusterEvents to frameworkOptions's
// clusterEventMap, which will be used to build event handlers.
Copy link
Member

Choose a reason for hiding this comment

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

// The events will be registered when instantiating the internal scheduling queue,
// and leveraged to build event handlers dynamically.

@Huang-Wei
Copy link
Member

/milestone v1.23

@k8s-ci-robot k8s-ci-robot added this to the v1.23 milestone Jul 14, 2021
@kerthcet kerthcet force-pushed the document/add_comment_for_enqueueExtensions branch from f420751 to 22f31b1 Compare July 15, 2021 02:06
@kerthcet
Copy link
Member Author

hey @Huang-Wei , thanks for your advices. would you mind to review the updated comments again.

// impacting scheduling will take effect, other implemented plugins are useless and
// harmless.
// When setting up a new scheduler, it will load events and convert them to gvks
// to build dynamic event handlers with.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
// to build dynamic event handlers with.
// to dynamically build event handlers.

or simply remove this line, as it is a redundant information.

Comment on lines 311 to 312
// impacting scheduling will take effect, other implemented plugins are useless and
// harmless.
Copy link
Member

Choose a reason for hiding this comment

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

not quite clear to me, do we have any plugin doesn't impact scheduling at all? also, I cannot understand this statement

other implemented plugins are useless and harmless.

Copy link
Member Author

Choose a reason for hiding this comment

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

sorry about the ambiguous words,I updated my comments right now. 🥲

@kerthcet kerthcet force-pushed the document/add_comment_for_enqueueExtensions branch from 22f31b1 to 6f7594e Compare July 15, 2021 14:19
@kerthcet
Copy link
Member Author

/retest

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.

Some nits. LGTM otherwise.

@@ -307,10 +307,14 @@ type QueueSortPlugin interface {
}

// EnqueueExtensions is an optional interface that plugins can implement to efficiently
// move unschedulable Pods in internal scheduling queues.
// move unschedulable Pods in internal scheduling queues. Plugins
// who will fail pod scheduling should implement this interface.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
// who will fail pod scheduling should implement this interface.
// that fail pod scheduling (e.g., Filter plugins) are expected to implement this interface.

// move unschedulable Pods in internal scheduling queues.
// move unschedulable Pods in internal scheduling queues. Plugins
// who will fail pod scheduling should implement this interface.
// With registered events, scheduler can build dynamically event handlers.
Copy link
Member

Choose a reason for hiding this comment

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

It's described in L316~L317, so let's remove it.

Copy link
Member Author

Choose a reason for hiding this comment

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

yep, it's duplicated👍

@kerthcet kerthcet force-pushed the document/add_comment_for_enqueueExtensions branch from 6f7594e to 1f87118 Compare July 16, 2021 01:44
@k8s-ci-robot k8s-ci-robot removed the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jul 16, 2021
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 16, 2021
Signed-off-by: kerthcet <kerthcet@gmail.com>

update comment with EnqueueExtensions

Signed-off-by: kerthcet <kerthcet@gmail.com>

update comment with EnqueueExtensions

Signed-off-by: kerthcet <kerthcet@gmail.com>

update comment with EnqueueExtensions

Signed-off-by: kerthcet <kerthcet@gmail.com>
@kerthcet kerthcet force-pushed the document/add_comment_for_enqueueExtensions branch from 1f87118 to d1e9da9 Compare July 16, 2021 01:56
@kerthcet
Copy link
Member Author

Updated the comments as advised. Thanks for all your patience @Huang-Wei @chendave , it's my first pr, twist but happy. Looking forward to contributing more codes. 💪

@Huang-Wei
Copy link
Member

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Huang-Wei, kerthcet

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 16, 2021
@kerthcet
Copy link
Member Author

/retest

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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/documentation Categorizes issue or PR as related to documentation. 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants