Thanks for the feedback Raj! I think you made a good point, the defaults
should be set to zero to make them none restricted.
What I observed is that when we set these values the containers get more
time to start.
Thanks
On Thu, May 21, 2015 at 2:33 AM, Rajkumar Rajaratnam
wrote:
> I went throug
I went through the code and figured it out :-)
If we don't specify these parameters, the default values will be cpu -> 1
and ram-> 1024. I guess that should be the way to do it.
Thanks.
On Thu, May 21, 2015 at 2:14 AM, Rajkumar Rajaratnam
wrote:
> This is great Imesh!
>
> If we don't specify t
This is great Imesh!
If we don't specify these parameters, the CPU and Memory won't be
restricted right? Do we have to explicitly set these to 0?
Thanks.
On Thu, May 21, 2015 at 12:54 AM, Imesh Gunaratne wrote:
> Hi Devs,
>
> I have now implemented support to specify CPU (number of cores) and
Hi Devs,
I have now implemented support to specify CPU (number of cores) and Memory
(in MB) in Docker Cartridges. These values will be passed to Kubernetes
when creating a Pod and Kubernetes will limit those resources to containers
accordingly.
If CPU and Memory should not be restricted, above pa
