Skip to content
This repository has been archived by the owner on May 25, 2023. It is now read-only.

Add resource predicates for tasks #694

Closed
k82cn opened this issue Apr 1, 2019 · 1 comment · Fixed by #717
Closed

Add resource predicates for tasks #694

k82cn opened this issue Apr 1, 2019 · 1 comment · Fixed by #717
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@k82cn
Copy link
Contributor

k82cn commented Apr 1, 2019

Is this a BUG REPORT or FEATURE REQUEST?:

/kind feature

Description:

Currently, we did not use resource predicates from upstream because of releasing resources; but it makes unnecessary sort and check on the full nodes. It's better to have a predicates to check Task.Resreq against Node.Idle and Node.Release resources.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 1, 2019
@k82cn k82cn changed the title Add resource predicates for nodes. Add resource predicates for tasks Apr 1, 2019
@k82cn k82cn added help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Apr 1, 2019
@k82cn k82cn added this to the v0.5 milestone Apr 2, 2019
@k82cn
Copy link
Contributor Author

k82cn commented Apr 4, 2019

@thandayuthapani , would you help on this one?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants