-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
update comment with EnqueueExtensions #103686
Conversation
@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 The 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. |
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 Once the patch is verified, the new status will be reflected by the 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. |
/ok-to-test |
/retest |
pkg/scheduler/framework/interface.go
Outdated
// move unschedulable Pods in internal scheduling queues. It's recommended for | ||
// plugins may impacting scheduling, other implemented plugins are useless and | ||
// harmless. |
There was a problem hiding this comment.
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.
pkg/scheduler/framework/interface.go
Outdated
// When setting up a new scheduler, it will load events registered by | ||
// EventsToRegister(), and convert them to gvks to build dynamic event handlers | ||
// with. |
There was a problem hiding this comment.
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.
pkg/scheduler/framework/interface.go
Outdated
// 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// scheduling failed by this plugin. | |
// failed by this plugin schedulable. |
pkg/scheduler/framework/interface.go
Outdated
// EventsToRegister() is called to fill ClusterEvents to frameworkOptions's | ||
// clusterEventMap, which will be used to build event handlers. |
There was a problem hiding this comment.
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.
/milestone v1.23 |
f420751
to
22f31b1
Compare
hey @Huang-Wei , thanks for your advices. would you mind to review the updated comments again. |
pkg/scheduler/framework/interface.go
Outdated
// 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// to build dynamic event handlers with. | |
// to dynamically build event handlers. |
or simply remove this line, as it is a redundant information.
pkg/scheduler/framework/interface.go
Outdated
// impacting scheduling will take effect, other implemented plugins are useless and | ||
// harmless. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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. 🥲
22f31b1
to
6f7594e
Compare
/retest |
There was a problem hiding this 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.
pkg/scheduler/framework/interface.go
Outdated
@@ -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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// who will fail pod scheduling should implement this interface. | |
// that fail pod scheduling (e.g., Filter plugins) are expected to implement this interface. |
pkg/scheduler/framework/interface.go
Outdated
// 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, it's duplicated👍
6f7594e
to
1f87118
Compare
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>
1f87118
to
d1e9da9
Compare
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. 💪 |
/lgtm |
[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 |
/retest |
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?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: