Skip to content
This repository has been archived by the owner on Dec 1, 2018. It is now read-only.

Export the machine container with the proper CPU limit #399

Closed
vmarmol opened this issue Jul 10, 2015 · 4 comments
Closed

Export the machine container with the proper CPU limit #399

vmarmol opened this issue Jul 10, 2015 · 4 comments

Comments

@vmarmol
Copy link
Contributor

vmarmol commented Jul 10, 2015

Today we convert shares to CPU limit, but this doesn't work for the root container since it always has 1024 shares even though it corresponds to all cores on the machine. We should take the NumCores from the machine and export that instead.
@vmarmol vmarmol mentioned this issue Jul 10, 2015
Closed
@vmarmol
Copy link
Contributor Author

vmarmol commented Jul 10, 2015

/cc @jszczepkowski @piosz

@piosz
Copy link
Contributor

piosz commented Jul 10, 2015

I can take a look on Monday

@dchen1107
Copy link

cc/ @dchen1107

@dchen1107
Copy link

kubernetes/kubernetes#10760

@dchen1107 dchen1107 mentioned this issue Jul 10, 2015
Closed
piosz added a commit to piosz/heapster that referenced this issue Jul 13, 2015
@piosz
Added exporting cpu/mem limits based on Kubernetes rather than cadvisor
43f6a55 
Fixes kubernetes-retired#399
@piosz piosz mentioned this issue Jul 13, 2015
Merged
piosz added a commit to piosz/heapster that referenced this issue Jul 13, 2015
@piosz
Added exporting cpu/mem limits based on Kubernetes rather than cadvisor
a5c8ca4 
Fixes kubernetes-retired#399
piosz added a commit to piosz/heapster that referenced this issue Jul 14, 2015
@piosz
Added exporting cpu/mem limits based on Kubernetes rather than cadvisor
041549e 
Fixes kubernetes-retired#399
piosz added a commit to piosz/heapster that referenced this issue Jul 15, 2015
@piosz
Added exporting cpu/mem limits based on Kubernetes rather than cadvisor
debbded 
Fixes kubernetes-retired#399
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vmarmol @dchen1107 @piosz