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

support scheduling framework #148

Conversation

TheBeatles1994
Copy link
Collaborator

No description provided.

@TheBeatles1994 TheBeatles1994 changed the title add scheduling framework design doc support scheduling framework Jun 16, 2022
@codecov-commenter
Copy link

Codecov Report

Merging #148 (b2a44b4) into main (dbc3d95) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #148   +/-   ##
=======================================
  Coverage   11.18%   11.18%           
=======================================
  Files          17       17           
  Lines        1681     1681           
=======================================
  Hits          188      188           
  Misses       1474     1474           
  Partials       19       19           
Flag Coverage Δ
unittests 11.18% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update dbc3d95...b2a44b4. Read the comment docs.


### Score

对于新 pod,根据其 pvc/临时卷信息 获取申请的存储量,并打分。
Copy link
Contributor

Choose a reason for hiding this comment

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

打分这里,是不是会存在binpack和spread两种策略?

设置 [nls](../api/nls_zh_CN.md) event handler 事件

- add
- 创建 cache 中的 node 和 存储池 allocatable
Copy link
Contributor

Choose a reason for hiding this comment

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

这里需要明确一下。对于nls annotation中的 持久卷 与 存储池 映射关系,这个中间状态是否需要cache。

@liyimeng
Copy link

Is this going to be ready soon? Love to see #144 come into the radar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants