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

First step of optimizing PodAffinity priority function #28952

Merged
merged 1 commit into from
Jul 15, 2016

Conversation

wojtek-t
Copy link
Member

@wojtek-t wojtek-t commented Jul 14, 2016

Ref #26144

This is obviously only a first step - I will continue working on this code. However, this is changing the general scheme of computations to what is described in: #26144 (comment)

@wojtek-t wojtek-t added do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. release-note-none Denotes a PR that doesn't merit a release note. labels Jul 14, 2016
@wojtek-t wojtek-t self-assigned this Jul 14, 2016
@k8s-github-robot k8s-github-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 14, 2016
@wojtek-t wojtek-t assigned davidopp and unassigned wojtek-t Jul 14, 2016
@wojtek-t wojtek-t removed the do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. label Jul 14, 2016
@wojtek-t wojtek-t changed the title [WIP] First step of optimizing PodAffinity priority function First step of optimizing PodAffinity priority function Jul 14, 2016
@@ -0,0 +1,95 @@
/*
Copy link
Member Author

Choose a reason for hiding this comment

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

@davidopp - I splitted non_zero.go file into two parts - this is mostly copy of that with some small changes.

@davidopp
Copy link
Member

My only comments are suggestions for additional comments to add, so that if the next person who reads this code is as dumb as me, it will at least take them less time to understand it than it did for me. :)

After you add the comments, you can apply LGTM label.

Thanks!

@wojtek-t
Copy link
Member Author

Comments applied - thanks @davidopp !

@wojtek-t wojtek-t added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 15, 2016
@k8s-bot
Copy link

k8s-bot commented Jul 15, 2016

GCE e2e build/test passed for commit a538045.

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-bot
Copy link

k8s-bot commented Jul 15, 2016

GCE e2e build/test passed for commit a538045.

@k8s-github-robot
Copy link

Automatic merge from submit-queue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants