-
Notifications
You must be signed in to change notification settings - Fork 249
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
TAS: Compute the topology assignments #3256
TAS: Compute the topology assignments #3256
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
735b626
to
27bbbab
Compare
/cc @tenzen-y |
/hold |
27bbbab
to
187e781
Compare
/cc @alculquicondor |
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 initial comments.
pkg/cache/snapshot.go
Outdated
@@ -76,6 +78,10 @@ func (s *Snapshot) Log(log logr.Logger) { | |||
} | |||
|
|||
func (c *Cache) Snapshot() Snapshot { |
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.
I suppose you plan to remove this function in a follow up?
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.
Yes, I intended to follow up. I could do it in this PR too, but it is used in a bunch of tests, so I didn't want to increase the size of the diff which is already large.
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.
Let's keep opening this thread so that we can avoid cleanup this function in a follow-up.
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.
I cleaned up the Snapshot function in this PR, last commit: cd977aa
d5ca699
to
8807023
Compare
f024f9d
to
7d0588c
Compare
cd977aa
to
915d1de
Compare
|
||
// domain holds the static information about placement of a topology | ||
// domain in the hierarchy of topology domains. | ||
type domain struct { |
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.
FYI: I have renamed it once again. I like just domain
because it is specific in this context (contrary to previous: info
or node
), yet short (compared to previous topologyDomainNode
)
cc @gabesaba
/test pull-kueue-test-multikueue-e2e-main |
FYI as mentioned under the issue I opened a spreadsheet to keep track of the follow ups. |
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.
Thank you for this great implementation!
This is an awesome feature! Thank you!
Note that I leave some trivial comments. Let's address those in a follow-up.
/lgtm
/approve
LGTM label has been added. Git tree hash: d1b5d6eebf128345d06fa257eb856a90e592f1e6
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mimowo, tenzen-y 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 |
/hold cancel |
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.
These are my final nits, thank you!
LGTM, great work! |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Part of #2724
Special notes for your reviewer:
I'm not setting any release note here as it is already set on the API PR.
This PR will be followed up with (based on the prototype in #3218)
Does this PR introduce a user-facing change?