-
Notifications
You must be signed in to change notification settings - Fork 919
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
[lfx-mentorship-2022-summer]Cluster Resource modeling #772
Comments
Hello @RainbowMango , hope you're doing well , this is Anutosh here from India . I'm an open source enthusiast and I'm currently involved with communities based on numerical and symbolic computations/algorithms in math and physics like numpy, sympy, networkx. I am keen to take part in the LFX Mentorship program for the summer term and this project interests me. But being new to the project , I would be glad if you could suggest any relevant resources/links I should be going through as a beginner for getting to know the project and the library better . Thank you ! |
Hey @RainbowMango Any Update on this comment, I would like to volunteer to work on this issue under LFX Mentorship Program? Happy to send you a proposal about the same, Thanks!! |
@AALEKH @anutosh491 Thanks for reaching us. This task requires some basic knowledge about Kubernetes, and after that, you can get started with Karmada quick start. |
Thank you @RainbowMango I have been learning more about karmada, the problem it solves and the functionality behind it . I will be going through the docs soon and then start working on my application ! EDIT1: I went through most of the resources shared above . I am now much more comfortable with Karmada and have a better understanding of how Karmada operates. Thanks for the resources : ) |
Hello @RainbowMango , I've been framing my cover letter for the LFX mentorship program and had couple doubts regarding this proposed model.
|
Also does this call for removing or rather deprecating the |
Hello @RainbowMango sir , could you please help me with the doubts I've asked above as today is the last day to apply ! I am actually ready with my application material but just want to confirm these basic doubts before turning in my application . Thanks in advance ! |
The
Probably. Given the
Please see the example:
Probably. |
@RainbowMango: GitHub didn't allow me to assign the following users: halfrost. Note that only karmada-io members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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. |
/assign @halfrost |
@halfrost Could you please post the API design here? I know some guys who are interested in it. |
OK, I will write a document about the detail of API design. |
/close |
@RainbowMango: Closing this issue. In response to this:
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. |
What would you like to be added:
We don't want to collect and store each node's resources in detail(That's a burden for Karmada to maintain the information), but we want to build a
resource model
for each cluster, something like:Why is this needed:
In the scheduling progress, the
karmada-scheduler
makes decisions as per a bunch of factors, one of the factors is the resource details of the cluster.We introduced ResourceSummary to the Cluster API. For example:
But the
ResourceSummary
is not precise enough, it mechanically counts the resources on all nodes, but ignores the fragment resources.(For example, a cluster with 2000 node, 1 core cpu left on each node, from theResourceSummary
, we get there are 2000 core CPU left for the cluster, that's not correct.)References
The text was updated successfully, but these errors were encountered: